Synth-DIY Yahoo! Groups Archives

Local Off - how?

2019-02-10 by Florian Anwander

Hello,

I want to set my Chroma Polaris to local off. The keyboard should send
MIDI-events, but the synth section should react only on events from the
MIDI-input. At the moment it does not matter, how CC's from the panel
are handled, as long as the panel sliders still act directly on the
synth section.

I tried to understand the description on page 86/87 of the owners
manual, but I have to admit, that I did not get it. I also did not want
to try it, and then find me with an unusable synth.

I really would appreciate if some one could explain those functions more
clearly.

Best regards
Florian

--
http://www.florian-anwander.de/

Re: [chromapolaris] Local Off - how?

2019-02-10 by David Clarke

> I want to set my Chroma Polaris to local off. The keyboard should send
> MIDI-events, but the synth section should react only on events from the
> MIDI-input...

Relative to the manual reference, LF_interface Controls

1) Whether the main instrument/link instrument/sequencer should receive 'local' keyboard events

2) Whether main instrument/link instrument/sequencer events should go out the Chroma port

3) Whether MIDI In messages go to the main instrument/link instrument/sequencer instrument

4) Whether main instrument/link instrument/sequencer events should go out the MIDI port

Local Off effectively means 'disconnecting the local keyboard' from the local sound generating hardware so:

If you want MIDI messages to be sent, then you want group 4 on.

If you want MIDI messages to be received (to allow events for the local synth to be played), then you want group 3 on.

If you DO NOT want the keyboard to directly 'play' the local synth, then you want group 1 off.

(Unless you have something connected to the Chroma port, you don't care about group 2).

So - if you want Local Off you generally would want:

Lower Function, Interface 1, 2, 3 OFF

Lower Function, Interface 4, 5, 6 OFF

Lower Function, Interface 7, 8, 9 ON

Lower Function, Interface 10, 11, 12 ON

> … . I also did not want
> to try it, and then find me with an unusable synth.

Generally speaking, anything you change in the standard selections can be 'undone' (e.g., you won't end up with an unusable synth).

Note - if you turn local off, then if you want the Polaris' keyboard to 'play' the Polaris, something external will need to echo back the MIDI traffic.

David Clarke

Re: [chromapolaris] Local Off - how?

2019-02-11 by Florian Anwander

Hello David

thank you for the detailled explanation. With your words the things
become understandable (the wording "...switch is toggled..." in the
manual would have been useful if there had been a graphic of the routing
with thecorresponding "switches").

> Note - if you turn local off, then if you want the Polaris' keyboard
> to 'play' the Polaris, something external will need to echo back the
> MIDI traffic.

That is how I plan to use it. I want to insert a Roland SH-01a as
step-clockable sequencer in the MIDI stream.

Florian

--
http://www.florian-anwander.de

Re: [chromapolaris] Local Off - how?

2019-02-14 by Florian Anwander

Hello David,

so I did my gig with the Chroma, but I was experienced, that "Lower Function, Interface, 1 -> Off" does not switchoff the keyboard only, but also the the sliders! Apparently the sliders are considered as a separate controller.

Florian

Am 11.02.19 um 00:32 schrieb 'David Clarke' ac151@... [chromapolaris]:

> I want to set my Chroma Polaris to local off. The keyboard should send
> MIDI-events, but the synth section should react only on events from the
> MIDI-input...

Relative to the manual reference, LF_interface Controls

1) Whether the main instrument/link instrument/sequencer should receive 'local' keyboard events

2) Whether main instrument/link instrument/sequencer events should go out the Chroma port

3) Whether MIDI In messages go to the main instrument/link instrument/sequencer instrument

4) Whether main instrument/link instrument/sequencer events should go out the MIDI port

Local Off effectively means 'disconnecting the local keyboard' from the local sound generating hardware so:

If you want MIDI messages to be sent, then you want group 4 on.

If you want MIDI messages to be received (to allow events for the local synth to be played), then you want group 3 on.

If you DO NOT want the keyboard to directly 'play' the local synth, then you want group 1 off.

(Unless you have something connected to the Chroma port, you don't care about group 2).

So - if you want Local Off you generally would want:

Lower Function, Interface 1, 2, 3 OFF

Lower Function, Interface 4, 5, 6 OFF

Lower Function, Interface 7, 8, 9 ON

Lower Function, Interface 10, 11, 12 ON

> … . I also did not want
> to try it, and then find me with an unusable synth.

Generally speaking, anything you change in the standard selections can be 'undone' (e.g., you won't end up with an unusable synth).

Note - if you turn local off, then if you want the Polaris' keyboard to 'play' the Polaris, something external will need to echo back the MIDI traffic.

David Clarke

Re: [chromapolaris] Local Off - how?

2019-02-14 by Florian Anwander

Am 14.02.19 um 22:52 schrieb Florian Anwander:

> ...but I was experienced, that...

please ignore the "was" - silly cut'n'paste error...

Re: [chromapolaris] Local Off - how?

2019-02-15 by David Clarke

> so I did my gig with the Chroma, but I ...experienced, that "Lower Function,

> Interface, 1 -> Off" does not switchoff the keyboard only, but also the the sliders!

> Apparently the sliders are considered as a separate controller.

The sliders should behave in a manner similar to the keyboard.

Specifically - you are disabling 'local' control. So - that means that local keyboard keys won't go to the sound engine, nor will local panel slider movement.

That said - if you have the other settings on, BOTH settings (keyboard and sliders) _can_ go out over MIDI. (You can confirm this by monitoring the MIDI data stream from the Polaris).

So - if you have an external device configured to echo MIDI data back, then you will still have slider control over the Polaris.

E.g., key and controller data will be produced, will not 'locally' affect the Polaris, will go out over MIDI. If that MIDI stream comes back into the Polaris, then the Polaris will play both the notes and the controllers (sliders).

Note - above I said that both data elements _can_ go out over MIDI. There are other settings that can come into play too.

Specifically - there is a separate setting that controls whether 'Panel' data (e.g., sliders) will be generated.

If you are seeing that note data is set out via MIDI but slider data is not, then then please check the Lower Function, Cassette settings. You will want specifically to look at setting #8 - this is the MIDI Panel Switch - and you will want this turned on/enabled for slider data to be set out via MIDI.

David Clarke