X32 Discussion

[Per Søvik]

Re: Rerouting aux inputs to other channels

Forgive me for my laziness, but a question arises. I want to route the aux in 3&4 inputs to channel 13 & 14, & the aux 5&6 inputs to Channels 15 & 16. How might I accomplish this?

You just do it 8)~~

Simply go into the config tab on each of the channels 13-16 and select the auxes as source

 

[Lance Richens]

Re: New scene system in 2.0

Thanx Buddy....

 

[Eric Eskam]

Re: New scene system in 2.0

A quick question for those playing around with V2 - have they sorted the mute group behaviour yet? i.e. added an option where a channel mute will always override a mute group, rather than the current version where a mute group always takes priority?

I sincerely hope so, but don't see it mentioned in any release notes anywhere

 

[Joe Sanborn]

X32 wiki

Dear All,

We are excited to announce that we have released the public version of the Official X32 Wiki.

It currently contains the full version of the X32 manual. If anyone is interested in becoming a contributor, please send an email to our Product Specialist team at [email protected]. Note that while registered users are able to add to the “discussion” areas of each page, they will have to be approved in order to edit and contribute to pages.

We look forward to the X32 WIKI becoming a dynamic resource for all X32 users.

The URL for the X32 Wiki is: X32 Digital Mixer Wiki

Thank you for your support!

 

[Per Søvik]

Re: New scene system in 2.0

I'm not understanding what a snippet actually consists of.

A snippet is a small part of a scene file. If you remember me writing about incomple or partial scene files and how they could be used, this is the same principle, but actually supported in full by the desk.
A scene file consists of 2050 lines, each line setting one parameter (and sometimes a group of parameters), and contain settings for all the recallable parameters. Which ones that get changed when the scene loads depends on the safes settings.
A snippet will only contain some lines, how many and which lines depends on the setting when the snippet is saved. When the snippet is activated, it will only affect the parameters that are held in the lines it consists of, and therefore can be loaded without any safes setting.
When a snippet and a scene makes up a cue, the scene will be activated first, and then the snippet will be activated, modifying a small set of parameters.
Cues can be scenes, snippets or both.

 

[Mick Berg]

Re: New scene system in 2.0

A snippet is a small part of a scene file. If you remember me writing about incomple or partial scene files and how they could be used, this is the same principle, but actually supported in full by the desk.
A scene file consists of 2050 lines, each line setting one parameter (and sometimes a group of parameters), and contain settings for all the recallable parameters. Which ones that get changed when the scene loads depends on the safes settings.
A snippet will only contain some lines, how many and which lines depends on the setting when the snippet is saved. When the snippet is activated, it will only affect the parameters that are held in the lines it consists of, and therefore can be loaded without any safes setting.
When a snippet and a scene makes up a cue, the scene will be activated first, and then the snippet will be activated, modifying a small set of parameters.
Cues can be scenes, snippets or both.

Thanks Per. Definitely clearer but I still have a ways to go!

Mick.

 

[Dan Mortensen]

Re: STP vs. UTP

Hi All,

A friend of mine got (for his work at a major theater here) a new Midas Pro3, and it came with a couple of 100meter reels of rugged Cat6 (I think, might be CAT5e) STP with Ethercons. He needed to put the CAT for his console in conduit from mix position to stage, so instead of chopping off an end of his cables, he got some raw cable, ran it through the conduit, and terminated it. All was well, and he kept the reels of terminated cable for future use.

I have a multi-stage festival coming up and have not yet found a permanent STP solution for the systems (all X32's), so he was going to let me borrow the reels of STP to cover two of the stages, and brought them by. When I connected one to an S16 and X32 and shocked the S16 with a modified BBQ sparker, it completely and immediately lost sync! All STP with Ethercon has been unfazed by sparking, whereas all UTP has lost sync. (See Brian Wynn's posts in the other place. behringer x32 cracking and popping with 2x S16 connected? I think he started around page 5 or 10.)

Looking closer at the cable, it clearly says "UTP" on it, not STP.

He hadn't looked closely at it (or even opened the boxes), and was shocked to learn that he'd gotten the wrong cable.

He called Midas Service, and, long story short, they didn't reply to him for several weeks, but finally did so today.

Actually, he said two guys separately called him, Frank and Kyle, and each told him the same thing: although some early versions of the XL8 had a problem with UTP, Midas went into them and fixed what was lacking, so that they and all other Midas consoles now work just fine with UTP. All Midas consoles now ship with UTP when cable is provided.

This seems significantly different than what we've heard about X32's and the reasons for their need for STP. It now appears to me that there is something lacking in the X32 in their resistance to sparking, and the STP is a bandaid to fix that lack.

Don't get me wrong, I'm not about to renounce the X32, I still think it's a wonderful console, it would just be nice to get a straight story and understand why things are as they are. If there's a way to fix the S16 so that it works with UTP, that would be money well-spent IMO.

Dan

 

[Antoon van den Oetelaar]

Re: STP vs. UTP

I was thinking about these ESD problems.
As I do work in electronic design all handling material in the lab and production has to be conductive, so no charge can build up. That doesn't mean it has to be shielded or made from metal.

Aren't there any UTP cable with some conductive plastic outer shield, that can't build up charge? Maybe this could solve all these ESD problems...

I can imagine that these newer midas consoles have better ESD clamps on there RJ connectors, so the issue is over. Maybe you can add ESD clamps also outside of the board, in a RJ (neutrik) chassis part on a patch panel...

 

[Dave Bednarski]

Re: Bus Send Pre Insert?

Is it possible to send to a bus, pre insert?

If want to tinker with Waves as a channel insert but concerned about additional latency in the monitors?

If you set the insert point to Post, the Pre EQ, Post EQ and Pre Fader are before the insert

Having success with Waves, one last hurdle that is giving me some mental grief...

Trying to isolate which insert point and to set to what... to my monitor mix is being sent to the bus BEFORE it runs through MultiRack. Want to keep my MultiRack modifications to the FOH mix only.

Is this the correct screen to make this correction or am I doing it on a per channel basis or other?

https://www.dropbox.com/s/k0p018xvs7at3d5/Screenshot 2014-02-20 11.42.23.png

 

[Per Søvik]

Re: Bus Send Pre Insert?

Having success with Waves, one last hurdle that is giving me some mental grief...

Trying to isolate which insert point and to set to what... to my monitor mix is being sent to the bus BEFORE it runs through MultiRack. Want to keep my MultiRack modifications to the FOH mix only.

Is this the correct screen to make this correction or am I doing it on a per channel basis or other?

https://www.dropbox.com/s/k0p018xvs7at3d5/Screenshot 2014-02-20 11.42.23.png

Yes, you can do it there or you can do it per channel, same difference. Just remember that when you change it in that tab, all your sends will be set to -∞.
The insert point has to be set for each channel, you probably want to move that to post to have more options for your monitor tapping point.

 

[Dave Bednarski]

Re: Bus Send Pre Insert?

Yes, you can do it there or you can do it per channel, same difference. Just remember that when you change it in that tab, all your sends will be set to -∞.
The insert point has to be set for each channel, you probably want to move that to post to have more options for your monitor tapping point.

Thank you!


Config 1:


This configuration on the channel, https://www.dropbox.com/s/yxp8ceqpkv58s1a/Screenshot 2014-02-20 12.22.26.png
...would route...


Gate -> EQ -> Dynamics -> Bus Sends -> to Waves MultiRack -> back to X32 -> LR


Config 2:


If I switched it to this, https://www.dropbox.com/s/r9bkpkqg3qlzlto/Screenshot 2014-02-20 12.25.27.png
...would route...


Gate -> to Waves MultiRack -> back to X32 -> EQ -> Dynamics -> Bus Sends -> LR


--


Thank you very much for your time.

 

[Dan Mortensen]

Re: STP vs. UTP

I was thinking about these ESD problems.
As I do work in electronic design....

I can imagine that these newer midas consoles have better ESD clamps on there RJ connectors, so the issue is over. Maybe you can add ESD clamps also outside of the board, in a RJ (neutrik) chassis part on a patch panel...

Hi Antoon,

What does this mean? I have no concept of what would be involved, but encourage you to do a prototype to see if it works or not.

Thanks,
Dan

 

[Mick Berg]

Re: Bus Send Pre Insert?

Yes, you can do it there or you can do it per channel, same difference. Just remember that when you change it in that tab, all your sends will be set to -∞.
The insert point has to be set for each channel, you probably want to move that to post to have more options for your monitor tapping point.

How are you going to physically connect the X32 to Multirack? How would you send sixteen channels back and forth? (You can probably guess I'm hoping to hook up the Waves Dugan Plugin) Ideally sends to the Dugan should be post-fader.

Thanks,
Mick.

 

[Per Søvik]

Re: Bus Send Pre Insert?

Config 1: Gate -> EQ -> Dynamics -> Bus Sends -> to Waves MultiRack -> back to X32 -> LR

Config 2: Gate -> to Waves MultiRack -> back to X32 -> EQ -> Dynamics -> Bus Sends -> LR

With config 2 you are obviously very limited with the monitors, they would have to come from the first tapping, but that's OK if you want monitors without any processing whatsoever.

One thing you have to bear in mind is the limitation on what you can get to and from the Multirack as inserts, you will be limited to the six auxes, rerouting them to and from card. (for now, hopefully that will change at some point)

 

[Per Søvik]

Re: Bus Send Pre Insert?

How are you going to physically connect the X32 to Multirack? How would you send sixteen channels back and forth? (You can probably guess I'm hoping to hook up the Waves Dugan Plugin) Ideally sends to the Dugan should be post-fader.

Thanks,
Mick.

It would be quite difficult at the moment, because there aren't really the routing options to do so, but if you sum the channels in Multirack and return just a stereo pair, at least that bit is a bit more painless, The easiest way of getting them to the multirack is to assign the channels to P16, and use P16 as source on the card.

 

[Dave Bednarski]

Re: Bus Send Pre Insert?

With config 2 you are obviously very limited with the monitors, they would have to come from the first tapping, but that's OK if you want monitors without any processing whatsoever.

One thing you have to bear in mind is the limitation on what you can get to and from the Multirack as inserts, you will be limited to the six auxes, rerouting them to and from card. (for now, hopefully that will change at some point)

Hmm. Okay, I am not using Multirack as inserts. Crap. Perhaps I miss stated my original question in 2013. I am routing all 32 inputs to Multirack via the card... and then back. If this is the case, this takes place before any other processing back at the board, there is no way to route to the buses before it heads over to Multirack?

If that is so, then... it explains why I have no success given my misinterpretation of the original advice and my poorly formed question.

 

[Per Søvik]

Re: Bus Send Pre Insert?

Hmm. Okay, I am not using Multirack as inserts. Crap. Perhaps I miss stated my original question in 2013. I am routing all 32 inputs to Multirack via the card... and then back. If this is the case, this takes place before any other processing back at the board, there is no way to route to the buses before it heads over to Multirack?

If that is so, then... it explains why I have no success given my misinterpretation of the original advice and my poorly formed question.

Yep, if you use the standard routing, then it happens right after the input converters. We keep nagging the Behringer guys to give us card-as-insert, we just have to keep at it.

 

[Pauly Mel]

Re: Bus Send Pre Insert?

I've been screaming for the capability to send post fader channels to the multitrack ( via the card) since the x32 was released! Hope you have more success than I did. In the end I tired of trying to explain why ;-)

Pauly

Hmm. Okay, I am not using Multirack as inserts. Crap. Perhaps I miss stated my original question in 2013. I am routing all 32 inputs to Multirack via the card... and then back. If this is the case, this takes place before any other processing back at the board, there is no way to route to the buses before it heads over to Multirack?

If that is so, then... it explains why I have no success given my misinterpretation of the original advice and my poorly formed question.

 

[Tamas Tako]

Re: Bus Send Pre Insert?

It would be quite difficult at the moment, because there aren't really the routing options to do so, but if you sum the channels in Multirack and return just a stereo pair, at least that bit is a bit more painless, The easiest way of getting them to the multirack is to assign the channels to P16, and use P16 as source on the card.

How could I use the P16??? How to get signal into and from the PC?

 

[Per Søvik]

Re: Bus Send Pre Insert?

How could I use the P16??? How to get signal into and from the PC?

If you go into the P16 tab, you'll see that you can select from a lot of sources. Once you have routed the signals to P16, you can then select P16 as source in the card out tab.

The card in (from PC) can be used as source for input channels and aux ins, and processed and routed from there. Exactly how you do it depends on how many channels you want to use in each direction, where you want to tap from etc.