0

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.

 

5replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
    • John Noble
    • John_Noble
    • 2 mths ago
    • Reported - view

    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 [988]
    Path:                  /Applications/ScreenFlow.app/Contents/MacOS/ScreenFlow
    Identifier:            net.telestream.screenflow10
    Version:               10.0.6 (31900)
    Code Type:             X86-64 (Translated)
    Parent Process:        launchd [1]
    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 [988]
    
    Like
    • John Noble
    • John_Noble
    • 2 mths ago
    • Reported - view

    Update: this happens without any transition! Turns out it didn't go away with the Cross Blur. Or rather, it did when I only exported a small segment for testing. Exporting the whole video causes the issue to re-occur.

    Now what?

    Like
      • CraigSModerator
      • Telestream Desktop Forum Moderator
      • CraigS
      • 2 mths ago
      • Reported - view

      John Noble Sorry but I'm not seeing it in the video. Can you please tell me what the precise point is?

      If it's only when exporting the complete video it could be RAM related, drive related, or encoder related. Please include all specs of the system, drive free space, encoder settings used.

      Like
      • John Noble
      • John_Noble
      • 2 mths ago
      • Reported - view

      CraigS The frame rate on the talking heads at the lower right drops noticeably at the 10s mark.

      We've fixed it by replacing this bit of video with ... the same bit of video. ¯\_(ツ)_/¯ Looks like some weird little bug, because I'm on a M1 Pro MBP with 32GB RAM and all the free space in the world. Exactly the same issue exhibits on my partner's M1 MBA with 16GB RAM and all the free space. Encoder settings are 1920x1080 and I've tried Slowest and Normal.

      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.

      All good, we worked around it.

      Like
    • CraigSModerator
    • Telestream Desktop Forum Moderator
    • CraigS
    • 2 mths ago
    • Reported - view
    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.

    Like
Like Follow
  • 2 mths agoLast active
  • 5Replies
  • 7Views
  • 2 Following