I presume that this is just the difference between working
with a standard, gm-based midi device setup VS a custom midi
device setup where you have drum patches/programs
mapped to midi channels other than 10?
So in the latter case, a channel setting of 'auto' would
not work for you as it is
'have been using 20.12 for a couple of days and all seems good.
Most of the updates don't affect me but I did try out the new marker
stuff and that seems to work fine. One thing that I have noticed in this
and previous versions is that my channel setting of 'auto' on a drum
track does not
'nice and moody! and handy to be able to play so many instruments :o) !
I can't remember if I've shared this on this list before but just in
case I haven't, here's a sample of what I have been able to produce
using this amazing (free!) piece of software plus a Korg M1 and M3.
My version of
Mystery solved!
The Korg-M3-GM device is not used in this composition
but all of the unused RG tracks had defaulted to this device
so RG was sending out a set of PCs for this device after
the set for the EDS device. As both are connected to the
same physical device (midi port), the second set
Ignore my last message. I was mistaken (it was late!)
New finding - RG is sending 2 sets of PCs on loading
this particular .rg file. Firstly the correct set as
configured in RG and then a complete set of channels
1-15 with different instrument settings and these are
overwriting the correct ones
I have tried this experiment.
It looks as if the PCs are being sent on the wrong
port. The connection for M3-INT-EDS is 131 inside
the Midi Manager but kmidimon shows the PCs being
sent on port 130. Maybe you can confirm.
BTW apologies - it was Abrolag who mentioned the
'send PC on play new
That has turned up some interesting findings:
under v16.02 selecting [no port] for the relevant M3 bank
does not send any PCs and nor does switching it back to
the midi port. I see only ALSA ports being subscribed etc.
(filtering other midi messages)
This version send PCs whenever a new segment
:06 AM, chuck elliot via Rosegarden-user wrote:
> > However, the M3 only behaves properly with v16.02.
> > With v17.12 It does not receive the correct instrument settings either
> > from the default studio setup or the composition studio setup when the
> > same composi
-0400, Ted Felix wrote:
> On 07/16/2017 07:06 AM, chuck elliot via Rosegarden-user wrote:
> > However, the M3 only behaves properly with v16.02.
> > With v17.12 It does not receive the correct instrument settings either
> > from the default studio setup or the composit
:
> On 07/15/2017 05:58 AM, chuck elliot via Rosegarden-user wrote:
>
> > instruments do not sound until I manually reset the program.
> > Then, even if I save the composition, the same thing happens
> > when I load it again. Have I missed something?
>
> You missed a le
Dear fellow Rosegardeners,
in all versions since 16.02 that I have tried (16.06, 17.04)
when I load a .rg composition, although all the correct parameters
are loaded into the Instrument Parameter box(es), the correct
instruments do not sound until I manually reset the program.
Then, even if I
11 matches
Mail list logo
