Frame rate changes (badly) after default Cross Dissolve
I have a ScreenFlow project whose main components are a screen capture, and a video capture of faces via Camo Studio. It's your standard talking-heads-in-a-corner video, nothing special. We've done a bunch of these, they all work A-OK.
Except this one particular video. 18 minutes in, after a transition to a full-screen super, the frame rate on our heads clearly goes to hell. We get real janky.
I've added a Starting Transition. Removing it makes the problem go away. Changing the default transition from a Cross Dissolve to a Cross Blur, the issue goes away.
I can only infer that there's a weird bug in the Cross Dissolve that's making this happen?
This only happens on export. The editor does not show the issue.
I've uploaded a video showing this segment. It starts 10s before the arrow and continues to the end.
Latest versions of everything. SF 10.0.6, macOS 12.5.
Oh FFS, and now at the end of an 8-minute export SF consistently crashes.
Come on, team. This is crazy-making.
------------------------------------- Translated Report (Full Report Below) ------------------------------------- Process: ScreenFlow  Path: /Applications/ScreenFlow.app/Contents/MacOS/ScreenFlow Identifier: net.telestream.screenflow10 Version: 10.0.6 (31900) Code Type: X86-64 (Translated) Parent Process: launchd  User ID: 501 Date/Time: 2022-07-31 14:39:29.6070 +1000 OS Version: macOS 12.5 (21G72) Report Version: 12 Anonymous UUID: 27CA4138-26CD-A7A9-06C6-61F33200B311 Time Awake Since Boot: 4500 seconds System Integrity Protection: enabled Crashed Thread: 45 Dispatch queue: com.Metal.CompletionQueueDispatch Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018 Exception Codes: 0x0000000000000001, 0x0000000000000018 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler 
John Noble said:
I say it's a bug because we've used identical settings for 30+ videos for the last 3 months with no issue. Then suddenly this one video.
I'm not sure that sounds like a bug since it would be happening all the time. If it previously didn't happen and then starts to happen, something changed. The issue is trying to figure out what changed and how easy it is to repeat the problem.
Perhaps just capture the Desktop and Cam Studio with no editing and "normal" export (and motion blur isn't checked).
If the issue is only on export that would mean capture is good. If it's only on some exports perhaps there's something intermittent. To confirm this you need to eliminate all other variables though.
If there are consistent steps I can test this on my 13" M1 MBP with Camo Studio.