[MbirameParticipant]

Thanks everyone. We are in the midsts of SxSW festival here in Austin, and we have five shows over the next few days. I’ll be able to take a closer look at this after this coming week, and I can change settings around the input stage as well then if needed. For now, I just boosted the fader on the specific Mix outputs and that at least gave me some more signal.

[MbirameParticipant]

<quote>Don’t forget to set your mixes to pre-fader</quote>

I’m going to assume that they are set that way as all the mix outputs are independent of the LR fader.

I’m not concerned with the levels that are going in to the Mixer from the USB-meaning that whatever they are I am fine with…..What I need to do is to keep whatever levels those are going in to be the same that they are going out of the Mix outputs.

What’s happening is that I have already mixed all the in-ear monitor mixes the way we want them, but then we use remaining mix outputs to send audio to the FOH. So some of the tracks are coming from the USB->QU-16 and then they are feeding the in-ears (levels are good) and feeding out the mix outputs -> (levels are really quiet). For now I just boosted the faders on the mix outputs that are going to the FOH, but they are all the way up so it makes me think that there is some gain stage issue somewhere along the way that I have messed up…and right now I’m not able to really make any changes to input levels because I don’t want to mess up in-ear mixes.

My question is: whatever level the signal is, if I have it set to 0db on the input gain, does that mean that it is not boosting or attenuating that signal, and then on the Mix out if I again have the fader set to 0db, shouldn’t the signal pretty much remain at unity?

[MbirameParticipant]

That worked great-thanks! I hadn’t worked with libraries before.

[MbirameParticipant]

ok. Thanks guys.

What happen to the extra 8 inputs on the 2412 when plugged in to a QU-pac? Am i understanding correctly that the maximum number of INPUTS for a QU-pac would be all the inputs on the QU-pac plus the inputs on a AB168, BUT the full number on OUTPUTS would be with a 2412?

In other words, there is not optimum external box that will give you both max inputs and outputs without having 8 unusable inputs?

[MbirameParticipant]

Yeah, the GS2 will not work for my needs. All the controllers I have seen have serious limitations-enough of an issue to not be worth the money in my opinion. The only controller that really does everything I want is the Nuage which would cost me $24,000 for a master section and fader unit. I’m not willing to pay the cost of a downpayment for a house on a controller at this point, so I think I’m just going to go with a little single Presonus Faderport since it gives me transport as well as a fader for automation (covers about 80% of my control surface needs) plus the single user assignable button will let me change monitors in Cubase’s control room. Then I can use the $23,850 that I save towards outboard gear. Ha!

[MbirameParticipant]

Yeah, the thing that appeals to me about this board in particular is the midi controller aspect. It seems like a great combo of getting a bunch of analog pres and then being able to do your DAW mixing with the controller. I was hoping to find enough users out there to get a clear idea of real-world use of the board as a controller, but user reviews are pretty sparse it seems. If I was going to go for the board purly for it’s analog side, I’d probably go for an older large format console for that price.

I use Cubase, and it’s a shame there aren’t really any mid-price controllers that seems to work well. The Eucon stuff is good but has some serious limitations and the Nuage looks incredible, but I’m not willing to pay the price of a house downpayment to get one.

[MbirameParticipant]

on further review, it looks like they are both discontinued. Shame-it’s an awesome looking board!

[MbirameParticipant]

Hi Andreas,
Thanks very much-it does clarify things! I did manage to finally get things working today after a full day of tweaking on it. On stage, I am primarily using Ableton to send all the midi information to the QU-16, so I did come across a few interesting issues that I had to overcome:

There were a few weird quircks that I had to deal with by using one macro knob in Ableton to control whether I was adjusting the L/R or the Mix control, but once I wrote a little Applescript to work some magic, I finally got it working. Now that I’m working with the NRPN a bit, it seems like you could really make a deep controller for your DAW (much deeper than what is currently offered) and maybe rival some of the higher-end controllers. I wonder if track select would change the NRPN value of the eq that is being tweaked for example so that you could select a new track in your daw and use the focus would switch so you could use the eq based on what track you are on.

[MbirameParticipant]

I am using a Max For Live plugin in Ableton right now to send NPRN out just to try and create the message I am needing to test before I deal with the foot pedal. I am having a hard time reconciling what the QU-16 manual is saying vs what NPRN signals seem to be coming out. For example, the manual says I am sending something in this format:

BN, 63, CH, BN, 62, 17, BN, 06, VA BN, 26, 07
Where VA –inf to +10dB = 00 to 7F, 0dB = 6B

I do not understand where the 63, 62, 06, and 26 above come from, as my limited understanding of NPRN, is that the center number for the NPRN message would be 99, 98, 06 (matches), and 38. Indeed, that is what the M4L patch sends out as well.

I also have no idea what “BN” is referring to above and I don’t see it anywhere in the manual.

What I am sending out of the M4L patch is this message:

176 99 1 (signifying channel one?)
176 98 17 (signifying the fader of that channel? The”ID” that the manual talks about)
176 6 0 (course control change, so this is the Data MSB I think? I have this at “0” for all the way down).
176 38 0 (Data LSB again at 0 so that it puts the MSB all the way down)

Then for full fader up (to 0db) I am sending:
176 99 1
176 98 17
176 6 107 (0 db)
176 38 107 (to push the MSB all the way up)

Does this make sense? Am I doing this correctly? I won’t be in the studio until tomorrow to test this, but I’m a total newbie with the NPRN stuff…

AH!! OK-I just switched my Midipipe to display HEX instead of Dec, and so not I am seeing 63, 62, 06, and 26. It also cleared up what the BN means-it was in HEX and was refering to the midi channel being sent. The only area of confusion I have now is that I’m not sure if the “ID” written in RED in the manual is in HEX or Dec. But I can check that in the studio tomorrow….wish me luck!

[MbirameParticipant]

Awesome! Any idea on how to achieve this (relatively)simple task? Because this makes no sense to me:

Attachments:

You must be logged in to view attached files.

[MbirameParticipant]

ok-I got it sorted. I had to turn on Output Patch->Block on Global Filters after setting the routing the way I needed it to be. Now scene changes will not reset the routing.

[MbirameParticipant]

Thanks. I’m seeing my problem. I thought I had set that USB Audio routing correctly, but as scenes change, that routing is going back to the default. I have to dig in to just figure out how to keep that from changing. Probably some “safes” thing. Thanks again.

[MbirameParticipant]

I wanted to repost as I found that my posted solution didn’t exactly meet our needs. With the solution I posted, the mix settings for the monitor mixes were not changing per scene.

So in order for this to work (for my needs), in step #6 above instead of “Safes->All” I needed to do “Safes->LR”.

Basically, I have all of our “FOH” mix outputs going all the time-whether I am in “No FOH” or “FOH” mode except in “NO FOH” mode all those channels are going both to their dedicated mix outputs AS WELL AS the LR. But then when I am in “FOH” mode, I am muting the “LR” output of the channels that will now only be going to their respective mix outputs.

[MbirameParticipant]

Using Safes->All is the answer.

Since a clear walkthrough hasn’t been posted to resolve this issue, I’ll post it here in case someone comes along in the future needing to do this. Here are the steps I take:

As Andreas mentioned, first I created a scene with the routing that I need when there is a FOH and saved it as “FOH”. I created another scene with the routing I need for no FOH and called it “no FOH”.

So here’s the steps:
1) turn on the mixer. push “sel” button for channel one so you can view your current routing.
2) push “routing” button so you can view the current routing. This just lets ye see if what you are trying to do is working.
3) push “scenes” button.
4) choose FOH or no FOH depending on your needs. load it up.
5) Push “routing” button and you should see the different routing that you are needing.
6) Push “scenes” button then “Safes->All” This will now mean that all the other scenes you select will be able to override the current routing.
7) You can check this by selecting a scene that would normally have a different routing and then pusy “routing” button to check.

I hope this helps someone someday. It helped me!

[MbirameParticipant]

Yeah, I looked at the manual and I don’t find the short descriptions very understandable:
Output patch (Sockets, Qu-Drive)
-what is a socket? Is that the XLR outputs do is THAT the routing?

Or:
Mix sends (Lev/Pan/Assign/Pre)
-in this case it seems like this means any level changes from scene to scene will not register.

[Author]

Posts