Author Topic: FPP 2.3 now available  (Read 3599 times)

Offline pixelpuppy

  • Hero Member
  • *****
  • Join Date: Aug 2015
  • Location: Dallas, TX
  • Posts: 1,160
  • Kudos: 34
Re: FPP 2.3 now available
« Reply #45 on: November 02, 2018, 09:11:36 AM »
It seems like the timer on the remotes carries over from a previous sequence.  Maybe some race condition between the previous sequence StopSync and the new sequence StartSync?   If you can clue me in on the best place(s) to look, I'll start digging
Probably the same idea... turn on excessive logging for multisync on the remote and reproduce.  It should show the masters current frame so we can see if it's getting some rediculous number.


Dan, I'm still looking deeper, but I've determined that this happens when an effect sequence is running in the background.  In my playlist I use events to trigger background effects.  In most cases, its an effect sequence for Tune To matrix that scrolls the song/artist/station, etc.  When an effect sequence gets triggered to start running in the background, and then an fseq sequence starts right after that, the sync times go crazy.   It has something to do with starting the background effect time (or frame number) messing with the foreground fseq time (or frame number)
xLights and Vixen3 for sequencing / FPP for scheduling and playing / Falcon controllers for pixels / homemade controllers for everything else

Offline pixelpuppy

  • Hero Member
  • *****
  • Join Date: Aug 2015
  • Location: Dallas, TX
  • Posts: 1,160
  • Kudos: 34
Re: FPP 2.3 now available
« Reply #46 on: November 02, 2018, 10:34:13 AM »
When an effect sequence gets triggered to start running in the background, and then an fseq sequence starts right after that, the sync times go crazy.   It has something to do with starting the background effect time (or frame number) messing with the foreground fseq time (or frame number)


Dan, 


Please take a look at these two logs (one from Master and one from Remote).  Look at the lines I've highlighted.  This has to be a bug.  I can reproduce it every time.  The first sync packet starts at frame 302.  I don't think its any coincidence that the effect sequence is approx. 300 frames long (20fps x 15secs).  I've also verified that playing the same fseq, without triggering the background effect first, starts syncing at frame 0


Quote from: MASTER
2018-11-02 10:21:52 (1371) events.c:318:TriggerEvent(1, 3)
2018-11-02 10:21:52 (1371) events.c:336:TriggerEventByID(01_03)
2018-11-02 10:21:52 (1371) MultiSync.cpp:698:SendEventPacket('01_03')
2018-11-02 10:21:52 (1371) events.c:216:Event Loaded:
2018-11-02 10:21:52 (1371) events.c:218:Event Name  : Tune To 15 sec
2018-11-02 10:21:52 (1371) events.c:222:Event ID    : 1/3
2018-11-02 10:21:52 (1371) events.c:229:Event Effect: TuneTo887-15sec
2018-11-02 10:21:52 (1371) events.c:230:Event St.Ch.: 30721
2018-11-02 10:21:52 (1371) effects.c:149:Starting effect TuneTo887-15sec at channel 30721
2018-11-02 10:21:52 (1371) effects.c:287:Effect TuneTo887-15sec step size 98304, model size: 98304
2018-11-02 10:21:52 (1371) MultiSync.cpp:425:SendSeqSyncStartPacket('Its Christmas Time Again.fseq')
2018-11-02 10:21:52 (17542) MultiSync.cpp:510:SendSeqSyncPacket( 'Its Christmas Time Again.fseq', 302, 8.21)
2018-11-02 10:21:53 (1371) MultiSync.cpp:553:SendMediaSyncStartPacket('Its Christmas Time Again.mp3')
2018-11-02 10:21:53 (17542) MultiSync.cpp:510:SendSeqSyncPacket( 'Its Christmas Time Again.fseq', 2, 0.03)
2018-11-02 10:21:53 (17542) MultiSync.cpp:510:SendSeqSyncPacket( 'Its Christmas Time Again.fseq', 6, 0.03)
2018-11-02 10:21:53 (1371) MultiSync.cpp:652:SendMediaSyncPacket( 'Its Christmas Time Again.mp3', 0, 0.52)
2018-11-02 10:21:53 (17542) MultiSync.cpp:510:SendSeqSyncPacket( 'Its Christmas Time Again.fseq', 10, 0.03)
2018-11-02 10:21:54 (17542) MultiSync.cpp:510:SendSeqSyncPacket( 'Its Christmas Time Again.fseq', 18, 0.03)
2018-11-02 10:21:54 (1371) MultiSync.cpp:652:SendMediaSyncPacket( 'Its Christmas Time Again.mp3', 0, 1.01)
2018-11-02 10:21:54 (17542) MultiSync.cpp:510:SendSeqSyncPacket( 'Its Christmas Time Again.fseq', 22, 1.06)


Quote from: REMOTE
2018-11-02 10:21:52 (2640) MultiSync.cpp:1422:ProcessEventPacket()
2018-11-02 10:21:52 (2640) events.c:336:TriggerEventByID(01_03)
2018-11-02 10:21:52 (2640) events.c:216:Event Loaded:
2018-11-02 10:21:52 (2640) events.c:218:Event Name  : Tune To 15 sec
2018-11-02 10:21:52 (2640) events.c:222:Event ID    : 1/3
2018-11-02 10:21:52 (2640) events.c:229:Event Effect: TuneTo887-15sec
2018-11-02 10:21:52 (2640) events.c:230:Event St.Ch.: 30721
2018-11-02 10:21:52 (2640) effects.c:149:Starting effect TuneTo887-15sec at channel 30721
2018-11-02 10:21:52 (2640) effects.c:287:Effect TuneTo887-15sec step size 98304, model size: 98304
2018-11-02 10:21:52 (2640) MultiSync.cpp:1360:ProcessSyncPacket()   type: 0   filetype: 0   frameNumber: 0
2018-11-02 10:21:52 (2640) MultiSync.cpp:1213:StartSyncedSequence(Its Christmas Time Again.fseq)
2018-11-02 10:21:53 (2640) MultiSync.cpp:1360:ProcessSyncPacket()   type: 2   filetype: 0   frameNumber: 302
2018-11-02 10:21:53 (2640) MultiSync.cpp:1235:SyncSyncedSequence('Its Christmas Time Again.fseq', 302, 8.21)
2018-11-02 10:21:53 (2640) MultiSync.cpp:1360:ProcessSyncPacket()   type: 0   filetype: 1   frameNumber: 0
2018-11-02 10:21:53 (2640) MultiSync.cpp:1252:StartSyncedMedia(Its Christmas Time Again.mp3)
2018-11-02 10:21:53 (2640) MultiSync.cpp:1360:ProcessSyncPacket()   type: 2   filetype: 0   frameNumber: 2
2018-11-02 10:21:53 (2640) MultiSync.cpp:1235:SyncSyncedSequence('Its Christmas Time Again.fseq', 2, 0.03)
2018-11-02 10:21:53 (2640) MultiSync.cpp:1360:ProcessSyncPacket()   type: 2   filetype: 0   frameNumber: 6
2018-11-02 10:21:53 (2640) MultiSync.cpp:1235:SyncSyncedSequence('Its Christmas Time Again.fseq', 6, 0.03)
2018-11-02 10:21:53 (2640) MultiSync.cpp:1360:ProcessSyncPacket()   type: 2   filetype: 1   frameNumber: 0
2018-11-02 10:21:53 (2640) MultiSync.cpp:1313:SyncSyncedMedia('Its Christmas Time Again.mp3', 0, 0.52)
2018-11-02 10:21:53 (2640) MultiSync.cpp:1317:Received sync for media Its Christmas Time Again.mp3 but no media playing
2018-11-02 10:21:53 (2640) MultiSync.cpp:1360:ProcessSyncPacket()   type: 2   filetype: 0   frameNumber: 10
2018-11-02 10:21:53 (2640) MultiSync.cpp:1235:SyncSyncedSequence('Its Christmas Time Again.fseq', 10, 0.03)
2018-11-02 10:21:53 (2640) MultiSync.cpp:1360:ProcessSyncPacket()   type: 2   filetype: 0   frameNumber: 14
2018-11-02 10:21:53 (2640) MultiSync.cpp:1235:SyncSyncedSequence('Its Christmas Time Again.fseq', 14, 0.03)
2018-11-02 10:21:54 (2640) MultiSync.cpp:1360:ProcessSyncPacket()   type: 2   filetype: 0   frameNumber: 18
2018-11-02 10:21:54 (2640) MultiSync.cpp:1235:SyncSyncedSequence('Its Christmas Time Again.fseq', 18, 0.03)
2018-11-02 10:21:54 (2640) MultiSync.cpp:1360:ProcessSyncPacket()   type: 2   filetype: 1   frameNumber: 0
2018-11-02 10:21:54 (2640) MultiSync.cpp:1313:SyncSyncedMedia('Its Christmas Time Again.mp3', 0, 1.01)
2018-11-02 10:21:54 (2640) MultiSync.cpp:1317:Received sync for media Its Christmas Time Again.mp3 but no media playing
2018-11-02 10:21:54 (2640) MultiSync.cpp:1360:ProcessSyncPacket()   type: 2   filetype: 0   frameNumber: 22
2018-11-02 10:21:54 (2640) MultiSync.cpp:1235:SyncSyncedSequence('Its Christmas Time Again.fseq', 22, 1.06)

Offline bh2545

  • Newbie
  • *
  • Join Date: Dec 2017
  • Location:
  • Posts: 7
  • Kudos: 0
Re: FPP 2.3 now available
« Reply #47 on: November 02, 2018, 06:34:49 PM »
I had the same experience with the spinning circle after clicking upgrade.   After waiting a bit and refreshing, it did upgrade to 2.3 (from 2.1). 


My current issue is on a Pi with a matrix adapter with 2.3 the panel seems to start on channel 1 vs what's configured in the LED Panel configuration (22873).   Worked fine on 2.1 (didn't try on 2.2)

I'm have the same problem with my matrix adapter starting on a completely different channel. We're you able to get it straightened out?


That should be fixed on master.


Confirmed it's working on master.  Thanks Dan!

Offline FrankAZ

  • Jr. Member
  • **
  • Join Date: Nov 2014
  • Location:
  • Posts: 54
  • Kudos: 0
Re: FPP 2.3 now available
« Reply #48 on: November 02, 2018, 06:46:54 PM »
One thing I'm noticing today is if I click on status "multisync" all of a sudden it will go super slow or stop responding on the web browser. It seems to be on all 2.3 ones that are master / remote. I have one running as a bridge, and one as a standalone that don't seem to be impacted.

Offline PeteyHall

  • Full Member
  • ***
  • Join Date: Sep 2016
  • Location: Boston
  • Posts: 225
  • Kudos: 3
Re: FPP 2.3 now available
« Reply #49 on: November 02, 2018, 06:58:37 PM »
One thing I'm noticing today is if I click on status "multisync" all of a sudden it will go super slow or stop responding on the web browser. It seems to be on all 2.3 ones that are master / remote. I have one running as a bridge, and one as a standalone that don't seem to be impacted.
Yup that seems to be a common issue.


Sent from my iPhone using Tapatalk

Offline PeteyHall

  • Full Member
  • ***
  • Join Date: Sep 2016
  • Location: Boston
  • Posts: 225
  • Kudos: 3
Re: FPP 2.3 now available
« Reply #50 on: November 03, 2018, 12:45:40 AM »
One thing I'm noticing today is if I click on status "multisync" all of a sudden it will go super slow or stop responding on the web browser. It seems to be on all 2.3 ones that are master / remote. I have one running as a bridge, and one as a standalone that don't seem to be impacted.
Yup that seems to be a common issue.


Sent from my iPhone using Tapatalk

I don't know if it's coincidence or if it was fixed, but I just downloaded the latest master build on my controllers and the multisync page is working again.  I did notice in the release notes a comment about making some changes to multisync so not sure if that was it or not.

Offline FrankAZ

  • Jr. Member
  • **
  • Join Date: Nov 2014
  • Location:
  • Posts: 54
  • Kudos: 0
Re: FPP 2.3 now available
« Reply #51 on: November 03, 2018, 05:35:45 AM »
Well, I moved all to master branch - I'll see what happens!

Offline Jradical

  • Newbie
  • *
  • Join Date: Apr 2015
  • Location: Australia
  • Posts: 30
  • Kudos: 3
Re: FPP 2.3 now available
« Reply #52 on: November 03, 2018, 05:53:26 AM »
I don't know if it's coincidence or if it was fixed, but I just downloaded the latest master build on my controllers and the multisync page is working again.  I did notice in the release notes a comment about making some changes to multisync so not sure if that was it or not.
It's probably just a coincidence, multisync page received some small changes but nothing that directly addressed the issue described here.
I have a BBB on 2.3 and the issue isn't present. Keep an eye out for if it happens again.
« Last Edit: November 03, 2018, 06:01:05 AM by Jradical »
7th year sufferer of CLAP
I dream of WS2811 Pixels.

Offline JonB256

  • Supporting Member
  • ******
  • Join Date: Mar 2013
  • Location: Granbury, Texas
  • Posts: 4,885
  • Kudos: 109
    • Granbury Christmas Lights
Re: FPP 2.3 now available
« Reply #53 on: November 03, 2018, 09:18:05 AM »
Multisync is checking more things than it used to check.

If you want to see "slow" click on the Advanced view. (but, Advanced is a great place to see what might need Updating)

 

Back to top