Conversion of 16-bit Pan/Tilt values into degrees.

I've found the answer to this question - EOS outputs pan/tilt data in 16-bit format in its ASCII export and the exported values match up with the 16-bit values I'd originally converted to degrees to type into EOS - so that's all fine.

Next question: I now have an Excel spreadsheet with more than 1,000 pan & tilt values converted from 16-bit to degrees. Is there any way of importing this data into EOS? I tried manually adding another focus palette record to an EOS ASCII export, but when I attempt to import that ASCII file I end up with a blank show file, even just selecting Palettes for import. Any ideas why this file doesn't import (see attached)? It'd be so much quicker to populate this file with all the focus palette data than it would be to type it all in to the OLE.

Thanks,

David

Hi Anne, yes the data is coming from Virtuoso.

The ASCII file I attached to my last post was exported by EOS, though. Browser, File, Export...

Using ASCII is it possible to import focus palettes, and if so what is the correct syntax to use?

Many thanks,
David

Eos currently exports ascii, but doesn't load any of the data in it's own ascii files other than the data specified in the USITT standard, which doesn't specify non-intensity data. That may sound odd, but importing the fixture specific data in an Eos ascii file would require different things than importing an Obsession or other console's ascii file, because that data is not in the standard.

So unfortunately for now, I don't think you will be able to add non intensity data to that file and have Eos read it yet. On monday I will talk to our show file conversion guy and ask him if any of the ascii formats we support are easily editable and could be used as a template file. I would guess no though, because for the consoles where we read in their non-intensity ascii data, I believe they export 16 bit values as two channels in ascii. This would make them more difficult to edit.

Cheers, Dan, that makes a lot of sense.

If you were able to find any ASCII format that EOS will read focus palettes from I'd be very keen to see it. I now have all the focus data I need to import in electronic format and can process it into any format that is suitable for EOS, even if that means splitting 16-bit values into two 8-bit ones.

I've got until Thursday to get this done so I can wait a couple of days to see if a suitable format exists, and after that the worst case is that I'll have to enter the data manually, which should only take a few hours. It's just very tedious :)

Thanks,

David