• State Not Answered
  • Date
    Rowan
  • Date
  • Replies 3 replies
  • Subscribers 184 subscribers
  • Views 3943 views
  • Users 0 members are here

Moving lights from a strand

Hi

I'm sure that this has been asked before, but I can't find it.

 

I'm trying to import a show from a 500 series onto an Ion. I have the show in Ascii. When I import it onto the Ion, all of the generics work fine, however the movers do not. I can go through the file and amend each of the movers in every cue, this is taking ages, and I don't think I'll have enough time in the venue to check that I haven't made any mistakes. I was just wondering if there was a better way that will import all of the info and reference data.

 

  • 0

    When you import from the ASCII file, are you importing as Eos fixtures, or as custom fixtures?

  • 0 in reply to Andi.Davis

    I've tried doing it as both, I get the same results each time

  • 0 in reply to Rowan

    Ok, what moving lights do you have in your rig?

    Generally speaking, what you should find is that importing as custom fixtures guarantees more of your data - but the resulting fixtures can be a little 'odd' (basically Eos has to try and 'guess' equivalent parameters for the ones used in your Strand fixtures). By contrast, importing as Eos fixtures gives you nicer end result fixtures, but you may lose more data during the transfer.

    I suppose what I'm asking is: is the problem that the data is importing but onto odd parameters (so for example you end up with edge information on the zoom parameter)? Or is it that the information is missing completely?

    Basically there are no quick fixes for this - and the results are always a little unpredictable because its often dependent on how the fixtures were built on the 500 Series (and how Eos then interprets that info). However, I do have a lot of techniques for speeding these kinds of processes up once I know a little more where things are going awry in your situation... :-)

Related

www.etcconnect.com