On 06/15/2016 10:40 AM, Abrolag wrote: > On Mon, 16 May 2016 20:39:59 -0400 > Ted Felix <[email protected]> wrote: >> Try the latest with the bank and program checkboxes unchecked and let >> me know if this part is now fixed. It should be. If not, it should be >> easy to fix. > Decided to have a look at this and I can't find any such check boxes - prolly > means I'm looking in the wrong place.
Those are in the "Instrument Parameters" box on the left side. That's where you set the initial bank select/program change/controllers to be sent out on each track when the composition is loaded. Uncheck them and no bank selects or program changes will go out on a track. > My take on this is that we should have the choice of being able to stop > Rosegarden doing *any* initialising of the destination synth(s) but still pass > through any MIDI messages embedded in a file, or sent from and external > source. The idea behind sending this stuff out is that Rosegarden is in control of bank/program/CCs. So, it needs to send out something initially to make sure everything is where it should be for the start of the composition. > Now I appreciate that some older devices may start up in an undefined state > but > no modern ones should, IME, all modern devices start up in a defined but useless state. My P-105 (not an old device at all) starts up with all channels set to play Piano (at volume 100 and pan center). This is useless to me and there is no way for me from the front panel of the P-105 to say "I want channel 2 to be bass and 10 to be drums." So, I rely completely on RG to set up the instruments on each channel. This is the way every synth I have works. What are you using, and how/why is it different? I'd like to run some experiments to better understand what you are getting at here. > so I wonder if a per device initialise checkbox should be > placed in Manage Midi Devices -> Midi Outputs. Something like this would belong in the device file for a specific device. I suspect that you aren't using device files tailored to your synth(s). And this might be why things aren't working as they should. > As for the existing controls would it be practical to make them still operate, > but actually embed the appropriate CCs in a running file? Or is that over the > top? That's what the rulers are for, if I'm following what you are saying. If you want us to record changes to the controller knobs in the Instrument Parameters panel or on the MIDI Mixer as they happen (automation), that's a pretty big feature request. Doable, but will take some time. I think it would be best for you to get me set up so that I can see what you are talking about. It all seems very strange to me right now. It's not how I work with rg at all. Give me a rough list of what I need to do to get in sync with you. I can figure out the details. Ted. ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381 _______________________________________________ Rosegarden-user mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
