Thanks for your reply Dave!
Well, I only tried this (out of curiosity): I installed the “AH Control App” and looked if I could control my Qu-Pac with Mainstage. It partly worked and party not (seemed like Mainstage was able to receive some data but could not send it back to Qu-Pac). Anyway, it seemed to me like I had to spend weeks to get it running (or not). So I gave it up and uninstalled the AH Control App (and one file which this App stored somewhere among the system files – I don’t remember what it was – I did it with the help of “ForkLift”).
So, to make it more clear: I don’t want to use the MIDI functions of Qu-Pac at all.
Even when the AH Control App is not installed (or has been uninstalled), once Qu-Pac is connected to the computer (I’m using Qu-Pac for multichannel recording and playback) it is listening to MIDI via USB. And that’s the problem. Whatever MIDI Control Command “crosses its path” is being immediately executed.
Example:
In my case Logic X sees these MIDI Outputs:
Off
All
Virtual Midi
V-Drums
Roland Fantom X
E-MU X Midi Out 2
QU-PAC MIDI In
If I open a MIDI file containing any MIDI CC’s I have to be very careful not to audition the file first. This would be the ultimate catastrophy and would definitely mess up Qu-Pac.
I have to assign all the track to any outputs other than the one of Qu-Pac and even then there is a possibility that Qu-Pac fetches some unwanted data and goes crazy.
It happened to me numerous times no matter how carefully I “tiptoed” around it.
The best thing would be to get rid of the Qu-Pac MIDI Input all together. But how? Hmmm.
Regards,
RackTangle
Attachments:
You must be
logged in to view attached files.
