
Originally Posted by
james
Recently, dchammonds, Dean, asked about adding a return path (blanked) from the last point back to the first in an ilda file.
From what I can tell, most application developers have their own idea about what an ilda file is and what it should contain.
Is it supposed to be something that can be directly clocked out of a DAC or is it just a way to get art into an application for further processing?
My app has no direct connection to being able to "play" an ilda file, so I don't really have any expectations about that.
It has utilities to make files for SD card readers.
What do you use to display directly from an ilda file?
James.
IMHO, as the ILDA Image Data Transfer Format Rev 011 implies this is merely a image data transfer format "standard" provided in order to share laser images that are expressed in a standard format, and it in no way implies that all the header and footer data bits must be used by any and all laser display software when displaying the image data. The header's number of points in a frame data can be useful when the footer "End Of File (EOF) " data is ignored. And the number of points in the frame can be ignored if the EOF is used to determine when to loop back to the start of image.
It always made the best sense to me to provide the necessary "beam(s) OFF) command at the end of an image along with the appropriate intra-point or repeat-point delay before the beam(s) are turned on at the start of an image, along with XY DAC driver and RGB software that responds accordingly.
It would seem that the capability dchammond asks for is already there for that blanked return path data to be added at the end of an ILDA frame. Its the DAC driver software that is the key to a successful implementation.
I would think Pangolin's software does this, I know mine does. I only have QuickShow but will soon find out how well it handles blanked return path data with old show images I'm converting to ILDA's format 5.
________________________________
Everything depends on everything else