• Date
    David Buffham
  • Date
  • Replies 8 replies
  • Subscribers 182 subscribers
  • Views 12252 views
  • Users 0 members are here

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

Hi, I'm in the middle of transferring an existing show into EOS. In the existing show file the pan/tilt values are expressed as 16-bit values, which I need to convert to degrees. I'm reasonably sure I know how to do this but I would like to just confirm what DMX values the EOS outputs at each end of the pan/tilt ranges. I'm working offline and I don't have access to a console right now so I can't check this for myself until next week, and I'd rather not get this wrong...

For a tilt range of -135 to +135 degrees, can I assume that -135 degrees => DMX 0, 0 degrees => DMX 32767, and +135 degrees => DMX 65535?

For a pan range of -270 to +270 degrees, can I assume that -270 degrees => DMX 0, 0 degrees => DMX 32767, and +270 degrees => DMX 65535?

If someone's able to confirm that those assumptions are correct then I can quite easily convert the existing show's 16-bit values into degrees for inputting into EOS.

Many thanks,

David

  • 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

     

     

    export.zip
  • in reply to David Buffham

    Funny, I was in the middle of converting pan and tilt to degrees for my Christmas show in excel when your post showed up. I don't have as much input work to do as you do, but I am very interested in the method for automating this. I am converting a show from Obsession I.

    Tim

  • in reply to David Buffham
    Hey David... a couple of things.  At the moment, the only file import we support other than .esf is ASCII.  And we don't currently export ASCII.  We are looking into that for sometime in '08, but felt our biggest priority needed to be show file importing.   You are trying to import this from Virtuoso show files?  

    a
  • in reply to Tim Wilson
    Tim for your imports, you will need to save your Obsession 1 show files in an Obsession 2 file format.  And then you need to save that Obsession 2 file as an ASCII file using Obsession 2 offline.  I believe there is information in the Obsession manual about this, but if you run into trouble, you can either ping tech support or call David West at Wunder Lighting (he's your rep).  He can talk you through this....

    Thanks!

    a
  • in reply to Anne Valentino

    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



    [edited by: David Buffham at 8:32 AM (GMT -6) on Sun, Nov 11 2007]
  • in reply to David Buffham

    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.

     

  • in reply to Anne Valentino

    Hi Anne,

    I did all the conversions and the show is in the board. I am now converting the pan/tilt values to degrees and inputing them. They were of course seperate channels in Obsn I. This is the only show I have to bring over for the time being.

    Tim 

  • in reply to Dan Duffy

    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

     

Related

www.etcconnect.com