I got a speedy reply from Joe of HLS. Here are the paraphrased suggestions he made followed by my thoughts in parentheses.
1) Keep it binary.
2) Have support for E131 packets that have less than 512 bytes by including number of bytes per universe in the header.
3) Wait for 16 bit support until it becomes more popular. (By adding version and format identifier we could easily change format later or just add a byte to specify data size and set it to '1' for now).
4) Include number of universes and starting universe. (Both of these were going to be implemented in webpage interface during setup of player).
He is very accommodating and stated he would support an export from HLS to the format we choose.
Ok, here's a quick revision for further review.
I'd like to see this done fairly well, as it's likely to wind up sticking around for a while (since the need for a simple binary sequence format has been described before).
This is not done, just another draft.
I look at this as: can all the enhancements be coded on an Arduino (ie: minimal hardware) in half an hour or less (beyond the barest minimum format)? I've only considered things which add some value or flexibility, but which are trivial to implement.
I like it. Where should the universe count and size of universe be located? In the sequence file itself or a separate "Player control file"? Having start universe in a player control file makes good sense because if you want to change start universe you do not need to change the sequences. But universe count and size of universe seems so closely related to data structure it may be good to include in sequence since converter or sequencer would have to recreate the file anyway. Also the "int" labeling in your spec gets my mind thinking 32 bits. 8-bit int[n] was hard for me to compute. Maybe we can change it to 8-bit byte[n] or char[n]. Just the programmer in me. If anyone else wants to jump in, please do. This is not the final decision just brain storming. Although we are leaning towards a binary file to keep Pi from having to compute large text files.
I ran a small FTP test to PI. Using FireFTP plugin for Firefox connected to a PI on LAN, it took 8 minutes to transfer one 1.65 GB file.
I thought i'd drop my 5c in about 16 bits. The Pixels we sell commercially, have 16 bits of control. However, as has been said, there is no need to be able to use *all* of these 16 bits. In fact, i'd argue that 7 bits are enough to represent enough states, so you can't distinguish between them. The 16 bit capablility gives us the ability to buidl extremely smooth responses right down to the very very low levels. in fact, at level 1, many people say they can only just see it turned on. ( some say they can't ). I can see a difference between 1 and 2, but beyond that, i cant' pick changes..
So, our controllers convert standard 8 bit DMX values into 'corrected' 16 bit values.. I'd suggest that it is the end controller that is the right place to put this capability surely?
