Audio driver for Realtek HD Audio Hardware? [Testing thread]

[space223]

will this driver work for alc897?

[deomsh]

Hello @space223 , can't say, there are no records of this codec with HDA2.DLL. Did you try already?

[Drew Hoffman]

@deomsh does your universal hdaicout.hda file work for any IDT and VIA HD Audio codecs or only Realtek? I'm looking for hints on what verbs I might be missing for my native WDM HD Audio driver which now works on most Intel chipsets with a Realtek codec but is still silent on IDT and VIA codecs . Unlike the Watler's driver I have a codec node parser if a very basic one taken from a hobbyist OS.

https://msfn.org/board/topic/187713-native-wdm-hd-audio-driver-for-windows-98seme/page/1/

[deomsh]

Hi @Drew Hoffman , didn't expect you in this thread....

I am aware of your project (I am reading MSFN daily). So far I had no time to test your driver, but your project looks promising, in case of Windows 98/ME.

About your question: difficult to say. If you search in this thread for IDT, it seems there is one report, working with some quasi-universal version of HDAICOUT.HDA. But that's a while ago...

I also 'did' one VIA codec (VT1708B) in this thread, additional verbs where needed in that case. But at home I did VT1705 on Asrock N68C-S UCC without.

Somehow Realtek codecs have the 'easiest' architecture, I 'did' a few. ALC66x-ALC88x and ALC1220 have roughly the same nodes and same output pin's Apart from extra's in ALC88x. ALC231/ALC260 are already different. This is in my notes (ment for personal use):

The lines in my quasi-universal version of HDAICOUT.HDA focus on a few nodes/ widgets for power up, open the playback path and to set the DAC and volume to default values. Because there are about max 200 verbs free for sending at once, and because in my approach HDAICOUT.HDA is used sent same verb to all nodes/ widgets, type of verbs is limited. As such this quasi-universal approach is fully 'blind', no intelligence at all (hopefully some in the maker). All based on Intel's High Definition Audio Specification, NOT on specific Realtek codecs.

In most of my versions of HDAICOUT.HDA I have concentrated on output's, but I had plans to make a new version to 'open' input-ampifiers too (mixers). But furthermore ignoring Connection Select will be the price to pay.

So maybe you can play with '35xxx', '36xxx' or L+R combined: '37xxx', just an idea. From my notes:

Set Amplifier Gain	3	Payload(s)
Set Amplifier Gain	3	5	0	8	0		Mute Input Channel 0 R
Set Amplifier Gain	3	5	0	0	0		UnMute Input Channel 0 R
Set Amplifier Gain	3	5	0	7	F		Max Input Volume Channel 0 R
Set Amplifier Gain	3	6	0	8	0		Mute Input Channel 0 L
Set Amplifier Gain	3	6	0	0	0		UnMute Input Channel 0 L
Set Amplifier Gain	3	6	0	7	F		Max Input Volume Channel 0 L
Set Amplifier Gain	3	7	0	8	0		Mute Input Channel 0 R+L
Set Amplifier Gain	3	7	0	0	0		UnMute Input Channel 0 R+L
Set Amplifier Gain	3	7	0	7	F		Max Input Volume Channel 0 R+L
Set Amplifier Gain	3	7	1	7	F		Max Input Volume Channel 1 R+L

But in case of EAPD, Unsollicited Response and GPIO, things are different and often model-specific (laptops). In that case more information is needed. I only did a few codecs/ chipsets, always on a n=1 basis, with help of study of Linux (ALSA)-sources to find appropiate verbs. 

However you have a parser, should make things more easy (Watler delivers a seperate parser too in version L, but his driver does not use a parser as such).

I am willing to help, but I am not a programmer, just an ordinary Joe with more spare time because I am not interested in sports (no offence to readers of this thread ment of course).

Edited 1 hour ago by deomsh
Addition