Great video, I will give this a go! thanks 😊 - BTW, if you use the ‘cc’ option in preset midi out, instead of ‘cc toggle’ option it will work when you press the button once to change the preset. You are sending the cc value and alternating between value 0 and 127 when you use the ‘cc toggle’ option which is why you need to press it twice at the moment, i hope that helps 😊
If you set on midi preset out on the QC - type ‘cc’ then set the cc number as you have it but with the ‘value’ set as 127 instead of the default of 0 then it works (i just tried it with the plugin) 😊 thanks again for all your great videos!!
Thanks so much, used this to figure out using the mission engineering expression pedal in combination with the QC and Gojira X. Set CC absolute / WOW pedal/1/CC#0
I don't think you need to use USB 3 as an output considering you aren't using any blocks in the QC. You can just use Input 1 or Input 2 as outputs in the plugin which will have less latency.
I tried that, but then the signal from the QC is too low. I can push up the input volume on the plugin but I think the tone is slightly better when the signal from the QC is stronger.
Does the +12dB on USB 3 actually do anything? Theoritically it should but I find if you turn it all the way to OFF, it appears to drive the plugin just as hard. Only changes to the IN 1 level make a difference. I'm also using USB Output 3 (from grid) as the Audio Input Channel.
I know what you mean. The signal looks the same, but I hear a big difference in how it sounds though. At least in the Nolly plugin I was recently trying.
@@davlavmusic7070 It makes a difference in Nolly but I only noticed an audible change when the Audio Input Channel is set to Input 1, instead of USB Output 3 (from grid). Which seems odd to me because you'd expect the Input 1 level to be taken from the source, and not be affected by changes to the USB 3 output block level. And if the input channel in the plugin is set to USB 3, you'd expected that +12dB block change to be audible in the plugin. So unless I'm mistaken it seems that they're the wrong way round. Perhaps a bug.
good old audio engineering - exactly the way I would'v done it. probably not the most reliable setup for live-use, though. I will not get a QC before it really has plugin-support. We'll probably have a V2 of the QC before they manage to do it. It's been forever :D
@@Tury1799 Thanks mate! I've seen it, too! Unfortunately not in the market for one of these right now. I totally stopped playing digital and started using my EVH 5150 III basically exclusively. I guess that'll change, as soon as I start recording music again :D
Great video, I will give this a go! thanks 😊 - BTW, if you use the ‘cc’ option in preset midi out, instead of ‘cc toggle’ option it will work when you press the button once to change the preset. You are sending the cc value and alternating between value 0 and 127 when you use the ‘cc toggle’ option which is why you need to press it twice at the moment, i hope that helps 😊
I had tried that but I wasn't getting any result receiving the midi on the plugin. Any thoughts on what to set the plug-ins on the receiving side?
If you set on midi preset out on the QC - type ‘cc’ then set the cc number as you have it but with the ‘value’ set as 127 instead of the default of 0 then it works (i just tried it with the plugin) 😊 thanks again for all your great videos!!
@@ClaireT8124 It worked. Thanks!!
I think you're capable of programming the space shuttle.
🤣
Thanks so much, used this to figure out using the mission engineering expression pedal in combination with the QC and Gojira X.
Set CC absolute / WOW pedal/1/CC#0
I'm attempting to do this in Logic w/ Goj as plugin. Wondering if you might have some insights there, I haven't quite got it working
Another phenomenal video! This will be extremely helpful! Thank you for all the QC love!
Great video though helps a lot!
Nice! Thanks for sharing!
If you change to CC toggle command to the PC it changes the preset with one stomp
I actually was able to get it to work with the CC command.
I don't think you need to use USB 3 as an output considering you aren't using any blocks in the QC. You can just use Input 1 or Input 2 as outputs in the plugin which will have less latency.
I tried that, but then the signal from the QC is too low. I can push up the input volume on the plugin but I think the tone is slightly better when the signal from the QC is stronger.
Does the +12dB on USB 3 actually do anything? Theoritically it should but I find if you turn it all the way to OFF, it appears to drive the plugin just as hard. Only changes to the IN 1 level make a difference. I'm also using USB Output 3 (from grid) as the Audio Input Channel.
I know what you mean. The signal looks the same, but I hear a big difference in how it sounds though. At least in the Nolly plugin I was recently trying.
@@davlavmusic7070 It makes a difference in Nolly but I only noticed an audible change when the Audio Input Channel is set to Input 1, instead of USB Output 3 (from grid). Which seems odd to me because you'd expect the Input 1 level to be taken from the source, and not be affected by changes to the USB 3 output block level. And if the input channel in the plugin is set to USB 3, you'd expected that +12dB block change to be audible in the plugin. So unless I'm mistaken it seems that they're the wrong way round. Perhaps a bug.
good old audio engineering - exactly the way I would'v done it. probably not the most reliable setup for live-use, though.
I will not get a QC before it really has plugin-support. We'll probably have a V2 of the QC before they manage to do it. It's been forever :D
I don't expect any hardware refresh anytime soon. Hopefully the plugin compatibility is around the corner. It's becoming too much of a joke.
plugin-support this week :)
@@Tury1799 Thanks mate! I've seen it, too! Unfortunately not in the market for one of these right now. I totally stopped playing digital and started using my EVH 5150 III basically exclusively. I guess that'll change, as soon as I start recording music again :D
SOON.....