images (photos) in sequences and FPP?

[rickswa]

Hi All,

This is my first year using a pi 3B+ with Falcon FPP.  I have it working now on a couple of elements I setup to test it out.  My question is about having images (photos) that show up on a Megatree during the sequence.  With all the new releases of Xlights and FPP, I just want to make sure I don't miss anything since that won't be put together until it's in the yard.  Is it still true that if I have an image like candy canes show up for part of the sequence on my tree that when x-lights creates the FSEQ file, the image is embedded in it so I don't have to upload any images to FPP in order for it to show up?  I was just confused by the "images" tab within the FPP interface so I was curious if I did have to upload, and possibly define this location somehow in xlights, of any images I use in the sequences.  Also, as I understand it so far, it's best to use the fseq v2 setting in x-lights when creating the file.  Would this be the correct way of thinking?  Thank you for any help you can give me.

[Emuney18]

You do not need to put images in FPP because they get encoded in the fseq like you said. The images get translated into defining what pixels need to light and what color to make up the picture.  I think the v2 fseq is the preferred choice now because it is smaller in size and if transferred to the FPP device through xlights then an optimization happens and only the needed channels get sent to that device.

[rickswa]

thank you so much for the reply.  I really appreciate it.  Makes it all clear again for me.

[JonB256]

I think the v2 fseq is the preferred choice now because it is smaller in size and if transferred to the FPP device through xlights then an optimization happens and only the needed channels get sent to that device.

There are Two V2 fseq choices (in xLights and FPP Connect)

There is V2 and then V2 Sparse

V2 uses compression to dramatically shrink the file sizes. All newer versions of FPP software support this for use on Standalone, Master or Remote (Bridge mode doesn't use any FSEQ files).

V2 Sparse is even smaller. If you've done a good job of defining your controllers and universes and channels in xLights, then FPP Connect will create custom FSEQs for each FPP containing only the channels defined for that specific controller. This is what you described as "only needed channels get sent"

Having just talked with Dan about this, the fastest way to update your FPP controllers with updated FSEQ files is by using FPP Connect in xLights. The "older" but still working method was to just update the Master and then have the Master update the remotes.