On Tuesday, April 24, 2012, D. Michael McIntyre wrote: > If you put instrument #3 or #12 or whatever into percussion mode, then I > don't think it should be dumping that stuff onto channel 10. Instead, it > should treat whatever associated channels as additional percussion > instruments, along with instrument #10.
I started to report a lot of problems with the current build, and then I realized I was using my Roland, not QSynth. This can be SO confusing, don't you think? So once I got set up with QSynth, here's what I experienced. 1. New doc with QSynth yadda yadda yadda 2. Highlight track 10. Play. Hear drum kit 1. 3. Highlight track 9. Play. Hear piano. 4. Check [x] Percussion. Play. Hear drums immediately. Nice! 5. Change the program on track 9. Hear drum kit 2. 6. Go back and forth. Kit 1 on 10, kit 2 on 9. This works just fine, Tom. Whatever you're doing down below is not apparent from the surface, and if it behaves like it's working, then it's working. The glitch I described earlier has gone away. Next test: I tried loading a composition, getting it playing, and then repeating the process of changing active tracks and banging around on the keyboard while the transport was rolling. I noticed some lag here, where I sometimes heard a different sound from what I expected for the track I was sitting on. It always eventually fell back in sync after changing tracks a few times. That's mildly disturbing, but I don't think it's a show stopper. Next test: I fired up ZynAddSubFX and loaded an .xmz file, then I loaded the .rg file that goes with it. It went most of the way through before I heard anything funky and disturbing. Eventually the auto channel allocator magic picked the wrong channel for something, and I had to go set "fixed" for that instrument. That took care of the problem instantly. This is acceptable. I don't think there's a lot of point dragging out Aeolus and friends, since the underlying principle is the same in all cases: If you load an old composition for something like this, and you hear wrong instruments, then you need to go set "fixed" for those tracks and all should be well. We just need a FAQ for this, and probably mention it right in the release note. POTENTIAL PROBLEM: It happend with QSynth, and I wrote it off. Then it happened with ZynAddSubFX too. Coincidence? Possibly not. I was playing the above ZynAddSubFX-based composition. While it was rolling, I set up a new track to record, and started recording. The recording worked fine, but ZynAddSubFX froze up and stopped producing sound. The only way out of this jam was to close it out and restart it. Earlier I had exactly the same thing happen with QSynth. It was working fine, and then suddenly it was silent, and it refused to respond to any additional MIDI input, and I had to restart it. Could Rosegarden be doing something funky and unexpected that makes both of these soft synths take a dump? Maybe trying to transmit on channels that are out of range or something weird like that, like a +1 problem? It's just a thought. All in all, except for the weird coincidence of both soft synths quitting on me in the middle of doing something with Rosegarden, it looks to me like this has pretty much shaped up to the point where I'm ready to release it. It would be nice to get some other people testing, since there is so much new stuff at play here, and everybody will try things a little differently. -- D. Michael McIntyre ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
