Question / Help Optimal recording settings for 10+ hours timelapse videos

busterlimiter

New Member
I'm trying to record 10+ hours of videos to later edit down to 3-5 minutes, but I found that doing that with the usual NVENC H.264 encoding settings absolutely kills my PC during editing and especially during exporting/rendering the file.
I tried to look around for solutions, but only one I can find is here: https://productforums.google.com/forum/#!topic/youtube/7NXCrXV4B7U
The person suggested using the Custom Output (ffmpeg) and setting Container Format to mov, Video Encoder to dnxhd and Keyframe interval to 8.
B8vMpPy.png

But using these settings gave me this error when starting the recording:
TM0Ok13.png

Anyone know any solution to this problem? Or can you guys suggest better ways to record and edit timelapse videos?
 

busterlimiter

New Member
I see, but at least I hope I still can get some advice on how to make my recording files more editing-friendly while still maintaining high quality
 

koala

Active Member
You didn't list the "usual NVENC H.264 encoding settings", so we don't know if you used some settings that produces video that is not editor-friendly. To correct this, switch to simple output mode and choose for recording:
Recording quality: Indistinguishable Quality (or high quality, try both)
Recording format: mkv (or flv, try both)
Encoder: Hardware (NVENC)

In case your video editor doesn't support mkv, record to mkv anyway and after you finished the recording click File->Remux Recordings and convert the mkv file to mp4 and try this with your video editor.

In case nothing helps, please explain better what you mean with "absolutely kills my PC". Is it only slow, or is it not possible to open and process the file at all?
 

busterlimiter

New Member
This is my original settings:
Rw7jkYs.png

MZ2fVZc.png

I'll try out the simple output mode. But the problem is that I can't really test it out quickly, since I need to produce a long recording footage first (editing was fine for shorter videos)

By "absolutely kills my PC" I mean it's really slow and often crashes the editor. Also, my PC become completely unusable during export.
 

koala

Active Member
You create videos with somewhat low resolution, with a fps value of 15, which is half of what is considered minimum acceptable value, and this is really slow and crashes the editor? You may consider a different video editor. I assume the problem is not the video format, it's the handling of the editor with large files - you said something about 10 hour long videos.

If your PC becomes unusable during export, your PC is probably not very powerful. Usually, the load during export is due to encoding the resulting video, not due to handling the source video. You will most certainly get these speed and load problems with every existing source format.
If long video files are a problem for your editor, consider splitting the recording by stopping and immediately starting it again.

But honestly, don't expect someone say: "use this" and it will immediately produce perfect files for you. These kind of problems are only solved with much trial and error.
 

busterlimiter

New Member
Yeah, I'm assuming that the length is what makes it slow. It was fine for 3 hour videos.
I think the editor is completely fine, I was using Shotcut and Lightworks
It's mostly likely because PC is pretty weak. But I don't mind long export times, I just want my PC to be at least usable during it.
I'll test out splitting the files, that might be an easier solution
 

Suslik V

Active Member
The original error (from the first post) caused by incompatible sample rate setting for audio. You need to set 48kHz in OBS Studio. Next is video resolution, framerate and bitrate. The mentioned codec has limited support of the options, like (see under the spoiler):
07:02:11.831: error: video parameters incompatible with DNxHD. Valid DNxHD profiles:
07:02:11.831: error: Frame size: 1920x1080p; bitrate: 175Mbps; pixel format: yuv422p10; framerate: 24000/1001
07:02:11.831: error: Frame size: 1920x1080p; bitrate: 185Mbps; pixel format: yuv422p10; framerate: 25/1
07:02:11.831: error: Frame size: 1920x1080p; bitrate: 365Mbps; pixel format: yuv422p10; framerate: 50/1
07:02:11.831: error: Frame size: 1920x1080p; bitrate: 440Mbps; pixel format: yuv422p10; framerate: 60000/1001
07:02:11.831: error: Frame size: 1920x1080p; bitrate: 115Mbps; pixel format: yuv422p; framerate: 24000/1001
07:02:11.831: error: Frame size: 1920x1080p; bitrate: 120Mbps; pixel format: yuv422p; framerate: 25/1
07:02:11.831: error: Frame size: 1920x1080p; bitrate: 145Mbps; pixel format: yuv422p; framerate: 30000/1001
07:02:11.831: error: Frame size: 1920x1080p; bitrate: 240Mbps; pixel format: yuv422p; framerate: 50/1
07:02:11.831: error: Frame size: 1920x1080p; bitrate: 290Mbps; pixel format: yuv422p; framerate: 60000/1001
07:02:11.831: error: Frame size: 1920x1080p; bitrate: 175Mbps; pixel format: yuv422p; framerate: 24000/1001
07:02:11.831: error: Frame size: 1920x1080p; bitrate: 185Mbps; pixel format: yuv422p; framerate: 25/1
07:02:11.831: error: Frame size: 1920x1080p; bitrate: 220Mbps; pixel format: yuv422p; framerate: 30000/1001
07:02:11.831: error: Frame size: 1920x1080p; bitrate: 365Mbps; pixel format: yuv422p; framerate: 50/1
07:02:11.831: error: Frame size: 1920x1080p; bitrate: 440Mbps; pixel format: yuv422p; framerate: 60000/1001
07:02:11.831: error: Frame size: 1920x1080i; bitrate: 185Mbps; pixel format: yuv422p10; framerate: 25/1
07:02:11.831: error: Frame size: 1920x1080i; bitrate: 220Mbps; pixel format: yuv422p10; framerate: 30000/1001
07:02:11.831: error: Frame size: 1920x1080i; bitrate: 120Mbps; pixel format: yuv422p; framerate: 25/1
07:02:11.831: error: Frame size: 1920x1080i; bitrate: 145Mbps; pixel format: yuv422p; framerate: 30000/1001
07:02:11.831: error: Frame size: 1920x1080i; bitrate: 185Mbps; pixel format: yuv422p; framerate: 25/1
07:02:11.831: error: Frame size: 1920x1080i; bitrate: 220Mbps; pixel format: yuv422p; framerate: 30000/1001
07:02:11.831: error: Frame size: 1440x1080i; bitrate: 120Mbps; pixel format: yuv422p; framerate: 25/1
07:02:11.831: error: Frame size: 1440x1080i; bitrate: 145Mbps; pixel format: yuv422p; framerate: 30000/1001
07:02:11.831: error: Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p10; framerate: 24000/1001
07:02:11.831: error: Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p10; framerate: 25/1
07:02:11.831: error: Frame size: 1280x720p; bitrate: 180Mbps; pixel format: yuv422p10; framerate: 50/1
07:02:11.831: error: Frame size: 1280x720p; bitrate: 220Mbps; pixel format: yuv422p10; framerate: 60000/1001
07:02:11.831: error: Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 24000/1001
07:02:11.831: error: Frame size: 1280x720p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 25/1
07:02:11.831: error: Frame size: 1280x720p; bitrate: 110Mbps; pixel format: yuv422p; framerate: 30000/1001
07:02:11.831: error: Frame size: 1280x720p; bitrate: 180Mbps; pixel format: yuv422p; framerate: 50/1
07:02:11.831: error: Frame size: 1280x720p; bitrate: 220Mbps; pixel format: yuv422p; framerate: 60000/1001
07:02:11.832: error: Frame size: 1280x720p; bitrate: 60Mbps; pixel format: yuv422p; framerate: 24000/1001
07:02:11.832: error: Frame size: 1280x720p; bitrate: 60Mbps; pixel format: yuv422p; framerate: 25/1
07:02:11.832: error: Frame size: 1280x720p; bitrate: 75Mbps; pixel format: yuv422p; framerate: 30000/1001
07:02:11.832: error: Frame size: 1280x720p; bitrate: 120Mbps; pixel format: yuv422p; framerate: 50/1
07:02:11.832: error: Frame size: 1280x720p; bitrate: 145Mbps; pixel format: yuv422p; framerate: 60000/1001
07:02:11.832: error: Frame size: 1920x1080p; bitrate: 36Mbps; pixel format: yuv422p; framerate: 24000/1001
07:02:11.832: error: Frame size: 1920x1080p; bitrate: 36Mbps; pixel format: yuv422p; framerate: 25/1
07:02:11.832: error: Frame size: 1920x1080p; bitrate: 45Mbps; pixel format: yuv422p; framerate: 30000/1001
07:02:11.832: error: Frame size: 1920x1080p; bitrate: 75Mbps; pixel format: yuv422p; framerate: 50/1
07:02:11.832: error: Frame size: 1920x1080p; bitrate: 90Mbps; pixel format: yuv422p; framerate: 60000/1001
07:02:11.832: error: Frame size: 1920x1080p; bitrate: 350Mbps; pixel format: yuv422p10; framerate: 24000/1001
07:02:11.832: error: Frame size: 1920x1080p; bitrate: 390Mbps; pixel format: yuv422p10; framerate: 25/1
07:02:11.832: error: Frame size: 1920x1080p; bitrate: 440Mbps; pixel format: yuv422p10; framerate: 30000/1001
07:02:11.832: error: Frame size: 1920x1080p; bitrate: 730Mbps; pixel format: yuv422p10; framerate: 50/1
07:02:11.832: error: Frame size: 1920x1080p; bitrate: 880Mbps; pixel format: yuv422p10; framerate: 60000/1001
07:02:11.832: error: Frame size: 960x720p; bitrate: 42Mbps; pixel format: yuv422p; framerate: 0/0
07:02:11.832: error: Frame size: 960x720p; bitrate: 60Mbps; pixel format: yuv422p; framerate: 0/0
07:02:11.832: error: Frame size: 960x720p; bitrate: 75Mbps; pixel format: yuv422p; framerate: 0/0
07:02:11.832: error: Frame size: 960x720p; bitrate: 115Mbps; pixel format: yuv422p; framerate: 0/0
07:02:11.832: error: Frame size: 1440x1080p; bitrate: 63Mbps; pixel format: yuv422p; framerate: 0/0
07:02:11.832: error: Frame size: 1440x1080p; bitrate: 84Mbps; pixel format: yuv422p; framerate: 0/0
07:02:11.832: error: Frame size: 1440x1080p; bitrate: 100Mbps; pixel format: yuv422p; framerate: 0/0
07:02:11.832: error: Frame size: 1440x1080p; bitrate: 110Mbps; pixel format: yuv422p; framerate: 0/0
07:02:11.832: error: Frame size: 1440x1080i; bitrate: 80Mbps; pixel format: yuv422p; framerate: 0/0
07:02:11.832: error: Frame size: 1440x1080i; bitrate: 90Mbps; pixel format: yuv422p; framerate: 0/0
07:02:11.832: error: Frame size: 1440x1080i; bitrate: 100Mbps; pixel format: yuv422p; framerate: 0/0
07:02:11.832: error: Frame size: 1440x1080i; bitrate: 110Mbps; pixel format: yuv422p; framerate: 0/0
The recording with any of this setting is not recommended (file is large, additional color space/depth conversation).

You may wanna look at:
Dan, I also tried Chron..I didn't like it for some reason..
Go here: https://windowsreport.com/best-time-lapse-software/
some info on pro codecs
ProRes codec was fine but now tearing badly

Splitting the files is nice idea.
Also, while using mov/mp4 you need to look at: Stopping recording never ends
 

koala

Active Member
Now I think I got what you are trying to achieve and why you use a fps of 15. Sorry that I didn't get it earlier. You want to record 10 hours real time and shrink the whole video to 5 minutes as massive timelapse. You don't want to cut scenes out of it using a regular video editor. Instead you just want to postprocess the whole video uncut and simply shrink it to 5 minutes. You want to show how a plant grows during one day in a 5 minute video or something like this.

There are video editors out there who can adjust the fps of a video without doing much computation. We just need to know at which fps we need to record to get our final fps if we speed up the video afterwards by patching a higher fps into it.

Let's compute a bit.
We have a source video with length s seconds. (that's our 10 hour long video)
We want to know the recording frame rate r to configure OBS accordingly.
We want a destination video with length t seconds (that's our timelapse video)
We want a destination frame rate of 60 (I made this up; this seems a nice rate for a smooth video)

We can compute the number of frames (n) in the destination video:
n = t * 60 [1]

We want the original video contain the same number of frames to not have to cut any frames away:
n = s * r
or
r = n / s [2]

[1] in [2]:
r = t * 60 / s

Suppose we have a source video of 10 hours (s = 36000 seconds) and a destination video of 5 minutes (t=300 seconds):
r = 300 * 60 / 36000 = 18000 / 36000 = 1/2

That means we need a frame rate of 1/2 in the source video. That's one frame every 2 seconds or 0.5 fps. We are able to configure this in OBS.
To get this frame rate, do this:
- go to Settings->Video and set the fps dropdown box to "Fractional FPS Value".
- set Numerator to 1 and Denominator to 2. This makes our 1/2.
Be careful at stopping a recording. This will take up to 1 minute (at least at my system it does this). This is due to the low frame rate and the encoder - don't ask why. The stopping time gets longer the lower the fps is. Don't go lower than 1/5 fps if you want to get faster timelapse.

To get a good video quality, you can set really high quality encoder settings, because your machine has to compress only one frame in 2 seconds. Use:
- Output mode: advanced
- on Recording tab: format mkv, Encoder x264, Rate Control CRF, CRF 10, Preset Veryfast. Keyframe interval: 1. This means every frame will be a keyframe, because we have 1 frame every 2 seconds. This makes seeking and cutting very fast, if you want to also cut some frames out.

Now get a video editor that has a filter to adjust the frame rate but not add or remove frames. I used Avidemux for this: http://avidemux.sourceforge.net/

We now have our 10 hour source video with frame rate 0.5
We want a video of 60 frames.
Add the video filter called "change fps" in avidemux.
Unfortunately, we cannot enter a fps of lower than 1 in that certain filter, but the source fps is somewhat ignored. Just enter 1 fps as source fps and 60 fps as destination fps. The resulting video will have the same amount of frames as the original video but will be played with 60 fps.

WHY THIS WILL WORK ON A LOW END PC:
We record with OBS exactly the amount of frames that will be in the final video. The original video is as small as possible due to this, no frames are thrown away. Avidemux will recode the video wile changing the fps, but there are also video file editors that only patch a new fps and leave the video data unchanged. You might look for these, if even the minimal recoding Avidemux does is too much for your machine.
 
Last edited:
Top