|
Post by mikalos on Sept 5, 2016 19:29:11 GMT -5
It is not clear to me if it is possible to transfer large portions of the patch information from Eos to Lightwright 6 (we have not upgraded yet, so i can't just try it).
I have inherited a show that used Lightwright 5 and recorded all channel numbers, most of the conventional dimmer numbers, and the start addresses of moving lights, but no addressing for other fixtures with DMX attributes.
If this can be done, is there some way to make a partial selection, or would we overwrite *all* the DMX information that is already in Lightwright?
I saw the "Compare console patch vs. Lightwright" function in the video, but it did not show actually importing the data.
I don't need to know the details right now, just if it is possible - that will help convince management to pay for the upgrade.
I assume i will first need to change all the fixture types using the new libraries - the LW5 file did not make use of multi-attribute fixtures.
Thank you Kevin for starting this forum!
|
|
|
Post by harrisoncity on Sept 6, 2016 8:48:25 GMT -5
The patch transfer is in only one direction and is not through the console connection. You can export your patching information to a file that can be uploaded to an Eos console. I believe this was done to keep a "Master" patch in console, so that someone couldn't randomly send a bad patch from Lightwright in the exchange.
|
|
|
Post by Kevin on Sept 6, 2016 14:16:35 GMT -5
The LW to EOS patch transfer is a huge time saver. You just choose Export , For EOS Family Consoles.
Then you bring the file to the EOS and choose File, Import, Lightwright.
You can then choose what data columns you want to map to what. You can also choose what ML libraries in LW you want to MAP to the ML libraries in the EOS, they are not the same and do not transfer directly.
But regardless it all beats typing it in manually!
|
|
|
Post by mikalos on Sept 6, 2016 19:17:00 GMT -5
Thanks guys, but i want to go the other way - send patch data *from* the Eos to Lightwright.
|
|
|
Post by mikalos on Sept 6, 2016 20:01:32 GMT -5
I found the other thing that confused me about this - on the mckernon.com page listing all the new V.6 features, it says "Export Patch & Purposes to Console" under Live Eos Connection, but the "Patch" part is not shown in the videos.
What i was really hoping is that the "Compare console patch vs. Lightwright" function would let you select which was correct and then make the other one match. Maybe that will be in a future version . . .
|
|
|
Post by johnmcsoft on Sept 7, 2016 8:39:57 GMT -5
The "compare console patch vs. Lightwright" feature can automatically update the Lightwright patch with data from Eos, but only when there's no ambiguity in the data. For instance, on Eos channel 42 has addresses 345 and 346 assigned to it. When the patch data comes to Lightwright, there's no way for it to know which worksheet rows get 345 and which get 346 without reading your mind. The compare patch report tells you which entries it can fix automatically, and which it can't.
The best way to see how this works is to give it a try - and you can do it without a console by installing the Eos software on the same computer as Lightwright.
|
|