On Sun, 23 Jul 2017 18:16:14 +0100
chuck elliot via Rosegarden-user wrote:
> 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 dev
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 were
[Resending because this hasn't appeared on the user list. Sorry if
duplicate...]
On 07/20/2017 12:15 PM, Ted Felix wrote:
Do you have two devices connected to the same port?
From digging through the .rg file, it appears that you do:
Korg-M3-GM -> "20:0 E-MU XMidi2X2 MIDI 1 (duplex)"
Ko
On 07/20/2017 07:37 AM, chuck elliot wrote:
v16.02 is also sending out 2 sets of PCs on load but they
are in the opposite order (correct set 2nd) so this explains
why the piece plays properly under 16.02...
Do you have two devices connected to the same port? I noticed that
you have one devi
On 07/20/2017 07:15 AM, chuck elliot wrote:
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 in the M3.
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 in
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 segmen
On 07/18/2017 07:32 PM, chuck elliot wrote:
That has turned up some interesting findings:
Indeed.
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 mid
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 i
On 07/18/2017 05:36 AM, chuck elliot wrote:
It seems that BS/PCs are sent out on load (v17.12) and my M1 responds to
these correctly but for some reason the M3 doesn't receive them.
I haven't been able to confirm this using kmidimon because loading
a file resets the internal connections and disc
It seems that BS/PCs are sent out on load (v17.12) and my M1 responds to
these correctly but for some reason the M3 doesn't receive them.
I haven't been able to confirm this using kmidimon because loading
a file resets the internal connections and disconnects kmidimon.
Is there a way to load a fi
On Mon, 17 Jul 2017 23:08:37 -0400
Ted Felix wrote:
> On 07/17/2017 07:12 PM, chuck elliot wrote:
> > so it looks to me that under 16.02 RG sends out program change
> > messages according to what's set up in the studio every time
> > you press PLAY.
> >
> > Under 17.12 RG does not send out progr
On 07/17/2017 07:12 PM, chuck elliot wrote:
so it looks to me that under 16.02 RG sends out program change
messages according to what's set up in the studio every time
you press PLAY.
Under 17.12 RG does not send out program changes when you press
PLAY...
I've confirmed this. 16.06 is the f
so it looks to me that under 16.02 RG sends out program change
messages according to what's set up in the studio every time
you press PLAY.
Under 17.12 RG does not send out program changes when you press
PLAY...
Chuck.
On Sun, 2017-07-16 at 11:25 -0400, Ted Felix wrote:
> On 07/16/2017 07:06 A
ok - under v16 I can see correct program changes being sent out while
playing the composition (piping M3 bank through kmidimon).
under v17.12 I am not seeing any program changes being sent out while
playing the composition and wrong instruments are sounding
Chuck.
On Sun, 2017-07-16 at 11:25
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 composition studio setup when the
same composition is loaded.
Try rewi
Having dug a bit deeper the problem is more subtle.
I am using a Korg M1 and a Korg M3.
The M1 seems to behave as it should with both v16.02 and v17.12.
The default studio sends the correct instrument settings to the M1
and these are correctly overwritten by the composition studio when it
that is
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 lengthy back and forth where Ted tried to sort a
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 save
19 matches
Mail list logo
