Sorry, got interrupted by other things here.
Question 1: Copying channel sends (faders) from one mixbus to another cannot be done using the X-Air Edit or any of the mixing apps. But it can be done with Live Toolbox with it's tidbits (basically snippets on steroids), using the Store and Recall commands.
If Mixbus 1 and 2 are stereo linked, you only need to copy one of the mixbuses. First clear the store area, then copy the mixbus 1 fader levels of the 16 channels (using the range feature)
Store 1 /ch/##/mix/01/level 1-16
Then use the Recall command (with the substitution wildcards) to change to the other buses (remember that you only need to change one of the mixbus pairs)
Recall 1 /ch/**/mix/03/level
Recall 1 /ch/**/mix/05/level
These commands can be put together in a text file with the .tid extension (eg. CopyMixes.tid). Then you can launch the tidbit file using the following command
Launch tidbit "CopyMixes.tid"
This can also be assigned to one of the custom buttons in Live Toolbox. Or you could use MX Terminal (or LT_Command) which uses the Live Toolbox engine.
Hi Chris @justChapman ,
Welcome to the forum. I'll leave the first question til last, since the answer is the most advanced and takes more to explain it.
Question 2: Soloing a channel only affects what goes out of the headphones output. That bus is called a "monitor" bus. So it will have no affect on the Aux 1-6 or Main LR outputs.
Question 3: Channel sends taps needs to be something other than post fader (on the channel strip, Sends screen). In other words, if you want the IEM 1 independant to what happens to the faders for Main LR, select each channel strip and select the Sends screen. Change the taps to the IEM 1 mixbus pair (eg. bus 1-2) to something like post-EQ).
Question 4: One thing I can think of is, if you mute a channel to the Main LR, it will also mute all sends of that channel to the mixbuses (IEM 1-3) as well. I use Main LR for what it was designed for. If I'm doing sound for a band that needs more than the 6 Aux outs, I would use my X32 Rack.
I'll answer question 1 in the next post
I hope you all had time to look around the DP48, just a question regarding labeling the groups. how do we do that ?
There are a couple of ways to add group names. As Gary @GaryHiggins mentioned, there is a place in the new firmware 4.0 (in the Library, AES50) where you can add then names, then broadcast them to the DP48's that are connected (and in slave mode). Another way to do it is by using the SD card. Add a csv file (called "names.txt") to the DP48 folder and add the names separated by commas. In the Setup of the DP48 is a setting to import those names.
Also you can use OSC commands either in a snippet or one of the 3rd party apps to change the names. I'm planning on adding a tool for this in Live Toolbox shortly.
I get 404 when trying to download some of the files (X-Edit Linux 32-bit, and RPI)
Hey Per, I successfully downloaded the RPi and Linux 64bit Edit (there is no 32bit version of 4.0) here.
I don't see a specific area for the DP48 setup, in edit anyway, did I miss it?
No you didn't miss it. The editor doesn't have it yet. But the firmware does, meaning you can access it from one of the other (non-core) X32/M32 models interface. I have Scene Parser almost ready for release and hoping to provide a DP48 tool in Live Toolbox in the near future (yes you can access it via OSC).
Hi Carl @dietzer ,
Welcome to the forum. The reason why you are getting that error is probably because the documentation they provided is quite old. The parent company of Behringer, Midas, Turbosound, etc. use to be called Music Group. That got changed to Music Tribe and their sites is now music-tribe.com. To register the X32, you can do that here.
The firmware upgrades etc. have been pulled (for reasons unknown) prior to the release of the new firmware (4.0 - to be released very soon) along with the respective apps. If you need any of the current files before 4.0 release, one of us can provide them. But I would highly recommend upgrading to the 4.0 when it is released. It has many feature (long requested) as well as the DP48 support.
I can assure you that you did not make a mistake in getting the X32.
I'm using an MR18 and trying to use the ultranet with my Turbosound Speakers. I can not get any connection with the MR18. I currently use my Turbosound speakers with my X32 console and have no issue getting the speakers to connect. I have used the ultranet for several years now, but not with the MR18. Has anyone hade this issue????
I just started using my iQ speakers with my MR18 last month and have also used them with my X32. Do you have the same output assignments on the Routing, Ultranet screen that matches what you have assigned to each of the speaker DSP's?