Sequence Issue
 
Notifications
Clear all

Sequence Issue

8 Posts
4 Users
0 Reactions
2,898 Views
Posts: 14
Topic starter
(@txtyphoon)
Eminent Member
Joined: 8 years ago
[#52971]

I started on this year's display and added some elements to an existing sequence in Vixen. After exporting it and uploading to FPP it now shows a sequence length of 0 and when I try to play it FPPD stops and starts and the following error is logged. Is this an FPP problem or a Vixen problem? Any suggestions on how to fix it?

2020-10-20 21:35:59.733 (11796) playlist/PlaylistEntryMedia.cpp:367: PlaylistEntryMedia::OpenMediaOutput() - Complete
2020-10-20 21:35:59.733 (11796) Sequence.cpp:189: OpenSequenceFile(test.fseq, 0, -1)
2020-10-20 21:35:59.734 (11796) fseq/FSEQFile.cpp:1622: Read position (2064) does not match expected header size 2056!
2020-10-20 21:36:00.791 (12210) log.c:232: =========================================
2020-10-20 21:36:00.791 (12210) log.c:233: FPP 4.3-5-g97c142a9
2020-10-20 21:36:00.792 (12210) log.c:234: Branch: v4.3
2020-10-20 21:36:00.792 (12210) log.c:235: =========================================

Thanks,

Brian


7 Replies
Posts: 150
(@jwamsley07)
Estimable Member
Joined: 12 years ago

Running into the same issue on one of my Halloween sequences. I exported using the pre 2.6 setting (Falcon Player Sequence instead of Falcon Player Sequence 2.6+) and it worked just fine. I reimaged back to 3.6.2 and exporting the same sequence using 2.6+ with compression works fine.


Reply
Posts: 401
(@kensington)
Reputable Member
Joined: 11 years ago

There's a thread over on the FPP section of falconchristmas.com that mentions the issue. As jwamsley07 indicated, the solution appears to be export to a pre-v2.6 file. The devs haven't chimed in yet, so it's unknown whether it's an FPP v4.3 issue or a Vixen issue.


Reply
Posts: 14
Topic starter
(@txtyphoon)
Eminent Member
Joined: 8 years ago

Running FPP v4.3-5-g97c142a9
Size: 3.5-4.5MB (I went back and deleted some elements to see if it was a file size issue. No joy!)
Tried it without compression too, file was ~30MB if I recall. That didn't work either.
Exported Version 2.6+
Not sure how to switch to master branch so no?

I did just re-export using the Falcon Player Sequence instead of the Falcon Player Sequence 2.6+ and it looks to have resolved the issue. It was working initially, I think I upgraded FPP in there somewhere, if I had to guess that was when it broke. Changing too many things at once to be sure.


Reply
Posts: 14
Topic starter
(@txtyphoon)
Eminent Member
Joined: 8 years ago

Is cross linking forbidden here? Can we post the link to the other thread?


Reply
Posts: 14
Topic starter
(@txtyphoon)
Eminent Member
Joined: 8 years ago

https://falconchristmas.com/forum/index.php/topic,13198.0.html
Doesn't seem to be getting much attention but seems like a bug. Is their an official way to report bugs for Vixen and FPP?


Reply
ShadowLight8
Posts: 233
(@shadowlight8)
Reputable Member
Joined: 10 years ago

I ran into this too and found if I exported an empty, default length sequence, I could get this error on FPP v4.2. I'm running Vixen build 977, but will upgrade to the latest release after Halloween.
Attached is the fseq file I generated (with .txt added to the end).
Here are my export settings as well:

Vixen Export Settings

Reply
Posts: 14
Topic starter
(@txtyphoon)
Eminent Member
Joined: 8 years ago

I opened a bug in the Vixen Jira and initial report is that this is a rounding error and that a fix will be available for it at some point.

Brian


Reply
Share: