Forum Replies Created
-
AuthorPosts
-
2023/06/06 at 9:37 am #113214
+1
2023/06/05 at 1:33 pm #113189Yes definitely a +1! This is such a great board, but there are common features that need some rethinking on their implementation because they make the board somewhat unprofessional to work with. Here is another feature with a similar uncommon implementation I am still hoping on and trying to push in the suggestions to hopefully have this solved one day: https://community.allen-heath.com/forums/topic/ducking-sidechain-source-follow-mute-key-feature
2022/09/15 at 4:57 pm #109013Yes, great and easy tool! heard about it in one of your A&H sessions 😉
2022/09/15 at 9:45 am #109007Found a solution, simple fix for me it was, try any midi channel other than 1 as your consoles midi ch.
Messages don’t seem to get through the translation ports on midi ch 1..2022/09/15 at 9:42 am #109006Ok, I’ve found the problem!
It’s a very simple problem within the translator script/ MIDI CONTROL.
It seems like the translator ports simply don’t seem to receive messages on midi channel 1, which was the only midi channel I’ve been using all the time since there seemed
no need to change it.
I just switched the console’s channel to Midi channel 2 (switching DAW control to 3), and everything’s working as expected.Simple fix. I haven’t seen anything in the documentation about not using Ch 1 for translation messages so maybe update this – or midi control.. Keith?
That’s probably the same issue orcascenter had over at https://community.allen-heath.com/forums/topic/trouble-with-midi-translator-and-qlab-midi-messages
cheers.
2022/09/15 at 9:17 am #109005Ok, so I tried the setup on a whole other system.
Exact same behavior, no messages getting through the translator inputs/ outputs ports to midi control.
To me it seems like a faulty translation script but then I shouldn’t be the only one having trouble..?
Anyone else keen to have a test and confirm or deny? With PC running latest Windows 10..
Thanks!2022/09/14 at 11:01 am #108993Thanks Keith, I will!
2022/09/14 at 9:11 am #108989..maybe similar problem here? :
also I’ve kicked all other midi ports out my system but didn’t help
2022/09/14 at 9:08 am #108988…similar problem here. Not using QLab but getting messages through the Translator protocols Inputs or Outputs ports doesn’t seem to work for me either on SQ5..
2022/09/14 at 8:45 am #108987…just had a quick check trying the USB-B connection: same behavior, no difference.
2022/09/13 at 6:54 pm #108978Thanks, Keith.
Yes, I have tried every possible combination of starting and setting up MIDI CONTROL First, chosing virtual ports, starting App.
I usually know my way around Midi Setups.
I try to clarify:
When I choose CC Translator Protocol in MIDI CONTROL and then start any Midi Message App three virtual Ports have been created: CC Translator Inputs, CC Translator Outputs, CC Translator Midi Thru.
If I choose “CC Translator Midi Thru” as the Apps Output all messages get through to the SQ, as indicated in the bottom right corner in MIDI CONTROL and the “reaction” of the SQ to that message.
When I choose CC Translator Inputs (or Outputs) as my Apps Output and send the exact same messages (or the simple CC’s and note on/offs that would be translated for the SQ) they don’t even seem to reach MIDI CONTROL since there is NO indication in the bottom right corner any more and no “reaction” from the SQ of course. As if those two Ports just “swallowed” all data. Change back to CC Translator MIDI THRU and everything’s working fine again.I’ve not heard of before but could other ports from other interfaces and such impede on those MIDI CONTROL Ports? I have quite a few up and running in my system (around 20) but have never had any problem.
I have not tried the USB Midi connection yet, which I will do out of curiosity. But TCP/IP it needs to be for me.
Of course, in the end I can run all messages through MIDI THRU as well, i was just wondering if there’s a fix or something I’ve missed.Thanks for your help!
2021/04/24 at 3:16 pm #100900Yes, I know this feature from yamaha QL / CL consoles and find it to be very useful and not slowing me down at all.
But Mfk is right, having additional info available about the source or destination of a patch would also do the trick.2021/04/23 at 6:47 am #100877I usually enter the patch mode and then do all the patching not having to press “patch” for each individually. And I find it useful having an info pop up stating the connection you’re about to cut because usually in more complex setups one doesn’t have the whole routing scheme in mind. But usually you know what connection you better do NOT change..
2021/04/22 at 11:01 am #100865+1 on that!
2021/04/19 at 5:04 pm #100804Hey Max, thanks.
I know there are several ways as a workaround but coming from the Qu Series I am rather surprised not having the sidechain feature source select implemented in the SQ Series.
In the Qu Series besides other the direct out can feed the sidechain source.And even if running groups as sidechain is a common thing to me a “per channel ducking” is also very common. Using groups or mixes just to use the sidechain properly is blowing resources.
Here is the topic over at general discussion where you can also read why I think this is a key feature missing:– Cheers!
-
AuthorPosts
