SLOW Effects Render and Export - OBS 2K Screen Capture With Effects

I would be very surprised if that media wasn't H.264/long-GOP.

Also ... there is a chance that it is VFR, variable frame-rate, as many screen capture and phone media apps use that type of recording. VFR means the app/device has a "suggested equivalent" frame-per-second or FPS setting, but ... then decides whether it really needs to use that many frames, or if perhaps it could get by with a bit fewer because it doesn't seem to have too many moving pixels at this moment.

So ... while OBS says the framerate is say 30, when you look at the media in something like MediaInfo you may see it listed as VFR, with frame-rates varying from 27.3 to 30.8 fps within the file.

The audio however is recorded on a constant basis ... so the video is varying frames per second, the audio isn't, and it's darn hard on an NLE to puzzle out.

This would be why the Help people suggested re-encoding in HandBrake ... to get the media into CFR, constant frame rate. Where you would need to go to the Video tab and both check the CFR box, and set a specific number frame-rate in the frame-rate selection box.

Neil

But I don't think my source is an H.264 encoded format.  Is it? Is QuickTime .mov H.264 encoded?

s814jdh,

Sorry for the poor performance with this particular workflow. There are several issues that can be addressed with some potential for performance improvments.

• Format + Sequence Size: The first issue is that you are working with a large H.264 file in a overly large sequence. 
  • H.264 is a codec that is perfect for screen captures, but does not do well as an editing or rendering codec.
  • You'd be better served with a smaller sequence, say HDTV sized, so you can edit more nimbly and render & export faster and easier.
• Workflow: A bit more care in your workflow might save you hours of time. It takes a lot of hard drive space up front, but I like to use smart rendering when I am advising those that have these kinds of issues. Tell you about that in a minute. Another workflow win is to create add edits (splices from the razor tool or shortcut) around any effects you are creating. That way, you are not disturbing the render files you already created, saving time and drive space.
• Hardware:
  • Ensure that your GPU is enabled in Project Settings > General. Your computer should use Metal protocol. 
  • Ensure that the SSD you are exporting to is separate from the drive containing macOS.

There are a couple of ways to approach a smart rendering workflow with screen capture. What I'd recommend to you are a few steps that are simple, yet effective.

1. In Sequence > Sequence Settings, set the Editing Mode to Custom. Scroll to the top of the list to find it.
2. In the section for changing your codec for rendering previews, set it to QuickTime > ProRes LT.
3. Your preview files will be in ProRes LT format. This takes up room, but you can delete these files upon completing the project. As you work, render the timeline every time you walk away from the machine, the goal being a fully rendered timeline of ProRes LT preview files that is ready to export. You should have a green bar across your entire sequence.
4. When exporting, choose to Match Sequence Settings and check the "Using Previews" box (important). The export process is very, very fast since you are only copying the files, harnassing your previously created render files. A ProRes master is the result. If the export is not lightning fast, something is amiss. I find this fast export an ingenius discovery. Try it.
5. With this ProRes master, feel free to upload that to YouTube, or encode an H.264 files from the master. It will be much faster than exporting a H.264 file from scratch.

Let me know if you have any questions about this workflow.

Thanks!
Kevin