X32 Discussion

Re: S16 and P16 issue

Hi Jared,
Checkout the table on page 19 of the S16 Quick Start Guide (downloadable on our website and included in the S16 box). You will notice that different S16 modes will route different signals out the S16's ULTRANET port. It sounds like you may have it on a mode that routes AES50 1-16 instead of the traditional AES50 33-48 that corresponds to the P16 out tab on the X32. Hope it helps!

Best,
John DiNicola
Senior Specialist, Product Support
MUSIC Group
BEHRINGER

That could be it. I will be the first to admit that the chart is confusing to me.

We have 2 x S16 daisy chained plugged into the AES50-A channel. S16 one is connected to the mixer via port A. I then have port B connected to port A on the second S16. Which setting should they be on in order to match the P16 configuration from the mixer?

Thanks,
Jared
 
Re: X32 Discussion

I agree Juergen!
But things can only be better and Behringer has really showed us that.

I have played around a little with the XIQ app, in sim mode, it is not self explaining, but I think I got the picture. I could not find any documentation on the Behringer homepage.

It also works fine on iPad retina in 2x mode.

Here some quick conclusions:

<snip>

Agreed. The XIQ app seems awesome. Now we just need some security/pre-assignments added so that I can make sure the musicians on stage don't accidentally pick the wrong bus and start messing with my reverb sends or something...

(Security on all the apps, requiring at least a password to connect to the console would be greatly appreciated).

Branin
 
Re: S16 and P16 issue

That could be it. I will be the first to admit that the chart is confusing to me.

We have 2 x S16 daisy chained plugged into the AES50-A channel. S16 one is connected to the mixer via port A. I then have port B connected to port A on the second S16. Which setting should they be on in order to match the P16 configuration from the mixer?

Thanks,
Jared

Hi Jared,
Your physical connections are correct. In this scenario, I would suggest using the X32 as the master (local sync) and setting both S16s to external clock. For the first S16, use the first mode. For the second S16 use mode 2, which will give you outs 9-16 (via AES50 Out 9-16) on the second S16. To change modes, press and hold the config button while turning the select/adjust encoder. Turning all the way left brings you to mode 1, and modes are indicated by the LED lights on the S16 as described on the table. There are other configurations but this should be a good starting point. Any mode that indicates AES50 33-48 in the P16 out column should follow the P16 out tab on X32.

Best,
John DiNicola
Senior Specialist, Product Support
MUSIC Group
BEHRINGER
 
Re: X32 Discussion

Of course John!
Forgot that when I wrote my long post, I know it is much to beg for, but....

Why not a tab in xcontrol with the user assignable control section as is on the x32 ?
By this you would have some possibility to tweak in some precious special controls in the xicontrol.

Cheers,
Jon
The whole idea is to be able to MIX remotely. I can't MIX without control of the delay time.
 
Re: X32 Discussion

Great work on the new apps...

What about a Master Aux Volume on the XiQ app, once you have your mix done, bringing the overall volume up or down is still needed...

The XiControl graphic EQ manipulation (not the knobs) could be smoother....

Keep it up Behringer, we're way closer to the perfect apps than before... Great Job !!!
 
Re: X32 Discussion

Had a quick play with Xi Control 2.0 offline on iPad 1. Looks really impressive but I managed to crash it twice quite quickly. Obviously this sort of post is not helpful to the developers but I was unable to repeat it. Anyone else had any issues?
 
Re: X32 Discussion

Had a quick play with Xi Control 2.0 offline on iPad 1. Looks really impressive but I managed to crash it twice quite quickly. Obviously this sort of post is not helpful to the developers but I was unable to repeat it. Anyone else had any issues?
I've played with it for more than a hour using my ipad3 connected to my console, running some multi track stuff, and have had no problems so far...

No issues with the iphone app either.

:D~:-D~:grin: :D~:-D~:grin: :D~:-D~:grin:
 
Multiple P16/Ultranet networks

Hi Jared,
Checkout the table on page 19 of the S16 Quick Start Guide (downloadable on our website and included in the S16 box). You will notice that different S16 modes will route different signals out the S16's ULTRANET port. It sounds like you may have it on a mode that routes AES50 1-16 instead of the traditional AES50 33-48 that corresponds to the P16 out tab on the X32. Hope it helps!

Best,
John DiNicola
Senior Specialist, Product Support
MUSIC Group
BEHRINGER

So a few weeks ago during one of the webinars I asked Behringer whether it is possible to have separate, simultaneous P16 networks by using the Ultranet port on the X32 and the Ultranet port on an S16 (as opposed to having the Ultranet ports mirror each other). (I'm precluding the somewhat obvious "solution" running analog outputs into a P-16I module.)

I was told that "No, the S16 Ultranet port mirrors that on the X32." [Not a direct quote.] While I guess that their answer is true with the "traditional" settings on the S16, I'd like to propose that a better answer to my question is "Yes, with caveats." The caveat is a judicous use of the blocks of eight on both half of the inputs and half of the outputs. The general concept is very similar to linking analog consoles.

So here's my illustrative example: An ensemble that wants to monitor up to 28 inputs or mixes, split into 2 groups of 14. Let's call the first group the rhythm section and the second groups the ]vocalists. Let's assume that they want to use IEM's, so we'll keep everything in stereo. X32 with two S16's. S16 'A' is connected to the AES50-A port on the X32 and is used by the rhythm section, and S16 'B' is connected to the AES50-B port on the X32 connected and is used by the vocalists and solo instruments. I think that connecting the two S16's directly/independently to the X32 is crucial. I've starred the steps that are different from the two S16's.

Configuring S16 'A':
--Set S16 'A' to any mode that returns AES50-A ch33-ch48 through the Ultranet port (Seq. 1, 2, or 3).
**--On the X32->routing->"aes50-a"->"Output 33-40" select something you want eight of, say in this case "AEs50 A1-8," which are the first 8 inputs into S16 'A.' We'll patch something into these 8 channels that we want the direct outs of, like 3 guitarists, a bassist, and two stereo keyboards.
--Inputs on 9-16 on S16 'A' are connected to the the 8 drum mics.
--On the X32->routing->"aes50-a"->"Output 41-48" select "P16 1-8."
**--On the X32->routing->"p16 out" assign Digital Output "P16 Out 07" to "Mixbus 01" and also "P16 out 08" to "Mixbus 02." Mixbus 01 & 02 should be a stereo monitor mix of the vocalists and solo instruments that are patched on S16 'B.'
**--On the X32->routing->"p16 out" assign Digital Output "P16 Out 01" to "P16 Out 06" freely as you like. In this example, you might choose kick, a mix of the rest of the kit, click track or stereo track if you're using it, and a couple lead vocals from the other group.

Configuring S16 'B':
--Set S16 'B' to any mode that returns AES50-A ch33-ch48 through the Ultranet port (Seq. 1, 2, or 3).
--On the X32->routing->"aes50-b"->"Output 33-40" select something you want eight of, say in this case "AEs50 B1-8," which are the first 8 inputs into S16 'B.' We'll patch something into these 8 channels that we want the direct outs of, like 8 vocalists (a couple lead plus BGV's).
--Use inputs 9-16 of S16 'B' to connect 4 solo instruments and a string quartet.
**--On the X32->routing->"aes50-b"->"Output 41-48" select "P16 9-16."
**--On the X32->routing->"p16 out" assign Digital Output "P16 Out 15" to "Mixbus 03" and also "P16 out 16" to "Mixbus 04." Mixbus 03 & 04 should be a stereo monitor mix of the rhythm section that's patched on S16 'A.'
--On the X32->routing->"p16 out" assign Digital Output "P16 Out 09" to "P16 Out 14" freely as you like. In this example, you might choose the four solo instruments and a stereo mix of the string quartet.

The stereo mix of the rhythm section and the stereo mix of the vocalists and solo instruments each may have to be actively mixed. In particular, if there are more active soloists connected to S16 'B' than you have available channels to send over to the rhythm section then you'll need to actively mix the stereo monitoring channels that go from the vocalist/instrumentalist section over to the rhythm section.

I don't think that you have to be tied to using direct outs. Given the trouble that Jared had, I think that you can intercept channels that assigned to the returns for a particular S16. Another possibility would be "Aux 1-6/Mon" or one of the card groups.

You can also set up a third P16 mix using the Ultranet port on the X32, but it's a bit more complicated to explain. One of the P16 groups of eight (like "P16 9-16") could do double duty for a return from the other sections, or one of the groups of 8 from the above paragraph selected.

Anyway, I think that those who find that having "just" 16 channels on the P16 a bit confining might be able to scratch their itch by running multiple Ultranet/P16 networks.
 
Re: Tap Delay weirdness?

I posted this before. Anyone else finding to tap function sporadic and inaccurate? I find if I tap it too many times it just applies a random time setting and I have to manually adjust with the knob to get it to 'see' the tap button again.
Ok, I've now played with the tap tempo feature for quite a while and found that I actually like the current implementation.

The tap tempo works like this, according to my own findings. When you start tapping it will average all taps up to your last ten taps into a tempo. This process will restart when more than three seconds have elapsed since the last tap.

The cool thing about this is that you can follow the music tempo change smoothly by just tapping away at the changing tempo!

The led will almost not be in sync with the live music anyway regardless how how accurate your tapping is since the band tempo changes all the time anyway. And since it is averaging your taps then it can't sync the led to your taps either.

I belive the issue many people are having with setting the tempo is that they initially tap too fast/slow in the beginning and don't realize that all the last ten taps are averaged. And if you don't wait for at least three seconds before trying to re-sync the tempo your i.e. two second delay before re-tapping, that delay will become included in the averaging making your tempo much slower than intended!

But if you know all this beforehand, then I belive the tempo matching implementation is great.
 
Last edited:
The whole idea is to be able to MIX remotely. I can't MIX without control of the delay time.

Hi John! Jon here !

I have not posted much here, but sometime you must start.
I was serious in my reply to your post. Not ironic :)
In my opinion, The lack of tap delay remote is an issue.
I also wanted to extend my thought/wish to the entire user assignable section.

And of course, MIX remotely, or setup things pre show remotely, or use the x 32/xicontrol to trig things is the whole idea!

As former FoH eng/head of rental dpt in the 90's and nowadays more weekend warrior band performer in smaller venues I really appreciate the x32/s16p16 Swiss Army knife architecture with price tag in respect. I am just about to upgrade a rig and within this extended process I have followed the roll out of the new Behringer lineup.

I am just so happy they made it this far. Far more than I anticipated.
With that excitement I happily cheer up now and propose things in this forum :)
 
Re: Tap Delay weirdness?

Ok, I've now played with the tap tempo feature for quite a while and found that I actually like the current implementation.

The tap tempo works like this, according to my own findings. When you start tapping it will average all taps up to your last ten taps into a tempo. This process will restart when more than three seconds have elapsed since the last tap.

The cool thing about this is that you can follow the music tempo change smoothly by just tapping away at the changing tempo!

The led will almost not be in sync with the live music anyway regardless how how accurate your tapping is since the band tempo changes all the time anyway. And since it is averaging your taps then it can't sync the led to your taps either.

I belive the issue many people are having with setting the tempo is that they initially tap too fast/slow in the beginning and don't realize that all the last ten taps are averaged. And if you don't wait for at least three seconds before trying to re-sync the tempo your i.e. two second delay before re-tapping, that delay will become included in the averaging making your tempo much slower than intended!

But if you know all this beforehand, then I belive the tempo matching implementation is great.

A very simple technique that works well is to do this on the console to set the correct tap tempo you want: Try 'practicing' tapping the tempo speed you need on the chassis next to the tap button, then move over and hit the tap tempo button only two times at the same speed. Done correctly, you will get very accurate tap tempo speeds. Hope this helps. -Rob
 
If you have a problem......

This was mentioned earlier in the thread I believe, but I think it is time to repeat that one exellent tool when in need of help is the scene save to stick. Whenever something isn't working right, take a snapshot and post the .scn file with the question/request for help. It is quickly done and will enable others to often quickly diagnose the problem at hand.
 
Last edited: