client / laptop

So I preface my remarks first that I am frustrated, po'd  and stressed out,  Also, I am positive that I don't understand all of the complexities regarding network connections!

 

Maybe it is just me, but the entire client / laptop setup is a train wreck.  In the two years that we have had our Ion and Eos, I can count on one or two fingers the times I was able to successfully connect my laptop to the console as a client (this is WITH tech support help) and I can count on about 10 or 15 hands the times I've attempted and given up.  Like I said, I cannot fathom all the complexities but the bottom line is that it needs to be easier....MUCH easier.  Also, we need useable wireless connectivity!!!!!!!!!!!!!  I am in a theatre with an EOS but not a real lighting network, so I have to run about 350 feet of cat 5 to get my laptop onto the stage. Wireless would make this so easy!  I believe we have a Yamaha LS9 sound console and it appeared that our sound designer for the last show was sitting out in the auditorium tweaking the sound from his laptop.

I thought the whole client thing would be so nice, "I can take my laptop out in the auditorium or onstage to fix problems...sweet!". Trailing a cable behind me is not my idea of convenience!   Frankly, it is not worth the trouble.  When I need it (client / laptop support), I don't have time to mess with all of the BS needed to get a connection...it just isn't worth it.  There needs to be a CONCERTED EFFORT to make this right!  I am not suggesting an effort like the Apollo program, but more than a side project.

I apologize for the tone of this post but I don't have time to mess with a process, it just needs to work.  Nobody is a bigger Eos/Ion/ETC fan than me...ok, maybe a few people!, but I am just a bit dissappointed!

 

Pat

Parents
  • Just one quick thing on wireless. Most of the time I've seen audio guys with their laptops / tablets in the house, they are not actually connected to their control system directly. They are actually using VNC to connect to another PC on the network that is hardwired to the control network. My understanding of why this is is because the amount of data being passed back and forth between the software and the master controller is quite large and is also very time sensitive. Wireless is not so great with time sensitive data. Packets are lost/dropped/resent quite often and the sound/lighting software is not built to handle those circumstances. 

    By using VNC, you are only having to send a screen image over the network and not all the extra crud that isn't needed.

    I will say that I have in a couple instances found that the ETC network seems very susceptible to bad and or finicky ethernet cables when it comes to a laptop and console The cable might work for console to nodes, or computer to computer network (internet), but not console to laptop. 

    HTH,

Reply
  • Just one quick thing on wireless. Most of the time I've seen audio guys with their laptops / tablets in the house, they are not actually connected to their control system directly. They are actually using VNC to connect to another PC on the network that is hardwired to the control network. My understanding of why this is is because the amount of data being passed back and forth between the software and the master controller is quite large and is also very time sensitive. Wireless is not so great with time sensitive data. Packets are lost/dropped/resent quite often and the sound/lighting software is not built to handle those circumstances. 

    By using VNC, you are only having to send a screen image over the network and not all the extra crud that isn't needed.

    I will say that I have in a couple instances found that the ETC network seems very susceptible to bad and or finicky ethernet cables when it comes to a laptop and console The cable might work for console to nodes, or computer to computer network (internet), but not console to laptop. 

    HTH,

Children
No Data
Related