isolar

Awesome thanks for clarifying the settings from HDAConfig.ini, that makes more sense now. I will try the outputs you recommend. Correct it can all seemingly be routed directly from the DAC to Mono Out ($07). I have had no success with that so far as it seems that one of the outputs may be hardwired to the speakers, being its running in a laptop with no actual line-out port. Just a headphone jack and a mic-in jack for ports which i'm testing too. As it passes through selector widget ($0B) there is an option listed in the notes of the datasheet to redirect the stream to the analog mixer ($0E) - which I have set in HDAICOUT, although the diagram does not show this path, there is just a greyed out arrow coming out of selector widget ($0B) and into sum widget ($0F) which I assume indicates this. I notice the path from DAC splits down to the Analog Mixer ($0E) but passes through amp ($11) and then a mute before hitting the sum widget. At the moment I have Mono Out ($07) set to 'not connected' so might be possible that ($11) - Amp going into Analog Mixer ($0E) is a candidate for Waveout.exe... unless the greyed out arrow on the datasheet is indicating to use ($0F) as the volume control. Lots to try!! Sure thing! Attached here \m/ VDMS.INI

This is why you are now the HDA sensei! Ah sorry I meant to control the volume using Waveout.exe - Which widget to set in hdaconfig.ini. Still to test but it should be either $11 (The amplifier between DAC and Analog mixer), or the analog mixer itself $0E according to the 1981HD datasheet. The physical volume buttons on the laptop DID work with Judas but only the mute button works in 9x. I'll have to have a look at the laptop datasheet to see how the volume button is wired to the speakers to see what controls it. Just for clarity in HDAConfig.ini - Sleeping Widget = The DAC? Volume Widget = The Amp connected to DAC OR the Analog mixer? Output Widget = The Amp connected to DAC OR the Analog mixer? There's a version of VDMS called 'Alpha3' and it seems to handle midi - to the point where the games are detecting the port at 0x330 and allowing me to select soundblaster pro, and then playing it. As for whether these are true midi sounds or how good the emulation is I can't say (I'll leave that to the midi critics) but certainly playing with no stutters. There's another item on my 'to test' list which is MUNT for 9x which seems to have had some success over at Vogons - Can handle Roland MT-32 in a 9x dos window apparently?

Thanks Deomsh! I went on a journey into binary and hex land and made it out the other side still in 1 piece! The reading on the IHDA specification made a lot more sense this time through. I was able to convert the hex offset bytes from the verbs into bits and then divide the bits according to the specs to see the settings. I was then able to decode the Default Configuration Parameters from my datasheet and tweak as necessary for this laptop. On further investigation regarding the '41' offset = This is indeed disabling the mono output to enable the DAC to send the stream to the analog mixer instead. I am still testing with the volume controls through hdaconfig. I'm down to 2 possibilities to test - either the amp attached to the analog mixer, or the analog mixer itself. Hoping to have some success today with that! I am also testing the jack-sense settings. Further studies: I attempted to run VDMSound for 9x to see if it plays nicely with HDA2.dll (to emulate a soundblaster on A220 I7 D1) and am happy to report it works great! I was able to run quite a few old DOS games in 9x with soundblaster audio (and midi) output through the HDA interface. The games that come with soundcard detectors in the install packages had no issues detecting and setting. I have 2 questions that i'm hoping you can help advise on: 1 - (I highly doubt, but) Would there be a way through the verb setting to tell the HDA controller to report itself as a soundblaster? The verb 'Subsystem ID' bytes 1 to 4 I am interested in. 2 - When I tested Judas according to your procedure it produced sound in DOS mode simply using the HDATSR. At that point I did not have sound working in 9x so Judas was able to interface directly with the HDA controller and produce sound in DOS by itself. Is there a way to determine how Judas was able to play audio, to be able to determine what Address, IRQ, and DMA it is using, and to be able to use that to get audio functioning in DOS mode for games and applications? Cheers! \m/

Hello gents! Very happy to report that after following this thread I have sound working in Win98SE on a HP 6710b laptop with Microsoft UAA (8086 27D4) and Soundmax AD1981HD (11D4 1981) on board. This laptop also has an Agere HDA modem attached and strangely the hdacfg.ini is registering this device as the codec.. I assume im not playing through the HDA modem codec as it sounds great! I typed up and rejigged the AD1984 HD HDAICOUT.HDA from DEOMSH's diagram to suit the widgets on the AD1981 but still no sound. I downloaded the HP manufacturer driver for the AD1981 and checked out the WDM inf to find verbs in there specific to this laptops configuration for the codec!! In this case I was trying to set mono out as the mixer by setting '00' after the '701' connection select verb. The inf file showed this set as '03' which worked! - 03 is the DAC I assume? as NID03 is the (only) DAC on this codec along with an S/PDIF on NID02. I found these 3 verbs - Set LineOut, HP and Mono out to the same initial levels (-3 dB) Whilst Lineout and HP used the '3B0' Amplifier gain/mute verb to set this, Mono out was set by '71F' verb - Config Def byte 4 (31:24) to '41'. - Still learning my bits and bytes so I have no idea what 41 means or how to calculate/find it other than the inf, but it works at full blast! Going to add some more to the HDAICOUT tomorrow and test with the volume control app. - To note the laptops volume button did not change levels (yet) but the mute button worked. Thanks very much to Deomsh and all of the testers on here for all of this great info! I will post back with any more updates. Side note: The laptop has an Intel 965GM video chip and is being driven by a patched version of the SVGA driver (1024x768x256) that was for Win3.1 \m/ Cheers!