previous by dateindexnext by date
previous in topictopic listnext in topic

Subject: Re: [chromapolaris] MIDI issues

From: Robert Stewart <bob@...>
Date: 2014-09-09

OK...

Had a chance to have a quick look at the Polaris, while the client was having his lunch.

Yes I can turn the immediate local control on, and off.

However, with 1-6 off, and 7-12 on, I'm still getting either double triggering (On Note On, and again on Note Off), or the note holding and not releasing (seems to depend on what patch I'm on.

Also I loose all editing/patch change control from the keyboard.


The client purchased the Polaris via Ebay, and it's going to need some work doing on it.
It's currently in his studio, but I'll be able to delve into it in more detail towards the end of the week with any luck.

Pretty sure this is all down to various settings.



On 07/09/2014 23:39, 'David Clarke' ac151@... [chromapolaris] wrote:
 

> That's all three LEDs off ya? 1,2, and 3

Yes, correct. These control whether the local controls (keyboard,
sequencer, etc.) will/won't send data to the internal sound generators
in the Polaris. So - if you turn those off, hitting the keys won't
trigger the Polaris to sound. You can test that without any MIDI
attached, just to confirm you're seeing the expected behaviour (e.g.,
lights on, keys make sounds - lights off, keys don't make sounds).

If you're not using the Chroma interface (you're probably not) then
settings 4-6 don't matter.

Settings 7-12 controls how the system handles MIDI In/Out.

So - for what you describe (and for simplicity of the other settings)
I'd expected:

LF - Interface: 1-6: off, 7-12: on

There are other settings that can also come into play - but those will
only adjust what 'sort' of MIDI data is sent (and on what channel,
etc.) - so I'd first look to confirm you can get the keyboard to not
trigger the local Polaris - and then go from there. (E.g., quantify
exactly what is/isn't being seen vs. what is expected/desired).

Let us know how you make out.

David Clarke