We are seeing similar issue when installing a second VDO with stabilisation off. Final Cut Camera app with similar topology works somehow.

Hello @DTS Engineer , I can confirm I tried it and still does not work reliably. Filing feedback is a very long way where it takes years, sometimes never to resolve the issue.

Thanks for the answer. I shall try and get back to you.

This was not my question, and white balance API is completely irrelevant here. My question is what pixel format should be used in videoSettings of AVCaptureVideoDataOutput for ProResRAW codec (which is 16 bit). I am looking for end to end configuration of AVCaptureSession using AVCaptureVideoDataOutput to be able to use ProResRAW codec.

Hello @Richard , this is about ProResRAW codec on iPhone 17 pro lines, not the other ProRes variants which are 10 bit. ProResRAW is supposedly 16 bit format.

What is the right way to configure ProResRAW pipeline and check it's availability?

The way I got it working is removing the .safeAreaPadding from the VStack and applying vertical .contentMargins to the ScrollView instead, plus giving all ticks same height. Still need to understand what's going on in your code which makes it working, and more importantly, what failed in my code and why.

Well its the standard AVCam sample code (latest) run on XCode 26 beta. Do I still need to go through the painful process of filing a bug report?

Yes, it has to do with @Observable and also a bug in iOS where second instance of State variable is leaked. I am not sure why SwiftUI is recreating State variable again on initialisation (this does not happen with ObservableObject and StateObject) . Details can be found on this answer on SO.

@DTS Engineer Thanks for answering, it works but onReceive only works on the view. I have to manage lot of state changes and they are best kept inside a View Model class than cluttering the view. Also, I see the same issue with AVPlayerViewController within a UIViewControllerRepresentable.

@Media Engineer FB16464516 has been filed.

@Media Engineer Yes, rotationCoordinator is an instance variable in the class which is an actor. Therefore it will get deallocated off the main thread(on actor's serial queue). But it happens the same way in AVCam sample code (where AVCaptureVideoPreviewLayer is used). We don't see this issue in AVCam sample code even though rotationCoordinator gets deallocated on the actor's serial queue. I shall submit a bug soon.

Ok I was able to fix it by running the method on main thread, marking all these properties inside the actor with @MainActor, grabbed a copy of AVCaptureDevice and used it in the main thread. Not sure if it is 100% correct as AVCaptureDevice is not sendable.

Thanks for the answer, but to move these operations to main thread, I will need to move off AVCaptureDevice to main thread (out of the actor context). How do I solve it?

Hello @DTS Engineer Thanks for the answer. I have gone ahead and filed two enhancements suggestions.