|
|
Post by Stray on Mar 5, 2015 14:07:29 GMT -5
MCU To HUI is a preset that runs in a simple runtime (called MT Player) that converts MCU data to HUI data and vice versa for use with PXT-General (which provides MCU Emulation) and Pro Tools (which doesn’t support the MCU protocol, but does support the HUI protocol). MT Player (with the MCU To HUI preset loaded in it) sits in between PXT-General and Pro Tools and handles the necessary translations. At this point, the translation is incomplete as there isn’t a one-to-one mapping between the two protocols. For that reason, some judgment calls need to be made to determine how to handle certain parts of the mapping to suit Pro Tools workflows. Also, I don’t currently have Pro Tools here (waiting for First to be released) and so I can’t actually test or analyze this very well. These are the reasons that MCU To HUI is currently an alpha release. For some quick background, here is what the MCU looks like. And here is what the HUI looks like. Notice the significant difference in the number of buttons on the two units. I found this very dated document that covers how the actual MCU emulation of the HUI works in PT, but this doesn’t really help my analysis as, again, I don’t have PT here. Also, it’s quite possible that some of the stuff covered in the document is no longer relevant or has changed in current versions of PT. And, finally, there are a lot of somewhat obscure button combinations mentioned in the document. I’m not sure implementing those would even be worthwhile. That all being said, I’m hoping some PXT-General users who want to use it with PT can offer some feedback on the current implementation, what should be added/removed, etc.
BETA INFOIf you’re interested in taking part in the beta you will need Windows or OS X, PXT-General, Pro Tools and an account on this forum. To sign up, please send me a private message and mention which email address you used for purchasing PXT-General.
KNOWN ISSUESAs of v1.0.0a1, the translation is incomplete. |
|
frabo
New Member
Posts: 8 
|
Post by frabo on Jun 22, 2015 8:51:08 GMT -5
Hey Stray,
if you don't have someone for this...
I have osx, protools and a push. but not PXT-General, but I really like to buy and use it, ... if it works with protools.
Have you a demo license for PXT ?
If so, send me a privat.
;-)
|
|
|
|
Post by Stray on Jun 22, 2015 9:33:09 GMT -5
Welcome to the forum. A PXT-General license is required for this alpha (demo licenses aren't available). To be clear though, the majority of the features of PXT-General work perfectly fine with PT. PT doesn't support the Mackie Control, it supports HUI. This alpha addresses that.
|
|
|
|
Post by sicijk on Jun 25, 2015 3:00:08 GMT -5
Hi, this is my 1st message here! Hello all, and thank you nativeKontrol for such fine work!
I am Gigi from Lecce (SouthItaly).
I am really interested in PXT-General even if I just own PXT-Live since three days and I am enjoying it alot.
I am long time PT user but hadn't find a good way to control plug-in parameters for automation.
Only the basic Mixer functions using a Yamaha 01V96 desk.
Stray, are you telling me that with PXT-General I can use Push's touch-sensitive encoders to write automation easily ?
Thanks in advance!
(=gg=)
d^_^b
|
|
|
|
Post by Stray on Jun 25, 2015 18:41:56 GMT -5
Welcome to the forum. No, PXT-General doesn't allow you to utilize the touch-sensitive nature of the encoders for anything currently. That could change in the future.
|
|
|
|
Post by sicijk on Jun 26, 2015 10:36:35 GMT -5
Ok, i see.
but is it anyway possible to control plugins ?
thanks!
|
|
|
|
Post by Stray on Jun 27, 2015 10:40:59 GMT -5
I believe so (the document in my original post seems to confirm that), but I haven't actually tried it myself.
|
|
|
|
Post by maikie on Sept 8, 2015 16:14:42 GMT -5
Hi all,
Is there any progress on testing with Pro Tools or are you in search of Beta testers?
Cheers Maik
|
|
|
|
Post by Stray on Sept 8, 2015 18:00:07 GMT -5
Welcome to the forum. Yes, alpha testers are still needed. Please see the first post of this for info on how to get involved.
|
|
frabo
New Member
Posts: 8
|
Post by frabo on Nov 11, 2015 17:59:02 GMT -5
Hallo Stray,
my first impressions:
great work and a good starting point. I hope you can enhance the features, because push is a nice controller and I’m always looking for a controller for protools.
Btw I have a Frontier design Alphatrack next to me, which can work quite good as a hui controller with protools, but the plugin control is limited and it is only one, but motorized, fader.
If there is something, how I can help to improve the MCU to HUI work, please tell me.
the most important thing for me is to get the encoders working as the faders in protools.
Next would be plugin control !
My other workhorse is a gamepad where I change the buttons with controller mate to keyboard shortcuts. It works very good, but I always miss some shortcuts. Maybe a special shortcuts mode for the push would be nice, look, how many pads we have, hmmm
first short list of faults:
- „Flip“ is not working, no event at the midi monitor !
it is very important, this is the way we can get the v-pot as the fader for leveling !! I gess..
- „Plug-in“ is not working, it changed the push to „sendD“
- „EQ“ is not working, it changed to „SendE“
- „Track“ is not working, it changed to „SendA“
All the best
frank
|
|
|
|
Post by Stray on Nov 11, 2015 22:50:30 GMT -5
Sorry, I don't have the docs or code in front of me currently. However, the names of buttons shown in PXT-General don't necessarily align with the functions the buttons perform in a given application. For example, the button labeled "EQ" in PXT-General may not perform a function having anything to do with EQ in PT. So, much of what you're saying doesn't sound like a fault. Regarding Flip, I'm not positive on this, but MCU to HUI may not utilize Flip or may use it for some otter purpose. The docs, accessible via the "?" button on MT Player should cover that.
If you need further help after looking at the provided docs, let me know and I'll try to clarify it for you tomorrow morning.
|
|
frabo
New Member
Posts: 8
|
Post by frabo on Nov 12, 2015 6:26:15 GMT -5
- However, the names of buttons shown in PXT-General don't necessarily align with the functions the buttons perform in a given application.
ok, but it seems that not all of them are programmed right? Because, "Track" has the same function as "SendA" !?
-Regarding Flip, I'm not positive on this, but MCU to HUI may not utilize Flip or may use it for some otter purpose.
ohoh, don't demotivate me... But I hope you have a vision, how we can use the encoder to control the fader ...?
btw I could give you some infos about the flip button, or other from my Alphatrack in hui mode, maybe a midi monitor could help ?
|
|
|
|
Post by Stray on Nov 12, 2015 9:41:27 GMT -5
ok, but it seems that not all of them are programmed right? Because, "Track" has the same function as "SendA" !? That's correct. The MCU Track button (labeled as Track in PXT-General) is mapped to the HUI's Send A button. FWIW, this is covered in the Mapping section of the manual. But I hope you have a vision, how we can use the encoder to control the fader ...? Yes, as mentioned in the Miscellaneous Buttons section of the manual, Flip performs a faked flip function that (when turned on) allows the encoders to function as faders. Flip doesn't send a MIDI message out as it's an internal function within the translator. |
|
frabo
New Member
Posts: 8
|
Post by frabo on Nov 12, 2015 10:31:23 GMT -5
>>That's correct. The MCU Track button (labeled as Track in PXT-General) is mapped to the HUI's Send A button. FWIW, this is covered in the Mapping section of the manual.<<
sorry, but this is what I don't understand, you have already the send and pan buttons! The six buttons on top right of the push in the MCU labeled with Track/Send/Pan/Plugin/EQ and Instr. They are morphed by the MCU to HUI to Send A-E and Pan as it is described in the manual !
Yes, as mentioned in the Miscellaneous Buttons section of the manual, Flip performs a faked flip function that (when turned on) allows the encoders to function as faders. Flip doesn't send a MIDI message out as it's an internal function within the translator.
Sorry, but this is not working. When I configure a button with "Flip", it lights up after pressing, but the encoders do nothing.
|
|
|
|
Post by Stray on Nov 12, 2015 10:51:02 GMT -5
sorry, but this is what I don't understand, you have already the send and pan buttons! The six buttons on top right of the push in the MCU labeled with Track/Send/Pan/Plugin/EQ and Instr. They are morphed by the MCU to HUI to Send A-E and Pan as it is described in the manual ! It sounds like you understand it perfectly. The encoder assignment buttons of the MCU and shown within PXT-General (Track, Send, Pan/Surround, Plug-In, EQ and Instrument) are mapped to the encoder assignment buttons of the HUI (Send A, Send B, Send C, Send D, Send E, and Pan). As an aside, the images in the first post of this thread show how these correlate. Sorry, but this is not working. When I configure a button with "Flip", it lights up after pressing, but the encoders do nothing. Providing the Scales button is turned off, it isn't possible for the encoders to do nothing. It is possible that PT isn't responding to them however. To better discern that, try using a MIDI monitor outside of PT (such as MIDI-Ox or MIDI Monitor) to monitor the data coming from From MT Player 1. Look at the data the encoders send when Flip is off and compare it to the data the encoders send with Flip is on. |
|
