music starts wrong in gzdoom and prboom when using a roland sc-55

[Storm934]

hello, i'm having an issue where the music will start wrong sounding like it skips a few notes or plays them too fast on a real roland sc-55. It only happens in these 2 source ports and nowhere else.

 

how it sounds in chocolate doom for comparison

 

Edited April 25, 2024 by Storm934

[Dark Pulse]

For ZDoom, it may be better to bring this to attention on their forums directly.

 

For PrBoom, all I can say is good luck. It hasn't been updated in 15 years. PrBoom+ is better at it, but even its last update was ten months ago from the time of this post, and that might be the last update it ever gets since the repository was archived shortly after.

Edited April 26, 2024 by Dark Pulse

[rfomin]

3 hours ago, Storm934 said:

how it sounds in chocolate doom for comparison

 

What version of Chocolate Doom are you using? In the developer builds of Chocolate Doom (and the latest Crispy Doom/Woof), special efforts have been made to support MIDI hardware in Windows (various reset types, capital tone fallback emulation, etc.).

[Storm934]

16 minutes ago, rfomin said:

 

What version of Chocolate Doom are you using? In the developer builds of Chocolate Doom (and the latest Crispy Doom/Woof), special efforts have been made to support MIDI hardware in Windows (various reset types, capital tone fallback emulation, etc.).

chocolate dooms the one that sounds fine. 

[Redneckerz]

18 hours ago, Storm934 said:

chocolate dooms the one that sounds fine. 

This literally means nothing. What synth are you using?

[Lippeth]

According to ceski on GitHub you'll have to fiddle with a reset delay setting in the cfg file of Woof, dsda and prboom+ as well as Chocolate.

https://github.com/chocolate-doom/chocolate-doom/issues/1547#issuecomment-1352241521

 

I've always assumed it was just the speed Roland hardware synths read all the info at the beginning of a MIDI file, because the issue is also present in every digital audio workstation and playback method that I've ever used which all have workarounds you can do and is not a specific issue with Doom source ports, though some also have their own ways around it.

 

Edited April 27, 2024 by Lippeth

[Dark Pulse]

3 hours ago, Redneckerz said:

This literally means nothing. What synth are you using?

He's not using a synth, he's using an actual, hardware SC-55. He mentioned this in his intro post.

[Redneckerz]

8 hours ago, Dark Pulse said:

He's not using a synth, he's using an actual, hardware SC-55. He mentioned this in his intro post.

Admittely i misread that, but On the one that sounds fine is incredibly vague.

[Storm934]

22 hours ago, Lippeth said:

According to ceski on GitHub you'll have to fiddle with a reset delay setting in the cfg file of Woof, dsda and prboom+ as well as Chocolate.

https://github.com/chocolate-doom/chocolate-doom/issues/1547#issuecomment-1352241521

 

I've always assumed it was just the speed Roland hardware synths read all the info at the beginning of a MIDI file, because the issue is also present in every digital audio workstation and playback method that I've ever used which all have workarounds you can do and is not a specific issue with Doom source ports, though some also have their own ways around it.

 

set the midi delay to 200 and it fixed the issue for prboom+. Wish GZDoom had a way to change it.

[Darkcrafter07]

GZDoom must have a setting to pre-cache midis in its gzdoom.ini file.

 

snd_midiprecache

 

try find this word with a notepad and replace it with

 

snd_midiprecache=true