Error "Unknown file format, expected FSEQ v2.0". Newer XLight uses FSEQ files V2.2 Incompatible with Tesla's V2.0 Requirement #67
Comments
|
I would expect V2.2 files should still play correctly in vehicle. I think the validator might need to be updated. |
|
That's what I thought at first too, but it seems like the vehicle's internal validator is also rejecting the |
|
The custom selection should only be greyed if the USB is not connected (or doesn't contain a LightShow folder), otherwise there should be an error message. |
|
Based on this comment, I have a suspicion that XLights for macOS changed more about the FSEQ files than XLights for Windows. That would explain why some can play their files on the car, while others can not. The file I have from 2023.04 Windows starts with PSEQ (according to this document it's always PSEQ). Meanwhile the comment mentioned above states theirs starts with FSEQ. If anyone has the latest version on macOS, it would be great if you can send me your .fseq and .xsq: [email protected] |
|
I have the latest version on Mac and this is the only difference I see (using old xlights show folder and existing xsq): @@ -1,5 +1,5 @@
-00000000: 5053 4551 9800 0202 2000 3000 0000 a504 PSEQ.... .0.....
-00000010: 0000 3200 0000 0000 03ad 30ba dbf7 0500 ..2.......0.....
+00000000: 5053 4551 9800 0002 2000 3000 0000 a504 PSEQ.... .0.....
+00000010: 0000 3200 0000 0000 4908 503f b2db 0500 ..2.....I.P?....Seems only relevant thing changing is the minor version number |
|
I think we can then assume that Mac files work fine in the car as well. |
|
I'm getting the following error too - Unknown file format, expected FSEQ v2.0 when I plug in the drive with fseq and mp3 file, I get the error invalid number of channels. surprisingly, despite this error custom light show worked partially once, it played half the song, and after that it does not work on any of my teslas. I need this custom light show to work ASAP, any help is appreciated. I'm attaching the fseq and sequence file here. |
|
I still haven't had luck playing V2.2 version as its greyed out on my tesla so i want to say there's more than just a header version modification. @tram01 can you confirm that you downgraded Xlights to the version I specified above? |
|
I didn't downgrade Xlight, I'm using the latest version |
|
Thank you for sharing the file. |
Opened your file in xLights 2023.05.1 on Mac. Clicked save, checked the .fseq and it had 0xc0 (196) channels which was causing this error. |
|
Can you send me the sequence file and fseq pls Do I need to still downgrade xLight? Sent from my iPhoneOn Apr 1, 2023, at 1:16 PM, Connor Monahan ***@***.***> wrote:
when I plug in the drive with fseq and mp3 file, I get the error invalid number of channels. surprisingly, despite this error custom light show worked partially once, it played half the song, and after that it does not work on any of my teslas.
Opened your file in xLights 2023.05.1 on Mac. Clicked save, checked the .fseq and it had 0xc0 (196) channels which was causing this error.
I went to the sequencer tab, hit render all, hit save. Checked the .fseq and it has 0x30 (48) channels now which will pass the validator on the car.
$ xxd lightshow.fseq | head
00000000: 5053 4551 9000 0202 2000 c400 0000 d42e PSEQ.... .......
$ xxd lightshow.fseq | head
00000000: 5053 4551 9000 0202 2000 3000 0000 d42e PSEQ.... .0.....
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
Should not need to downgrade xlights, but lmk if the steps I provided don't fix your issue. lightshow.fseq.zip Maybe try downloading a new copy of the tesla xlights show folder. |
|
@cmastudios didn't work for me. were you able to play in your Tesla ? |
|
Update as of February 2024:
I think this issue can be closed. @xingxu21 @tram01 can you confirm this issue is resolved for you as well when using the latest version of XLights and the latest |
|
I tried xlights 2024.02 and 2023.01 versions. The sequencer worked inside the xlights program. But they both gave errors in the standalone validator and in the Tesla drive as error. The current master file on line may also be incompatible with FSEQ version 2.0. I need to create a Lightshow for a charity. Can someone help? Thanks. |
|
I cannot reproduce your issue in 2024.02, and 2023.01 is known to be working. You probably didn't set the FSEQ Format to V2 Uncompressed in xLights preferences. The issue mentioned in the original comment is fixed. |
|
Hello:
Thanks for helping me. I did set as V2 Uncompressed. These are the screen shots and files that are causing errors. Please advise what I was doing wrong.
Thanks
Jimmy Chan
469.408.8838
From: spaceXrace ***@***.***>
Date: Sunday, February 11, 2024 at 11:53 AM
To: teslamotors/light-show ***@***.***>
Cc: IDMJ24 ***@***.***>, Comment ***@***.***>
Subject: Re: [teslamotors/light-show] Error "Unknown file format, expected FSEQ v2.0". Newer XLight uses FSEQ files V2.2 Incompatible with Tesla's V2.0 Requirement (Issue #67)
I cannot reproduce your issue in 2024.02, and 2023.01 is known to be working. You probably didn't set the FSEQ Format to V2 Uncompressed in xLights preferences.
The issue mentioned in the original comment is fixed.
—
Reply to this email directly, view it on GitHub<#67 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BFUJHRK74WZ3KB7JA3KVKBDYTEAP7AVCNFSM6AAAAAAWIVRM76VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZXHAZDEMBWGY>.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
@IDMJ24 did you use the latest version of Clicking the Render All button documented here might also help (not sure if this helps in your case, but it did fix some issue for me in the past). |
Users are getting Validation Error: Incompatible with newer versions of XLight Generating Error "Unknown file format, expected FSEQ v2.0" when validating the generated FSEQ file despite following the README.md file precisely. The root cause of this occurs due to XLight defaulting to FSEQ versions 2.2 while Tesla vehicles require version 2.0 without Xlight giving users options to set specifically 2.0.
Overview
Multiple people (Lazy-Double-6538, BradB132, Relevant_Resolve9671, foxbat7777) in the last 7 days including myself have reported validation errors despite following the directions precisely on the
README.mdwith regards to step 4select V2 Uncompressed. This issues affects users using XLight downloaded on the app store with version 2023.04.The newer updates of XLights uses fseq files V2.2 of fseq rather than Tesla's required version of V2.0, with the Tesla and validator files rejecting newer versions. Any user attempting to create light shows on a mac with Xlights downloaded with the app store (and likely future versions of xlights on windows) will no longer be able to develop without resorting to older versions of xlight.
Workaround
A temporary workaround can be achieved by downgrading to 2022.01 version of XLight until this bug is resolved through XLight and Tesla via a software update.
Issue
As stated above, multiple users including myself have noticed that despite having the V2 Uncompressed option selected in sequence settings, the
.fsqfile synthesized fails the validation scriptvalidator.pyissuing the error"Unknown file format, expected FSEQ v2.0". The root cause of this issue exists for the 2023-04 downloaded through the app store as recommended in the Xlights releases documentation. This fittingly corresponds to the timing of the complaints from above.Replication
When downloading xlights on OSX via the app store for version 2023-04, clicking select V2 Uncompressed under the setup instructions, and following the steps listed under
Creating a New Sequencein theREADME.mdfile, and saving the file, once you run the validator on the<file.fseq>, the"Unknown file format, expected FSEQ v2.0"pops up. A look at the fseq binary files (visible by printing the values ofstart, minor, major = struct.unpack("<HBB", file.read(4))from the validator) will indicate that the fseq uses version 2.2 and not version 2.0.This can also be proven by using any of the provided example fseq files provided by Tesla. Without modifications, the file passes validation. After making one change and saving, the example file fails the validation.
Suggestion/ Conclusion
It is in Tesla's interest to either internally update vehicles to support FSEQ v2.2 or have the developers of XLight to allow users to use
V2.0(note this is different from the current V2 uncompressed selection that leaves the minor version ambiguous) explicitly in the UI sequence settings of XLights. Otherwise this bug will frustrate future users without the knowledge of downgrading as a workaround in their efforts to develop custom light shows.The text was updated successfully, but these errors were encountered: