Import ashow file and move the colour palletts HELP

Hi,

I've done this on a number of occasions. If your Presets only contain colour information (quite likely from a Strand) you can simply do Preset 261 Thru 268 Move To (double tap Copy To) Color Palette 261. All your cues will be updated with the references to the new Color Palettes.

Hope that's a help.

Oh my.... i knew its was going to be something easy.

On another note some of our intensities have a big + next to them 100+

Is this a hang up of strand scaling? 

That'll be because you have additional intensity parameters, most likely mechanical dimmers for tungsten movers I expect. If you tap [Format] until you can see the table view you should see additional parameters within the Intensity section. If not hold [Params] and enable them using the soft keys.

Indeed they are TW1's 

Go-on i'll hit you with one more.....(i ve just re-read and its more like 2) 

Are there any hard and fast rules to converting from Stand to EOS,

Is the Blocking/Asserting Xfading an isssue?

Not knowing the show but we have some hard commands blocking individual parameters, but no Blocks in the show file. (i may have to crack open the old OLE and look at the two side by side)

When we imported we choose 'Use Library Fixtures" is this the right option 

Many Thanks 

Olly B

Indeed they are TW1's 

Go-on i'll hit you with one more.....(i ve just re-read and its more like 2) 

Are there any hard and fast rules to converting from Stand to EOS,

Is the Blocking/Asserting Xfading an isssue?

Not knowing the show but we have some hard commands blocking individual parameters, but no Blocks in the show file. (i may have to crack open the old OLE and look at the two side by side)

When we imported we choose 'Use Library Fixtures" is this the right option 

Many Thanks 

Olly B

So...

I'm pretty sure the import does takes blocks across, but obviously the Eos has the Assert concept which was kind of integrated into Block on the Strand and if I remember correctly Eos doesn't create asserts for every block. So I expect you'll need to add Asserts back in where necessary.

Import 'As Library Fixtures' will try and match the fixtures from the imported file with built in Eos fixtures, but as Strand didn't include anything to identify fixtures it's not absolutely bullet proof. If you're just wanting to pull a show and run it without much work it's safer to use 'As Custom Fixtures', but if you're planning on doing some relighting I'd personally go with Library Fixtures, you may lose some of the original though.

Effects are also one thing to watch out for. On the Strand the effect was attached to the cue, but on Eos they're attached to channels, so often the effects will keep running in subsequent cues. You'll likely need to go through and put stop commands on the subsequent cue to stop the effect running.

It's always handy to have the OLE or a print out of the strand show file as well!

I hope that's a help!

Dan

Thanks Dan, That all makes sense now. Its nice to have a brief step back in time!