[Fixed] Restream.io suggested settings

[sneaky4oe]

Hi guys. I'm at restream.io support now, and would like to ask you to set keyframe interval to 2 instead of random number when "enforce streaming service encoder settings" is enabled. It causes lots of troubles for users at end platforms since most of them needs 2 as their keyframe value.

Would be nice to see this change.

 

[RytoEX]

Hi guys. I'm at restream.io support now, and would like to ask you to set keyframe interval to 2 instead of random number when "enforce streaming service encoder settings" is enabled. It causes lots of troubles for users at end platforms since most of them needs 2 as their keyframe value.

Would be nice to see this change.

I'm confused by this request. The current rtmp-services services.json shows this:

{
    "name": "Restream.io",
    "common": true,
<snip>
    "recommended": {
        "keyint": 2
    }
},

So it should already be doing what you're asking. Are you saying the behavior of "enforce streaming service encoder settings" for this instance is buggy?

 

[sneaky4oe]

Yeah. I've faced some users who had it at 8 for some reason with the "enforce" option enabled for restream.

See the logs: https://gist.github.com/anonymous/2317270bd6442483dea1076219b03791

Keyint at 0, enforcing service's settings.
Keyint at 2, not enforcing anything.
Simple settings.

Keyint's for each case at 30 fps:
250
60
60

Spoiler: log parts

[x264 encoder: 'streaming_h264'] preset: veryfast
[x264 encoder: 'streaming_h264'] settings:
rate_control: CBR
bitrate: 2500
buffer size: 2500
crf: 0
fps_num: 30
fps_den: 1
width: 1280
height: 720
keyint: 250

[x264 encoder: 'streaming_h264'] preset: veryfast
[x264 encoder: 'streaming_h264'] settings:
rate_control: CBR
bitrate: 2500
buffer size: 2500
crf: 0
fps_num: 30
fps_den: 1
width: 1280
height: 720
keyint: 60

[x264 encoder: 'simple_h264_stream'] preset: veryfast
[x264 encoder: 'simple_h264_stream'] settings:
rate_control: CBR
bitrate: 2500
buffer size: 2500
crf: 0
fps_num: 30
fps_den: 1
width: 1280
height: 720
keyint: 60

So, yeah. Enforcing leaves keying at ~8 for some reason.

 

[sneaky4oe]

If you set keyint to 2 manually with "enforce" enabled, it works tho.
But if 0 should be auto - why is it 8.33 then with "enforce" enabled?

 

[sneaky4oe]

Another thing from current case. OSx user has it on 2 with "enforce" enabled. KF interval is a variable around 1.8 on stream.

 

[Boildown]

Are you counting i-frames generated by scene changes?

 

[RytoEX]

A keyint of 250 is the default value for FFmpeg/x264. It seems like if a user creates a new profile and does not modify the default Keyframe Interval value of 0, OBS will not set the service recommended value until the user changes the value to something, and then changes it back to 0. It will instead use the FFmpeg/x264 default, which is the 250 you're seeing.

I'm still looking at the code paths to see exactly why this happens. To clarify, this occurs with all streaming services, not just Restream.


Edit: I do see why this happens now, but I haven't figured out the best way to fix it yet. To workaround it, change any setting in the streaming section, then change it back, and hit apply/OK. For now, I've filed Mantis Issue 1061.

 

[sneaky4oe]

@RytoEX Thanks, but is there a way to force keyframe of 2 if user won't change it manually? It causes many problems for unexperienced streamers.

 

[RytoEX]

Not that I know of currently, other than the workaround that I've already outlined (change any encoder setting, change it back, hit apply/OK).

 

[sneaky4oe]

Why can't you just trigger those "manually changed settings" upon switching to advanced mode?..

 

[RytoEX]

I probably could, but I don't think that's the best way to solve the issue. I've had other responsibilities away from OBS, and then I was away for a while. Jim has been focused on other development items, and the PR queue had gotten a bit large. This is something that is on my mind and in my backlog of items to address, I just need time to sit down and think it over or talk it out with another contributor (or Jim).

 

[sneaky4oe]

Ok, I see. It would help us a lot, if you'd release a fix at some point. :-)

 

[sneaky4oe]

Today I've had a user who for some reason had keyframe interval of 0.8-1.0 when it was set for 2 with unchecking suggested settings at x264. Switching over to nvenc helped though. Is it legal? :-D

 

[sneaky4oe]

I probably could, but I don't think that's the best way to solve the issue. I've had other responsibilities away from OBS, and then I was away for a while. Jim has been focused on other development items, and the PR queue had gotten a bit large. This is something that is on my mind and in my backlog of items to address, I just need time to sit down and think it over or talk it out with another contributor (or Jim).

Any news on this bug fix?
With profile selected to "none" with that "enforce" option ticked, user had "baseline" instead of "main".
And I still have a lot of users with keyint 8 instead of 2.

 

[sneaky4oe]

bump

 

[DarkDench]

Hello. I have an interval of keyframe 2 (x264) in obs, but restream.io in the statistics after streaming the interval of the keyframe 1. Tell me how to fix this

 

[sneaky4oe]

Yeah, that's exactly what I was talking about. Untick those recommended settings.

@RytoEX @Jim can someone react to this at last please?

 

[DarkDench]

"use the encoder settings of the streaming service" - need to disable.

I rightly understood?

 

[sneaky4oe]

Yes

 

[DarkDench]

Thank you