Status
Not open for further replies.

ball2hi

Member
So I decided to (since I now have some time in between matches) to test streaming with h.264. Unfortunately it seems that after a minute or two my entire computer locks up, sound loops, and my monitors go black and then my drivers restart. I haven't used h.264 since before the Win10 update.

https://gist.github.com/c22ae3aae654cf937936d5f8cb42992a

I'm not sure exactly how to capture what is going on. It's as if my card is overclocked and then the clock was unstable and shitting on itself but I'm actually underclocking.

I have uninstalled (DDU) my drivers, and reinstalled the current hotfix drivers (after re-downloading them).
 
Last edited:

Xaymar

Active Member
When I used VCE encode, then stop and close OBS, It will crash.
I can't reproduce this crash here. Also please read the first post to find out where to report bugs and crashes.

So I decided to (since I now have some time in between matches) to test streaming with h.264. Unfortunately it seems that after a minute or two my entire computer locks up, sound loops, and my monitors go black and then my drivers restart. I haven't used h.264 since before the Win10 update.

https://gist.github.com/c22ae3aae654cf937936d5f8cb42992a

I'm not sure exactly how to capture what is going on. It's as if my card is overclocked and then the clock was unstable and shitting on itself but I'm actually underclocking.

I have uninstalled (DDU) my drivers, and reinstalled the current hotfix drivers (after re-downloading them).

https://github.com/GPUOpen-LibrariesAndSDKs/AMF/issues/22

Also please start submitting issues to github, otherwise I will just skip over and forget them eventually.
 
Last edited:

ObZidianLP

New Member
Hi everyone! Thanks for your hard work Xaymar. Without the plugin I wouldn't even be able to record in the first place, but I've run into some issues with the recorded files.

When I open the files in VLC, everything works fine and the video plays without any issues. However when importing the files into Sony Vegas Pro 13 there is always a certain point in the recording - usually around 4 minutes and 30 seconds - where the video starts to flicker and corrupt the colours. The audio is not affected by this. Here's a video of it: https://youtu.be/IoPC5-aKlNQ

The only workaround that I have found so far is to convert the recordings to mp4 with VLC, even though they're already mp4s. If I do this the corruption is gone and the video is perfectly fine. I can then import it into Vegas or play it in WMP without any issues.

I included the log of the same recording that I uploaded to YouTube, but all videos recorded show the same corruption after ~4:30.

Any and all help would be greatly appreciated!
 

Attachments

  • 2016-10-03 15-34-48.txt
    97.8 KB · Views: 30

Xaymar

Active Member
Hi everyone! Thanks for your hard work Xaymar. Without the plugin I wouldn't even be able to record in the first place, but I've run into some issues with the recorded files.

When I open the files in VLC, everything works fine and the video plays without any issues. However when importing the files into Sony Vegas Pro 13 there is always a certain point in the recording - usually around 4 minutes and 30 seconds - where the video starts to flicker and corrupt the colours. The audio is not affected by this. Here's a video of it: https://youtu.be/IoPC5-aKlNQ

The only workaround that I have found so far is to convert the recordings to mp4 with VLC, even though they're already mp4s. If I do this the corruption is gone and the video is perfectly fine. I can import it into Vegas or play it in WMP without any issues.

I included the log of the same recording that I uploaded to YouTube, but all videos recorded show the same corruption after ~4:30.

Any and all help would be greatly appreciated!

Open up an Issue on Github and also report this as a bug to the makers of that software. If it plays fine in Windows Media Player, MPC-HC, VLC or any other decoder but doesn't work in whatever software Vegas Pro is, the issue isn't the plugin.
 

horst

New Member
I tried Version 1.3.2.0, and i could record for 23 minutes and it still had video frames by that time, so that is great! Unluckily the mp4 is not skipable in vlc now. It does skip to keyframes, but doesn't play the video from the skipped position. The file seems to create problems for my editing software too, it is not responding when i import the file. I will give it another try later.

edit: Tried some more and i keep having that that non skip problem, also tried the default recording preset.
 
Last edited:

ball2hi

Member
I tried Version 1.3.2.0, and i could record for 23 minutes and it still had video frames by that time, so that is great! Unluckily the mp4 is not skipable in vlc now. It does skip to keyframes, but doesn't play the video from the skipped position. The file seems to create problems for my editing software too, it is not responding when i import the file. I will give it another try later.

edit: Tried some more and i keep having that that non skip problem, also tried the default recording preset.
What is your keyframe set to? I had this problem with AMF when my encoder was set to 0. Use 2 or 1.
 

Xaymar

Active Member
Xaymar updated AMD Advanced Media Framework Encoder Plugin for OBS Studio with a new update entry:

1.3.2.0 - Massive Preset Updates

  • Changed: All Presets now default to use maximum available 'B-Picture Pattern' for higher quality at lower bitrates.
  • Changed: All Presets no longer override 'Frame Skipping', 'B-Picture Reference' and 'Custom Buffer'.
  • Changed: 'Twitch', 'YouTube' and 'Recording' Presets no longer override 'Target Bitrate' and 'Peak Bitrate'.
  • Changed: 'Twitch' and 'YouTube' Presets no longer override 'Minimum QP' and 'Maximum QP'. (Always forced to 0/51.)
  • Changed: 'Enforce HRD Compatibility' is now set to disabled for all Presets.
  • Changed: 'Debug Tracing' will now log additional information, it is recommended to disable this for non-test sessions.
  • Added: You can now override Preset parameters instead of having to manually deselect the Preset.
  • Fixed: Potential Crash when quitting OBS directly before the Encoder is completely initialized.

Read the rest of this update entry...
 
Last edited:

Xaymar

Active Member
Xaymar updated AMD Advanced Media Framework Encoder Plugin for OBS Studio with a new update entry:

1.3.2.1 - Bug Fixes for Presets and Timestamps

  • Fixed: Audio desynchronization and video corruption caused by timestamp drifting.
  • Fixed: Fields would be defocused when the plugin tried to deselect a preset.
    Update: Did not actually fix it.
1.3.2.0
  • Changed: All Presets now default to use maximum available 'B-Picture Pattern' for higher quality at lower bitrates.
  • Changed: All Presets no longer override 'Frame Skipping', 'B-Picture Reference' and 'Custom Buffer'.
  • Changed: 'Twitch', 'YouTube' and 'Recording' Presets no longer override 'Target Bitrate' and 'Peak Bitrate'.
  • Changed: 'Twitch' and 'YouTube' Presets no longer override 'Minimum QP' and 'Maximum QP'. (Always forced to 0/51.)
  • Changed: 'Enforce HRD Compatibility' is now set to disabled for all Presets.
  • Changed: 'Debug Tracing' will now log additional information, it is recommended to disable this for non-test sessions.
  • Added: You can now override Preset parameters instead of having to manually deselect the Preset.
  • Fixed: Potential Crash when quitting OBS directly before the Encoder is completely initialized.

Read the rest of this update entry...
 
Last edited:

meredith

New Member
v1.3.2.1 fix all my problem, Thanks a lot.
but now I found new issue, when I input Target Bitrate, It will unfocus, I don't know how to explanation it.
 

Xaymar

Active Member
Xaymar updated AMD Advanced Media Framework Encoder Plugin for OBS Studio with a new update entry:

1.3.2.2 - Minor Fixes

  • Removed: Automatic override of Preset, caused more issues than features it added.
  • Fixed: The plugin would initially report an incorrect queue size delta.
1.3.2.1
  • Fixed: Audio desynchronization and video corruption caused by timestamp drifting.
1.3.2.0
  • Changed: All Presets now default to use maximum available 'B-Picture Pattern' for higher quality at lower bitrates.
  • Changed: All Presets no longer override 'Frame Skipping', 'B-Picture Reference' and 'Custom Buffer'.
  • Changed: 'Twitch', 'YouTube' and 'Recording' Presets no longer override 'Target Bitrate' and 'Peak Bitrate'.
  • Changed: 'Twitch' and 'YouTube' Presets no longer override 'Minimum QP' and 'Maximum QP'. (Always forced to 0/51.)
  • Changed: 'Enforce HRD Compatibility' is now set to disabled for all Presets.
  • Changed: 'Debug Tracing' will now log additional information, it is recommended to disable this for non-test sessions.
  • Added: You can now override Preset parameters instead of having to manually deselect the Preset.
  • Fixed: Potential Crash when quitting OBS directly before the Encoder is completely initialized.

Read the rest of this update entry...
 

ObZidianLP

New Member
Open up an Issue on Github and also report this as a bug to the makers of that software. If it plays fine in Windows Media Player, MPC-HC, VLC or any other decoder but doesn't work in whatever software Vegas Pro is, the issue isn't the plugin.
Thanks for your response and the time you put into answering all these!

I thought that it had to do with Sony Vegas or WMP at first too, but VLC is the only program that can play it back without issues. Sony Vegas, WMP and QuickTime Player all show corruption.

As for the fix that I found, if I convert the recording (doesn't matter what base filetype) to mp4 using VLCs convert/export option, the corruption is fixed. Could this be because it extracts the audio codec and video codec and puts them back together?
 

Xaymar

Active Member
Thanks for your response and the time you put into answering all these!

I thought that it had to do with Sony Vegas or WMP at first too, but VLC is the only program that can play it back without issues. Sony Vegas, WMP and QuickTime Player all show corruption.

As for the fix that I found, if I convert the recording (doesn't matter what base filetype) to mp4 using VLCs convert/export option, the corruption is fixed. Could this be because it extracts the audio codec and video codec and puts them back together?

As I already said, the issue is not in the encoder but with the decoder only accepting one way of muxing a file. 1.3.2.1 and newer slightly help with this by using fixed step timestamps and there will be more fixes to come in the future.

Turns out it's ffmpeg doing that. Should be fixed now-ish.
 
Last edited:

ball2hi

Member
Currently using v1.3.2.2...

Holy shit Xaymar, this is incredible. I don't know how you solved it, but CBR is currently working on Twitch. The quality is incredible even without b-frames since I'm on my rx 480, using the quality preset and 2500 bitrate. I am also currently not crashing so far, but it was just a short test stream (6min 38sec).

Temporary VOD: https://www.twitch.tv/3ybx/v/92966678

I don't know how this quality compares to x264 (too lazy to test side by side right now) but this is beautiful. If the local encoding issue video freeze issues is fixed, I might be able to stream/record my matches in 48 fps now.
 

Xaymar

Active Member
Currently using v1.3.2.2...

Holy shit Xaymar, this is incredible. I don't know how you solved it, but CBR is currently working on Twitch. The quality is incredible even without b-frames since I'm on my rx 480, using the quality preset and 2500 bitrate. I am also currently not crashing so far, but it was just a short test stream (6min 38sec).

Temporary VOD: https://www.twitch.tv/3ybx/v/92966678

I don't know how this quality compares to x264 (too lazy to test side by side right now) but this is beautiful. If the local encoding issue video freeze issues is fixed, I might be able to stream/record my matches in 48 fps now.

Driver 16.9.2 fixed the CBR partially for RX 4xx cards, 16.9.3 will fix even more. And yes, the local recording issue should be fixed, I recorded 1 hour and 16 minutes with it to test it - thrice just to make sure.
 

ball2hi

Member
Driver 16.9.2 fixed the CBR partially for RX 4xx cards, 16.9.3 will fix even more. And yes, the local recording issue should be fixed, I recorded 1 hour and 16 minutes with it to test it - thrice just to make sure.
Unfortunately, my matches can take up to 1 hour 40 minutes so I will have to test something on my own. I was originally using 16.9.2 driver and CBR issue wasn't fixed still up until me testing today.

Also want to note that I am unable to override the profile level on the Twitch preset, I have to remove the Twitch preset and set it to blank in order to set it to "main" which is what I need to maximum transcoding options.

unknown.png
 

Xaymar

Active Member
Unfortunately, my matches can take up to 1 hour 40 minutes so I will have to test something on my own. I was originally using 16.9.2 driver and CBR issue wasn't fixed still up until me testing today.

Also want to note that I am unable to override the profile level on the Twitch preset, I have to remove the Twitch preset and set it to blank in order to set it to "main" which is what I need to maximum transcoding options.

unknown.png

That is the intended behavior until I find a way to make it automatically apply/replace the preset. See patch notes for 1.3.2.0, 1.3.2.1 and 1.3.2.2
 

Xaymar

Active Member
Xaymar updated AMD Advanced Media Framework Encoder Plugin for OBS Studio with a new update entry:

1.3.2.3 - Timestamp fixes and UI Updates

  • Fixed: Latency Constrained Bitrate was incorrectly hiding Target Bitrate option.
  • Fixed: Timestamps now work for all framerate options.
1.3.2.2
  • Removed: Automatic override of Preset, caused more issues than features it added.
  • Fixed: The plugin would initially report an incorrect queue size delta.
1.3.2.1
  • Fixed: Audio desynchronization and video corruption caused by timestamp drifting.
  • Fixed: Fields would be...

Read the rest of this update entry...
 
The B-frames feature isn't working with my R9 290. B-picture Pattern 1-3 makes the image pixelated, but setting it to 0 fixes it. I'm assuming this is because setting B-picture Pattern to 0 disables the use of B-frames, but please correct me here if I'm wrong.

Here is a sample video with B-picture Pattern set to 3 (1 and 2 produce similar results):
https://www.twitch.tv/everyth1ngtv/v/93029772

And here is a sample video with B-picture Pattern set to 0:
https://www.twitch.tv/everyth1ngtv/v/93030078

All of the other settings are set to the Twitch preset settings as of 1.3.2.3.

Also, I'm still getting the skyrocketing bitrate issue where I have to stop and start the stream to get the bitrate to stay on target.
 

Attachments

  • 2016-10-04 17-23-29.txt
    31.4 KB · Views: 37
Status
Not open for further replies.
Top