Author Topic: Huge fseq file  (Read 1132 times)

Offline Traneman

  • Jr. Member
  • **
  • Posts: 55
    • View Profile
Huge fseq file
« on: November 18, 2016, 08:48:25 PM »
I have one fseq file that is huge. 1,416,825KB the sequence is alittle over a minute long.
the next closest size fseq is 637,468KB and the sequence is over 3 min. long.

The huge file wont play on my Rpi to my matrix.

What should I look for? or what other info do you need to help

Thank you

Offline bwinter

  • Full Member
  • ***
  • Posts: 193
    • View Profile
    • First Show 2016
Re: Huge fseq file
« Reply #1 on: November 18, 2016, 09:26:46 PM »
I noticed recently that one of my fseq had gotten pretty large too.  I simply deleted it, and opened the XML file (in XLights) and rendered/saved (which re-created the fseq file).

The new fseq was 1/5 of the "bloated" size.  Dunno why/how...

Offline Traneman

  • Jr. Member
  • **
  • Posts: 55
    • View Profile
Re: Huge fseq file
« Reply #2 on: November 19, 2016, 05:55:55 AM »
ok Thank you I will give that a try

Offline Traneman

  • Jr. Member
  • **
  • Posts: 55
    • View Profile
Re: Huge fseq file
« Reply #3 on: November 19, 2016, 06:09:11 AM »
Wow that did it Thank you the file is only 134,991KB Now

Thanks again

Offline CaptainMurdoch

  • Full Member
  • ***
  • Posts: 124
    • View Profile
Re: Huge fseq file
« Reply #4 on: November 19, 2016, 01:33:06 PM »
I wonder if this happens by users temporarily having a model start channel set extraordinarily high and then correcting it.  xLights won't reduce the size of the file unless you delete it even if you lower your channel count.

Offline bwinter

  • Full Member
  • ***
  • Posts: 193
    • View Profile
    • First Show 2016
Re: Huge fseq file
« Reply #5 on: November 19, 2016, 03:22:29 PM »
I wonder if this happens by users temporarily having a model start channel set extraordinarily high and then correcting it.  xLights won't reduce the size of the file unless you delete it even if you lower your channel count.

That would make sense in my scenario:  I've been having to re-set my channels as I'm learning and testings--so my channel mapping has been all over the place.