News:

LATEST RELEASE:  FPP 6.1 - Download from here - https://github.com/FalconChristmas/fpp/releases/tag/6.1

+-+-

+-User

Welcome, Guest.
Please login or register.
 
 
 
Forgot your password?

+-Site Stats

Members
Total Members: 15527
Latest: Murfdog510
New This Month: 35
New This Week: 23
New Today: 1
Stats
Total Posts: 127423
Total Topics: 15642
Most Online Today: 111
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users Online
Members: 6
Guests: 31
Total: 37

file system space considerations...

Started by Steve Gase, July 18, 2013, 07:48:29 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Steve Gase

The DLA file format has ALL potential channels preallocated even if they are not used... so 16,384 channels every 50ms.  The files are big.

With 32,768 channels will the Falcon PI files adopt the same scheme, and therefore use 2x the space for the same show length... even with a small number of channels actually in use?

What about refresh rates...  DLA recommended 50ms, in part because faster was said to be less perceptible.  Are you also limiting Falcon PI to 50ms?

Next, what about media?  I'd expect 64GB Class10 SD cards to work with the PI, but would it make more sense to mount a USB dongle?  would there be enough bandwidth over USB to serve the data?  Would wear on the SD card be a problem?

I'd suspect that our new use of the PI is no worse that what the camera industry puts on the SD media.  Maybe the bandwidth over USB is not a concern -- unless interrupts create too much load.

I'm interested to hear the existing thoughts into these questions...   
http://WinterLightShow.com  |  110K channels, 50K lights  |  Nutcracker, Falcon, DLA, HolidayCoro

JonB256

Quote from: Steve Gase on July 18, 2013, 07:48:29 AM
The DLA file format has ALL potential channels preallocated even if they are not used... so 16,384 channels every 50ms.  The files are big.

With 32,768 channels will the Falcon PI files adopt the same scheme, and therefore use 2x the space for the same show length... even with a small number of channels actually in use?


Steve, while I have converted many xLights xseq files to Conductor seq files (they are exactly the same size when done, and the number of channels and amount of content has no effect), I have never converted an xseq file to Falcon Pi format to see the difference. Bigger, smaller, same size - just need to test (when I get home, probably).

Jon
Long time Falcon, FPP and xLights user

MyKroFt

A 4G SD card is all that is going to be required for the base image, as designed now - you will need a usb flash drive (or usb powered hub, portal usb HD etc) to hold configuration, sequence, music, playlists and video files.

This way if for some reason your SD card gets corrupted, all your files/configuration is save on the flash drive.  If corruption happens, all you have to do is plug in a usb keyboard, and hook it up to some video output.  Reboot the pie, and when it tells you hit "shift" for recovery, press your shift key, and you will be able to reload the SD card in a matter of min without have to take it out of the pie.

We are trying to make it as painless as possible, as with any linux/windows/mac system, if it looses power while writing to its file system, there is a possibility of corruption.  The fail-safe recovery will help with that possibility.

Myk

smeighan

Quote from: Steve Gase on July 18, 2013, 07:48:29 AM
The DLA file format has ALL potential channels preallocated even if they are not used... so 16,384 channels every 50ms.  The files are big.

With 32,768 channels will the Falcon PI files adopt the same scheme, and therefore use 2x the space for the same show length... even with a small number of channels actually in use?

What about refresh rates...  DLA recommended 50ms, in part because faster was said to be less perceptible.  Are you also limiting Falcon PI to 50ms?

Next, what about media?  I'd expect 64GB Class10 SD cards to work with the PI, but would it make more sense to mount a USB dongle?  would there be enough bandwidth over USB to serve the data?  Would wear on the SD card be a problem?

I'd suspect that our new use of the PI is no worse that what the camera industry puts on the SD media.  Maybe the bandwidth over USB is not a concern -- unless interrupts create too much load.

I'm interested to hear the existing thoughts into these questions...

Hi Steve;

currently the Conductor file and PI Player file ar enot the same size.

I did one of my 12K channels shows.

Carol of the Bells.

Here were the files

01 - Carol of the Bells.xml    30kbytes. This has the entire show, timings and effects. This is what u share with people
01 - Carol of the Bells.xseq 34.4 mbytes. This is the binary form of your sequence in xLights form
01 - Carol of the Bells.seq   46.6 mbytes. This is the conductor file.
01 - Carol of the Bells.fseq  34.4 mbytes. This is the file for the Pi Player

So i would say the Pi Player and xlights files only store what you have created, in my case 12K channels. COnductor always creates 16K channels.

thanks
sean
Sean
Littleton, CO Latest releases http://nutcracker123.com/nutcracker/releases xLights/Nutcracker Forum http://nutcracker123.com/forum/index.php Facebook [url=https://www.facebook.com/groups

JonB256

Sean, in absolutely every case, my Conductor files and my XLights sequence files have been the same size. I'm using the Convert tab, loading the xLights file (xseq), then converting to Conductor (seq).

You show them as different sizes.

This is with every xLights version I've tried - 3.0.13, 3.0.17, 3.0.18 and even 3.0.19

And my Conductor files from version 3.0.13 did work just fine at the academy.
Long time Falcon, FPP and xLights user

smeighan

Quote from: JonB256 on July 18, 2013, 12:24:10 PM
Sean, in absolutely every case, my Conductor files and my XLights sequence files have been the same size. I'm using the Convert tab, loading the xLights file (xseq), then converting to Conductor (seq).

You show them as different sizes.

This is with every xLights version I've tried - 3.0.13, 3.0.17, 3.0.18 and even 3.0.19

And my Conductor files from version 3.0.13 did work just fine at the academy.

Jon, I know the conductor file is 16K channels. If you only have 500 channels, coductor makes 16K.

Xlight files are whatever channel count you have in your setup tab. How many E1.31 universes are you setup for?
PI Player files are just xLight files with some header data.

I just converted a number of my files, pi player, xlight files were smaller.


So i now went and defined just 10 E1.31 universes

Made a smaller megatree and created carol of the bells.

I called the file "01".

So;
01.xseq was 14.576 mbytes
01.fseq  was 14.576 mbytes
01.seq   was  46.641 mbytes

dave confirmed he only makes a pi player file as big as the xlights file.

The only thing i can think of is you had 32 universes in your setup tab??

thanks
sean
Sean
Littleton, CO Latest releases http://nutcracker123.com/nutcracker/releases xLights/Nutcracker Forum http://nutcracker123.com/forum/index.php Facebook [url=https://www.facebook.com/groups

JonB256

#6
That explains it, then. I have all 16,000 channels configured (32 universes/8 pix net).
That's why they're the same size.

Update - I did "downsize" my xLights config and resaved. Sure enough, the xLights xseq file did get smaller. (not a lot, since I was using 12,000 of the 16,000 channels).
Long time Falcon, FPP and xLights user

Support FPP

+- Recent Topics

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod