I have thought about this several times. However, in the interest of keeping things simple, I am not inclined to make the timing configurable.
Can't xLights just read the timing from the Vixen sequence or profile that it's playing and adjust accordingly--so there would be no configuration required? Or is there something I'm missing?
Sorry if this thread if grating on you as so many people are asking for this feature.
It is not grating on me at all. I think it is a good discussion.
My input:
xLights now has several roles - it is a scheduler capable of driving a variety of protocols, it is a sequence file conversion tool, it is a test tool, and most recently, RGB effects generator (thanks to Sean and Nutcracker). ALL of these roles are based on 50ms timing. If I give you a choice of timing, I can't do it for just one section of the program, I need to make it work with all of xLights - across all functions and all protocols and all platforms (Windows, Mac and Linux). This would be a HUGE task, requiring a huge amount of testing, and raise new issues that would need to be addressed. For example, the xLights (xseq) format is based on 50ms timing. Now various xseq files in your show directory might each contain different timing. The scheduler would have to be prepared for this scenario, requiring extra code, and making playback slightly less efficient. The xseq file format would need to change, at least slightly to accommodate this. How do each of the timings work with each of the supported protocols (needs testing)? And on and on...
From my point of view, the costs outweigh the benefit. I would much rather spend my time adding capabilities to the RGB effects generator.
Sincerely,
Matt
