Zebra midi control

[mattrobertson]

Hi,

does anyone have any problems setting up a control surface for Zebra?

Specifically

- and cant seem to assign anything to LFO amplitudes, or or user definable mod sources (the midi controller scrolls through the mod sources when assigned rather than the amount of the selected source.

- the osciallator tune doesnt seem to stick to semitones when assigned to a midi controller

Im in Logic 9, and using the logic midi learn function

many thanks

[3ee]

I'm using FL Studio 10 .. and I can't assign most of the LFO parameters as well.

The only thing that seems to be assignable is the the LFO delay.

This is also true with TyrellN6.

[Howard]

Im in Logic 9, and using the logic midi learn function

??? Try the Zebra2 MidiLearn function!

[justin3am]

I think this will become a bigger and bigger issue as more midi devices get their assignment from automation hooks via the host as opposed to interfacing directly with the instrument via MIDI.

I have this issue already with my APC 40, I imagine that more and more devices will work this way in the future.

[Shabdahbriah]

I think this will become a bigger and bigger issue as more midi devices get their assignment from automation hooks via the host as opposed to interfacing directly with the instrument via MIDI.

I have this issue already with my APC 40, I imagine that more and more devices will work this way in the future.

I see that as a severe limitation if not a deal-breaker for future hardware choices, particularly if one were using a host without that "feature", or a Synth in stand-alone mode (which I frequently prefer).

I wasn't aware the APC-40 had that dependancy.

[justin3am]

Not many controllers are completely forgoing traditional MIDI functionality yet but I can see it becoming more common in the future. Even when a controller interfaces with a host via the hosts control surface SDK, the device is still communicating via MIDI, it's just using predefined sysex messages which determine dynamic mapping schemes.

While this sounds potentially limiting, it opens up a lot of possibilities for navigating a software interface directly from hardware.

I agree that it would be silly to develop general purpose MIDI controllers without user configurable controls, but with a purpose specific device (like the APC 40) it makes more sense.

[Shabdahbriah]

Not many controllers are completely forgoing traditional MIDI functionality yet but I can see it becoming more common in the future. Even when a controller interfaces with a host via the hosts control surface SDK, the device is still communicating via MIDI, it's just using predefined sysex messages which determine dynamic mapping schemes.

While this sounds potentially limiting, it opens up a lot of possibilities for navigating a software interface directly from hardware.

I agree that it would be silly to develop general purpose MIDI controllers without user configurable controls, but with a purpose specific device (like the APC 40) it makes more sense.

I have been hot for an APC-40 since they were announced, and was impressed at the time by their 'integration' and its "possibilities", indeed, though I too fret over it going too far in the not too distant future, if user configurable options are preempted. Then too, BOMES midi-translator has always saved me from most of those annoyances.

I currently use three BCR2000's for knobbiness duties, and am content with them.

Thanks for the heads-up though.