Falcon Player - FPP v1.9 is now available

Author Topic: Falcon Player - FPP v1.9 is now available  (Read 20059 times)

Offline Sawdust

  • Hero Member
  • *****
  • Join Date: Nov 2015
  • Location: Northern CA
  • Posts: 500
  • Kudos: 6
Re: Falcon Player - FPP v1.9 is now available
« Reply #60 on: May 12, 2018, 03:41:45 PM »
I am not liking 1.10.....if I keep a log in excel, it will drop the trailing zero, making it 1.1  What would be wrong with going to 1.9.1 or maybe 1.9A, or 1.9x1


« Last Edit: May 13, 2018, 08:46:17 AM by Sawdust »

Offline jnealand

  • Developer
  • ******
  • Join Date: Aug 2013
  • Location: Kennesaw, GA
  • Posts: 2,484
  • Kudos: 50
Re: Falcon Player - FPP v1.9 is now available
« Reply #61 on: May 13, 2018, 02:29:42 PM »
Too late to change now and besides it is going away by mid year.  But I feel your pain.
Jim Nealand
Kennesaw, GA Falcon and Lynx, all 12v Multisync with Pi and BBB P10 and P5

Offline Sawdust

  • Hero Member
  • *****
  • Join Date: Nov 2015
  • Location: Northern CA
  • Posts: 500
  • Kudos: 6
Re: Falcon Player - FPP v1.9 is now available
« Reply #62 on: May 14, 2018, 07:13:58 AM »
Yes, too late for 1.10, but knowing 1.9 to 1.10 presents an issue can help guide how 2.x is handled.

Offline stevej

  • Newbie
  • *
  • Join Date: Mar 2018
  • Location:
  • Posts: 3
  • Kudos: 0
Re: Falcon Player - FPP v1.9 is now available
« Reply #63 on: June 03, 2018, 06:00:55 PM »
Is this or the github page the better place to report an issue?


Anyhow, I'm seeing a UI problem on v1.10 when I try to save the "other" channel config.  The row disappear and I get the following javascript error in the console. 


Code: [Select]
channeloutputs.php:1251 Uncaught TypeError: Cannot read property 'Outputs' of nullat PopulateChannelOutputTable (channeloutputs.php:1251)at Object. (channeloutputs.php:1512)at fire (jquery-1.9.1.js:1037)at Object.fireWith [as resolveWith] (jquery-1.9.1.js:1148)at done (jquery-1.9.1.js:8074)at XMLHttpRequest.callback (jquery-1.9.1.js:8598)

It should be noted that manually editing the channeloutput file is a viable workaround.


Also, using a PiCap, it seems to work if I exceed the 1000 pixel limit imposed by the UI.  Limited testing with 1440 pixels seems to work fine.  Can anybody confirm the real limits?

Online JonB256

  • Supporting Member
  • ******
  • Join Date: Mar 2013
  • Location: Granbury, Texas
  • Posts: 4,327
  • Kudos: 89
    • Granbury Christmas Lights
Re: Falcon Player - FPP v1.9 is now available
« Reply #64 on: June 03, 2018, 08:05:22 PM »
I dont know of much development still on v1.10

V2.0 is getting the attention

Sent from my SM-G955U using Tapatalk


Offline dkulp

  • Developer
  • ******
  • Join Date: Sep 2013
  • Location: Framingham, MA
  • Posts: 828
  • Kudos: 35
Re: Falcon Player - FPP v1.9 is now available
« Reply #65 on: June 03, 2018, 08:15:01 PM »

Also, using a PiCap, it seems to work if I exceed the 1000 pixel limit imposed by the UI.  Limited testing with 1440 pixels seems to work fine.  Can anybody confirm the real limits?


Depends on the sequence timing.... If you use 25ms sequences, the limit is really about 800.   If you exceed 800 pixels with 25ms timing, I'm not sure what will happen.  The F8-* capes will start dropping frames.  Not sue what the Pi's would do.
Dan Kulp

Offline pixelpuppy

  • Hero Member
  • *****
  • Join Date: Aug 2015
  • Location: Dallas, TX
  • Posts: 859
  • Kudos: 19
Re: Falcon Player - FPP v1.9 is now available
« Reply #66 on: June 04, 2018, 02:12:17 PM »
Also, using a PiCap, it seems to work if I exceed the 1000 pixel limit imposed by the UI.  Limited testing with 1440 pixels seems to work fine.  Can anybody confirm the real limits?

As Dan said, it depends on your sequence timing.  I can't *confirm* these limits, but my coctail-napkin-math says the limits (using 2811 pixels at 800khz clocking) should be pretty close to this:

25ms = 40fps = 823 pixels per frame max
33ms = 30fps = 1101 pixels per frame max
50ms = 20fps = 1656 pixels per frame max
100ms = 10fps = 3323 pixels per frame max
xLights and Vixen3 for sequencing / FPP for scheduling and playing / Falcon controllers for pixels / DIY controllers for everything else

Offline stevej

  • Newbie
  • *
  • Join Date: Mar 2018
  • Location:
  • Posts: 3
  • Kudos: 0
Re: Falcon Player - FPP v1.9 is now available
« Reply #67 on: June 08, 2018, 09:44:01 AM »
Thanks for the response.  I can confirm that 1440 WS2812B pixel matrix does work at 50ms.  I thought before I split that into two channels that I would try it at 25ms.  Over the course of 3 minutes, I maybe saw one glitch.  It performed better than I expected perhaps because it of the short inter-led distance.  Or perhaps I'm not seeing it.  What would you expect a failure to look like?  Does the whole panel miss a frame or just the first or last pixels?  When you miss a frame, would you expect it to be black or the previous value?  Thanks again for sharing your experience.

Offline dkulp

  • Developer
  • ******
  • Join Date: Sep 2013
  • Location: Framingham, MA
  • Posts: 828
  • Kudos: 35
Re: Falcon Player - FPP v1.9 is now available
« Reply #68 on: June 08, 2018, 09:53:09 AM »
Thanks for the response.  I can confirm that 1440 WS2812B pixel matrix does work at 50ms.  I thought before I split that into two channels that I would try it at 25ms.  Over the course of 3 minutes, I maybe saw one glitch.  It performed better than I expected perhaps because it of the short inter-led distance.  Or perhaps I'm not seeing it.  What would you expect a failure to look like?  Does the whole panel miss a frame or just the first or last pixels?  When you miss a frame, would you expect it to be black or the previous value?  Thanks again for sharing your experience.


Try something like a shimmer that would change the whole string every frame.    It would either stay black (only the black frames), white (only the white frames) or some portion of the string would shimmer and the rest static.   Also, if the Pi is outputting e1.31 data as well, it MAY cause glitches there as it may be waiting to finish a frame before sending.   Not really sure.   


That said, you also have to keep in mind that the last pixel on that string is getting it's data almost 40ms after the first pixel.  Thus, if it's anywhere close to the first pixel (like zig zagging on a matrix), it may be noticeably lagging compared to the first pixel.     Also, if that first pixel dies, that's a lot of pixels that go out.  :)

 

Back to top