Question / Help WARNING: Taking too long to encode. Skipping Frame!

E

EagleTalonTv

New Member
Every time i try to record anything, OBS gives me a notice saying WARNING: Taking too long to encode. Skipping Frame! and i dont know how to fix it and i tried to use one of the moderator's log analyzer, but it doesnt show me anything is wrong! and everytime i try and record it just crashes! Heres my log and a crash report.
 

Attachments

  • crash.txt
    5.5 KB · Views: 332
  • log.txt
    4.7 KB · Views: 536
dodgepong

dodgepong

Administrator
Community Helper
That is a pretty weak processor, and OBS is giving you that error because your CPU can't handle what you're telling it to do.

Try downscaling by at least 2x and don't use 60fps (try 25fps). If you're still having problems, change your x264 preset to superfast or ultrafast.
 
E

EagleTalonTv

New Member
dodgepong said:
That is a pretty weak processor, and OBS is giving you that error because your CPU can't handle what you're telling it to do.

Try downscaling by at least 2x and don't use 60fps (try 25fps). If you're still having problems, change your x264 preset to superfast or ultrafast.
Click to expand...

Before the update for 0.57b, my OBS worked perfect and i streamed in hd and recorded in HD with the same exact settings
 
E

EagleTalonTv

New Member
0.57 Beta - 2013-09-24
* Moved encoding to a separate thread to avoid issues with keyframe interval timing and made CFR default
I think this might be causing the problems. I got this from your chagelog
 
dodgepong

dodgepong

Administrator
Community Helper
The warning thing is a new message that didn't exist in older version of OBS. It's more likely that you're still having problems, but OBS just isn't notifying you.

Can you post as log from 0.554?
 
Krazy

Krazy

Town drunk
Like this video? http://www.youtube.com/watch?v=M9sWcHxeezg

If you notice how jerky/choppy it is, that's because the encoder wasn't able to maintain the proper framerate. You will have to downscale and/or lower FPS in order to get everything working smoothly, there's really no way around it. Your frames times actually got BETTER in the new version, but you still had an underlying problem that wasn't highlighted by previous versions which didn't have the warning message.
 
L

Lain

Forum Admin
Lain
Forum Moderator
Developer
In your 0.554 log file, make note of this:

Total frames rendered: 1228, number of late frames: 780 (63.52%) (it's okay for some frames to be late)

and this:

frame - [100%] [avg time: 23.748 ms]

You are not actually encoding at 60fps even in 0.554. You are encoding at approximately 41ish FPS average total. Due to the fact that encoding is taking so long, even in 0.554 you are not getting 60fps. Which means that 0.554 was not actually performing perfectly for you either. The majority of your frame timings were late.

In 0.57, it now forces the stream to send at exactly the FPS you set to prevent encoder issues and to prevent twitch streaming issues, so it was not giving you that warning in error, it was a legitimate error given because you are set to a framerate you cannot actually handle. I would recommend setting your stuff up to 30fps. Maybe 40 at most (because you already can't get much over that anyway regardless of version)
 
C

CaMaK

New Member
Hi,

I have the same issue with duel PC setup (i3770k@4.3 reserved for OBS). Do i need to downgrade to the 0.554 ?

Regards,
 
FerretBomb

FerretBomb

Active Member
Just waiting to see this progression in Jim's patch notes:

-Added error message to notify users of encoding problems formerly silently written to the log files.

-Users complaining about performance hit in latest version. What happened?

-Users actually just complaining about error message. Removed error message. Let them eat cake.


Again: READ THE THREAD, PEOPLE.
The problem existed before. It was actually worse. OBS just didn't have a helpful indicator to let you know that your settings were too high, and your stream quality was suffering the whole time.
 
C

CaMaK

New Member
Ok, for the fact that the problems already exist. But now he feels the record is, whereas before it was not.

I'm reading the thread, I see no solution because I think my processor is more than enough being dedicated to the task. If anyone sees a concern in my settings I'm not saying "no" :)

PS: I will post my logs after work
 
V

vaesauce

Member
Original poster's CPU is DEFINITELY not up to task to stream at those settings which is the reason why it's dropping all those frames and etc.

As for CaMaK, you're going to have to be a lot more specific, make your own thread so we can assist.
 
C

CaMaK

New Member
Ok,

New broadcast, new settings (fast), CPU at 70% max and again WARNING: Taking too long to encode. Skipping Frame!

Can somebody explain to me why ?
 

Attachments

  • 2013-10-06-1909-59.log
    9.7 KB · Views: 156
You must log in or register to reply here.
Top