Professional Documents
Culture Documents
Here are a few things that I have done to improve the X-TOUCH's
behavior:
The way I can see the timecode MIDI is to define a virtual MIDI port
in Bome and send the output from Pro Tools to the virtual MIDI port
(into Bome), then have Bome pass that MIDI to the X-TOUCH MIDI
INT port. It is like having Bome sit between Pro Tools and the X-
TOUCH which then can monitor and translate/filter the MIDI
message being sent to the X-TOUCH or simply pass the MIDI thru.
The reverse is true too: set up a second virtual port to connect back
to Pro Tools. Then, commands sent from the X-TOUCH to Pro Tools
can be watched, translated, filtered, or passed thru.
Yes, there is a lot of MIDI chatter when the timecode and meter
data is being sent to the X-TOUCH. Dissecting that might be
painful. Bome seems to handle the load just fine. I've only had
problems when I'm changing the translators on the fly when it is
running doing the translations. I don't blame it for crashing then -- it
reminds me that I am expecting too much from what is already an
excellent tool! Ha!
*name of buttons are the ones from HUI Layout (not the one on the
actual unit).
** "CTRL" on mac = "START" on PC / "CMD" on mac = "CTRL" on
PC
Seems only sends A,B,C can be assigned to the rotary knobs, and
flip does not work at all unfortunately, so sends cant be assigned to
faders. Being able to flip sends to faders is pretty crucial. Also meter
LED's seem to be broken which is a bit of a drag.
Are you saying with HUI, Plugins dont work, and therefore will never
work via HUI into PT? Is plugin parameter control only possible
through MC?
HUI protocol CAN control plug-in but uses some dialog message to
select an insert (plug-in), navigate into pages of parameters (banks
of 8 paramaters), etc....
Also, the original HUI used to have 2 LCD displays (1 for indiviual
track names, another one for plug-in parameters and user dialog
screen) so I don't know how Behringer dealt (or will deal) with the
dialog system (through the indivual track name display I suppose).
Hi,
Here are my 1st impression (I will only talk about HUI mode here,
MCU mode is Off topic). I tested with Mac OSX.8.5 and OSX.9.5 (I
will test OSX.11 later), Pro Tools 10.3.10 and PT12.4.
Positive points :
- very well built (it is a bit taller and far heavier than I thought)
except the jog wheel. Case frame is in metal (only the side panels
are in plastic).
- button are soft and quiet.
- all 3 interface modes are working (MIDI, USB AND Ethernet) for
both HUI and MCU protocol and can be use straight away (no driver
needed on Mac).
- HUI's buttons are pretty well implemented and consistent (leds are
reflecting the actual status of each button and interaction with Pro
Tools is close to perfect)
- possibility to change automation modes track per track (but also
for all tracks, for selected tracks etc)
- the 4 arrows to edit/zoom implementation is great (I will post more
details if you want)
- lots of good surprises (see my own answer to my "01-13-2016"
questions below)
=> including a good interaction with modifiers keys and buttons
- also few disappointement (see negative points below)
Neutral :
- fader are neither very noisy, nor very quite => a motor off option
would be useful (but I found a workaround using hide/show tracks in
Pro Tools if I need to focus on a single track, or to listen to the full
mix without having fader movements).
- metering is working (but sometimes it disappear, I don't know
why), clip leds do NOT work though.
2/ "In" and "Out" buttons are simply displaying the input and output
routing. While it may be useful, it is far less important than
controlling all sends. Maybe Behringer could reallocate Encoder
assignment buttons, and use modifier keys to access to in/out
routing display.
(for example :
- shift+Track => "In"
- option+Track => "Out"
- Track => pan left/right
- all other buttons => Sends A to E
- shift + all other buttons => Inserts A to E
7/ F8 does exactly the same as ESC key : Cancel for sure, but also
cycles through the Edit tool modes =>