X32 Discussion

Re: Firmware 2.05

Hi Jan, i have post this http://forum.behringer.com/showthread.php?4309-Maybe-a-Bug-at-XEdit-window-Dual-Fair-Compressor some days ago. Did you ( or Behringer ) notis this ? Is it fix in 2.05 ? ...

YES

Hi Jan, does this mean if we have already loaded from the previous links we should reload - both firmware and xedit,
Many thanks Nick

In fact, I tried to subtly express this by 'ONLY use these files', but you might get away with just downloading the firmware and PDF again. :roll:

Best,
Jan
 
Re: Firmware 2.05

YES



In fact, I tried to subtly express this by 'ONLY use these files', but you might get away with just downloading the firmware and PDF again. :roll:

Best,
Jan


Suppose guessed that (just checking you meant the actual files and not the links to the files) - BTW presume Ok to load the new 2.05 on top of the old 2.05 and not to have to revert to 2.04 first -the former is what I have done!

Ta
 
Re: X32 Discussion

As far as I've been able to tell, the flashing is always in tempo with the tempo that is set, it always reflects the actual parameter. Of course, if you double tap on beat so there is no averaging, the flashing will tend to be slightly behind your beat, while if the parameter is set by dialling, the flash will be quite randomly placed.

Thanks Per - next time I have mine out I will have to try this. I like the visual feedback it provides.

My 2 cents - I would think that doing this from any Wifi device would never be consistent. Packets do arrive in their own good time, and sometimes never, not when you tap.
 
Re: Firmware 2.05

YES



In fact, I tried to subtly express this by 'ONLY use these files', but you might get away with just downloading the firmware and PDF again. :roll:

Best,
Jan


Jan I wonder if some will include resource management for technical'm in a Church and this feature would be useful to prevent yourself from unwanted change functions or the like, the Soundcraft SI Expression already has this feature would have a prediction ... to inform me about?
 
Re: X32 Discussion

I'd like to create a snippet that loads the truegraphic eq into effect slot 8, sets it's levels appropriately, chooses the correct analog outs (for the monitors I'm using) and.. ummm I think that's it for now.

What would the syntax for that be?

You would add three lines that looks like this to the snippets you already have:
/fx/8 TEQ
/fx/8/par -7.0 -2.5 0.0 2.5 0.0 -1.5 1.0 0.0 0.0 0.0 -0.5 -1.5 -3.0 -2.5 -0.5 0.0 0.5 0.0 -4.0 0.0 -1.0 0.0 2.5 0.0 1.5 0.0 -3.0 0.0 1.0 0.0 -2.0 -3.5
/main/st/insert ON PRE FX8L

However, there is no way to insert the effect slot into the monitor path, so you would have to insert it on the mains (the last line), not getting the benefit of the eq for anything that is solo'd. Note that the /fx/8/par line has been shortened compared to what you save, there are a lot of trailing zeros there that have no function with this effect, so I omitted them
 
Re: X32 Discussion

Thanks Per - next time I have mine out I will have to try this. I like the visual feedback it provides.

My 2 cents - I would think that doing this from any Wifi device would never be consistent. Packets do arrive in their own good time, and sometimes never, not when you tap.

With 2.05 this changes a bit, now if you tap on beat, the light will actually flash on beat with very little (not perceptible) latency.

It has worked for me from the iPad, I'm not sure if the tap is calculated inside the iPad app and the value is transmitted, it is certainly the way I'd program it if it were me.
 
Re: Firmware 2.05

To Per,
please note that the tap function actually responds to button-down, rather than release, for measuring the time. So, it is consistent with the flashing LED. I intensively tried small and radical tempo changes, and the new tap-routine with plausibility check seems to follow easily whatever I do. Let me know it feels more intuitive and reassuring for you as well. Happy tapping, everybody :D~:-D~:grin:

Yes, I checked again, and you are right of course.
The X32Edit still times on the release, and it might be different from the console in more ways, as it does feel better able to cope with some of my tests.
The sanity check seems designed to drive me insane :razz:; if I tap 1-3-1-3-12 it changes to the shorter interval about half the time. If I go 1-3-1-3-1---12 I sometimes get the short interval, and I sometimes get the full bar. This is not the way that I'd normally be tapping, but since this sort of tapping has been very much the topic, I wanted to see how it responded, and the results I achieved certainly didn't encourage me to walk down that path in the future.

I like it better now, and that is the main thing for me.

Great work Jan, keep it up.
 
Re: Firmware 2.05

Yes, I checked again, and you are right of course.
The X32Edit still times on the release, and it might be different from the console in more ways, as it does feel better able to cope with some of my tests.
The sanity check seems designed to drive me insane :razz:; if I tap 1-3-1-3-12 it changes to the shorter interval about half the time. If I go 1-3-1-3-1---12 I sometimes get the short interval, and I sometimes get the full bar. This is not the way that I'd normally be tapping, but since this sort of tapping has been very much the topic, I wanted to see how it responded, and the results I achieved certainly didn't encourage me to walk down that path in the future.

I like it better now, and that is the main thing for me.

Great work Jan, keep it up.

Still wondering why there has to be ANY kind of scheme at all....man.....
 
Re: Firmware 2.05

Still wondering why there has to be ANY kind of scheme at all....man.....

It's better, or appears to be. I installed 2.05 earlier today but didn't have the ability to fire the system up and hear it (set up in a casino lobby for tomorrow). The numeric display seems to reflect the tempos I'm tapping, and the lights flashes accordingly. Overall it seems to be a better implementation, but I agree that beyond switch de-bounce, there is not need for a scheme at all. Just make it a user option in 2.06.
 
Possible bug

Hi,

I came across what I think is a bug during a dress rehearsal this evening. I doubted myself at first, because it's quite an unusual set-up, but I've triple checked and can't see why this isn't working...

Several input channels with a pre fader send (at unity) to a linked bus (15 & 16 in case it makes a difference!) That bus goes to LR, and is assigned to DCA2. Then, the AUX2 channel has the input set in the config as Bus 15, fader for this channel is at unity. Then that channel has a post fader send to Bus 11. Only Bus 15 & 16 have DCA2 assigned - nothing else has.

Problem is, although the expected signal is received in the AUX2 channel (obviously only when the DCA is up), it doesn't pass to Bus 11 at all.

Basically, it's to get several radio mic channels into a chorus group which can be faded up on the DCA, and for them to only pass to Bus 11 (feeding monitors in the orchestra pit) when they're being used in the FOH mix. Obviously ideally I'd just send Bus 15 straight to Bus 11, but you can't - hence going back to an input channel first.

Anyone fancy double-checking?! I vaguely remember someone reporting a similar issue many many pages ago, but I thought that had been fixed in a firmware update (board is running 2.04).

Thanks.
 
Re: Firmware 2.05

It's better, or appears to be. I installed 2.05 earlier today but didn't have the ability to fire the system up and hear it (set up in a casino lobby for tomorrow). The numeric display seems to reflect the tempos I'm tapping, and the lights flashes accordingly. Overall it seems to be a better implementation, but I agree that beyond switch de-bounce, there is not need for a scheme at all. Just make it a user option in 2.06.

I had it on the rack/iPad last night and was able to come up with some pretty nonsensical tempos....plus there is no indication of when the averaging cycle is complete. Plus the fact that all my buss, Aux, FX and main faders were disabled.
 
Re: Firmware 2.05

Plus the fact that all my buss, Aux, FX and main faders were disabled.

Came here now to ask: did today's new 2.05 (from the ONLY page we are supposed to download it) fix this problem from the old 2.05 (which you must have downloaded yesterday from another page), or are they both causing it?

And you mean disabled in iPad but not on desk, right?

Edit: When you didn't answer in five minutes, I decided "what the hell, why not?" and went and loaded the new 2.05 on a console. All works fine, all faders work and are visible in iPad.

Loaded it onto a Rack, and same result.

Maybe you said it was in X32 Edit? I don't use that one, so can't talk about it.

Edit again: I see you said iPad, so don't know what's going on. Do you have the latest app, which I think is from some time ago? When they intro'd 2.04? You're not trying it on your iPad1 are you?

Good luck,
Dan
 
Last edited:
Re: Firmware 2.05

Came here now to ask: did today's new 2.05 (from the ONLY page we are supposed to download it) fix this problem from the old 2.05 (which you must have downloaded yesterday from another page), or are they both causing it?

And you mean disabled in iPad but not on desk, right?

Edit: When you didn't answer in five minutes, I decided "what the hell, why not?" and went and loaded the new 2.05 on a console. All works fine, all faders work and are visible in iPad.

Loaded it onto a Rack, and same result.

Maybe you said it was in X32 Edit? I don't use that one, so can't talk about it.

Edit again: I see you said iPad, so don't know what's going on. Do you have the latest app, which I think is from some time ago? When they intro'd 2.04? You're not trying it on your iPad1 are you?

Good luck,
Dan

Do I need to revert to 2.04 then redo 2.05? The 'new' 2.05 is not seen as an update.
 
Re: Firmware 2.05

Came here now to ask: did today's new 2.05 (from the ONLY page we are supposed to download it) fix this problem from the old 2.05 (which you must have downloaded yesterday from another page), or are they both causing it?

And you mean disabled in iPad but not on desk, right?

Edit: When you didn't answer in five minutes, I decided "what the hell, why not?" and went and loaded the new 2.05 on a console. All works fine, all faders work and are visible in iPad.

Loaded it onto a Rack, and same result.

Maybe you said it was in X32 Edit? I don't use that one, so can't talk about it.

Edit again: I see you said iPad, so don't know what's going on. Do you have the latest app, which I think is from some time ago? When they intro'd 2.04? You're not trying it on your iPad1 are you?

Good luck,
Dan

iPad 3... Newest app...only channel and DCA faders are colored and working.
 
Re: Firmware 2.05

did the Fw update screen not come up?
I installed 2.05 on 2.05

Came up with
2.04
2.05
& update for 2.05
I think - was v quick!

My consoles both treated today's 2.05 as an update to 2.04; didn't install yesterday's 2.05.

It didn't want to load on the Rack; I had to try multiple times even holding down the button. Finally the update screen showed up but the last line said something like "Waiting for USB Stick" and hung up there, so I pulled the stick and reinserted it and the update immediately went to the next step and continued. I think it did that for 2.04, too. Weird.

John, sorry you're having that problem, and hope you figure it out. I used an iPad 2 with the console and a Mini on the Rack, and all is well.

Dan
 
Re: Firmware 2.05

It didn't want to load on the Rack; I had to try multiple times even holding down the button. Finally the update screen showed up but the last line said something like "Waiting for USB Stick" and hung up there, so I pulled the stick and reinserted it and the update immediately went to the next step and continued. I think it did that for 2.04, too. Weird.

The instuction tells you to start up holding the button, and only insert the stick when it asks for it, so not weird at all
 
Re: Firmware 2.05

I had it on the rack/iPad last night and was able to come up with some pretty nonsensical tempos....plus there is no indication of when the averaging cycle is complete. Plus the fact that all my buss, Aux, FX and main faders were disabled.
The current tempo 'fix' is local on the x32 and does not affect the external apps.

The external apps calculate the tempo locally and then update the delay on the x32.