Tom & Michael: I finally succeeded in reproducing the problem.
The problem does not exist in version 11.11.42 (which is what comes with Ubuntu 12.04). The problem can only be reproduced using the development version (glenfidich). I have attached several MIDI files. The "-a" files are one of the tracks isolated from the original, and the "-b" files are the second of the tracks isolated from the original. The "1.mid" files are the way they were when I originally extracted them, with the channel 2, or 3. The "2.mid" files are from when I exported them after having changed the MIDI channel to 1 (but it exported it as channel 2). The "3.mid" file is the case where I used a setting of "fixed" (instead of "auto"). I noticed that after I changed the channel, the setting went back to "auto". I changed it back to "fixed" and exported the MIDI file, but it still exported it as channel 2 (not 1, as I had changed it to). Again, the problem appears to be only reproducible with the latest version of Rosegarden. - Aere On Fri, 2012-09-07 at 00:17 -0400, D. Michael McIntyre wrote: > On 09/06/2012 11:20 PM, Tom Breton (Tehom) wrote: > > > There has always been a separate conductor track in RG exported MIDI. > > There's the problem then, Tom. > > He wants to get all the stuff on channel n by assigning everything to > instrument n. There is no direct way to set the channel, but choosing > instrument #n with the channel fixed to it ought to do the job. > > Now we apparently export a separate conductor track. I didn't even know > that. (I just never use standard MIDI files, and everything I've done > of any consequence for the past 10 years is in .rg format.) > > The MIDI export logic probably just grabs channels on a first come, > first serve basis and starts with 1 for the first track, which is the > conductor track, then increments from there. The result I'd expect to > see is that we always export stuff to use channel n+1, with n never > attainable unless n >= 2. > > What we could do about that, I can hardly imagine. Maybe just export > the conductor track *and* the first real track in the composition on > channel 1. Maybe. > > (Bear in mind I'm using "end user" MIDI channel numbers where they're +1 > relative to the actual numbers we use internally. 0 is 1, 1 is 2, etc.) > > I think that's the gist of it anyway. Just popping in, and not studying > anything at all. > -- Sincerely, Aere
MIDI-Export-Problem-a1.mid
Description: MIDI audio
MIDI-Export-Problem-a2.mid
Description: MIDI audio
MIDI-Export-Problem-a3.mid
Description: MIDI audio
MIDI-Export-Problem-b1.mid
Description: MIDI audio
MIDI-Export-Problem-b2.mid
Description: MIDI audio
------------------------------------------------------------------------------ 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
