Jump to content

Vigami

Member
  • Posts

    6
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Germany

About Vigami

Profile Information

  • OS
    98SE

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Vigami's Achievements

0

Reputation

  1. I was curious and I asked myself: If the modem is the issue, what would happen whithout it? So I opened the laptop and completely removed the modem card. The result was partially as expected, but partially surprising ... As before again zero nodes are reported during initialization first, but now the driver tries again until it sees a proper vendor ID and at least one node: $000F0000=$00000000 $000F0000=$83847690 $000F0004=$00000000 $000F0005=$00000000 $000F0000=$83847690 $000F0002=$00102201 $000F0004=$00010001 $001F0011=$C0000004 $001F2000=$102801BD $001F000F=$0000000F $001F000A=$00000000 $001F000B=$00000001 $00224011=$00000000 $00270610=$00000000 $00270500=$00000000 $00B3A01C=$00000000 $00B39033=$00000000 As expected I now see only one codec in HDAcfg.ini and Vendor ID and CODEC_AFG_xyz settings are populated correctly (?). But unfortunetly the volume control with waveout.exe still doesn't work. And what's really strange, my volume reduction in HDAICOUT.HDA also doesn't work anymore. So the speakers shout again with full volume. And I didn't manage to reduce the volume again. Therefore I decided to put the modem back in and told myself I should be happy with what I got: Audio output with fixed volume as set in HDAICOUT.HDA. 🙂 I have attached HDAcfg.ini and HDAICIN.TXT without modem for your information. If you ask me, I whould now keep it as it is (with modem back in and fixed volume). But if you would like to try something more, I will be happy to do further tests for you. HDAcfg.ini HDAICIN.TXT
  2. Thanks a lot for this information! 👍 Unfortuantely I slowly get the feeling that there is not much one could do in this case. I played around with the wait settings, but that didn't have any positive effect (it only made the whole computer slower?!). Then I had a look into the driver source code. I'm not a pascal programmer and don't know much about drivers, but from my understanding the driver checks every codec and determines the number its nodes. It then steps though all theses nodes until it finds the (first) audio node ('AC_GRP_AUDIO_FUNCTION'). Unfortunately in my case the reported number of nodes for codec $0 is zero, so the driver does not look any further and continues at codec $1. I think it's a bit strange, that codeg $1 at first also reports zero nodes, but the driver then asks again and gets a different result. But I don't think it's worth the effort to dig even deeper and clarify this. Do you know if the 'commands' in HDAICOUT.HDA are executed before or after this driver initialization?
  3. Maybe I should clarify one thing first: I don't really need the system sounds! I have only set up this WIN98SE installation for fun, so the system sounds are only important for the 'nostalgic' feeling. The solution now is much better than I thought it would be, so any further investigations only are from curiosity. Don't spend too much effort on my case. About the behaviour of WAVEOUT.EXE I was (again) not fully precise. When I change the slider for the bluetooth device, the value is kept (also when I press the button again or restart waveout) and it is also kept when I then switch to the HDA device and try to do some change there (but it does not have any effect on the speaker volume). But when I change the sliders when HDA is selected, waveout will always jump back to its last setting (after pressing the button again). I hope, this expresses it clearly. I don't know if the bluetooth audio is a HDA device, but I do not think so. It was installed together with the bluetooth driver and is already a bit older. And as far as I know this device is not mentioned in the HDAcfg.ini file. I have attached all the files you asked for, but I don't get two versions of HDAICIN.TXT, because this file will not be generated without HDAICOUT.HDA (the windows folder then contains the HDAICIN.TXT from the last try with HDAICOUT.HDA). I don't know if it is useful, but I have also attached the HDALOG.TXT files (these files differ with or without HDAICOUT.HDA). Again I say thank you for your help! Please note that I will not available over this weekend, so my next answer might take a bit longer. HDAcfg.ini HDAICIN_with_hdaicout.TXT HDALOG_without_hdaicout.TXT HDALOG_with_hdaicout.TXT
  4. @deomsh Oh wait, one more thing (😉): Would you mind to briefly explain the steps, which typically need to be done in HDAICOUT.HDA? It is difficult to understand without explanation because (from my understanding) you are trying to cover different hardware in only one file. So far I have only seen that there is an initialization at the beginning followed by powering up all the nodes. And of course you are setting the volume and unmute the output. Inbetween I saw something about a Stream-ID (whatever that is) and a comment regarding the stream format (but the command seems to be wrong for my case, because it's not described in the spec). But there are lot more verbs in this file, for which I don't know what they are supposed to do. I have not yet finally decided if I will try any further, but in case I do, a short explanation of the (typical) necessary steps would help at lot.
  5. Hello @deomsh, thank you for your quick reply and thank you for sharing your opinion, that I am not completely on the wrong way ... 🙂 So went through your questions and remarks: Yes, it's in the Windows directory (I just checked again 😉). And it seems to work for my bluetooth audio (device 0). But for for HDA (device 1) it doesn't have any effect. When I change the sliders and than press "waveOutGetDevCaps" again, both chanels jump back to 32256. When I do the same thing for bluetooth audio, the sliders will stay in place. I wasn't aware of this, but you can configure it in the WinAmp settings. And when I choose the DirectSound output plugin there, the WinAmp slider can actually control the volume! 😀 However, the bad thing is, that the maximum volume is whatever I set in the HDAICOUT.HDA. It doesn't change the volume of the system sounds and when I set the volume too high in HDAICOUT.HDA, all those system sounds will be too loud (and if possible, I would like too keep them activated). With Windows Media Player 9 it's the same (I hadn't tried before), but I have not checked any othe players. And Winamp can change the buffer size as well (currently it's set to 2000ms). But I have not (yet) checked if this setting has any effect, because currently the audio quality is not my highest priority. But I might try this when everything else ist set up properly ... Sounds like a good idea, but unfortunately I can only choose between "Bluetooth Hands-free Audio" and "HDA Sound" there, so no possibly to configure DirectSound there. 🙁 Of course I cannot be sure, but according to the specification the widgets $0B and $11 are the only output widgets with volume control. And yes, I think I tried it before, but to be sure I just tried again: $11 does not work at all. Even adjusting the volume in HDAICOUT.HDA does not have any effect on the speaker output. It really looks like I'm stuck with my fixed volume setting in HDAICOUT.HDA. This is a little disappointing, but on the other hand it's much much better than no sound at all! If you have any further ideas, please let me know. But if not, I say thank you anyway!
  6. Hello everyone, I have been reading this thread more or less from the beginning to the end and I think the knowledge and the support, which @deomsh is providing here, is just incredible. A big thank you from my side! But anyhow, despite all this information I still have an issue, so I decided to sign up to this forum and ask ... 🙂 I was trying to get audio running in WIN98SE on a DELL Inspiron 6400 notebook. After the HPA installation I first got some bluescreens, but that was quicly fixed with the [vcache] limitation in system.ini (I first tried without that). Without hdaicout.cpa I had no sound, but this was also quickly fixed using the hdaicout.cpa from the driver package (HDADRV9J). However, the sound is far too loud ... in fact I never expected that the little speakers in this notebook could be that loud. And unfortunetely waveout.exe does not have any effect on this. 🙉 The Dell Inspiron 6400 uses an IDT (Sigmatel) STAC9200 codec. A corresponding datasheet can be found here (for example): https://www.recomb-omsk.ru/published/SC/html/scripts/doc/IDT_STAC9200_DST_20120530.pdf From the widget diagram I take that SleepingWidget and OutputWidget should be $02 and VolumeWidget shoud be $0B. I tried that (and many other combinations), but without any success. The volume level just cannot be changed, neither in waveout.exe, nor in Winamp, nor by setting a volume level in HDAcfg.ini. And now comes the strange thing: I had a look into Hdaicout.cda and (after some time to understand) I saw that it sets the master volume to full level at widget $0B (as I expected). And when I change the lines ... $00B3901F $00B3A01F to (for example) $00B39008 $00B3A008 ... I get an acceptable volume level. However, this level is still fixed, the volume sliders don't have any effect. But from my understanding the VolumeWidget $0B seems to be correct. But even with this setting in HDAcfg.ini the Windows applications do not control volume correctly. 🙁 Do you have any idea what's going wrong here?
×
×
  • Create New...