2022.19 F16V4 Build 22 Incomplete Frames

[breese]

I recently started getting Incomplete Frame messages when turning on the Output to Lights in XLights.

I am including the Log file from my F16V4

You cannot view this attachment.

[JonD]

They did release a newer version of xlights, but I did not see that error listed in the fixed section. 

Seems like I have seen that in the past.  Don't remember the fix though.  Could you have FPP running at the same time?  Might have been my FPP start channels did not match xlights after the 6.1 upgrade.  On the xlights controller tab, it will list the FPP start channels and compare them to what FPP has listed.  Not sure it was happening when outputting from xlights though. 

I am a lot of help aren't I?  

Have you added ports to your controller, upgraded to 6.1, or anything else new recently?  I want to say it was a mis-configuration, or deleting the ports and recreating them.  Seems like on the status page there was a lot of activity on one of the universes or something. 

[breese]

So I did a little more digging.
Seems the issue happens when I switch the Falcon from Player to E131.
If I do not Reupload the configuration from XLights (even if nothing has changed or been added) the Incomplete frames happen.
Once I resend from XLights, all is well.

Do we really need to reupload the configuration everytime we switch the falcon?

[JonD]

Seems the issue happens when I switch the Falcon from Player to E131.

I am only aware of player/remote settings on the FPP and did not realize there was an E1.31 option?  How are you doing this? 

My show is typically played from a FPP player.  If I want to output directly from xlights, I just turn off the FPP playlists, and then hit the light bulb in xlights and turn it yellow.  As long as both are not trying to play at the same time, it works fine.  I had the same issues, but it was a once and done.  Not something I have dealt with since I corrected it.  It does seem like I had to recompile the sequences in xlights, after I figured out what the problem was.

[breese]

Seems the issue happens when I switch the Falcon from Player to E131.

I am only aware of player/remote settings on the FPP and did not realize there was an E1.31 option?  How are you doing this? 

Correct, FPP on a Pi or other device is player or remote.
The Falcon can be set on the status page as e1.31, DDP, player, remote, and something else.
If the Falcon is set to player mode and you turn on the Output to Lights, then the Messages start happening on the Falcon.

[Poporacer]

If the Falcon is set to player mode and you turn on the Output to Lights, then the Messages start happening on the Falcon.

If the Falcon is set to Player mode, then you are saying that it be the "conductor" of the show (AKA Boss) but if you have the Output to Lights on in xLights, then xLights is trying to be the conductor/boss.... I don't think your F16 like someone else trying to be the boss when you told him that he was the boss. If you want the Falcon to listen to xLights when you turn on the output to lights, then you have to let him know that he is now demoted to E1.31/DDP status and no longer the boss.

[JonD]

The Falcon can be set on the status page as e1.31, DDP, player, remote, and something else.

Gotcha... I missed your were referring about the Falcon Controller.  Too many dang things called Falcon something!