VOGONS


Reply 20 of 33, by standal

User metadata
Rank Newbie
Rank
Newbie

Hi,
I am playing with it on one old laptop (VT8231) and want to ask for default config for /midi? How many parameters are needed? Because if I use only one than it errors parsing argument and if 3 than failed to set up game port. The laptop does not have any game port or midi port, but VIASGBCFG set it anyway.
And second question. I need to run via_ac97 two times. First with parameters but after that sound does not work. After second run of via_ac97 without parameters, the sound starts to work.
Regards
standal

Reply 21 of 33, by standal

User metadata
Rank Newbie
Rank
Newbie

Also found that /v_line2:<volume> and /micbooost:<0/1> are not working.

Reply 22 of 33, by Oerg866

User metadata
Rank Member
Rank
Member

Hi, thanks for testing!

Yes, this is intentional because I'm assuming if you run it without parameters you want "easy default setup" which unmutes the sound and sets up the legacy audio like the bios configures it.

If you configure it manually to enable/disable features or set the I/O ports, then you also need to set the output volume using /v_master:<volume> and /v_wave:<volume>.

I think probably from a usability point of view, I should add a /auto parameter and without parameter show the parameter list instead. That will probably eliminate some confusion.

Regarding MIDI - you're right, there's a bug that makes it fail to parse the argument. I'll fix that real quick...

Reply 23 of 33, by Oerg866

User metadata
Rank Member
Rank
Member

I pushed a fix to github that fixes /midi.

Regarding /v_line2, I don't have a board with two line outputs, but it seems to be working just fine for me:

h2DlQka.png

Mic boost should work too, but there's no visual confirmation whether it is enabled or not...

Best,
Eric

Reply 24 of 33, by standal

User metadata
Rank Newbie
Rank
Newbie

OK I tried a little bit more and line2 and probably mic parameter are ok. The problem was that I put all possible parameters after via_ac97, and it looks that it is too much to parse. If I add 13th parameter it fails with parameter / not recognized. It looks like your variable for input parameters is too small and cannot save the complete string with parameters.
Next i tried to run via_ac97 with my needed parameters (with volume as your default) and after that v97tsr.exe r. But no sound. Sound comes only if i run old viafmtsr.com instead.
The only case when the sound is working with your v97tsr is, if i run again via_ac97 but without parameters. It looks like the default setting is setting something what is missing in my parameters. Can you write what is the default?
I would let your easy default, that is ok. But i cannot make it working without that. But /auto parameter would be also ok.
Also as info, in my bios there is no settings for SBPRO. Before I found your project I used some tool from here to set the register in via chipset to enable SBPRO. But your project is setting it automatically as i have seen.

Reply 25 of 33, by standal

User metadata
Rank Newbie
Rank
Newbie

So my fail. I used for volume as parameter 10, but this is too low. At 15 the sound is almost not to hear. So the problem was only because I set the volume too low. But anyway i think at 15 the volume should be half and not almost no sound.
So v97tsr is working ok. viafmtsr.com is probably setting volume back to 31 and your default also.

Reply 26 of 33, by standal

User metadata
Rank Newbie
Rank
Newbie

I am an idiot. I set master and all other volumes to 10, thats why. I should more think and less write 😁

Reply 27 of 33, by Oerg866

User metadata
Rank Member
Rank
Member

Heh, all good! A few improvements to the way that default setup is handled can be made for sure.

Also regarding the "13 parameters" thing - DOS has a pretty strict limit for the command line, and that's what you may be seeing here - I do not limit the amount of arguments and I'm purely using argc/argv as provided by the main function...

Reply 28 of 33, by standal

User metadata
Rank Newbie
Rank
Newbie

In that case it would be a posibility to shorten parameter names. delete v_ at volumes and shorten master to mas etc. Or show warning if the parameter string is too long.

Reply 29 of 33, by eM-!3

User metadata
Rank Newbie
Rank
Newbie
eM-!3 wrote on 2025-03-21, 07:16:

I'm very interested and I follow this topic. Still I'm not sure if it's compatible with my hardware as I didn't try it on my PC yet.

According to HWiNFO my device has VT8237(R) chipset which is not supported here.

Reply 30 of 33, by igna78

User metadata
Rank Member
Rank
Member

Great job, I am impressed with what you have accomplished. I have already downloaded the latest version. Thank you so much for this wonderful gift you have given to the community 😀

Reply 31 of 33, by Bruno128

User metadata
Rank Member
Rank
Member

Testing ver.0.6 on VIA 686B
Doom shareware: sound and FM music is good.
Duke3D: sound and FM music works but with severe lags and distortion.
Dyna Blaster: sound and FM music is good.
Hocus Pocus: no sound, no FM music.
Prehistorik: no sound, no FM music.
Quake: sound is good.

SBEMU compatibility reports list | Navigation thread

Reply 32 of 33, by polpo

User metadata
Rank Member
Rank
Member
Oerg866 wrote on 2025-03-14, 04:30:

I've optimized the hell out of the Nuked OPL core but I think it's just too heavy.

I'm very interested in the Nuked optimizations - getting OPL3 working on RP2040 or RP2350 has been my goal for a very very long time!!

Reply 33 of 33, by Oerg866

User metadata
Rank Member
Rank
Member

It's kind of specific to this sort of real-mode MSC setup, but you can diff against the official repo from this:

https://github.com/oerg866/via_ac97.866/tree/master/nukedopl

And here are some implementations in assembly for some nuked functions:
https://github.com/oerg866/via_ac97.866/blob/ … ter/vfm_opt.asm

Not sure how helpful this will be for a pico port though 🤔