I'm stumped figuring out how or why, but Rosegarden is doing something ugly.
I'm starting from an init GS, which is the same as rebooting my synth. All controllers go back to the defaults I stored 10 years ago. I load RG with my standard autoload. My synth flashes "Midi Offline!" which I have never seen before in 10 years. The active track is track 1, assigned to channel 1, no particular program or bank. I start playing the keyboard. The VU meter moves, the IN and OUT lights blink as expected, and the synth doesn't do anything. I have no explanation for this. Something Rosegarden is doing as part of initial startup is putting my synth in a mode where it refuses to play noise. I checked the parameters on its panel, and it's not muted, has a volume of 100, etc., but the test note button doesn't produce noise either. This is very damn strange. So I init GS again. Now I play on the keyboard, and the synth is holding out the notes as though sustain was on. It isn't. The blinkie lights do not reveal an obvious problem. I release the key, and the lights go out, but the notes continue to hold anyway. Hitting the panic button shuts it up. Now I GS reset from here for good measure, so there is no longer any possibility that RG has sent a controller. (I haven't hit play yet.) I continue playing on the keyboard, and the notes are still sustaining for no reason. Now I go into QJackCtl and disconnect RG from the MIDI IN port. About three seconds later, it re-connects automatically. I can't disconnect it and make it stick. I think that's not the behavior we now expect. So I close out Rosegarden, and then manually connect MIDI IN to MIDI OUT with QJackCtl, and play the keyboard. Everything is normal. I start RG back up, and repeat the experience I just described. I can't play the keyboard without these weird sustain problems with Rosegarden as part of the loop, and it always sends this weird thing at startup that triggers the "Midi Offline!" message from my synth. Damn damn strange. If I record something, the synth keeps sustaining everything while I'm playing, but the notes are recorded correctly, and play back without this sustain problem. Damn damn damn *damn* strange. I haven't tried to do anything like this for some considerable time, but my setup hasn't changed. It's possible I have old hardware going south, but since it works fine with Rosegarden out of the loop, I think it *must* be Rosegarden. Even though I can't for the life of me figure out what it could be doing that would break this. Here, let me dump my autoload. Now that I think back, things have been weird ever since I saved an autoload where track 1 was assigned to channel 1, but had the percussion box checked. Maybe it's subtly corrupted. I also have the little tested "Always use default autoload when loading files" option checked. Well, here, I'll turn *that* off first. No change. I do notice, incidentally, that the chorus is coming on when I File -> New. That makes no sense because chorus is at 0 in the autoload for every channel, and chorus is at 0 by default on the synth. I almost never use chorus. I hate chorus, except on clean electric guitars. This makes me think Rosegarden is transmitting initial controllers incorrectly. Maybe a +1 problem or something. What's chorus +1 or chorus -1? Could it be that one of my other controllers is being transmitted as a sustain? Went back to the factory autoload. Now it's trying to talk to my emu10k1 by default. It had a soundfont, and was working, but now it's not making any noise. Not working if I pmidi a file to it either. asfxload -i&&asfxload my_soundfont Now it's pmidi-ing. Now I File -> New and even though "use your own autoload instead of the one in the file" is now un-checked, and I have even restarted RG for good measure, the connections are still set up the way I just set them. IOW, the first device is playing out 64:0 now, not 65:0 as I would expect. It seems to be keeping the old studio. Or this is a side effect of being aware of external ALSA MIDI connection management. Close out RG. Nothing MIDI connected to anything now. Re-start. Now it's playing out 65:0 as expected. No sustain problem here. Power off my synth. Power on. Re-connect so that the first device is once again going to 64:0 (to my Sound Canvas if that wasn't already obvious). Play notes, and the sustain is on again. So this is only affecting hardware MIDI out. I still don't see how it could be Rosegarden, but it's still nevertheless true that this doesn't happen if I close out Rosegarden and connect the hardware IN to the hardware OUT in QJackCtl. I'm stumped. I sure can't use it like this though. Kernel/ALSA issues are probably beyond consideration. This isn't just a kernel rolled to STG specifications, but the self same kernel tarballed up and moved over here. I just checked md5sums to confirm this. I guess there's a chance my 10 year old Sound Canvas is about to give up the ghost. Why does that strike me as less likely than some new Rosegarden bug? Sorry you had to plod through all this, because I'm too lazy to go back up and try to summarize my findings into something more succinct. -- Michael McIntyre ---- Silvan <[EMAIL PROTECTED]> Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/ http://rosegarden.sourceforge.net/tutorial/ ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
