EOS Pre-visualization

Hello, I have two questions about pre-visualization using EOS. First, how do I get the  EOS offline to talk to Wysiwyg R22 on the same computer? I've tried everything and it still does not see it. I bind an EDMX output to EOS 8K or 4K board in device manager. I even just tried using ETCnet2 to see if that would work. On the EOS offline, I enabled the all the ethernet protocols and outputted them offline. I even added a loopback adapter. Still nothing. Am I missing something here?

Second question: because I could not get Wysiwyg to work, I am using another pre-viz program called Light Converse which seems to work great and I am only outputting Art-Net from EOS. The only problem I have is that it does not create a fluid movement with the lights since the network packets being sent are intermittent. I tried everything imaginable to increase the network speed between programs but same problems. I know that the pre-viz software is fine because I run GrandMA on Light Converse and it runs as fluid as water. Also, in addition to the jerky signal, I also get network spikes every couple of seconds that brings all my lights to full then goes out. This is all getting quite annoying which is why I am trying to get my Wysiwyg to work. Any help anybody can give me on these problems would be greatly appreciated.

Thanks

  • Are you using Windows Vista?

    Wyg r22 is known not to work properly under Vista - I believe that Cast are working on it, but I don't know how far they have progressed yet.

    However, you shouldn't need to use Device Manager at all under Wyg - just use the straight EDMX option and patch to the EDMX multiverse.

    There is a specific option in Eos Offline to enable output when running Offline, which is to ensure that an Offline console doesn't interfere with a show or plotting session. The option can be found from the 'Shell', under "Settings">"Network" and is labelled "Enable Output in Offline Mode"

    As to the 'slow' movement of Light Converse connected to Eos Offfline - this is deliberate.

    Most PCs cannot cope with high framerates of the extremely complex graphics involved with pre-visualisation, so the output of Eos (and Congo) Offline is deliberately slowed down to reduce the amount of work the PC has to do. This also frees up a considerable amount of CPU time from the console software, allowing the visualisation software more processing power if it's being run on the same PC.

    The 'flash to full' effect is there to ensure that Eos Offline is only used offline. At random intervals the output will be flashed to either full or zero for a single frame.

    The Offline software is free, and thus we can't afford for people to simply download that and run their show from it instead of buying or hiring a console. ETC have a longstanding policy of not doing PC-based control, because we feel it's a very poor solution for lighting control as it's impossible to create a user interface on a PC anywhere near as good as a real console facepanel.



    [edited by: Richard at 6:04 AM (GMT -6) on Fri, Nov 28 2008] [edited by: Richard at 6:04 AM (GMT -6) on Fri, Nov 28 2008] [edited by: Richard at 5:57 AM (GMT -6) on Fri, Nov 28 2008] [edited by: Richard at 5:56 AM (GMT -6) on Fri, Nov 28 2008]
  • Hi.

    We are testing LightConverse with EOS offline and it working fast without any lags. Try to use sACN connection protocol, this is native for EOS. There is may be an issue with your Ethernet adapter. Due to all communications is done through the active adapter, it should be fast. 100Mbit LAN or virtual LOOPBACK is fine, WiFi is not!

    And the last question, which version of LightConverse have you used? You can save a CPU power by a command line run in our modern software versions.

  • Dude, I asked the question about the "jerkyness" myself and was told it's deliberate to stop you using the software professionally :(

     

    Also, I found that the Eos devices don't work in WYG. As in, when you go to set up a device in WYSIWYG, you will not get the offline editor to work like that. When you connect the offline software with WYG, what isn't explained is that you don't have to setup a device in WYSIWYG and there is no "device connected" indicating that it's talking to the desk. It just works! I found the same thing out myself! Just follow the instructions as explained here http://moicestpilou.free.fr/pdf/Wysiwyg_and_ETC_setting.pdf and trust me, it's just works. I spent days getting an error telling me that there was no desk found and realised after all that, it didn't matter, it was working all along anyway and I just didn't know because it appeard as though there was no device connected! I think if I remember correctly, you just have to patch your fixtures all to EDMX and not any other universes that you may have created in WYG.

    Information from all LX desk manufacturers seems far to unclear when it comes to visualization connection. Even with other offline editors I have used, you spend two weeks just trying to figure out how to connect the darn things because you're expected to know half of what's going on already, whereas when I was a beginer who knew very little about pre-viz stuff I really struggled! Bring on the age of the idiots guides :D

    Hope this helps man!

    Kraig.

  • I think it has probably been covered here, but there is a Wiki article about this:

    http://community.etcconnect.com/wikis/products/knowledgebase-connecting-eos-ion-element-to-a-visualiser.aspx

    If you feel it is lacking, well...it is a Wiki!

    -luke-

Related