Re: X32 Discussion
You are correct. I totally missed his point. My apologies to Mr. Williams.
You are missing Lee's point.
You are correct. I totally missed his point. My apologies to Mr. Williams.
You are missing Lee's point.
I do the exact same thing as you brother... I do a few "practice taps" before I'm ready to start tapping fo reals. That is not an issue with any other digital desk (that I've been on) or an old school piece of outboard like a TC d2.
Actually, that's a lie! Now that I think about it, I mixed on a soundcraft si somethingorother that had a weird tap reaction as well... It had the same "averaging" feel as the x32.
For example, If I want to tap between a 1/4 note and switch to half note mid way through the chorus of a song, it takes awhile for the delay time to actually change.
I just tried this on the x32 windows edit software, and it did exactly what I'm referring to:
Tapping along with a 120 bpm 1/4 note click, it goes there right away... 500ms. Then change to an 1/2 note tap, and it takes 4 taps to get it to the desired delay time (1000ms). Change it back to 1/4 note and it takes another 4 taps. This would be fine, if it wasn't for the averaging going on where you get 3 delay times between 500ms and 1000ms. 500, then 630, 760, 890 and then 1000. Those steps in the middle really mess with the sound, especially when feedback is involved. And, it should not take a full bar to change the delay time. I want it to change NOW, not eventually get there a bar from now...
Thanks for the reply.
I have to 2 cascaded S16's .. so
S16 1 - Outputs 1-8outs
S16 2 - Outputs 9-16outs
Both seem to take the x32 P16 routing though, not the local IO's
Is there another option I should be look at?
Hi again Jan,
Thanks to you and Dan, I have created two presets - one for small and one for large monitors, and they configure the ouputs correctl;y = YAY - NO MORE WHINE!! Thanks!
Yay, too!
The amazing thing is that you've put up with it this long. I posted that solution here January 2013 if not earlier.
Happy mixing, though!
Dan
while we are on the subject, what's your advice on an elegant way to go from small to large monitors using the user defined keys?
Pauly
<Edit> while we are on the subject, what's your advice on an elegant way to go from small to large monitors using the user defined keys?
Sorry, someone else will have to answer this. I have no clue.
Thinking about it for a second: Wouldn't there need to be a mute component to those keys for it to work? Don't think those buttons have that as an option, do they? They only do one thing, afaik, and you need them to do at least two (turn one on/one off). Or maybe selecting a source would unselect the other source, I don't know.
Maybe a snippet-based solution would work better? Snippets are still in the realm of magic for me, so afaic they can do anything.
How are you doing that now?
Just assigning two outs to Monitor and unassigning the other two outs?
<SNIP>
The advantage of editing away the other channels is that now these snippets will not affect anything else you have going on with the outputs, so if you make a patch change somewhere, the snippets will not affect those changes.
Thanks again Dan,
Ok.. I'll try to take Pers advice which is probably a little over my head but worth a shot eh - I'll post the results.
By the way - Thanks for starting this forum thread Dan - Whenever any of us get in a pickle, it's usually solved by someone. For that matter - I appreciate all the helpful people here .. you know.. the ones like you that understand nobody knows everything!
;-)
Pauly
Then Dan's suggestion to use a snippet will work, actually, if you can save it to a scene or a preset you can save it to a snippet.
Your snippets will look something like this after editing
<SNIP>
After loading into two snippet slots, assign one button to invoke one snippet and another button to invoke the other. Haven't tried assigning snippets to buttons, it doesn't seem to work on the editor, but hopefully it works on the console.
The advantage of editing away the other channels is that now these snippets will not affect anything else you have going on with the outputs, so if you make a patch change somewhere, the snippets will not affect those changes.
Hmmm this is deteriorating, had the launch of our new venue on Friday, with the band "fat white family", great gig. Unfortunately at some point during the gig mute button for channel 2 stopped working which was a bit of a problem as one of the main box was on it (and also on layer 1 snare drum) this is in addition to the sticky button problem on bus sends 1-4 button. Made it quite tricky to mix the gig, but the main problem we now have is that we don't have enough downtime between gigs to send the desk for a well needed repair. This is the second desk we've had and both have had the sticky buttons issue. Next gig is Friday, so in a bit of a pickle. So much for putting all your eggs into a digital basket eh?
Hi Per,
Thanks for putting in the work to type that lot in.
It works beautifully - The only thing I'll add is that snippet files have a .SNP extension.
You guys are great. Everyone. Someone asks a question and it is like a fire department getting a call.
Every day I find something more it can do. I could have save a few bucks on the XENYX CONTROL1USB in my studio using this advice.
I have not found a way to make it brew a K-Cup, but I am still hopeful.
Like I've said before, think of this board as a Swiss Army Mixer.
Hi Pauly,
You're welcome again, only I had nothing to do with starting this thread.
The OP is Rob Spence and it seems to be a continuation of another thread; I wasn't here at that time, but I believe the helpful and generally friendly tone (and probably the earlier thread?) comes directly from Christian Boche, who AFAIK was the first civilian to have an X32 and post at length about it. His willingness to report and his attention to detail, as well as his in-depth answers to questions and looking for answers when he didn't already have them, made this product much more acceptable to the community and thus accelerated its acceptance by people who would otherwise have had no interest in it.
<SNIP>
Dan
PS I've never said "shit" so much in a thread; sorry for the bad attitude. Shit!!
<SNIP>