AMD Hardware Encoder(s) [Deleted]

Status
Not open for further replies.
locodicegr

locodicegr

Member
I saw the convestation in the github between you and mikhailAMD,
its a good thing that he helps you...hope the testing is going well.
Thanks for your hard work you putting on this..
 
ball2hi

ball2hi

Member
Xaymar said:
I hope that 1.3.0rc3 reduces how often it happens, I still haven't been able to reproduce it completely stopping returning anything. :/
Click to expand...
Not sure how to install from Github so I'll wait for a pre-made installer posted here. I saw this in your rc3 patchnotes:
Code: 
* Changed: Encoder will now drop frames instead of closing if the input queue grows too large.
I do hope it doesn't happen too often as it would suck to have a bunch of dropped frames during action, or cause an entire second or few to disappear. I probably have about one or two weeks until the tournament starts. Can't wait to test it.
 
Xaymar

Xaymar

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

1.3.0rc3 - The AMF SDK Path

  • Changed: Shared Encoder now initializes DirectX and OpenCL devices internally.
  • Changed: Always force NV12 color format for now, since other color formats are too slow.
  • Changed: Encoder will now drop frames instead of closing if the input queue grows too large.
  • Updated: Simple Interface Presets for Recording and Streaming.
  • Updated: Languages en-US (American English).
  • Fixed: Plugin should no longer crash on shut down due to requesting to join a terminated thread.
  • Fixed: Memory Leak when stopping streaming and/or recording.
  • Fixed: 'Enforce Streaming Service Settings' no longer applies permanently.
Click to expand...

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

Xaymar

Active Member
ball2hi said:
Not sure how to install from Github so I'll wait for a pre-made installer posted here. I saw this in your rc3 patchnotes:
Code: 
* Changed: Encoder will now drop frames instead of closing if the input queue grows too large.
I do hope it doesn't happen too often as it would suck to have a bunch of dropped frames during action, or cause an entire second or few to disappear. I probably have about one or two weeks until the tournament starts. Can't wait to test it.
Click to expand...

Let's hope that I can figure out how to solve an issue that doesn't make sense and that 16.9.2 hits fast.
 
ball2hi

ball2hi

Member
@Xaymar
I just tested the new version rc3 streaming + recording. I regret to inform you that it did not solve the issue and my local-recording got stuck frozen after a while. Here is an OBS log:
https://gist.github.com/d5455b8ce71fe9347815a9d81818f789

Do you know if perhaps this may be related to the refresh rate of my monitor, or perhaps that I have two monitors? I have two separate monitors in Win7 that are both 60hz, and I have my main one I use for gaming overclocked to 70hz.

EDIT: Also had some weird bug that I'm not able to reproduce atm. For some reason my fan-speed got locked at max (5050 RPM) until I restarted. Haven't modified drivers yet, just updated this plugin. Will keep on the lookout for it to happen again.
 
Last edited:
V

vapeahoy

Member
As single 0.01 pixel clock too much can be enough to tilt things off. If the monitor is unstable at responding to clock between it's components at critical juncture, random stuff will happen.
 
Xaymar

Xaymar

Active Member
ball2hi said:
@Xaymar
I just tested the new version rc3 streaming + recording. I regret to inform you that it did not solve the issue and my local-recording got stuck frozen after a while. Here is an OBS log:
https://gist.github.com/d5455b8ce71fe9347815a9d81818f789

Do you know if perhaps this may be related to the refresh rate of my monitor, or perhaps that I have two monitors? I have two separate monitors in Win7 that are both 60hz, and I have my main one I use for gaming overclocked to 70hz.
Click to expand...

Refresh rate shouldn't matter, since I can reproduce a similar issue but it doesn't really make sense. I'm currently trying to reproduce the complete stop while encoding with a debugger attached, at 43:02 right now without any issues.

Have you tried recording at a higher resolution yet? It could be a bug for that exact resolution, since 540p is not really a normal resolution. 360p, 480p, 720p and 1080p are the most used ones at the moment.

Edit: 58:08 now, no issues.
Edit: 1:05:04 now, still nothing.
 
Last edited:
ball2hi

ball2hi

Member
Xaymar said:
Refresh rate shouldn't matter, since I can reproduce a similar issue but it doesn't really make sense. I'm currently trying to reproduce the complete stop while encoding with a debugger attached, at 43:02 right now without any issues.

Have you tried recording at a higher resolution yet? It could be a bug for that exact resolution, since 540p is not really a normal resolution. 360p, 480p, 720p and 1080p are the most used ones at the moment.

Edit: 58:08 now, no issues.
Edit: 1:05:04 now, still nothing.
Click to expand...
I stream and record in different resolutions/encoders. My stream is 540p, my recording is 720p(no downscale). I just recently lowered my graphic's card's settings to factory default since it was overclocked by the manufacturer. I will test later today to see if I get the same issue. I am still waiting for the new driver updates though because not having CBR really sucks since my bitrate keeps going all over the place.

I use H.264 (Your plugin) for both encodings. However recently I've been having to use x264 Ultrafast for local since I keep getting those corrupted recordings. I'm not sure what to do about my stream though because it gets very pixely due to dropping to 140 kb/s.

I've also tried just local encoding (no stream). it would still happen even though it's the only encoder running.
 
Last edited:
Xaymar

Xaymar

Active Member
ball2hi said:
I stream and record in different resolutions/encoders. My stream is 540p, my recording is 720p(no downscale). I just recently lowered my graphic's card's settings to factory default since it was overclocked by the manufacturer. I will test later today to see if I get the same issue. I am still waiting for the new driver updates though because not having CBR really sucks since my bitrate keeps going all over the place.

I use H.264 (Your plugin) for both encodings. However recently I've been having to use x264 Ultrafast for local since I keep getting those corrupted recordings. I'm not sure what to do about my stream though because it gets very pixely due to dropping to 140 kb/s.
Click to expand...

Right, I have a recording where it seems to have happened now. Seeking only works fast up until 0:16:13 and then it takes ages to seek in the file - also bitrate drops as low as 40kbit/s. After that, the timestamp is permanently at 2:22:02, which is the end of the file. Also can only be played back in VLC, so a remux with ffmpeg might be needed.

Edit: File is not recoverable, there is about 20:48 total written data - explains the low file size.
 
Last edited:
ball2hi

ball2hi

Member
Xaymar said:
Right, I have a recording where it seems to have happened now. Seeking only works fast up until 0:16:13 and then it takes ages to seek in the file - also bitrate drops as low as 40kbit/s. After that, the timestamp is permanently at 2:22:02, which is the end of the file. Also can only be played back in VLC, so a remux with ffmpeg might be needed.

Edit: File is not recoverable, there is about 20:48 total written data - explains the low file size.
Click to expand...
Yup, sounds exactly like my problem.

I thank you for all this hard work and trouble you are going through to help better the encoder for us. I do wish AMD was a lot more stable in their releases and such.
 
Last edited:
Xaymar

Xaymar

Active Member
locodicegr said:
How is it going @Xaymar do you reproduse those problems?
Or are you waiting for some driver update to fix some of those bugs.
Cheers!
Click to expand...

I've reported all of them to AMD, there is not much I can do now. I have an experimental version that fixes some things but makes another issue happen a lot more often than normal...
 
Xaymar

Xaymar

Active Member
Last edited:
Xaymar

Xaymar

Active Member
ball2hi said:
Uninstalled and currently using the most up to date version RC 4. I am unable to stream/record right now as my OBS instantly crashes. Here is a log:

https://gist.github.com/f358c76d6279a2527f2ee2d7a2438245

Here is a crash log I managed to snag before the entire program locked up on me, as it was refusing to let me click the crash log option: http://pastebin.com/cUnGwHpJ
Click to expand...

Looks to me like DirectX 11 failed to initialize, this can have many reasons. Broken drivers, missing GPU support or even a corrupt operating system.
 
Status
Not open for further replies.
Top