- Posts: 2
- Joined: Thu Oct 07, 2021 4:15 pm
- Real Name: Alex Scott
Thu Oct 07, 2021 4:31 pm
Hey there, new to this forum and hoping to get some help from those wiser than myself. Thanks in advance for any input!
I work with a commercial content production company that specializes in online guitar courses. We shoot with a 4-cam setup and edit the lessons into an overlay format that features multiple angles of the guitar so that viewers can see what the instructor's hands are doing. This requires some VFX, particularly image stabilization/object tracking so that the close-up shots of the guitar neck stay stationary on screen, even when the instructor is moving.
We recently upgraded our studio to an ATEM Mini Extreme ISO and 4x BMPCC6ks for camera control and the ATEM ISO proxy workflow. It looked perfect - we expected we would edit and stabilize our footage using the ATEM files, then swap in Camera Originals for RAW color and export. However - we're having a strange and somewhat problematic issue that I can't figure out.
When looking at the RAW clips, they are shorter (up to 30 frames!) than the ATEM ISO files. There's 10 or so frames missing at the start of the RAW clips vs the ATEM clips, and around 20 missing from the end. The timecode is correct, and they sync properly. However, I've learned that in Resolve, both the normal stabilizer and planar tracker in the Fusion page use a reference frame as a start point to create their tracking keyframes. Because of the discrepancy in frame count, when we stabilize the ATEM footage and then switch the the RAW, the stabilization is 8-10 frames out of sync with the file. This makes editing with the ATEM files as proxies impossible for us.
Am I missing something here? What can be done about this? Any help would be great. If this is an inherent issue with the ATEM ISO and in-camera recording, we will just generate normal proxy media, but that would defeat the whole purpose and one of the main selling points of the ATEM system.
Thanks for reading!
I work with a commercial content production company that specializes in online guitar courses. We shoot with a 4-cam setup and edit the lessons into an overlay format that features multiple angles of the guitar so that viewers can see what the instructor's hands are doing. This requires some VFX, particularly image stabilization/object tracking so that the close-up shots of the guitar neck stay stationary on screen, even when the instructor is moving.
We recently upgraded our studio to an ATEM Mini Extreme ISO and 4x BMPCC6ks for camera control and the ATEM ISO proxy workflow. It looked perfect - we expected we would edit and stabilize our footage using the ATEM files, then swap in Camera Originals for RAW color and export. However - we're having a strange and somewhat problematic issue that I can't figure out.
When looking at the RAW clips, they are shorter (up to 30 frames!) than the ATEM ISO files. There's 10 or so frames missing at the start of the RAW clips vs the ATEM clips, and around 20 missing from the end. The timecode is correct, and they sync properly. However, I've learned that in Resolve, both the normal stabilizer and planar tracker in the Fusion page use a reference frame as a start point to create their tracking keyframes. Because of the discrepancy in frame count, when we stabilize the ATEM footage and then switch the the RAW, the stabilization is 8-10 frames out of sync with the file. This makes editing with the ATEM files as proxies impossible for us.
Am I missing something here? What can be done about this? Any help would be great. If this is an inherent issue with the ATEM ISO and in-camera recording, we will just generate normal proxy media, but that would defeat the whole purpose and one of the main selling points of the ATEM system.
Thanks for reading!