AMD New Release 22.10.3 & Realtek ALC1200-TOSLINK

Yelandkeil wrote on 10/29/2022, 7:12 AM

Finally somewhat refreshing goody from AMD since almost half a year!

The performance in VEGAS is raised well noticeable, both by HDR and SDR projects.

And watching 4k/8k videos no problem as usual.
Annoying is HDR-video to play back.
A new start or switch between full/windowed screen, even move the player from one display to the next, it suddenly bursts black-out, one or 2-3 times, it happens too when opening some HDR-projects in VEGAS.

Of the new release it's a hard enforcing that you must turn off the "10bit pixel format" if you use HDR-display; otherwise no WCG-management in Windows10.

I think this is the reason for the crazy black-out.

In addition, my RX6900XT likes "Rage" instead of "Overclock", VEGAS-performance dislikes the "SmartAccess Memory" which is only profitable for gaming.

The Windows HD color setup should not be a problem for everyone.

I've organized an LG surround-soundbar with Dolby/DTS, no "Hello Siri" or such bullsh*t (original wish JBL but too exp).
A modified AAFOptimusDCHAudioPack for the on-board-chip ALC1200 is very beliebt by me.

Hence the recommendation.

Comments

Cielspacing wrote on 10/29/2022, 12:32 PM

Interesting. This post appears to come with several useful recommendations, however my command of English or my ability to extract those from OP's message, seems incompetent.
Would someone help with a translation?

walter-i. wrote on 10/29/2022, 2:23 PM

You would have to tell us what language you want.

Yelandkeil wrote on 10/29/2022, 3:27 PM

@Cielspacing, pardon me for my jump-to-conclusion introduction. It's not because of your English but you didn't follow the topic of AMD's driver versions.

1, the new release has been improved and solved problems like invert color preview in VEGAS.
2, it has handed totally its 10-bit color management over to Windows system; thus you'd be aware and go shut down that 10-bit activation else your HDR-display will not work.
3, personal observation: it seems the improvement sucks huge energy!
With driver 22.5.1, my RX6900XT takes only 5-8 Watt power in idle with 34-36°C, but now it's keeping alarm RED all time with about 30Wat/45-48°C.
I'll wait for 22.11.1-release. If it's still so power hungry, I'll back to 22.5.1.

About the patched on-board-audio driver I think you only need it when you connect 5.1-sound device through TOSLINK.

I downloaded it and forgot from where, but you can google/edge, e.g. to this one:

https://github.com/AlanFinotty/AAFOptimusDCHAudio-Generic/releases

Cielspacing wrote on 10/30/2022, 5:36 AM

Thank you Yelandkeil. I am usually happy and welcome AMD updates, so after reading your initial post went ahead and applied this optional update. Turns out, have to be wary of power usage since my gaming laptop sips its battery life quite fast if left unattended... Happily, it allows switching to integrated GPU (if restarted).

Now, with your detailed 2nd post, am getting a much clearer view of your experience with recent AMD drivers. You give precise info there.
Again, thanks for that. I'll remain attentive.

Yelandkeil wrote on 10/30/2022, 8:25 AM

Thank you @Cielspacing!
It's an honor to chat with you.

As saw your first response, I knew that's a kind elevating irony, not language incompetence at all.
Noble and cold-blooded.

But be tender and patient to us the non-english native speakers! Every time I write something, I must look up in dictionary frequently and translate my thought into Pidgin-English.

If the conversation were in Chinese, I'll charge you so embarrassed crying in a remote corner! 😄😄
OK, joke aside.
Our common target is VEGAS and its peripheries. Confronting with confusion, then list questions as:
Answwer me please
1,...
2,...
3,...

Let's remain attentive to the AMD-Releases.
Cheers.

Cielspacing wrote on 10/30/2022, 12:21 PM

Yelandkeil. We are together on handling English as a 2nd language here.
I became interested in your focused review of AMD's new optional driver, detailed and bringing specific advice in your first post. However, I wasn't able to take advantage of it because of the way it was worded.

Something similar had happened to me before. There is this forum where users from all places contribute and a particularly competent user posts regularly providing all kinds of detail and ideas. Every time I read his posts could guess there was valuable content in it, however it was impossible for me to understand its exact content. Amazingly Attila the main developer and very gentle forum administrator always got every little detail and very often build upon his advice.

So, I hold the belief there might be fellow forumites who understand unexpected English language much better than me and genuinely ask for help when that happens. I wasn't asking for you Yelandkeil to rewrite your post. You did it, great! and I welcome it.

About AMD driver updates, some of us have been commenting on them in this forum at specific issues threads, like this one where we commented up to 22.10.2 version released at 10/21/2022

Yelandkeil wrote on 10/31/2022, 2:58 AM

Additional experience:

I have two HDR10 displays.
If I open an VEGAS 8-bit full range project and use external preview, the 2nd monitor stays dimmed after I close VEGAS/my editing session.

I must deactivate and reactivate the HDR button in Windows color management to get back the normal view.

Lost patience to the AMD stories and returned to 22.5.1

For your info guys!

Wolfgang S. wrote on 10/31/2022, 6:23 AM

And watching 4k/8k videos no problem as usual.

Annoying is playback of HDR-video.

Checking the preview speed, to have about 30 fps for an UHD 60p project seems to be not bad to me. At least not for Vegas, and an ACES transformation in work. I wonder, if it would help a little bit to set the preview quality from good(half) to preview (half)?

The footage is a long-GOP footage? Because, here the GPU improvement in the preview speed works great anyway. If you try that for all-i, then the GPU improvement is weaker maybe.

Yelandkeil wrote on 10/31/2022, 7:48 AM

Your citation is not accurate (the words are about video-player, not timeline playback in VEGAS) @Wolfgang S.

VEGAS timeline:

I use invariably only Good/Half in preview, It's proper quality for judging footage (fps/motion smooth or jerky, interlace/deinterlace clean or ghostly, image noisy?...); it loses such abilities in Preview/Draft.
I cut and edit in 8-bit pixel mode, normally full project speed; if not, I use swapping, no proxy.
Changing into HDR10 mode, events are carrying FX(s) and swapped back to original, playback speed only in few fps if not in dots, dots and dots; here is the job color grading.
The HDR speed in your observation happens only by testing, without any plugins or add-ons; it's ProRes footage, usually, X-AVC (long-GOP?) also friendly.
Anyway, AMD CPU+GPU, yes!

Yelandkeil wrote on 10/31/2022, 8:03 AM

@Cielspacing, I overlooked we've already met each other in that post, so, quasi old friends, are we!?

What's your mother-tongue? Hawaiish full of sun beam and sand beach?

Where have you got your grammar for such beautiful sentence:

We are together on handling English as a 2nd language here.

Wolfgang S. wrote on 10/31/2022, 8:31 AM

Your citation is not accurate (the words are about video-player, not timeline playback in VEGAS) @Wolfgang S.

"Annoying is playback of HDR-video in external media player" would have been easier to understand for me.

And I am not sure if I understand why one should loose the ability to judge footage in preview/draft in a general way? Even with your 16 core processor it seems to be necessary to switch your workflow between the 32bit mode, and the 8bit mode. I understand why you do so - to avoid a low number of frames in the Vegas preview. But that is where preview/half would also help. At least I see no huge difference if you scale down the preview from UHD 60p to 720 30p. We have different solutions for that in Vegas, but each of the solutions are a compromise.

But on my machine with 24 cores that is not better really. I also see that the preview in Vegas could be better, and it is sad to hear that this is not only true for my nvidia 3080 Ti 12GB, but also for your hardware.

Yelandkeil wrote on 10/31/2022, 8:50 AM

Preview/Draft will not deinterlace your timeline view no matter what you've set in your project.

And watching 4k/8k videos no problem as usual.

Annoying is playback of HDR-video.

I think watching (TV) already indicated it's a media-player. 😍😍 anyway, a minor case.

Apropos HDR-color grading.
I appreciate the CGP so much for my last process. Its appendix into the plugin-chain doesn't interfere my performance made in the 8-bit modus.
My sincere thanks to the develop-TEAM!

Yelandkeil wrote on 10/31/2022, 9:24 AM

At least I see no huge difference if you scale down the preview from UHD 60p to 720 30p.

On my 2 UHD-displays, it's very huge -> unbearable.

Wolfgang S. wrote on 10/31/2022, 10:12 AM

I have not read the word "TV" there. And watching... well.

And why do you think, that deinterlacing is still so important - since we shoot progressive footage today in most cases? I do not even remember, when I have shooted interlaced last time.

The color grade portal is a very huge increase in Vegas - no question. I like it too.

But I really wonder about grading HDR footage in 8bit. I have tried that long time ago, must be around Vegas Pro 17 or so. That was long before the CGP and the improve in ACES. So maybe I test the grading of HDR footage in 8bit again?

Yelandkeil wrote on 10/31/2022, 10:29 AM

1, family DV-AVIs etc. from yesterday.

2, will create another post for 8-bit grading or so, tomorrow?

(übrigens, Du bist Österreicher, nicht wahr?)

Wolfgang S. wrote on 11/1/2022, 2:48 PM

Ja, ich bin Österreicher. Aber derzeit international unterwegs.

Yelandkeil wrote on 11/2/2022, 12:38 AM

Hallo @Wolfgang S., Problem ist, Du findest keine richtige LUTabelle für das HDR-Material zum Einsatz im 8-bit-Pixel oder 32-bit-Gleitkommazahl Format.

Meiner Erfahrung nach benutze ich die V-Log-Tabelle als universale Richtschnur.
Die REDLog-Tabelle scheint auch vielsagend.

illustr. V-Log-LUT, CGP-Lift-Gain-HSL

illustr. REDLog-LUT

Ich hab meine neue Post "Why Footage in 10bit 12bit Log or RAW" hochgeladen, falls Du Zeit und Lust hast, kannst mal schnell blättern.

Wolfgang S. wrote on 11/2/2022, 1:08 AM

Von welcher Kamera ist denn das log Material?

Yelandkeil wrote on 11/2/2022, 1:22 AM

Nicht verstanden, welche Log-Material?

Wenn die Blumenszene gemeint, es kommt aus HDR10-video (YouTube), gerendert in VEGAS.

Detail-Parameter:

Wolfgang S. wrote on 11/2/2022, 2:47 AM

Hallo @Wolfgang S., Problem ist, Du findest keine richtige LUTabelle für das HDR-Material zum Einsatz im 8-bit-Pixel oder 32-bit-Gleitkommazahl Format.

Ich verstehe das noch nicht. Es gibt sehr wohl LUTs für vlog zu rec709. Du filmst doch mit einer Kamera?

https://na.panasonic.com/us/resource-center/v-log-v-709-3d-lut

Yelandkeil wrote on 11/2/2022, 3:13 AM

Tsja, wenn ich mit bestimmter Kamera erfasse dann weiß ich wohl welche LUT zu nehmen.

Problem is wenn das Material aus unbekannter Quelle oder mit zu allgemeinen Parameters, was tun?
z.B. ein HDR10-clip.

Aaach! Ich begreife jetzt, Du betrachtest Log-File als HDR-Material; meiner Meinung nach, nicht ganz.

Yelandkeil wrote on 11/2/2022, 3:19 AM

Oder genauer, findest Du eine LUT die den Rec2020-ST2084-Farbraum in den Rec709/sRGB-Raum konvertieren kann?

Wolfgang S. wrote on 11/2/2022, 3:32 AM

Log Material ist natürlich auch HDR-Material, da es mehr als die 7 Blendenstufen umfasst. Es hast allerdings eine andere Gamma-Kurve als PQ oder HLG, das stimmt natürlich.

Bei einer unbekannten Quelle ist es schwer, eine Input-Transformation anzugeben. Egal, mit welchem Werkzeug. Ein HDR10 clip müsste allerdings PQ sein. Und ich meine mich zu erinnern, dass es auch dafür Einstellmöglichkeiten in Vegas gab (aber ich habe derzeit hier kein Vegas, kann das nicht probieren).

Luts zur Wandlung des Gamuts vom Farbraum rec2020 zum Farbraum rec709 gab es irgendwo. Eventuell von Alister Chapman zum Wandeln des Farbraums von HLG (rec2020) zu HLG(mit rec709).

Yelandkeil wrote on 11/2/2022, 4:00 AM

Bei einer unbekannten Quelle ist es schwer, eine Input-Transformation anzugeben. Egal, mit welchem Werkzeug. Ein HDR10 clip müsste allerdings PQ sein. Und ich meine mich zu erinnern, dass es auch dafür Einstellmöglichkeiten in Vegas gab (aber ich habe derzeit hier kein Vegas, kann das nicht probieren).

Sei bitte nicht beleidigt:

Input-LUT ist aller großer Farbraum zu dem einzigen kleinen Rec709-Raum zu transkodieren um das Rec709-Produkt zu rendern, klare Einbahnstraße.

Input-Device-Transform ist aller groß/kleiner Farbraum zu dem (virtuellen) ACES/AP0/AP1-Raum zu transformieren, es kommt noch ODT-Rendern; quasi Autobahn aller Richtungen.