Hi. I am fresh Transform User and our suplier gave me the fourier to test it. I was using Waves Superrack with WNS and F6 and some tools for years with SD Consoles. Now happy to test new fourier, but…
First of all, yes, Dante Patch and settings are made and seem to be correct.
We have problem, that suddenly a few chains lost the audio-output. Consequence ist that inserted Chains in the Quantum lost audio complete. Signal arrives in the fourier and it displays output too. But even in DanteController you can see that it is not leaving / sending from transform engine.
Biggest suprise was that ist just happens with a few chains, while others are working fine!
Our solution was to restart the engine and everthing woks fine again!
Has someone made experience like this?
2nd question: Is it normal that after restart, it took like 3 minutes to build all chains and pass audio through? Talking about 10 Chains with mainly SSL Sourcerer and Soothe.
I woulw be happy just to know if we maybe have a buggy machine or if others have made such experiences too.
Thanks a lot…
next show with Quantum & fourier will be this evening…
I checked in the Plugin compatibility list, that the SSL sourcerer is not in there yet.
Maybe this could cause a Problem, you could try some tested PSE Plugins (Waves?).
For Booting: Yes, it takes some time until everything is running. I didnt check the exact timing with our engine but i think it’s between 1 and 2 minutes. The Show Loading itself is usually really quick. If this takes longer (i once had an issue with a neural DSP Plugin (also not in the compatibility list) with lightning symbols next to some Plugins, there could be a problem with the loading process. In my case it helped to restart the “blocking” chains.
Amazingly, the SSL Sourcerer is part of the transform suite. I really hope that all plugins in this bundle (that is offered by Fourier Audio) will be more than only tested. I expect that a plugin bundle, which is advertised by the manufacturer, is working stably, and the user can trust in stability when they are used in live performances.
Thank you for the input of “restarting chains.” We did this a few times, but without audio coming back. We could see audio coming in the chain, as well the metering of the audio output in Fourier.
Because of this, we checked our Dante connections, repatched them, but the audio output was already missing in the Dante controller (here you see signal metering in the green symbol).
We are sure that the Fourier lost its “internal connection to Dante output.” Restarting the machine fixed the problem but is no solution for a live show, because it needs a few minutes until audio is back !!!
The Transform Engine has now performed flawlessly in two shows.
However, we noticed that recalling a scene on the console triggers a DSP peak in the Fourier engine. In the DSP Load view, there are six blue bars – and the first one spikes into the red briefly with every scene recall. We have excluded all plugin chains, so in theory, no plugin data or setting changes should be recalled.
Still, the first DSP bar consistently turns red during every scene recall on the Quantum. Additionally, every recall triggers a DSP overrun in the system overview.
This behavior undermines confidence in using the Fourier engine live. For that reason, we have implemented two workarounds:
a) Walk-in music is now also routed through an insert using the Fourier engine. This way, we would notice if the engine starts losing audio streams again before the actual show begins. b) We created a macro button on the Quantum 338 that disables all inserts routed through the Fourier engine.
I would really like to get these issues under control, because the ability to use SSL plugins or Soothe Live is fantastic. However, if the Fourier audio streams drop out again, I will refuse to use the engine in future shows. If the kick, snare, or vocals suddenly disappear during a concert, and will be until the machine is restated (2-3 minutes) … who do you think will be under pressure to explain? Reliability is everything in live music!
I am absolutely willing to check whether the problem lies on my end.
But if other users have had similar experiences, please drop a quick comment here.
In that case, it would be very helpful to report these bugs to the Fourier team so they can fix them as soon as possible.
I also think the possibility is great but unfortunately at least in this space it seems that there is not so much support activity. I can Imagine that its hard (and maybe also not necessary) to support every Plugin on the Planet, but good support especially plays a big role imo.
I am thinking if the Digico Integration is causing some problems?
Because we have our engine running everyday for approx. 6 months now and never had any audio issue, only loading issues (with not compatible Plugins) or sometimes strange graphic issues in previous Versions.
But: we are running the engine on a SD7 (which has no direct Fourier Integration) through an orangebox (optocore-dante).
In 2 months we will Install a Quantum 8, but i am not sure If the Digico integration is safe for a running Show at the moment.
I hope Fourier and Digico are working on an solution.
But i also think a “Bypass Insert” macro is a good Idea.
Firstly, I want to sincerely apologise for the issues you’ve each encountered. We understand how critical stability and reliability are in a live environment, and I want to assure you that we’re committed to resolving these problems as quickly as possible. If there’s anything urgent in the meantime, please don’t hesitate to contact our support team directly at [email protected]
The error you’ve encountered is definitely concerning and not something we take lightly. To investigate this further, could you please send us:
Your showfile
The corresponding DiGiCo session
Download and send your log files
Note the approximate time the error occurred
Once received, we’ll conduct a thorough review on our end to determine the root cause. We completely agree with you, reliability is everything in live music, and we’re committed to doing everything we can to restore that stability for you.
RE: Question 2: Delayed Startup Post-Reset
This is unusual behaviour. Under normal circumstances, the transform.engine plugin host should be up and running within a minute of reboot. To help isolate the cause, could you confirm the following:
Does the delayed startup occur with and without DiGiCo integration enabled?
Have you observed any patterns related to when or how the issue manifests?
This information will allow us to pinpoint what’s gone wrong and why. As this is not an error we’ve seen previously, we’re very keen to get to the bottom of it.
Thank you all for your patience and for bringing these issues to our attention. We truly value your feedback and are here to support you however we can.