Control connection creashed

Bug Reports 🐛
1

Hey folks, not for the first time, the control connection to the mac where the client is running on and to the console suddenly was lost and didn´t reconnect. I had to restart the engine. Not cool in the middle of rehearsals, not thinking about what´s going on if this happens during a show… Any ideas how to figure out what is wrong? Currently I’m using a simple 5 port unmanaged netgear switch.

Best, Chris

2

Not really an Idea.
We have our unit since 6 months, running nearly every day through our Network structure (several managed switches) and didnt have this issue. Connection was always stable.

But we have only Windows PCs as clients…

1 Like
3

Had this happen as well. I think responsible were plugins, that for some reason kill the proper functionality of TFE. In my case it was Autotune Pro 11 that wreaked havoc.

First signs of one of those plugins possibly being in the show are sudden unexplainable DSP Overruns.

1 Like
4

Hi Chris,

As always, if there are support issues and need quick answers, please do get in touch with the team on [email protected]. These forums aren’t monitored at all times.

This sounds more like a network issue, but hard to diagnose from the limited information.

  • Can you confirm what you mean by ‘crashed’? I’m guessing it disconnects?
  • Are you able to ping the transform.engine from the Mac at this point?
  • What else is on the network? How is it configured?
  • Further info on this ‘the control connection to the mac where the client is running on and to the console suddenly was lost and didn´t reconnect’, you had Digico integration and transform.client running on a Mac? Both lost connection to the transform.engine at the same time?
  • Can you ping the console from the Mac when this issue occurred?

If you want to send transform.engine log files and transform.client log files (Macintosh HD/Users/USERNAME/Library/Logs/transform.client) to support, that would also help the team understand what has happened.

Thanks,

Elliot

5

Hey, so the “Crash” did not happen one more time. Maybe it had sth. to do with the uncompatible BM60 Plugin… I’ll monitor it and we’ll see what happens :wink: