Audio Drift on Exports (Screenflow 6.2.2)

Hi! Just wanted to find out if this is a known issue:

I have several 1+1/2hr screenflow 6.2.2 projects composed of a wide variety of imported files and screen recordings. Projects play in realtime no problem, with great audio sync. Exporting Prores 422HQ at 30fps works ok, but exporting Prores 422HQ at 29.97 yields significantly audio-drifted renders. 

I haven't so far found this issue on the forums.

 

Screenflow 6.2.2

OSX 10.10.5

MacBook Pro (Retina, Mid 2012)

2.6 GHz Intel Core i7

16 GB 1600 MHz DDR3

Intel HD Graphics 4000 1024 MB // Nvidia GeForce GT 650M

10replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Unless you're doing broadcast work, 30fps should be fine.

    Have you tested the ProRes file with whatever workflow is destined for (NLE, as a master for compress, etc)? How are you determining the audio drift?

    Reply Like
  • I'm compressing the exported renders at 29.97, so I'd rather render at 29.97 to begin with. Regardless, I lost a day trying to figure out what the cause of the problem was. There's no way to determine the working framerate for editing, but any video renderer should have 30, 29.97, 24, 23.976 export options, and they should probably function, so I figure this is an oversight/bug. ;)

    The workflow it's destined for is as master for compression.

    The audio drift is noticeable as soon as there's any audible cue, or a cut. It's off by a small but noticeable amount in the beginning, and proceeds to wander to the point that it's off by at least a full second after 30 or 40 minutes.

    Thanks for the help, Craig!

    Reply Like
  • Carey Smith said:
    There's no way to determine the working framerate for editing,

     ScreenFlow 7.x now has a Timeline Framerate selection but only 30 or 60 fps 

    Reply Like
  • Carey Smith said:
    any video renderer should have 30, 29.97, 24, 23.976 export options, and they should probably function

     It would seem picking NTSC compatible frame rates in ScreenFlow would otherwise result in audio drift.

    Carey Smith said:
    The audio drift is noticeable as soon as there's any audible cue, or a cut

     It's important for us to know what you're using as a player. Are you playing in Quicktime X or an NLE, something else?

    Players and NLEs do handle differently as an NLE will try to lock to an NTSC compatible frame rate normally whereas a file player may not.

    Reply Like
  • Viewing in Quicktime X. Both before and after compression through Adobe Media Encoder CS6.

    I hope that helps. Thanks again, Craig.

    Carey

    Reply Like
  • Carey Smith said:
    Viewing in Quicktime X.

     Have you tested with ScreenFlow ProRes export or just MP4?

    Reply Like
  • I only export ProRes 422HQ, and then use dedicated compression to get an mp4.

    Reply Like
  • Carey Smith Thanks for that. 
    I'd ask you to test with a free trial of ScreenFlow 7.1.1 but you'd have to move to an OS compatible with that. I want to check if this is fixed in the current version of ScreenFlow.

    Development on the 6 series has ended and even if there were a bug fix it likely wouldn't be compatible with Yosemite. There is a ScreenFlow 6.2.3 you could test but that also require El Capitan (10.11.x) at a minimum compatible OS but I can't promise a fix will happen in the 6 series.

    Let me know if you can test 7.1.1 on 10.11.x and up. If not, I understand. I can still have you report the issue and provide the steps so we can test in 7.1.1. If it's still an issue we can investigate a fix so you'd know when upgrading would make sense for you.

    Reply Like
  • CraigS thanks, I'm not on 10.11.x due to Adobe's CS6 suite not being supported, but I will be upgrading soon, and I can certainly test out either 6.2.3 or 7.1.1 then if that helps. Do I need to contact anyone in particular to set that up?

    Reply Like
  • Carey Smith If you go to 10.11.x (or higher) do test on 7.1.1. You can use the free trial. It's watermarked but other wise fully functional. If the issue is present post back here and you can report it to our techs to investigate the fix.

    Reply Like
reply to topic
Like Follow
  • 11 days agoLast active
  • 10Replies
  • 71Views
  • 2 Following