I had a big disaster at Boomtown festival, where a generator I think lost the neutral and blew up a lot of my kit, including the switch that was connected to all of my etherdreams.. I am testing my etherdreams back home now, and I am seeing some of them on the network, but I cannot connect with Liberation. It just has the red square next to the arm button, indicating a network issue.. We used to have a Latency setting, but I can’t seem to find that now for some reason.. Weirdly I was able to connect to some of them with mad mapper, so maybe there is something i am doing wrong in liberation? But I’ve never had connectivity issues in Liberation before, so it makes me feel like something has been affected when the event happened. I was just wondering if anyone had any tips I may have forgotten when testing.
Just a shout out to Sam Valiant from Limehouse town hall for helping me out when my stage blew up, thanks for the support, and glad I met Sam through the Liberation training day! Many thanks, Ben
Very strange.. I was able to output from the etherdream eventually, but I had to click reconnect controller in the controller assignment like 20 times, then the box went green. It stayed green and stable, untill I hit reconnect controller again, when it went back to red, and only went back to green after maybe 20 more clicks! What’s going on with my network?
ok, so I went back to Liberation version 0.9.6 and I could see the etherdreams fine with green lights! so version 9.9 is giving me issues seeing the etherdreams fo some reason.. Oh god this isn’t helping me figure out if they are damaged or not When they do connect, they behave correctly, as in laser output is what it should be.
I think the key thing here is that 0.9.6 connects fine straight away, while 0.9.9 struggles. I don’t think there’s any significant difference in the Ether Dream connection code between those versions, so that suggests the DACs themselves are fine and the issue is on the PC side.
My best guess is that it’s Windows firewall / permissions - Windows treats each Liberation build as a new application, so you’ll need to allow 0.9.9 through the firewall again. That would explain why you can see the DACs in the list (the discovery protocol is a UDP broadcast) but can’t establish a TCP connection until you keep retrying. A quick test is to temporarily disable the firewall - if connections become reliable, that confirms it.
Also worth:
Resetting to the default project to rule out corrupt settings.
Latency setting – this hasn’t been removed, it’s now under Liberation → Settings (Cmd/Ctrl + ,).
Since output works fine once a connection goes green, my guess is that the Ether Dreams are OK.
When they do connect, they behave correctly, as in laser output is what it should be.