Question / Help Invalid NAL unit size? 0.14.2 Introduced this.

Hey guys.

I haven't really been running into any issues with OBS as I ran a stream with 0.14.2 yesterday without any issues, but I was noticing that the log was getting spammed with the following error messages:

Code:
...
22:22:49.653: error:   Error splitting the input into NAL units.
22:22:50.218: error:   Invalid NAL unit size.
...

This is something new to 0.14.2, as this never appeared in any log files prior to updating to the newest version. I haven't changed any settings, so I'm fairly confident this is an issue with the program itself.

Every now and then it was also reporting some dropped frames, apparently, but I nor my viewers noticed anything of the sort. Here's the full log: http://pastebin.com/K2pEAZUc

Also, isn't it weird that OBS is only reporting 2GB of RAM? I've got 8GB. It hasn't been reporting the correct amount of memory for as long as I've used OBS-Studio.
 

Lain

Forum Admin
Lain
Forum Moderator
Developer
Also the 2GB (it's actually 4GB even though it says 2) of ram thing is a limitation of using the 32bit version of the program. 32bit address space can only use approximately 4 gigabytes max. If you open up the 64bit of the program you'll note that the log will report all your actual ram, and not just the amount of ram the program is limited to (which for 64bit address space is 9 billion gigabytes max)
 
@R1CH:
Huh, weird! If all else fails I suppose I'll just re-encode the same file with x264 or something. I'll check it out to see if I can fix it. Thanks for pointing that out.

@Jim:
Yeah, I thought that was weird! If it actually reported 4GB I would've known for sure that it was a 32 bits thing. Is this a little weird bug or is there a reason why it's reporting 2GB?
 

Lain

Forum Admin
Lain
Forum Moderator
Developer
Don't know why it's reporting 2gb exactly but it's still due to the same 32bit limitation. I'll probably just change the log message to say "2 or 4 gigabytes max for 32bit programs" instead of just "4 gigabytes max" to clear up any confusion in the future for others who encounter it.
 
Ahh, that makes sense R1CH :) I'll be using the 64 bit version from now on. I took it for granted that it would create a shortcut to the version most suited to the OS.

Oh hey, that does look like it may be relevant. Weird, though. For the time being I've recorded a 10 minute clip of the scrolling background animation. It cuts poorly at the end, but I suppose it works.

I was initially using some HTML + CSS for this, but this seems to be incredibly difficult to render for the browser plugin (often capping my CPU when streaming). Interestingly enough it works just fine in a regular browser. Probably a hardware acceleration thing.

Thanks for checking it out, dudes.
 
Top