From: D. M. M. <ros...@gm...> - 2009-02-06 01:08:24
|
On Thursday 05 February 2009, Jani Frilander wrote: > I know this is minor thing but it annoys a little bit. Is this fixed in > newer versions. No, it isn't fixed. Let's see, the closest existing report I can find is this one: >https://sourceforge.net/tracker2/?func=detail&aid=1870001&group_id=4932&atid=104932 As you can see from the comment thread, it took a long time for me to even completely prove to myself that the bug is real. I really don't understand the problem, and therefore I have no idea how to fix the problem. Let's do up another example while I'm thinking about it. 1) I start KMidiMon 2) I start Rosegarden 1.7.3 3) I use Manage MIDI Devices to point the top device slot at KMidiMon 4) I delete all tracks except the top track (so there's no confusion about the one and only track I have to look at) 5) 4) I set pan all the way left; volume, chorus, reverb all the way right on the first track 6) I save the file 7) I quit Rosegarden 8) I start a new session in KMidiMon 9) I start Rosegarden 10) I save the KMidiMon session and start a new one 11) I load the file I just saved Now, let's dissect what happens when I load the file. First we get a: 7.44825,130:3,Control change,n,7,100 7.44757,130:3,Control change,n,10,64 on every channel where n is from 16 down to 2. These are the defaults of 100 for volume, and 64 for pan. Now we get down to the part for channel 1: Change volume to 127: 7.38878,130:3,Control change,1,7,127 Change pan to 0: 7.38807,130:3,Control change,1,10,0 Change reverb or chorus (I forget, and don't care) to 127: 7.38678,130:3,Control change,1,91,127 Change reverb or chorus (I forget, and don't care) to 127: 7.35459,130:3,Control change,1,93,127 So now it's confirmed one more time that KMidiMon reveals we are, in fact, transmitting these MIDI controller messages the way we're supposed to be. Now the problem with figuring out this bug is that the only diagnostic tool I have to sniff the MIDI stream shows a MIDI stream that makes sense, but in the past when I have watched my Roland Sound Canvas in real time, I could see the controllers were not being received. Another person on the bug comment thread remarked that he could see... Let's see, QSynth has a message window? Let's try QSynth next then. Repeat previous procedure, substituting QSynth for KMidiMon. This could be a clue, actually. 20:00:29.228 qsynth1: fluid_synth_set_reverb(0.19,0,0.21,1) 20:00:29.229 qsynth1: fluid_synth_set_chorus(3,2,0.3,8,0) fluidsynth: warning: ALSA sequencer buffer overrun, lost events fluidsynth: warning: ALSA sequencer buffer overrun, lost events I got a long string of those. I have no idea what it means though. In the meantime, Dear New User, you're not imagining this problem. We just don't know how to fix it. Maybe we need to introduce an intentional delay in here. Maybe we're sending this out in too fast of a squirt or something. Anyway, we won't get around to investigating this again with an aim to fix it for quite some time I'm afraid. So you'll have to jiggle your knobs upon loading a file to make the controllers work properly. Sorry. -- D. Michael McIntyre |