Yahoo Groups archive

Analogue-sequencer

Index last updated: 2026-04-28 23:15 UTC

Message

Re: [analogue-sequencer] p3 with a g2

2008-05-06 by josh

Possibly the midi ch. for each slot on the G2 is set to the same midi ch. as
it's global midi ch.?
On my NR3 I have slots A,B,C,D set to midi ch 1-4 respectively, and the
global midi ch set to like 12 or something, which receives the performance
changes.
But then again I have my setup much differently than yours it would seem.
Why do you need to turn off local midi control to get FTS thru the P3?
What does your midi signal path look like?

On Tue, May 6, 2008 at 3:23 PM, <jeff@arcosanti.org> wrote:

>
> For a while I've been trying to figure out how to do this maybe someone
> here with a Nord G2 and a P3 can help.
>
> When I set my G2 up so that it no longer has local control and route midi
> thru the P3 so I can use force to scale I get the problem where the knobs on
> the g2's control surface affect all the slots on the G2. So if I have 3
> patches loaded on the G2 and I have the keyboard split so only the upper
> half controls one of the pathes the knobs seem to effect every patch.
> Normally only the patch that's in focus gets controled by the knows. This
> gets especially annoying if you only want to fade out one patch and keep
> another going as the patch volume will affect all of the other patches as
> well.
>
> I'm not sure the p3 is to blame. It could be that the G2 is sending
> control signals on all midi channels. I've also tried assigning different
> midi channels to the different patches as well. That works with the
> keyboard, but I still get the control surface effecting all patches.
>
> I'm using the latest beta os with the memory expansion. Maybe there's a
> way in the G2 editor to only turn off local control for the keyboard but I
> haven't found it yet.
>
> Any ideas?
>
>  
>


[Non-text portions of this message have been removed]

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.