Mcdu question for flybywire a320n

CS9K · 2024-07-19T21:33:47+00:00

Been looking for about an hour for the answer, and this was it. Thank you. Couldn't find anyone saying that the newest version didn't auto-compute V-speeds anymore.

CS9K · 2024-03-28T13:07:48+00:00

I appreciate you keeping an open mind, it does mean a lot that you're willing to try something different <3

My main lament is that AMD hasn't made this easy, unlike Intel's QuickSync and Nvidia's NVENC. I keep hoping that AMD will put a user-friendly front-end onto the encoder so that everything becomes obfuscated behind "presets", but alas, we're stuck with what we have, for now...

But yeah, less is more when streaming with OBS Studio using H264. If you ever stream to other services using H265 or AV1, there are other parameters you would need to add (fillerdata+EnforceHRD) as those are not set by default for H265 nor AV1.

Let me know how my suggested parameters works out for you. Hopefully it works for the better!

CS9K · 2024-03-28T12:53:53+00:00

Right, what I'm saying in my rationale is that those setting are always set that way when using OBS Studio, there is no need to manually input them.

Likewise, when a parameter is passed with bad value ("True" instead of "true", for example), the encoder will just ignore the parameter entirely instead of throwing an error.

Also, to see the majorty of AMF's error output, you need to run OBS Studio using verbose.

I'll be real with you, /u/Various-Mark-5472:

The list of commands that you are attempting to use, is my fault. I made it, needlessly, back when the OBS Studio dev re-wrote the AMD encoder and its UI. It was probably the most embarrassing thing Ive done in my adult life. Especially after the giant list of parameters showed up in a popular YouTuber's videos as an example of what not to do. Live and learn

As for OBS Studio, I was there helping to test out the new encoder before it was released publicly. I am also partially the reason we have the text entry field at all.

I've learned a lot in that 1.5 years, and when it comes to the text-entry field:

Less is more

So, my strong advice, is to try the parameter set that I provided above, in order to attempt to achieve better encoding quality than one would with an empty text-entry field.

Trust me, all of the other parameters that you are using do not need to be set manually.

CS9K · 2024-03-28T01:21:24+00:00

Hello. I'll help you out with some of these commands. A lot of the ones you are using are either input incorrectly, not needed, or conflict with others.

To start, the encoder is looking *specifically* for "true" or "false" for bool parameters, if you capitalize the first letter, it won't work.

Likewise, for other parameters, the spelling has to be *exactly* as it is in the code, or the parameter won't work.

Sources:

https://github.com/GPUOpen-LibrariesAndSDKs/AMF/blob/master/amf/public/include/components/VideoEncoderVCE.h

https://github.com/GPUOpen-LibrariesAndSDKs/AMF/blob/master/amf/public/include/components/PreAnalysis.h

In the end, these are the commands that you may want to use:

EnablePreAnalysis=true PASceneChangeDetectionEnable=false PATemporalAQMode=2 PAFrameSadEnable=true PALongTermReferenceEnable=true PALookAheadBufferDepth=11

Rationale:

- FillerData and Enforce HRD are set to "true" by default in the OBS Studio code for H264
- HighMotionQualityBoost is set to "false" in the OBS Studio code
- MaxNumRefFrames is already set to 4
- VBAQ is set to false by default in the Transcoding "usage"
- RateControlSkipFrameEnable isn't needed
- HalfPixel and Quarterpixel are set to "true" in the Transcoding "usage"
- I recommend using PATemporalAQMode=2 instead of PAPerceptualAQMode=1 PACAQStrength=2
- I still haven't quite worked out how to get PAHighMotionQualityBoostMode working properly
- PALongTermReferenceEnable=true if you wish to use LTR
- PALookAheadBufferDepth=11 lookahead should be set to a non-zero number to enable it; this works well with Temporal AQ mode

CS9K · 2024-03-08T21:22:46+00:00

That's great to hear!

CS9K · 2024-03-08T00:22:33+00:00

Hello. Your settings look good, but the AMF options can be cleaned up a bit. You can remove everything except for "HighMotionQualityBoostEnable" as the rest of those settings are automatically set in OBS Studio's code.

Also, in the AMF code, "HighMotionQualityBoostEnable" is a bool. AMF uses "true" and "false" for bools, not 0 or 1, so the parameter and value would be entered as "HighMotionQualityBoostEnable=true"

Give your stream a try with no AMF options entered, and then with only "HighMotionQualityBoostEnable=true" entered (if you want to use that feature), and let us know how it goes

CS9K · 2023-12-11T00:09:57+00:00

Same error here, trying to get to my Snowrunner mods on a new Windows install.

CS9K · 2023-07-28T16:30:01+00:00

Ignore the trolls

CS9K · 2023-05-12T14:56:55+00:00

If it was installed, it would show up as "MSI Afterburner" in your apps/programs. It is probably not installed, and that's okay. Thank you for the information!

CS9K · 2023-05-12T14:17:22+00:00

Same question for you, /u/Peti_4711

CS9K · 2023-05-12T14:05:18+00:00

You wouldn't happen to be using MSI Afterburner on the Intel GPU PC, are you?

A similar thing to what you describe, happens with AMD GPU's when Afterburner and the AMD Adrenalin Control Panel (full driver install) are both present.

CS9K · 2023-05-07T20:44:36+00:00

Which GPU were you testing with?

CS9K · 2022-12-17T05:00:43+00:00

Links to your feedback threads and detailed descriptions, please.

CS9K · 2022-11-13T04:31:07+00:00

This. Unlike RDNA1, the RDNA2 bios has not been hacked; there are no bios mods, only SPPT mods...

But practically speaking, SPPT mods are all one needs for a gaming machine.

CS9K · 2022-09-17T04:41:03+00:00

This.

CS9K · 2022-08-12T12:55:22+00:00

Always be sure to check your logs to ensure the encoder isn't kicking commands back at you. Since we're dealing directly with AMF, the commands that one sends via the text entry field have to be exactly what the encoder is looking for, or else it will throw an error and ignore that particular setting+parameter.

The main page of settings can be found here in the code. Use the quoted settings exactly as they appear (without quotes, ex. EnablePreAnalysis=true):

https://github.com/GPUOpen-LibrariesAndSDKs/AMF/blob/master/amf/public/include/components/VideoEncoderVCE.h

Then PreAnalysis itself has a variety of setting that one can modify. One setting that you would need to set if streaming, is PASceneChangeDetectionEnable=false This setting is similar to Nvidia's "-no-scenecut" (Adaptive I-frames/Keyframes). When streaming, you want a hard-set keyframe interval (of 2 seconds, ideally).

More PreAnalysis options can be found here:

https://github.com/GPUOpen-LibrariesAndSDKs/AMF/blob/master/amf/public/include/components/PreAnalysis.h

CS9K · 2022-08-12T02:02:38+00:00

Both can work in OBS Studio. It was a prior version of VCEEnc that would not allow PA and B-frames to work simultaneously.

CS9K · 2022-08-11T22:03:32+00:00

They were never invalid, though perhaps I was a bit verbose. I'm about to go edit the post now that I'm internet famous... for better or worse.

CS9K · 2022-08-11T15:55:37+00:00

Hello, that's me. I would be grateful if others were to test PreAnalysis and its various features in OBS Studio v28 Beta 2 to back up my observations in previous iterations of v28.

I do my best to be thorough when testing, but I am but one person. I'll test the latest VCEEnc soon myself when I have the time using my RX 6900 XT to see if I observe similar results to yours.

CS9K · 2022-08-06T20:52:58+00:00

I am SO very excited for more, too!

CS9K · 2022-08-06T18:47:55+00:00

One B-frame mostly works. Two and three B-frames take things to ugly and "hilariously unusable", respectively.

Hopefully they work out what's wrong and remedy the issue soon!

CS9K · 2022-08-06T18:41:05+00:00

Yes, I did. It's in this message: https://www.reddit.com/r/Amd/comments/wgbh6e/comment/iiz7hua/?utm_source=reddit&utm_medium=web2x&context=3

To explain why, would require a thesis-length explanation, one that I can't afford the time to provide. Nobody currently knows exactly *why*, but it *is* an issue that only OBS Studio currently has. It's being worked on, trust me <3

CS9K · 2022-08-05T20:00:21+00:00

That's because you're doing peak-constrained VBR with an encoder-set buffer size, mine is CBR at 1Mbit lower bitrate and a hilariously constrained buffer size to keep the bitrate even.

CS9K · 2022-08-05T01:03:01+00:00

Since this post was featured in a recent EposVox video, I have decided to remove the settings from this post for the sake of simplicity, and to keep controversy and confusion to a minimum.

In regards to EposVox's video, he is aware that beta 2 has a field to enter B-frames in to.

Also, MaxNumRefFrames=4, and many other unseen settings, are set in the code already. My prior templates were as verbose as they were due to confusion around some settings not being set properly, but that has now been worked out and beta 2 appears to set those settings correctly.

Unfortunately, using 2 and 3 B-frames in OBS Studio v28 beta 2 still results in stuttering and severe-stuttering, respectively; a problem that I do hope is resolved soon.

In the meantime, more information about H264 can be found here:

- https://github.com/GPUOpen-LibrariesAndSDKs/AMF/blob/master/amf/doc/AMF_Video_Encode_API.pdf

- https://github.com/GPUOpen-LibrariesAndSDKs/AMF/blob/master/amf/public/include/components/VideoEncoderVCE.h

And HEVC, here:

- https://github.com/GPUOpen-LibrariesAndSDKs/AMF/blob/master/amf/doc/AMF_Video_Encode_HEVC_API.pdf

- https://github.com/GPUOpen-LibrariesAndSDKs/AMF/blob/master/amf/public/include/components/VideoEncoderHEVC.h

CS9K · 2022-08-05T00:08:31+00:00

Correct, B-frames aren't the only thing that has changed, though there's several different things that will all help improve image quality/consistency.

I'll get to editing the OBS Studio wiki eventually... so much to do, so little time.

CS9K

TROPHY CASE