Recent Posts

Pages: [1] 2 3 ... 10
Falcon Player (FPP) / Re: Master/Remote vs Multiple Standalones
« Last post by jnealand on Today at 01:45:42 PM »
But, since it has Zero file storage, each FPP can be running from a 4GB uSD card.

A little off topic, but I have not seen a 4Gb uSD card in a very long time.  My last visit to MicroCenter I could only find a couple that were less than 32GB.  How things change.
Falcon PiCap / Re: How to setup DMX output on PiCap
« Last post by rjhodgefamily on Today at 01:37:40 PM »
So created a cable where I swapped the orange data lines. With no luck. Unless I screwed up the dongle some how. Attached an image. I was able to trace the RS485 lines on both the Lynx and the Hanson. RS485 Pin 6 goes to Ethernet Pin 1 and RS485 Pin 7 goes to Ethernet Pin 2. Which I believe is correct looking at the specs for RS485 on TIs website.
Falcon Player (FPP) / Re: Master/Remote vs Multiple Standalones
« Last post by JonB256 on Today at 01:14:45 PM »
When you have multiple FPP running a show, and you expect them to be accurately synchronized, you have two choices.

Basic setup
1.  One Master, multiple Remotes. All of them will have the FSEQ files needed. Only the Master has the Audio.

2.  One Master, multiple FPPs in Bridge Mode. The FPPs in Bridge do not need ANY files on them. They receive E1.31 or DDP from the Master. The Master outputs to an Ethernet Switch and all Bridge modes are also connected to that Switch

#1 uses less cabling in the yard if that matters to you because Sync can be done over Wireless. But if you update a sequence, all the affected Remotes need to be updated.

#2 needs CAT5 to each FPP. Wireless isn't fast enough. But, since it has Zero file storage, each FPP can be running from a 4GB uSD card. Also, it is virtually impossible to develop any LAG. If you plan to play MP4 files on a non-Master, this setup will not work for you.
Falcon Player (FPP) / Bleeding edge testers wanted....
« Last post by dkulp on Today at 12:53:19 PM »

I know everyone's show is running really well and no one wants to mess with it at this point, but if you are board and want to try something new, I could use a tester or three...   One requirement: you need to be familiar with the Linux command line at this point.  None of this is hooked up to the web front end and nothing is done automatically (yet).

Basically, for 2019, the fseq file format that FPPD uses is going to change a bit.  The old format will still be usable so xLights/Vixen don't need to change anything immediately (or maybe at all).   However, once on the Pi/BBB, we can convert the old format to the new format.   (I will update the FPPConnect stuff in xLights to upload the new format directly to avoid the conversion time, but want to stabilize things first)    There are two things that are new in the format:

1) Compression:  channel data is now compressed using zstd compression.   The result is that the fseq file is WAY WAY smaller.  Once we update xLights to generate the new format, the transfers will be much quicker.

2) Sparse: the fseq file CAN contain ONLY the channels needed on that FPP instance.   It doesn't need all the data.   Thus, on slower/smaller SD cards, we can generate fseq files that are fully optimized for that FPP instance.

To test is out, you would need to go to /developer.php and flip to the "zstd" branch.   It will take a while.  :)    A reboot at the end might be needed as this also has some other stuff from master that Captain has been working on. 

Once done, the newly running FPPD will support both and everything should "just work".  That would be a good first test.   Is it working with your existing v1 sequences.

The second test would be to compress the fseq files.   First do:
Code: [Select]
mv /home/fpp/media/sequences /home/fpp/media/sequences_orig
mkdir /home/fpp/media/sequences
cd /home/fpp/media/sequences_orig
to save the old sequences (easy to flip back).   Then do something like:
Code: [Select]
find  -name "*.fseq" -exec /opt/fpp/src/fsequtils -f 2 -o "../sequences/{}" "{}" \;
That will compress all the fseq files.   It will take a while.  If you are adventurous, there is also a "-l #" flag where you can set a compression level from 1-20.  (default is 10).  1 is faster but larger, 20 is very slow but results in smaller files.      Anyway, give those a try.   Make sure they work. 

The next step would be to create sparse versions.   In the fppd.log right when fppd starts up, it prints out the range it needs.   Copy that range.   Then run something like:

Code: [Select]
find  -name "*.fseq" -exec /opt/fpp/src/fsequtils -r 48120-84991 -f 2 -o "../sequences/{}" "{}" \;
where the -r flag specifies the range to use.  (that example is from my TuneTo sign)   Let that go for a while and then test. 

Anyway, this is all highly experimental, the v2 file format may still change, etc...   To give you and idea about the size difference, my tuneto sign :

Code: [Select]

du -skc seq*
124272 sequences
14543688 sequences_orig
Significantly less than 10% of the space.   

The "sparse" versions are very specific to that FPPD instance and aren't really usable anywhere else.   If you don't create a sparse version, you can do all the compression on the master and sync them out to the remotes (assuming the remotes are all on the zstd branch).   The eventual plan is to sync the "full" versions around, but have fppd automatically create the sparse versions it needs in a "cache" directory or similar.    Lots more work to do, but this is a start.

Falcon PiCap / Re: How to setup DMX output on PiCap
« Last post by JonB256 on Today at 12:24:20 PM »
Perhaps the wires are swapped. 1 to 2, 2 to 1.  Can you make an adapter?
Falcon Player (FPP) / Re: Oldest FPP Version for Raspberry Pi 3 B+
« Last post by Bassun on Today at 12:02:18 PM »
Oh, I am a Creative Labs fan for sure.  I've ran multiple sound blasters from them over the years.  I still have an old one from a decade or two ago that I just ran across the other day, lol.  I will probably eventually pick up a newer one for the rig I'm running now, but have not really used it for much of anything that really demanded more quality for sound.  To be candid, with the video card being so big, and having added a USB card for VR...I don't even know for sure that I have an available slot for their normal cards, lol.  Ironically, now I have a need for better sound... go figure.

I initially was looking at different audio options, and IIRC there was a Signstek for around $50-$60 that I was looking at, or even the FM02, then ran across a bunch of people having success with the CD002.  Figured for 1/10th the price, why not buy a couple.  And, to be honest, I was fine with the audio quality when I tested it on the PC.  To be fair, I was actually blown away.  I expected it to sound, well, like it does off the PI to be honest, lol.  But instead it had great range, no distortion, and while sure it was not the absolute best quality possible, it was plenty good for this.  Read that as it was clear, and sounded fine for all viewing areas to my show.  I think the range alone surprised me, and that may have jaded my initial impression on quality.  All that was using a 30 inch piece of electric fence for the antenna, gator clipped to a lead I soldered to the board.  (Hey, I was just testing.)

Then I hooked it up to the PI an it's been an uphill battle ever sense.  Hopefully running the sound blaster will get things into better shape then I have all of next year to figure out a better solution, if this doesn't sound as good as I want.

At any rate, thanks for the input and suggestions!  I appreciate it!

Gadgetsmith - I apologize, I overlooked your post.  I was thinking 2.0+ was for the 3's, and you confirmed that.  I appreciate it!  With both of you, and other posts I've seen, championing the sound blaster - that will be my next step in getting things to sound decent.  I should have tested off the Pi, but I was rushing to get everything else done and thought things were good to go.  You live, you learn...

Last night I created a eseq using xLights and it worked fine. Must be in an issue in how Vixen exports them. 

Thanks again for the help!
Falcon Player (FPP) / Re: Master/Remote vs Multiple Standalones
« Last post by CaptainMurdoch on Today at 11:05:26 AM »
Master/Remote using FPP MultiSync means one playlist and all the FPP instances are playing in sync with each other.  Standalone systems means that you have multiple playlists and are hoping they start at the same time and play the duplicate playlists in sync with each other.
Falcon PiCap / Re: How to setup DMX output on PiCap
« Last post by rjhodgefamily on Today at 10:44:19 AM »
So I isolated the Lynx Express so it was no longer daisy chained to any other LE just to make sure one of the others wasn't causing the conflict. But still no go. I am going to go move the LE to try testing on one of the 10 working Falcon PiCaps just to triple check that it isn't the LE.

I also just put in a support request to Hanson Electronics to see if they have any ideas. I'll let y'all know what I hear.

Falcon Player (FPP) / Master/Remote vs Multiple Standalones
« Last post by SethOF on Today at 10:38:06 AM »
Any reason NOT to have 2/3 standalone FPPs versus a master/remote setup?  All are to be connected to the same switch.
Pages: [1] 2 3 ... 10
Back to top