MIDI In

Your Woovebox can receive MIDI notes and messages via wireless MIDI over Bluetooth, and via physical MIDI (hardware revisions 15 B2 and up, including all SE and Pro models).

Please note that the required circuitry to allow of a physical MIDI input is not available on earlier hardware revisions (15, 15B, 15B1). On these earlier hardware revisions, MIDI input is limited to Bluetooth MIDI only.

To enable physical MIDI In for your song, on its GLob page, set 9/A1/Md.Pt to "Out".

Your Woovebox responds to incoming MIDI data in two distinct modes, selectable by 10/A2/Md.In;

• "Auto"; when editing tracks (e.g. on the 'Seq' page and any of the subsequent pages), any incoming MIDI messages (notes, controller information) regardless of their original MIDI channel are directed to the active track. This behavior allows you to quickly switch sounds by switching active tracks on the Woovebox itself, rather than having to change MIDI channels on your controller. This allows you to use your Woovebox as a performance sounds source for a MIDI connected input device. It also allows you to perform sound design quickly and easily. When using any other mode (Live, Song), your Woovebox acts like a regular 16-part multi-timbral synthesizer and sound module. Incoming MIDI is played on the track (1/Cd-16/A8) that corresponds to the incoming MIDI channel (1-16) information.
• "1-16"; the MIDI channel your controller is broadcasting on is not ignored, and always maps channel 1-16 to 1/Cd-16/A8. Your Woovebox always acts like a regular 16-part multi-timbral synthesizer and sound module.

Track 1/Cd allows up to five notes polyphony, while the other tracks are monophonic. Track 1/Cd - on the Seq ('Sequencer') page exclusively - also detects incoming chords (via MIDI IN), briefly displays them, and makes sure that chord is used next time you program a step using write + key 1-16. Paraphonic tracks will only sound "correct" if the playing chord's root note is played.

To make better use of your Woovebox' more advanced sample playback capabilities, sample kit tracks (e.g. tracks with 'bEhv/'traK bEhv'/'track behavior' on the under 7/hh on the 'GLob' page set to 'SMPK') have subtly different sets of the 16 kit's slices spread over the keyboard;

• notes before C4 play the slices in reverse
• C4-F5 play slice 1-16 as normal
• the next 16 notes play slices 1-16 as normal, but with PLFO trigger set (see PLFO conditional)
• the next 16 notes play slices 1-16 as normal, but with ALFO trigger set (see ALFO conditional)
• the next 16 notes play slices 1-16 as normal, but with FLFO trigger set (see FLFO conditional)

Your Woovebox responds to note velocity, and responds to both "velocity 0" and note off messages to turn off notes. Your Woovebox also responds to filter cut-off (CC#74) and pitch bend (+/- 2 semitones range). The latter responses are temporary (for performance purposes) and are not permanently stored anywhere. Any automation (by song fragments or live scenes) will also override these temporary "performance" settings. E.g. to permanently change the filter cut-off frequency as part of a patch on a track, please change 'Cut.F'/'Cut FrEq') under 2/bS on the 'Fltr' (Filter) page of the relevant track.

Your Woovebox further responds to CC#75, which allows for filter automation to be temporarily negated (turn to full/127) or applied again (turn to 0/off). This is useful for adding live filter tweaking to a performance;

• Make sure you set CC#75 to 0 (the default value) at the start of your song or performance.
• Off/0 for CC#75 is always the natural position to finish knob performances on (but not mandatory!).
• A programmatically closed filter can always be opened using CC#75
• A programmatically fully opened filter cannot be closed using CC#75

Note and chord programming workflow enhancements

On a track's "SEq" page, incoming MIDI notes or chords are detected and automatically placed in the programming buffer. This means that you can play a note or chord on a connected keyboard, and then program it directly into a step as usual, by holding write and pressing the 1-16 key corresponding to the step where you want the note or chord to go. This mechanic works with any connected regular Bluetooth typing keyboards as well.

Avoid ground loops and long cables

Please note that in some cases, ground loop issues may arise if powering both your Woovebox and MIDI sender/receiver using the same USB power source. in In such cases, physical MIDI IN and/or OUT may not work reliably (or at all). To solve this, run your Woovebox off its internal battery, or run the two devices off of different USB power sources. Please also avoid very long MIDI cables, as they may attenuate the signal too much, potentially causing drop-outs in the data stream; this may result in hanging notes, or missed controller messages.