Re: Adding named blocks of channels, to handle universes and more!
Zeph,
You input has been enlightening. I do not mind it in this thread.
Re: WWxD - What would xLights do?
About supporting the concept of DMX style universes in the file format...
Zeph wrote:
And if all that requires is two optional fields in the header, for number of universes and a common channel count for all universes, that's easy! So I'm waiting to hear responses to your question about whether that's sufficient. I'm guessing that implies that the the first N channels would be in universe 1, the next N in universe 2, and so on sequentially.
I'm going to shelve this discussion until that gets resolved.
Re: WWxD - What would xLights do?
Zeph wrote:About supporting the concept of DMX style universes in the file format...I'm going to shelve this discussion until that gets resolved.
We can do both. Different counts for universes and same count for all universes. We can create a field for universe size that will be size for all universes. For most players that will be fine. For those players that need to send different channels counts to different devices. The splitting up of the channels of each step can be setup in the configuration of that player.
Zeph wrote:Phil, would you want to be able to describe different rates for different (groups of) channels?Based on that suggestion, which I hadn't considered, I thought "we could let the speed be configured by universe, or by channel block". But then how would we interleave the data for channels being played at different rates?
If so, my thought would be that if you really want channels to be played back at different rates, make a file for each rate and put the relevant channels into it, then write a player which can play multiple files at once. That could be tricky (the time to send out one set of channels might be just as you were trying to load another set), but the RPi might be able to handle it (big programs, big ram, fast processor - compared to uCs anyway). Using separate files probably makes it easier, if one does take that on.
I'm not thinking it would need to go into the file format. A single speed for the file seems appropriate.
(This is similar to the idea of putting the music in another file to be played simultaneously, rather than try to interleave music sample data with pixel data at different rates).
I was just thinking that different hardware ports might have different data rates, such as DMX at 250 kbps, Renard at some other rate, native pixels perhaps at yet another rate. How to interleave data seemed to be a problem to me, although I know there are various ways to handle this quite economically.
P. Short wrote:I was just thinking that different hardware ports might have different data rates, such as DMX at 250 kbps, Renard at some other rate, native pixels perhaps at yet another rate. How to interleave data seemed to be a problem to me, although I know there are various ways to handle this quite economically.
Yeah, every output will have its own bit level data rate for sending data out, ranging from 100 Kbps to 20 Mbps for pixels, and ethernet speeds for e1.31, etc. I don't think we are discussing dealing with that aspect in the file format tho (being more of a local configuration thing). I think the rate dpitts is talking about is how often new values are sent to the outputs, the timeslice used when sequencing (eg: 50ms timeslices = 20 Hz refresh rate). A player needs to know this so it can play through the steps at the speed intended - and keep in sync with the music.
The only interaction is that the player needs to be able to get all its channels sent out before it's time for the next step.
The sequence time can be found from the number of steps and the play rate.
