I actually have made a start on this proj with the Akai MidiMix.
Also using a laptop mastering a USB powered hub (tail) and the midimix and CQ plugged into the port sockets.
So in this setup, the laptop which I use normally as a DJ app setup for interval music via the USB audio channel on the cq. It has the Bome Midi Translator Pro software running in the timed trial mode for now to experiment.
I cant comment on the Bome box but I fear you still need to pay out for translator pro as well, as included software may not have the same needed functions.
So as far as I have got with trials, you need the trns pro facilities such as multiple bi directional midi connections using the midimix. Mainly because the mute, solo, rec, and even bank buttons illuminate and need the same hex messages returned to illuminate/extinguish etc. as well as sending to the cq. You CANNOT DO THIS ON THE FREE BASIC APP available on `bome website.
I have successfully scripted various trials individually, such as pressing midimix mutes that then illuminale and set the cq first 8 channels for now. I have had banking working as well as a separate trial. Finally banking the sliders.
Once agaun, this is all pie in the sky ideas and trials, whilst separate tasks, combining it all into a practical working package will be a massive challenge that I may feel is just not worth it plus additional cost of Bome MTP.
This task is not for the faint hearted.
You need good knowledge and experience in:-
Midi messenging, raw, hex and the high resolution midi that the CQ and any other dig mixer uses…something like NPDT or whatever acronym it is ???.
You also need to be conversant in logic programming as in spread sheets, algebraic equasions etc but in the Bome style syntax which differs from that of say Microsoft Excel.
Scared yet?
So my overall package overview is…….
Creating all buttons functions with correct illuminations and interactions from either control surface as in the midimix OR direct control on the cq. Mute/unmute can be done on either and the indicators/reactions as should be.
Banking, using the bank buttons on the midimix then providing three usable banks as follows, bank left button on (illuminated)is bank 1 or first 8 sliders, both in is 9 to 16, and right is 17 to 24.
So thats the easy part as is purely LOGIC SWITCHING…an on or an off at either end of the controls.
Sliders however are a variable AND then add the problem that the midimix is NOT motorised. So syncronising the two systems/devices has a whole new set of challenges.
If you do not have a method of sync’ing ech channel slider, as soon as you nudge a midimix slider, the CQ level will jump to that of the midimix. My last attempts at writing logic comparisons and exclusions if not matching ended in tired frustrations of course a few weeks ago. My goal was, usual CQ surface control as normal. Midimix slider value had to match that of the CQ, or a plus, minus window if you like, where it then creates a “Pickup” function, avoiding massive value jumps and probable feed back etc.
Well Im afraid thats it for now. It CAN be done with a bucketload of knowhow and a logic understanding of workflow etc….