Status
Not open for further replies.

Pinky

New Member
Either OBS or the Plugin (or both) arent playing nicely with these versions.

In the presets I managed to record using 'recording' preset but if I change to 'high quality' clicking start recording does absolutely nothing.

I am genuinely surprised how much bother these new versions are giving me when the previous versions had none of these issues.
 
I'm having a similar problem to Pinky, though I've nailed it down to CQP. I can record with the AMF encoder if I use VBR (Latency Constrained) or Recording preset, as well as CBR, but not CQP (high quality preset).

Using OBS Studio 0.16.4, Crimson 16.11.2, and an R9 380

Log: https://gist.github.com/bcb1fc7a23a99b64916443681b9fd669

I'm not sure if it's strictly OBS, strictly AMF encoder, or a blend of both. I did make a post in Windows Support about a separate problem (settings not saving), but figured I should post here about the CQP issue. I'm very sorry if I should've posted this in Windows support as well.

I also would like to say how grateful I am for your work on the AMF encoder. I'm not able to recording smoothly on my processor, so being able to use the AMF encoder is a lifesaver. Really, thank you.

Edit: Would a post in the issue tracker be more helpful?

Edit 2: Another log, has working CBR recording
https://gist.github.com/c36efe783e34478b396d5c5afc8bb166
Also, not strictly related to the AMF encoder, but changes to settings aren't (always?) showing for me. In that log, it shows I recorded with CBR. But I checked Settings immediately after stopping recording and OBS is showing Rate Control Method as CQP, along with the CQP settings.
 
Last edited:

Xaymar

Active Member
Xaymar after much fiddling it appears that obs is fine and this only occurs when 'use opencl' is set to 'enabled'.

That's strange and worrying then. OpenCL doesn't link to any av*.dll files, it links to opencl.dll and that doesn't actually fail on your system. Could you put a check in the "Debug" option and upload a log where it crashes with a crash log?

Either OBS or the Plugin (or both) arent playing nicely with these versions.

In the presets I managed to record using 'recording' preset but if I change to 'high quality' clicking start recording does absolutely nothing.

I am genuinely surprised how much bother these new versions are giving me when the previous versions had none of these issues.

CQP is broken, I'm working on it.

I'm having a similar problem to Pinky, though I've nailed it down to CQP. I can record with the AMF encoder if I use VBR (Latency Constrained) or Recording preset, as well as CBR, but not CQP (high quality preset).

Using OBS Studio 0.16.4, Crimson 16.11.2, and an R9 380

Log: https://gist.github.com/bcb1fc7a23a99b64916443681b9fd669

I'm not sure if it's strictly OBS, strictly AMF encoder, or a blend of both. I did make a post in Windows Support about a separate problem (settings not saving), but figured I should post here about the CQP issue. I'm very sorry if I should've posted this in Windows support as well.

I also would like to say how grateful I am for your work on the AMF encoder. I'm not able to recording smoothly on my processor, so being able to use the AMF encoder is a lifesaver. Really, thank you.

Edit: Would a post in the issue tracker be more helpful?

Edit 2: Another log, has working CBR recording
https://gist.github.com/c36efe783e34478b396d5c5afc8bb166
Also, not strictly related to the AMF encoder, but changes to settings aren't (always?) showing for me. In that log, it shows I recorded with CBR. But I checked Settings immediately after stopping recording and OBS is showing Rate Control Method as CQP, along with the CQP settings.

CQP is already known as broken, I have it fixed in the repository already.
 

Pinky

New Member
Thanks Xaymar I will try to get some time to do that but dont forget its not crashing, just immediately stops recording and throws an error.

Im also seeing some settings not saving as Commander Matt mentioned.
 

Xaymar

Active Member
Thanks Xaymar I will try to get some time to do that but dont forget its not crashing, just immediately stops recording and throws an error.

Im also seeing some settings not saving as Commander Matt mentioned.

If you have a Preset selected, it will override most of your settings for values in the preset instead. That is by design, it's what the word preset stands for. :P
 

Pinky

New Member
heheh that's fine, I had assumed I could select a preset then edit it and save it as I liked.

I can't get the recorder to start again, tried loads of presets and the errors keep popping up. Have attached a log that has some debug entries. I tried with memory type set to host but I still can't get it to work.

I had it working last night for a while but can't get it working today.

I did notice this in the debug log:

14:06:26.338: [ffmpeg muxer: 'adv_file_output'] os_process_pipe_write for packet data failed
14:06:26.338: [ffmpeg muxer: 'adv_file_output'] Output of file 'Z:/Recordings/2016-11-05 14-06-23.flv' stopped

Maybe the opencl is a red herring, if it is I apologise but it seemed to do the trick last night.

Not easy trying to get time to look at this properly with 3 kids running round my feet :/
 

Attachments

  • log1.txt
    273.8 KB · Views: 26

Xaymar

Active Member
heheh that's fine, I had assumed I could select a preset then edit it and save it as I liked.

I can't get the recorder to start again, tried loads of presets and the errors keep popping up. Have attached a log that has some debug entries. I tried with memory type set to host but I still can't get it to work.

I had it working last night for a while but can't get it working today.

I did notice this in the debug log:

14:06:26.338: [ffmpeg muxer: 'adv_file_output'] os_process_pipe_write for packet data failed
14:06:26.338: [ffmpeg muxer: 'adv_file_output'] Output of file 'Z:/Recordings/2016-11-05 14-06-23.flv' stopped

Maybe the opencl is a red herring, if it is I apologise but it seemed to do the trick last night.

Not easy trying to get time to look at this properly with 3 kids running round my feet :/

Still the same ffmpeg issue, the encoder started and stopped properly in the log. Something is somehow messing with your setup and disallowing the ffmpeg muxer from working.
 
CQP is already known as broken, I have it fixed in the repository already.
Okay, thank you very much! Sorry to repeat what you already knew. Is there anywhere I could've checked to find out you already knew about it?

Also:
If you have a Preset selected, it will override most of your settings for values in the preset instead. That is by design, it's what the word preset stands for. :P
I feel very, very silly for not realizing this x_x
 

Xaymar

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

1.4.1.1 - The Oversight Fix (Part 2)

Another update but this time it's much smaller, it fixes the problem with Constant QP and Automatic Profile Level.

Notes
Due to the nature of changes in this update, your previous settings may end up lost or incorrect. Make sure to revalidate them before attempting to record or stream.

Changelog
  • Fixed: Automatic Profile Level will no longer always pick '4.1'.
  • Fixed: Constant QP should now work properly again.
  • Fixed: Plugin should...

Read the rest of this update entry...
 
@Xaymar, I'm glad to see that you made a post on r/amd regarding CBR ignoring settings. I'm definitely still experiencing that issue. Stopping and starting the stream still seems to work to reign in the bitrate to what is specified, but it's annoying to have to deal with that.
 
Last edited:

Xaymar

Active Member
Will you push 1.4.1.2 for OBS 0.16.5 (I saw 16.5 on github) ?!

No, 1.4.1.2 isn't completely ready yet.

@Xaymar, I'm glad to see that you made a post on r/amd regarding CBR ignoring settings. I'm definitely still experiencing that issue. Stopping and starting the stream still seems to work to reign in the bitrate to what is specified, but it's annoying to have to deal with that.

I hope that things can be figured out with Mikhails help, this seems to affect everyone on VCE3 and newer cards.
 

i670120

New Member
Hi,

I was just wondering if there was anyway to overcome the problems with AMF in Source games? In non-Source games I can stream at 720p/30@3000 and have it be smooth, but in Source games streaming at 720p/30@3000 I will get massive stuttering and will start dropping towards 90% frames.

Or is this something that can't be overcome and should switch to x264 when I stream Source games ?
 

SogeHige

Member
I have same CBR issue with A10-7850k and 16.9.2 drivers.

I noticed that when I start streaming with image and audio (intro), bitrate is 500-700kbps, but after scene change to gameplay it ups to 4000+.

If I start streaming only on gameplay, my selected bitrate is holding on selected 2500. Not sure if it helps or not.
 

ball2hi

Member
Hi,

I was just wondering if there was anyway to overcome the problems with AMF in Source games? In non-Source games I can stream at 720p/30@3000 and have it be smooth, but in Source games streaming at 720p/30@3000 I will get massive stuttering and will start dropping towards 90% frames.

Or is this something that can't be overcome and should switch to x264 when I stream Source games ?
Do you have frame skipping enabled? What are your settings?
 

i670120

New Member
Do you have frame skipping enabled? What are your settings?

Would frame skipping be the problem? Also I have fresh install default settings, minus changing bitrate from 3500 to 3000, setting Quality preset and disabling B-Frames (I use an APU).

Like I said, I only have issues in Source based games where the game itself would stutter pretty heavily and I would be dropping frames really bad in OBS.
 

Xaymar

Active Member
Would frame skipping be the problem? Also I have fresh install default settings, minus changing bitrate from 3500 to 3000, setting Quality preset and disabling B-Frames (I use an APU).

Like I said, I only have issues in Source based games where the game itself would stutter pretty heavily and I would be dropping frames really bad in OBS.

Frame Skipping is an encoder flag that is used to "drop" frames if it can't keep a given bitrate. Your issue sounds like the game somehow also uses the encoding/decoding unit on the GPU for something.
 
Status
Not open for further replies.
Top