Please let me know if I should start a new post instead. Not sure whether I am hijacking this thread (not my intention) by posting the following. I have an Icon Platform M+ which uses the same MIdi controller messages as the X touch one and do not have any issues with midi remote - the same script would work so far as the fader is concerned with both controllers (I know I’ve looked at the midi remote scripts for both). Another considertaion is the midi sent back to the X touch one - is it connected to the correct port - nope scratch that, you said it moves with the midi track so it is clearly connected correctly. Hmm, now that I think about it you should find moving the software fader on the screen returns to the same position if its not setup correctly (it’s not unlikely to be the controller). There’s several ways the Write automation can be performed so perhaps re-check. Just noting that behaviour sounds like you have Read automation enabled but not Write and when you touch the fader it disables the motor then when you release will immediately return to the previously recorded position. I hope I have explained it a little better and if you can offer a solution I’d be most - sure you got the automation Write setup the way you are expecting it to work? You can imagine how tedious this becomes with bigger projects of 100 tracks upwards. If I then want to work on track 19 I would need to press the “bank advance” button 3 times as track 19 would be in the 3rd bank. ![]() Should I wish to go back to work on track 6 I would need to press the “bank reverse” button as track 6 is in the previous bank of 8. After doing this I can once again use my mouse to select any tracks from 9 – 16 and the X-Touch One will respond accordingly. If I then decide to work on track 9 and I select it with my mouse the X-Touch One does not respond unless I press the “bank forward” button. If I use my mouse so select any track from numbers 1 – 8 the X-Touch One will immediately adjust the powered slider and other controls to match the settings of that selected track. Therefore, due to the Mackie protocol my X-Touch One only “sees” tracks in banks of 8 tracks or less.īy way of example, imagine I have a project with 21 tracks, and I have my X-Touch One connected. From what I have learned the Mackie protocol can only see 8 tracks / channels at a time. Ok so now I’ll do my best to explain what’s happening. Except the X-Touch still doesn’t work.Thanks for your kind offer, it’s appreciated. But if the X-Touch is off at launch then the Mackie In & Outs will show as “not connected.” Then if you turn the X-Touch on, the Mackie device will change its In & Out to X-Touch. The X-Touch uses the Mackie device and if it is on when launching Cubase then the MIDI In & Out for the Mackie device will be the X-Touch and all works as expected. Meanwhile the QC worked as expected throughout. Then if I plug the AI in it does not cause the AI device to show up in Remote Devices and of course it doesn’t work. In Remote Devices the CMC-AI device doesn’t even show up. I unplugged the AI before launching Cubase. Just did a little test and that seems to be the case. ![]() I always assumed that it was because of it using a Remote Device. ![]() Perhaps initially you launched Cubase and then powered up the X-Touch rather than the other way around?Ĭubase should recognise newly connected MIDI Device when Cubase is running.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |