On (142) the annoying Midi bug is back. The Midis do the same thing as when it was on 2.10. I turned the Strict switch off and on, and didn't seem to do anything. Also, I was using the small windowed verison of ZC from the Launcher, in case that helps.
The Midi Bug is Back
What is the size of your alleg42.dll file in bytes?
confirm this
my allegro42. file in 210b10b is dated 27-12-2006 and is 958.411 big
and this one is dated 20-12-2006 and is 1.031.749 big
Shoelace wrote:On (142) the annoying Midi bug is back. The Midis do the same thing as when it was on 2.10. I turned the Strict switch off and on, and didn't seem to do anything. Also, I was using the small windowed verison of ZC from the Launcher, in case that helps.
Can you please describe the bug what it's actually doing so people will know what it's doing and can find a solution to how to fix it.
cbailey78 wrote:Can you please describe the bug what it's actually doing so people will know what it's doing and can find a solution to how to fix it.
It was a fixed bug but returned again so I think they know the problem 😉
It is a bug that also excist in the 210 version so it's nothing new
My allegro42.dll file is .98MBs big (1,031,749 bytes).
And the Midi bug for those who don't know is where some Midis will play notes constently and hold it so it basically is playing the same note forever when it isn't supposed to. So basically the notes run into each other and the Midis don't play correctly. It can get annoying if you have high pitched notes. And now Shoelace wins the award for worst description ever.
Shoelace you actually described that well, but can I add "nails on a chalkboard" as a description of the sound it makes? I hope this one gets squashed quick. This bug was the most annoying bug from 2.10.
I think this one's my fault ... also I think it's fixed now. I enabled a "strict" switch by mistake.
question ! what does the strict option actually do? does it limit the length a note can be held for? thus vastly reducing the effect of the bug?
While you're at this, you may want to find another solution.
Strict MIDI messes up some MIDIs. Take Exate's MIDI pack, for instance. Play "dkc2woodsexate.mid" with the option ON, and it sounds..... terrible. It messes up the sounds. Turn the option OFF, and it sounds like it should. Play the related MIDI from VGMusic.... Same result. Strict MIDI is not very useful at all. It fixes SOME MIDIs, but messes up others. That's either a bug, or intended effect, and if it's the latter.... Oh, I hope not. >_<
Nope, this isn't fixed yet. Yet there in build 204.
franpa wrote:question ! what does the strict option actually do? does it limit the length a note can be held for? thus vastly reducing the effect of the bug?
What it does is filter out MIDI control codes, some of which apparently cause problems for some MIDI adapters on some computers. I'm working on a fix for this.
Pikaguy or somebody else with more knowledge of MIDIs than I do, could you please take a look at dkc2woodsexate.mid and determine what MIDI controller codes it is using which, when disabled, makes it sound bad, like in ZC?
DarkDragon wrote:What it does is filter out MIDI control codes, some of which apparently cause problems for some MIDI adapters on some computers. I'm working on a fix for this.
o_O i can play all the "buggy" midi files outside of zelda classic and zquest fine and dandy... so it has to be that zelda classic and zquest themself hate certain midi control codes.
Well, it's the Allegro engine that hates them. The old solution was to ignore all controller codes, but this unnecessarily crappifies some MIDIs; my hope is to pin down which controller codes are OK and which cause problems.
ok, glad we agree that its most likely not the soundcards them self that crap out on the midi codes 😊
How would I tell what codes are messing it up?
disable them one by one till you get it to sound like it does in zelda classic, then re enable them 1 by 1 till you get the midi bug in zelda classic 2.10
that is the simplest way... and yes... use 2.10 and not 2.10.1 or 2.10.2
Uh, WHAT? I'm having difficulty understanding how I'm supposed to do that....
ooooooooooohhhhhh*dawning comprehension*......So thats the midi bug. I always assumed it was just the way ZC interpereted the midi. And I heard peopel reference the bug, but I never put 2 and 2 together.
pikaguy900 wrote:Uh, WHAT? I'm having difficulty understanding how I'm supposed to do that....
learn about audio editing software then 😊
Ok, in the next beta the midi behavior should be back to how it use to be. As soon as I get any data about "safe" MIDI controller codes (if there is only one broken one I should be able to pinpoint it in 7 manual tests using binary search 😉 ) I'll enable them and hopefully improve the playback of the MIDIs you mentioned.
Are all MIDI problems corrected in the latest build?
to me it seems yes, and as a added bonus (that im aware that you know of as well 😊 ) the midi music has vastly improved in quality.
Ah perfect, that's what I wanted to hear 😊
Well I don't notice any improvement in quality, but I sure can confirm that there are no issues with midis anymore in build 219. Way to go DD, you're too awesome! 😊
i tested maybe 7 quests (but only like the intro etc.) and found significant quality increase 😊 HOWEVER quality increase doesn't mean the "bug" itself was fixed... i currently don't have any quests which i remember exposing the bug in question.