smeighan wrote:When Matt Brown designed xlights, one of his architecture designs was that xlights would only support one timing, 50ms. Currently you cannot change this., If you have a 25ms frame timing and cinvert it in xLights, the new sequence will be 50ms.
Thanks Sean - I was afraid that was the case and the extra step is not that bad, I just go into a 50ms vixen temp sequence and then convert to 25ms. -
fyi My Vixen 2.1 sequences @ 25 ms & 6,000 channels are only running ~ 50 MB on average 🙂
klyneshouse wrote:Thanks Sean - I was afraid that was the case and the extra step is not that bad, I just go into a 50ms vixen temp sequence and then convert to 25ms. -
fyi My Vixen 2.1 sequences @ 25 ms & 6,000 channels are only running ~ 50 MB on average 🙂
Vixen uses base64 to store the effects. This is the second most efficient way to store the data.
Here is a comparison to the file sizes of the same song in the different sequencers
So here are the sequencers. You see how long it took xlights to export the file and how big the final file was. These were all on my 20x120 , 2400 node megatree (so 7200 channels). Song was TSO Winter Palace.
1) LOR *.lms. 157 seconds, 704mbytes
2) Vixen *.vix. 14 seconds, 31mbytes
3) Xlights *.xseq. 3 seconds, 23mbytes
4) HLS *.hlsnc. 23 seconds, 57mbytes
thanks
sean

