VOGONS


VSBHDASF: Fork of VSBHDA with Soundfont support

Topic actions

Reply 61 of 110, by Nemo1985

User metadata
Rank Oldbie
Rank
Oldbie

Do you have any sf3\sfo soundfont to advise?
They should also have a smaller footprint compared to sf2.

Reply 62 of 110, by Cacodemon345

User metadata
Rank Newbie
Rank
Newbie

I'd instead suggest converting existing soundfonts to SF3/SFO if possible. Be aware that there will be quality losses on such conversions.

Reply 63 of 110, by Nemo1985

User metadata
Rank Oldbie
Rank
Oldbie
Cacodemon345 wrote on 2025-02-01, 14:02:

I'd instead suggest converting existing soundfonts to SF3/SFO if possible. Be aware that there will be quality losses on such conversions.

Ok I will try and report back.
It would be possible to support the sfPack format?

Edit: tried the latest version there must be a regression bug because once again the card don't get detected on duke3d and blood (it complains about dma and blabla), also I noticed the pentium mmx executable is now missing (I'm using the one for p4 anyway), doesn't matter if a sf2 or sf3 soundfont is used.

Reply 64 of 110, by Cacodemon345

User metadata
Rank Newbie
Rank
Newbie
Nemo1985 wrote on 2025-02-01, 14:04:
Ok I will try and report back. It would be possible to support the sfPack format? […]
Show full quote
Cacodemon345 wrote on 2025-02-01, 14:02:

I'd instead suggest converting existing soundfonts to SF3/SFO if possible. Be aware that there will be quality losses on such conversions.

Ok I will try and report back.
It would be possible to support the sfPack format?

Edit: tried the latest version there must be a regression bug because once again the card don't get detected on duke3d and blood (it complains about dma and blabla), also I noticed the pentium mmx executable is now missing (I'm using the one for p4 anyway), doesn't matter if a sf2 or sf3 soundfont is used.

The Pentium MMX executable was removed since it provided little benefit.

I don't have any idea why it isn't getting detected again on your side since I haven't altered anything on the AC97 driver since the SiS7012 fixes. Try altering BLASTER environment variable until it works again.

sfPack isn't planned at the moment.

Reply 65 of 110, by Falcosoft

User metadata
Rank l33t
Rank
l33t
Cacodemon345 wrote on 2025-02-01, 11:48:

https://github.com/Cacodemon345/VSBHDASF/releases/tag/v1.6

This release adds support for SF3/SFO soundfonts, and should be much more General MIDI compliant.

Note that SF3/SFO soundfont support is untested at this moment.

Hi,
What does 'much more GM compliant' mean exactly?
I have seen you have added Mod wheel (CC#1) support. Are there any other changes?

Website, Facebook, Youtube
Falcosoft Soundfont Midi Player + Munt VSTi + BassMidi VSTi
VST Midi Driver Midi Mapper

Reply 66 of 110, by Cacodemon345

User metadata
Rank Newbie
Rank
Newbie
Falcosoft wrote on 2025-02-01, 14:55:
Hi, What does 'much more GM compliant' mean exactly? I have seen you have added Mod wheel (CC#1) support. Are there any other c […]
Show full quote
Cacodemon345 wrote on 2025-02-01, 11:48:

https://github.com/Cacodemon345/VSBHDASF/releases/tag/v1.6

This release adds support for SF3/SFO soundfonts, and should be much more General MIDI compliant.

Note that SF3/SFO soundfont support is untested at this moment.

Hi,
What does 'much more GM compliant' mean exactly?
I have seen you have added Mod wheel (CC#1) support. Are there any other changes?

Reset All Controllers message now behaves as per the specification, no longer affecting bank selects and channel volume. Omni On/Off is implemented as an alias of All Notes Off. And the velocity-to-attenuation curve was fixed.

Reply 67 of 110, by Nemo1985

User metadata
Rank Oldbie
Rank
Oldbie
Cacodemon345 wrote on 2025-02-01, 14:51:
The Pentium MMX executable was removed since it provided little benefit. […]
Show full quote
Nemo1985 wrote on 2025-02-01, 14:04:
Ok I will try and report back. It would be possible to support the sfPack format? […]
Show full quote
Cacodemon345 wrote on 2025-02-01, 14:02:

I'd instead suggest converting existing soundfonts to SF3/SFO if possible. Be aware that there will be quality losses on such conversions.

Ok I will try and report back.
It would be possible to support the sfPack format?

Edit: tried the latest version there must be a regression bug because once again the card don't get detected on duke3d and blood (it complains about dma and blabla), also I noticed the pentium mmx executable is now missing (I'm using the one for p4 anyway), doesn't matter if a sf2 or sf3 soundfont is used.

The Pentium MMX executable was removed since it provided little benefit.

I don't have any idea why it isn't getting detected again on your side since I haven't altered anything on the AC97 driver since the SiS7012 fixes. Try altering BLASTER environment variable until it works again.

sfPack isn't planned at the moment.

I tried to change from irq 7 to 5 and 2, no changes. According to the setup file the problem is with dma (or highdma), standard setting is dma 1, I tried to switch to dma 3, tried the non p4 exe. No changes unlucky.
Is there any troubleshoot\debug utility I can run?

Reply 68 of 110, by Cacodemon345

User metadata
Rank Newbie
Rank
Newbie

Try disabling MPU-401 emulation as a last resort. If the TinySoundFont message still appears, unset SOINDFONT and try again. And then see if it fixes the problem.

Reply 69 of 110, by Nemo1985

User metadata
Rank Oldbie
Rank
Oldbie
Cacodemon345 wrote on 2025-02-01, 15:17:

Try disabling MPU-401 emulation as a last resort. If the TinySoundFont message still appears, unset SOINDFONT and try again. And then see if it fixes the problem.

Disable the soundfont did the trick. For further testing I don't know how to disable the mpu-401 emulation, do I need to use a specific switch?

Reply 70 of 110, by Cacodemon345

User metadata
Rank Newbie
Rank
Newbie
Nemo1985 wrote on 2025-02-01, 15:26:
Cacodemon345 wrote on 2025-02-01, 15:17:

Try disabling MPU-401 emulation as a last resort. If the TinySoundFont message still appears, unset SOINDFONT and try again. And then see if it fixes the problem.

Disable the soundfont did the trick. For further testing I don't know how to disable the mpu-401 emulation, do I need to use a specific switch?

You need not test any further. This looks like a speed issue.

Reply 71 of 110, by Nemo1985

User metadata
Rank Oldbie
Rank
Oldbie
Cacodemon345 wrote on 2025-02-01, 15:54:
Nemo1985 wrote on 2025-02-01, 15:26:
Cacodemon345 wrote on 2025-02-01, 15:17:

Try disabling MPU-401 emulation as a last resort. If the TinySoundFont message still appears, unset SOINDFONT and try again. And then see if it fixes the problem.

Disable the soundfont did the trick. For further testing I don't know how to disable the mpu-401 emulation, do I need to use a specific switch?

You need not test any further. This looks like a speed issue.

Confirmed, I reduced the clock from 3.06 to 2.30 (fsb from 133 to 100) and it works. What doesn't work it the converted sf2 to sf3. If I load the sf2 everything works fine, if I load the sf3 there are audio issue (I'm going to load a video).
SF2: https://youtu.be/eXm2CMTZuGw
SF3: https://youtu.be/LofcIMGDLDw
I used sf2convert-1.2.2-win so I don't know if it's a program issue or the sf3 implementation. I also tried another sf3 converted file but the result is the same the only output is a swish noise.
Edit: I used Polyphone 2.5.1 to convert the sf2 file to sf3, the sound is still broken but the pattern is different, like less broken the music is distorted but more familiar.

Last edited by Nemo1985 on 2025-02-01, 16:27. Edited 1 time in total.

Reply 72 of 110, by DarthSun

User metadata
Rank Member
Rank
Member
Nemo1985 wrote on 2025-02-01, 16:04:
Confirmed, I reduced the clock from 3.06 to 2.30 (fsb from 133 to 100) and it works. What doesn't work it the converted sf2 to s […]
Show full quote
Cacodemon345 wrote on 2025-02-01, 15:54:
Nemo1985 wrote on 2025-02-01, 15:26:

Disable the soundfont did the trick. For further testing I don't know how to disable the mpu-401 emulation, do I need to use a specific switch?

You need not test any further. This looks like a speed issue.

Confirmed, I reduced the clock from 3.06 to 2.30 (fsb from 133 to 100) and it works. What doesn't work it the converted sf2 to sf3. If I load the sf2 everything works fine, if I load the sf3 there are audio issue (I'm going to load a video).
SF2: https://youtu.be/eXm2CMTZuGw
SF3: https://youtu.be/LofcIMGDLDw
I used sf2convert-1.2.2-win so I don't know if it's a program issue or the sf3 implementation. I also tried another sf3 converted file but the result is the same the only output is a swish noise.

I have a good 4GHz processor clock. Roland 26MB and GM 16MB SF2 patterns - ok.

The 3 body problems cannot be solved, neither for future quantum computers, even for the remainder of the universe. The Proton 2D is circling a planet and stepping back to the quantum size in 11 dimensions.

Reply 73 of 110, by Nemo1985

User metadata
Rank Oldbie
Rank
Oldbie
DarthSun wrote on 2025-02-01, 16:21:

I have a good 4GHz processor clock. Roland 26MB and GM 16MB SF2 patterns - ok.

Probably it's configuration dependant, with the older version it was working fine. Do you use the ac97 codec?

Reply 74 of 110, by DarthSun

User metadata
Rank Member
Rank
Member
Nemo1985 wrote on 2025-02-01, 16:28:
DarthSun wrote on 2025-02-01, 16:21:

I have a good 4GHz processor clock. Roland 26MB and GM 16MB SF2 patterns - ok.

Probably it's configuration dependant, with the older version it was working fine. Do you use the ac97 codec?

TUF B450PRO/RyZen 3800X/7900GS/ALC S1200A/SB0060.
The SB0060 is settings now come on. It works well, but I haven't tried it with VSBHDASF yet.

The 3 body problems cannot be solved, neither for future quantum computers, even for the remainder of the universe. The Proton 2D is circling a planet and stepping back to the quantum size in 11 dimensions.

Reply 75 of 110, by RayeR

User metadata
Rank Oldbie
Rank
Oldbie

For me the v1.5.1 runs ok on 4.5GHz i7 on SBA, so it't not generic cpu speed issue.

Gigabyte GA-P67-DS3-B3, Core i7-2600K @4,5GHz, 8GB DDR3, 128GB SSD, GTX970(GF7900GT), SB Audigy + YMF724F + DreamBlaster combo + LPC2ISA

Reply 76 of 110, by Cacodemon345

User metadata
Rank Newbie
Rank
Newbie

SF3 support on upstream appears to be broken as well. I will do a release removing support for it for now.

Reply 77 of 110, by Nemo1985

User metadata
Rank Oldbie
Rank
Oldbie
Cacodemon345 wrote on 2025-02-01, 18:09:

SF3 support on upstream appears to be broken as well. I will do a release removing support for it for now.

not a big loss, I tried to find some informations if a sf3 file is faster to load than a bigger sf2 file (I wanted to try the Musyng Kite soundfont) and despite producing smaller files the loading time is still crazy.
Removing the support could also fix the speed issue with my configuration in your opinion?

Reply 79 of 110, by Nemo1985

User metadata
Rank Oldbie
Rank
Oldbie

Ok I did a roundup of testing with latest version at full speed (3.06ghz):
Doom works fine
Fastdoom works fine (with novcpi)
Blood works fine
Duke 3d with latest version the sound shooting doesn't work, but it does with v1.5.1.3. ok I don't know what's wrong now during the demo when duke shoots there is no sound but if I play it works fine
Also (I don't know how much is important) the /F switch doesn't work, I used /F44100 but it shows 48000hz that always happened.