Re: Problems with XControl
What a mess this thread has become! All the topics are mixed up. It should have been a separate forum of its own.
If it gets too bad, X32 User Net
http://www.x32user.net/phpbb2/index.php is ready to take the X32-specific overflow, but I for my part think it is good to have this thread with lots of info on a big mainstream forum. And there is of course the Behringer forum, allthough waiting for an updatet forum over there.
Anyhoo, I have been playing with XControl in anticipation of getting the real thing for one of my venues. It seems to me that there is no read-only default "initial settings" scene. I found this out the hard way, by overwriting the scene that XControl was in when first installed. There's no way to get it back, that I can find. I have even re-installed the program, and it still has my own scenes in it. That seems impossible but true. Can anyone help me to get back the initial scene in XControl?
Hopefully there is an initial settings scene in the real X32.
Setup menu/Config tab bottom left corner (now kick yourself
~;-)~:wink: )
After initializing, save scene to file and there you have it
http://www.x32user.net/phpbb2/download/file.php?id=10
Just import the scene in the same menu.
Regarding the "crossover in the mixer" discussion, it seems a ridiculous idea to me these days, and the few people who would want it definitely does not justify using up DSP in the console which could be used for plenty of other missing features. I suppose it could be implemented as an effect, with a stereo in and six outputs.
Here's a bit of history for you. I used to work for Midas, many years ago, and the crossovers were in the console! The crossover points were fixed however, (optimised for the Martin PA system) and could only be altered by changing internal components. Once the BSS (Brooke-Siren) crossovers appeared (both Chas Brooke and Stan Gould of Siren Systems worked for Midas) we no longer included crossover modules in the consoles.
Mick Berg.
If implementing crossover was using up DSP I could understand the resistance to having this as an option. Obviously every little thing that is added will use up some firmware memory, and there is a limit to the features that can be added, but no matter how dsp-intensive a feature is, as long as that feature is not enabled, it won't use up any dsp resources.
Basically, to do crossover, we are talking about a slight upgrade to the high- and lowcut filters, ie selectable slopes, and a way to lock down certain areas and throw away the key (or keep it in the pocket of the person responsible and knowledgable). This extra safe feature is not exclusive to crossover implementation, but something a few users have asked for to do other things like church installs etc.
And we are not in a segment of the market where we are talking about replacing Meyer or Lake processors or disabling the dsp of a d&b D12, but crossing over between subs and tops that are most likely to be powered with internal dsp that take care of protection and internal processing. I understand how eons of experience (no pun intended) can make this whole concept seem like a bad idea, but I believe that many of the naysayers are looking at this as a much more complex task than it really is, simply because most experienced operators are used to more complex systems. Most users of powered top on stick on powered sub will be using the crossover in the sub, some will go to the probably totally unnecessary step of adding a low end processor like a dbx drpx or drpa+ to this set up, and some might like to cross over in the mixer to have some control over alignment and exact crossover frequency and be able to control the balance between subs and tops.
Some might want to try aux send subs without having to invest in new hardware etc.
Some adventurous souls might want to take it further and do things that might backfire on them, but that is another story.
