Remedial Training R...
 
Notifications
Clear all

Remedial Training Requested

3 Posts
3 Users
0 Reactions
868 Views
Posts: 3735
Topic starter
(@algerdes)
Famed Member
Joined: 15 years ago
[#54997]

I asked this up on Facebook, but thought I'd ask here as well.

When xLights (and Vixen) creates the .fseq file, the instructions are in order. I believe there are no gaps. (Correct me if I am mistaken.)

The players (xSchedule and FPP) read this file and send the data out onto the line.

The controllers (all forms) receive the data and tell pixels connected to their outputs to set their levels accordingly.
Controllers are looking for specific Universes, ignoring what is not assigned to them.

At what point does the order of commands get paired up with the proper universes?

(And yes, I have a reason for asking.)


2 Replies
MartinMueller2003
Posts: 7614
(@martinmueller2003)
Illustrious Member
Joined: 14 years ago

You are putting too much emphasis on the existence or even need for a universe. When a show player needs to send a frame of data to a controller, the show player will map the frame to the protocol being used to transport the frame data over the Ethernet media. In the case of the E1.31 protocol, the show player further breaks the frame down into smaller blocks that fit within the E1.31 protocol packet. E1.31 calls that smaller block a universe. That is the only use for a universe.

FYI: controllers do not need the concept of a universe either. For example: The ESPixelStick when configured to receive E1.31 data will take the universe data and map it to a frame buffer and then forget the E1.31 layer exists.

There are also altrnatives to E1.31 like DDP. DDP uses a completly different mechanism to map the frame data to Ethernet packets. No universes at all.


Reply
Barnabybear
Posts: 1583
(@barnabybear)
Noble Member
Joined: 15 years ago

Hi Al, it’s a wile since I looked into this, from what I remember (please correct if I’ve lost the plot).
To define the elements:
A sequencer: This is used to cerate a show. A series of channels are defined against a time line and saves them as a file.
A player: This takes the file produced by a sequencer and converts it using ‘mapping’ to send the data contained in the file to the appropriate receiver.
A controller: This receives data from the player and illuminates the lights accordingly.

As there are many combinations of sequencers, players and controllers these days I’ll run through the most common.
You use XLights or Vixen as a sequencer to create your show. This creates a number of ‘channels’ that are numbered 1 to the extent of your show (I’ve had 1 to 35,000 in the past with a matrix. I’m guessing people may be running 100’s of x that). That is the sequencers job done and the it outputs is a .fseq file. As you correctly stated this contains the output level for every single element in your show.
For reference:
If you have as I did 35,000 channels at 40 FPS for a 2 minuet display this equates to 2.8 million values of data.
Back to the answering the question.
Once a sequence (.fseq file) has ben created it needs to be transmitted to a controller, this is the job of a player. XLights, Vixen or FPP (Falcon Pi Player) are more commonly used as players. It is at this point that the channels that where created by the sequencer are divided up in to blocks to be transmitted to the players.
This sort of answers your question.
A player takes a channel and maps it to a DMX, Renard or E1.31 universe and subsequently transmits it, the controller receives these channels and outputs as instructed.


Reply
Share: