Error "Unknown file format, expected FSEQ v2.0". Newer XLight uses FSEQ files V2.2 Incompatible with Tesla's V2.0 Requirement

[xingxu21]

Error "Unknown file format, expected FSEQ v2.0". Newer XLight uses FSEQ files V2.2 Incompatible with Tesla's V2.0 Requirement

[cmastudios]

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

[IDMJ24]

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.

[cmastudios]

I would expect V2.2 files should still play correctly in vehicle. I think the validator might need to be updated.

[xingxu21]

That's what I thought at first too, but it seems like the vehicle's internal validator is also rejecting the .fseq file. The custom light show selection was still greyed out in my 2022 vehicle running version 2023.2.12 using the V2.2 files. This leads me to believe an over the air update is necessary. I was also unable to update the vehicles software to investigate hacba0's claim that the file would still work ("your vehicle is running the most up to date software as of now") despite failing the validator

[cmastudios]

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.

[spaceXrace]

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]

[spaceXrace]

I think we can then assume that Mac files work fine in the car as well.
The comment I mentioned before claiming their file on Mac is FSEQ1 is wrong. It’s PSEQ & V2.2, as it should be.

[tram01]

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.
Archive.zip

[xingxu21]

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?

[tram01]

I didn't downgrade Xlight, I'm using the latest version

[spaceXrace]

Thank you for sharing the file.
you can downgrade to 2023.1 to get a working file

[cmastudios]

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.....

[tram01]

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: ***@***.***>

[cmastudios]

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.

[tram01]

@cmastudios didn't work for me. were you able to play in your Tesla ?

[EdwinOtten]

Update as of February 2024:
It looks like both issues described above have been fixed in validator.py:

1. Unknown file format, expected FSEQ v2.0
   • Fixed in #68
2. Expected 48 channels, got 200
   • Fixed in #86

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 validator.py?

[spaceXrace]

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.

[IDMJ24]

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: ***@***.***>

[EdwinOtten]

@IDMJ24 did you use the latest version of validator.py from the master branch?

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).