Falcon Pi Player Pr...
 
Notifications
Clear all

Falcon Pi Player Proposed sequence format

84 Posts
11 Users
0 Reactions
30.6 K Views
Posts: 135
(@ptone)
Estimable Member
Joined: 16 years ago

Just want to say this has been a great thread - I think the input to have a version identifier is good, and I think it can be optional to have the universe mapping in the playback file, perhaps that would be a different config file, or would be setup manually through the player UI.

-P


Reply
dpitts
Posts: 1020
Topic starter
(@dpitts)
Noble Member
Joined: 16 years ago

Besides hammering out the details of the format we are also going to need a name for format. Something that looks good in a drop down list of Xlights, HLS or any other programs that may want to export to it.


Reply
Posts: 135
(@ptone)
Estimable Member
Joined: 16 years ago
dpitts wrote:Besides hammering out the details of the format we are also going to need a name for format. Something that looks good in a drop down list of Xlights, HLS or any other programs that may want to export to it.

I do think keeping this focused on a "dumb" uncompressed format makes sense. Basically a raw stream of values akin to uncompressed video or audio. There can always be compression formats added later as warranted.

so with that, here is my take-it-or-leave-it brainstorming seed contribution:

blizzard
squall
surge

-P


Reply
Posts: 843
(@captainmurdoch)
Prominent Member
Joined: 14 years ago

Re: WWxD - What would xLights do?

dpitts wrote: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.

I think if you leave it up to the player then does there even need to be anything in this file format to handle universe size? I could see each player having their own 'map' file either internally in the player itself or as a separate user-configurable file.

FPP's internal map might look like this:
* channels 1-128K go out E1.31 as Universes 1-256.

If FPP supported other output methods such as a USB DMX dongle, the map might look like this:
* channels 1-128K go out E1.31 as Universes 1-256.
* channels 131073-131584 go out the USB dongle channels 1-512.

OR perhaps the user-configured map overlaps like this:

* channels 1-128K go out E1.31 as Universes 1-256.
* channels 1025-1537 go out the USB dongle channels 1-512.

Another configurable player's map might look like this:
* channels 1-512 go USB DMX dongle as channels 1-512
* channels 513-4608 go out E1.31 as Universes 1-8
* channels 4609-4636 go out another driver/output.
* etc.

I see this file as raw channel data and the player is responsible for mapping that data onto the outputs the player is playing through. The converter is responsible for mapping the sequencer file channels onto this raw channel data file. Theoretically a converter program could allow other features such as duplication of a single sequencer channel's data onto multiple raw file channels for instance if a user wanted to send the same values out two separate E1.31 universes' channels to drive separate lights on opposite sides of their yards while the rest of those two universes' channels were unique.


Reply
dpitts
Posts: 1020
Topic starter
(@dpitts)
Noble Member
Joined: 16 years ago

Re: WWxD - What would xLights do?

CaptainMurdoch wrote:I think if you leave it up to the player then does there even need to be anything in this file format to handle universe size? I could see each player having their own 'map' file either internally in the player itself or as a separate user-configurable file.

FPP's internal map might look like this:
* channels 1-128K go out E1.31 as Universes 1-256.

If FPP supported other output methods such as a USB DMX dongle, the map might look like this:
* channels 1-128K go out E1.31 as Universes 1-256.
* channels 131073-131584 go out the USB dongle channels 1-512.

OR perhaps the user-configured map overlaps like this:

* channels 1-128K go out E1.31 as Universes 1-256.
* channels 1025-1537 go out the USB dongle channels 1-512.

Another configurable player's map might look like this:
* channels 1-512 go USB DMX dongle as channels 1-512
* channels 513-4608 go out E1.31 as Universes 1-8
* channels 4609-4636 go out another driver/output.
* etc.

I see this file as raw channel data and the player is responsible for mapping that data onto the outputs the player is playing through. The converter is responsible for mapping the sequencer file channels onto this raw channel data file. Theoretically a converter program could allow other features such as duplication of a single sequencer channel's data onto multiple raw file channels for instance if a user wanted to send the same values out two separate E1.31 universes' channels to drive separate lights on opposite sides of their yards while the rest of those two universes' channels were unique.

I believe mapping at the player level makes alot of sense. I really am leaning towards a simple format such as the one Zeph first proposed with an integer refresh rate instead of numerator/denominator. With added field to change number of channels per universe but if set to zero ignore it. The FPP will be a fixed 512 channel universe. Unless someone comes up with a good reason to be able to change it. Just for clarity the FPP will output 128 universes or 65536 channels.


Reply
Page 9 / 17
Share: