On Wed, 11 Feb 2015 14:22:24 -0500
"Tom Breton (Tehom)" wrote:
> > 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 MID
> 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
> 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,
> 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
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
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
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
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
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
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
On Wed, 4 Feb 2015 20:20:11 -0500
"Tom Breton (Tehom)" wrote:
> > On 02/04/2015 05:49 PM, Abrolag wrote:
> >> Yes tried that. It still sends CC 121 (reset all controllers) and it
> >> sends it at
> >> the start of every segment of every track!
> >
> >ChannelManager::setControllers() appears t
> On 02/04/2015 05:49 PM, Abrolag wrote:
>> Yes tried that. It still sends CC 121 (reset all controllers) and it
>> sends it at
>> the start of every segment of every track!
>
>ChannelManager::setControllers() appears to be the function doing this.
Oh, my. It's right where I wrote:
// Th
On Wed, 04 Feb 2015 17:59:05 -0500
Ted Felix wrote:
> On 02/04/2015 05:49 PM, Abrolag wrote:
> > Yes tried that. It still sends CC 121 (reset all controllers) and it sends
> > it at
> > the start of every segment of every track!
>
>ChannelManager::setControllers() appears to be the function
On 02/04/2015 05:49 PM, Abrolag wrote:
> Yes tried that. It still sends CC 121 (reset all controllers) and it sends it
> at
> the start of every segment of every track!
ChannelManager::setControllers() appears to be the function doing this.
Ted.
--
On Wed, 4 Feb 2015 17:00:52 -0500
"Tom Breton (Tehom)" wrote:
> > Every time Rosegarden starts up, and every time it starts a run from the
> > beginning it sends reset CCs.
> >
> > I can't seem to find a way to stop this - they are not mentioned in any
> > filter
> > options that I can see.
>
>
> Every time Rosegarden starts up, and every time it starts a run from the
> beginning it sends reset CCs.
>
> I can't seem to find a way to stop this - they are not mentioned in any
> filter
> options that I can see.
Sounds like the normal setup stuff.
Have you tried unchecking all the checkboxe
On 02/04/2015 08:03 AM, Abrolag wrote:
> Every time Rosegarden starts up, and every time it starts a run from the
> beginning it sends reset CCs.
>
> I can't seem to find a way to stop this - they are not mentioned in any filter
> options that I can see.
>
> It makes a mess with the new version of
Every time Rosegarden starts up, and every time it starts a run from the
beginning it sends reset CCs.
I can't seem to find a way to stop this - they are not mentioned in any filter
options that I can see.
It makes a mess with the new version of Yoshimi which responds to these
messages and tries
18 matches
Mail list logo
