Question / Help Failed locking bitstream buffer: invalid version (15)

Gozen

New Member
Hello,

About a week ago, right at the launch of OBS Studio version 20.0.0, I switched my encoder from x264 to NVENC H.264.

For the most part, I have been able to stream with no issues since switching to the NVENC encoder. However, there have been a couple of times where I have been streaming via my Elgato HD60 S, and I notice that my upload speed drops to 0 kbps. Eventually my chat tells me that my stream has gone offline. When this has happened I usually have been streaming for about an hour and a half, or a little longer.

If I then try to click on the "stop streaming" button within OBS Studio, nothing happens. I then have to click on the "stop streaming" button a second time for the stream to apparently stop, even though the stream stopped broadcasting some time prior. If I immediately try to click on "start streaming" again, it appears like it does connect to the streaming service, but my upload speed remains at 0 kbps within OBS and my stream does not go back online.

I then have to exit out of OBS entirely, re-launch, and then if I click "start streaming" everything works normally again without me having made any changes whatsoever.

I believe that I have only encountered this when streaming via my Elgato HD60 S so far. I can't recall seeing this happen when using Game Capture to stream directly from a PC game.

The actual errors that appear in the log, immediately before the stream itself crashes are as follows:
error: Failed locking bitstream buffer: invalid version (15)
[NVENC encoder: 'streaming_h264'] nvenc_encode: Error encoding: Invalid argument
error: EncodePicture failed!: invalid version (15)
Error encoding with encoder 'streaming_h264'

Also worth noting is that the following settings are identical from what I was using with x264 previously, so I can't say I made any changes with these:
Rate Control = CBR
Bitrate = 6000
Keyframe Interval = 2
Profile = High

I also was not using NVENC as my encoder prior to the release of version 20 of OBS Studio, so I can't say if something changed in this new version or if I would have seen this same issue when running on version 19.x.

I have attached my most recent log where this has happened.

Thanks.
 

Attachments

  • 2017-08-16 19-02-16.txt
    17.7 KB · Views: 50
Last edited:
Top