Question / Help OBS Video Cut Short Issue

A

AdamskiRidders

New Member
hey all, so I am fairly new to OBS so please be kind, I wanted to record a short video (about a minute and 45 seconds). It's a really short video to record Pro-Tools for a bit, Just to become familiar with it. ANYWAY, I recorded almost two minutes and when I stopped the recording and checked both files (including the remux) It was only 5 seconds long.

I know I wanted a short video but C'mon I definitely recorded for longer than 5 seconds. I've include the Log hope that helps

A.




https://obsproject.com/logs/AYYQSXeYWP1xn5oz
 
Heya! You have a few recording attempts in there, so I'll just use the last one:
20:19:45.021: ==== Recording Start ===============================================
20:19:45.021: [ffmpeg muxer: 'simple_file_output'] Writing file 'G:/Youtube Viseos/2020-03-27 20-19-44.mkv'...
20:20:03.424: [ffmpeg muxer: 'simple_file_output'] Output of file 'G:/Youtube Viseos/2020-03-27 20-19-44.mkv' stopped
20:20:03.424: Output 'simple_file_output': stopping
20:20:03.424: Output 'simple_file_output': Total frames output: 76
20:20:03.424: Output 'simple_file_output': Total drawn frames: 452 (553 attempted)
20:20:03.424: Output 'simple_file_output': Number of lagged frames due to rendering lag/stalls: 101 (18.3%)
20:20:03.426: ==== Recording Stop ================================================
20:20:03.445: Video stopped, number of skipped frames due to encoding lag: 86/116 (74.1%)
Click to expand...
This shows a 15-second recording time, with 18% lagged frames due to rendering stalls, and 74% frames skipped due to encoding lag.
Most of the other attempts show the same, or similar.

You're using a system with an AMD APU, which are... notoriously anemic, to put it politely, and are trying to use the AMF encoder, along with a Display Capture.
Fortunately, it also appears you're only trying to record, not stream. We might need to try a few things, but can probably get you going.

The first thing to try is going into the Settings->Output menu, and swap your Encoder to x264 Low-CPU.
Also, set your Recording Quality to 'Indistinguishable'.
If you don't have those options, make sure you're on Simple output mode at the top.

Explanation:
AMD's AMF is similarly notorious for its poor quality and ability to overload the GPU. The fix? Not using it. That hopefully will lighten the load up enough to fix the rendering stalls (which are a sign of GPU overload), and use a very low-efficiency compression method (which is very CPU-light) to hopefully fix the skipped frames due to encoding lag. As that compression method will give poor video, we're going to use a quality-target method (Indistinguishable) which will throw a TON of bitrate at the problem to bring the quality back up... you're just recording to the local disk after all, and don't need to worry about the bottleneck of streaming bitrate constraints. You can use something like Handbrake to re-encode the video files later with a better compression method in non-realtime to bring the filesizes down. :)
 
FerretBomb said:
Heya! You have a few recording attempts in there, so I'll just use the last one:

This shows a 15-second recording time, with 18% lagged frames due to rendering stalls, and 74% frames skipped due to encoding lag.
Most of the other attempts show the same, or similar.

You're using a system with an AMD APU, which are... notoriously anemic, to put it politely, and are trying to use the AMF encoder, along with a Display Capture.
Fortunately, it also appears you're only trying to record, not stream. We might need to try a few things, but can probably get you going.

The first thing to try is going into the Settings->Output menu, and swap your Encoder to x264 Low-CPU.
Also, set your Recording Quality to 'Indistinguishable'.
If you don't have those options, make sure you're on Simple output mode at the top.

Explanation:
AMD's AMF is similarly notorious for its poor quality and ability to overload the GPU. The fix? Not using it. That hopefully will lighten the load up enough to fix the rendering stalls (which are a sign of GPU overload), and use a very low-efficiency compression method (which is very CPU-light) to hopefully fix the skipped frames due to encoding lag. As that compression method will give poor video, we're going to use a quality-target method (Indistinguishable) which will throw a TON of bitrate at the problem to bring the quality back up... you're just recording to the local disk after all, and don't need to worry about the bottleneck of streaming bitrate constraints. You can use something like Handbrake to re-encode the video files later with a better compression method in non-realtime to bring the filesizes down. :)
Click to expand...

awesome I’ll give that a go the now and report back soon as.
 
FerretBomb said:
Heya! You have a few recording attempts in there, so I'll just use the last one:

This shows a 15-second recording time, with 18% lagged frames due to rendering stalls, and 74% frames skipped due to encoding lag.
Most of the other attempts show the same, or similar.

You're using a system with an AMD APU, which are... notoriously anemic, to put it politely, and are trying to use the AMF encoder, along with a Display Capture.
Fortunately, it also appears you're only trying to record, not stream. We might need to try a few things, but can probably get you going.

The first thing to try is going into the Settings->Output menu, and swap your Encoder to x264 Low-CPU.
Also, set your Recording Quality to 'Indistinguishable'.
If you don't have those options, make sure you're on Simple output mode at the top.

Explanation:
AMD's AMF is similarly notorious for its poor quality and ability to overload the GPU. The fix? Not using it. That hopefully will lighten the load up enough to fix the rendering stalls (which are a sign of GPU overload), and use a very low-efficiency compression method (which is very CPU-light) to hopefully fix the skipped frames due to encoding lag. As that compression method will give poor video, we're going to use a quality-target method (Indistinguishable) which will throw a TON of bitrate at the problem to bring the quality back up... you're just recording to the local disk after all, and don't need to worry about the bottleneck of streaming bitrate constraints. You can use something like Handbrake to re-encode the video files later with a better compression method in non-realtime to bring the filesizes down. :)
Click to expand...

IT WORKED.
Thank you for your help
 
You must log in or register to reply here.
Back
Top