Re: [Rosegarden-user] Unwanted CCs - update

2015-02-11 Thread Tom Breton (Tehom)
> On Thu, 5 Feb 2015 20:22:34 + > Abrolag wrote: > > [...] > I've tried attaching the MIDI version of my test file if anyone wants to > have a > look at it and see what happens. > Have looked at your test MIDI and let MidiEvent::print trace it out. Thank you, and also thank whoever created M

Re: [Rosegarden-user] Unwanted CCs - update - !!!AHA!!!

2015-02-11 Thread Tom Breton (Tehom)
> Perhaps I misunderstood your setup - are you reading a MIDI file in, it > contains bank changes, and when you play back they are messed up? Or they > show the wrong banks in the Instrument Parameter Panel? That would make > this code suspect, otherwise I'm afraid I don't see a connection. OK,

Re: [Rosegarden-user] Unwanted CCs - update - !!!AHA!!!

2015-02-11 Thread Tom Breton (Tehom)
> I just had a nose around in MidiFile.cpp - without full hazmat too :) > > At line 1221 you have the start of a section that interprets bank changes. > This > is very risky as almost every synth maker has a different way of handling > them. > > Commenting out both the msb and lsb code appears to c

Re: [Rosegarden-user] Unwanted CCs - update - !!!AHA!!!

2015-02-11 Thread mskala
On Tue, 10 Feb 2015, D. Michael McIntyre wrote: > I was wondering about that, now that you mention it. Controller banks? > Does anything support more than 127 controllers? Are bank changes Controllers have standardized numbers - e.g. 7 is "master volume" - so the main issue isn't really that a

Re: [Rosegarden-user] Unwanted CCs - update - !!!AHA!!!

2015-02-10 Thread D. Michael McIntyre
On 02/10/2015 01:46 PM, Abrolag wrote: > I just had a nose around in MidiFile.cpp - without full hazmat too :) > > At line 1221 you have the start of a section that interprets bank changes. > This > is very risky as almost every synth maker has a different way of handling > them. I was wonderin

Re: [Rosegarden-user] Unwanted CCs - update - !!!AHA!!!

2015-02-10 Thread Abrolag
I just had a nose around in MidiFile.cpp - without full hazmat too :) At line 1221 you have the start of a section that interprets bank changes. This is very risky as almost every synth maker has a different way of handling them. Commenting out both the msb and lsb code appears to cure the proble

Re: [Rosegarden-user] Unwanted CCs - update

2015-02-10 Thread Abrolag
On Mon, 09 Feb 2015 20:30:31 -0500 "D. Michael McIntyre" wrote: > On 02/09/2015 05:10 PM, Abrolag wrote: > > > I've tried attaching the MIDI version of my test file if anyone wants to > > have a > > look at it and see what happens. > > I'm piddling around... > > > The bank changes (CC32) in o

Re: [Rosegarden-user] Unwanted CCs - update

2015-02-09 Thread D. Michael McIntyre
On 02/09/2015 05:10 PM, Abrolag wrote: > I've tried attaching the MIDI version of my test file if anyone wants to have > a > look at it and see what happens. I'm piddling around... > The bank changes (CC32) in order should be: > CH1, 105 > CH1, 105 > CH1, 7 > CH2, 110 > CH3, 105 > CH1, 5 105 1

Re: [Rosegarden-user] Unwanted CCs - update

2015-02-09 Thread Abrolag
On Thu, 5 Feb 2015 20:22:34 + Abrolag wrote: > Just tried build 13868 and can confirm that it now sends the correct data. > > However on *importing* a midi file CC32 values are set as either 0 or 255. > This > is bank LSB and should be settable 0-127. A value of 255 should be quite > imposs