From: Julie S <msj...@ya...> - 2010-09-08 21:10:45
|
Hello Aurelien, Answer: ======= Concerning: > > Is there a way to get rosegarden sending only the > events contained in > > the segments on a track? > > > > Thanks a lot. Yes. Say you have 1-16 tracks each assigned to instrument 1 - 16 of a MIDI device. * Select track 1 * In the Special Parameters -> Instrument Parameters (found typically on the left side of the RG main screen) * Remove the check from the sends program change box * Remove the check from the sends bank change box * Repeat for each track Now you should save that file as an RG file to use as a base file, or save it as the default studio file (which should load on each new file created). ... Discussion you may wish to ignore: ================================== Concerning: > > Just to precise, the box called "Send all the MIDI controls > at the > beginning of the playback" is disabled by default in my > version > (packaged version from Debian SID), and enabling/disabling > it jst > doesn't change anything to my problem. Interesting point. I'm certain the intent was to either enable or disable sending of the visible controllers displayed on Special Parameters -> Instrument Parameters for each track that has a MIDI device as an Instrument. But, the reality is that a Controller change and a program / bank change are just a pair of controller changes. Inside RG, we treat these differently, but the actual codes that are outputted to devices are merely a pair of controller number / value pairs (four bytes). I think in MIDI world we also think of program and bank changes as different than other controller changes...but again this is all convention. Therefore, RG reflects in architecture and presentation the MIDI idiom. In my mind, I'm contemplating whether RG should suppress all controller, and program changes and bank changes using that switch, or if we should create a toggle next to that option to in bulk turn off all MIDI program / bank changes as well. The problem I have with creating the other toggle is that we can already toggle these on a per instrument level. You are not the first to have asked this question recently. We've had more of these inquires since I rewrote how these codes are sent. I feel that I fixed a long term bug and that the toggle boxes and sequencing of the sends of controllers and program changes are effective being communicated to devices. They were not so effectively communicated in the past. Now that the more effective code is in place...we should consider if an instrument level toggle is sufficient, or should there be a device level toggle instead or in place of it...or a application level toggle like we have for controllers. ... Our current implementation of what get sent and what does not is not consistent across the GUI. Controller sends are determined by the application level toggle and whether the controller is a "visible" controller, and if the instrument is assigned to a track. Program and bank changes are sent based on if the instrument is assigned to a track and whether the instrument level check boxes are set. Food for thought. Sincerely, Julie S. |