Best hardware controller for Zebra

[zerocrossing]

I think this comes down to patch building vs performance. Frankly, during a performance the last thing I want is a million options. What I want is a KORE style of interface (so much so I got it) but I think KORE falls down a bit because the best thing they could think of were... knobs? In 2008 all we get are KNOBS!? Oh yeah, and a few buttons...

Yeah that's one reason I got a VSynth - so my control system is a combination of KORE and the VSynth's 2 DBeams and TimeTrip pad.

Mmmmm Timetrip... I've always coveted one of those babies. I do have the d-beam technology in my Handsonic who's outputs are going through and AirFX and AirSynth so that's something.

[aMUSEd]

DBeams are nice but have one disadvantage which is that they seem to reset the params they are controlling to zero as soon as you take your hand away which means once you've started playing a param you need to keep your hand in place while you play (which is achy and means I only have one hand to play the keyboard). Not found a way round that.

[Cyoon]

I use the Korg Nano Pad for controlling the pads. But ist a bit of a hassle to set them up in cubase..

cheers

[pdxindy]

DBeams are nice but have one disadvantage which is that they seem to reset the params they are controlling to zero as soon as you take your hand away which means once you've started playing a param you need to keep your hand in place while you play (which is achy and means I only have one hand to play the keyboard). Not found a way round that.

Ewww...that is not so good...

I love my Z1 x/y pad cause it has a switch. It can either return to middle, or stay where ever you leave it. I use both frequently.

[aMUSEd]

It doesn't happen when playing the VSynth's own patches - just when used as a midi controller for external stuff - I guess the problem is the VSynth doesn't have any way to "know" the final state of the plugin.

Doesn't happen with the Timetrip pad either - just the Dbeams

[zerocrossing]

DBeams are nice but have one disadvantage which is that they seem to reset the params they are controlling to zero as soon as you take your hand away which means once you've started playing a param you need to keep your hand in place while you play (which is achy and means I only have one hand to play the keyboard). Not found a way round that.

Yeah, that's a PITA, but I never think of it that way. To me it's like a pitch wheel or any other type of control that has a resting spot. It melts in and just is part of the instrument.

I used to have a Korg guitar effect processor that had this spring loaded button so you could lean into it and modulate what ever parameter you assigned to it. It felt amazing. Yeah, you could't park it like a wah pedal, but it felt so nice having to throw your weight into it to get it to work. Felt like aftertouch for guitar. I've wished that someone else would offer something similar, but no dice. Sometimes I think I should get one just to use for that.

[o8o8]

...just to bring something into the discussion that has not yet been mentioned:

what about a controller based on the MIDIBox?

...a quick solution might be a box which rebuilds the (main) components of the different modules available in Zebra2 - so one area for oszillators, one for filters, one for effects etc. ...

...add to this one additional selector, like a fader or one-or-two-buttons to allow the whole arrangement for one module be transposed to another channel or different set of CCs, which in turn allows to address different objects within Zebra2...

...at first i'd think a one-time-onscreen assignement to connect the controls to the software would be sufficient, and, also on first thought, i guess each module might exist a couple of times within one instance of Zebra2...so 6 oszillators shouldnt be a problem...

[aMUSEd]

...just to bring something into the discussion that has not yet been mentioned:

what about a controller based on the MIDIBox?

...a quick solution might be a box which rebuilds the (main) components of the different modules available in Zebra2 - so one area for oszillators, one for filters, one for effects etc. ...

That's exactly how I approached designing my Kore template - it has a separate page for each module so it can also be used in a modular way - for each patch you select the pages that match up with the modules in that patch.

[o8o8]

...adding another link...this time for a MIDIBox-based controller for Ableton Live...

...somewhere there must be a movie that shows Robert Henke presenting the possiblities with his Monodeck...its about an hour long, so i think it must have been on Google-Video...

[o8o8]

...a quick solution might be a box which rebuilds the (main) components of the different modules available in Zebra2 - so one area for oszillators, one for filters, one for effects etc. ...

That's exactly how I approached designing my Kore template

...i hope to be able to upgrade my Lemur to the final of version 2 and then start doing something like this with the Lemur - my hope is: less weight, more flexibility as new modules/modifications of existing modules pop up in the future...

[macsearcher]

bumnp

[Howard]

It doesn't happen when playing the VSynth's own patches - just when used as a midi controller for external stuff - I guess the problem is the VSynth doesn't have any way to "know" the final state of the plugin.
Doesn't happen with the Timetrip pad either - just the Dbeams

The VSynth's DBeam works exactly the same whether its data is used internally or externally. Or I misunderstand...

Whoa - how OLD is this thread?

[ryandfl]

The APC40 works well for me.