LMS data layer import out of sync by ~300ms (lights ahead of audio) on FPP

[nmiller0113]

I'm throwing this out there as I'm seeing this as a new FPP user.  Here's some context.  I've been using the latest version of LOR S3 for many years and have about 24 sequences I've built out over the years.  I decided this year to start using xLights as my sequencer and did a data layer import of all of my LOR S3 sequences into the latest version of xLights.  To add a bit more context, I've been using LOR S3 player in previous years and I did tests in the latest version of xLights, not just using a visualizer/layout but with my controllers and lights...and I've never seen any sync issues in the LOR S3 or xLights players.

So, I then decided to move down the FPP path as many of you have.  All installed well and looked good.  I'm running on a Pi2 with 32GB flash for the appliance and 64GB USB Flash (high end/fast) for the media.  I then started testing and went through playing all of my sequences with the controllers and lights.  To clarify again...These are all fseq files from data layer imports in the latest version of xLights from LOR S3.  The result is I found that all of my data layer imported sequences have my lights ahead of my audio by ~300ms.  So I started working with the team over at Falcon and we went through many different tests...only one proved to yield different results.  If I create a new xLights sequence without any import from LOR S3 I don't have any sync issues.  So the only thing I can think of is there is something happening when the fseq is created and a data layer import is included...the strange thing is, these imports work just fine in the xLights player.

So at this point...I'm at a loss.  I have a couple different fseq's, xml and lms files I'm willing to share for someone to test with and see if they are getting the same results as me.  The falcon folks have seen the same delay from my fseq's with the exception of the one that didn't include a data layer import.  I'd love your thoughts

Here is the link of the issue on the Falcon forums if you'd like to read further...thanks for your time in reading this!

http://falconchristmas.com/forum/index.php/topic,3190.0.html

[Gilrock]

Why didn't they just have you import an LMS sequence that only turns on one node for 1 frame and then you can analyze the FSEQ file to see exactly where the data lands.  They should be experts on the layout of those files.

[Gilrock]

And actually data layers are saved in ISEQ files which are basically exactly the same as FSEQ files except we used a different extension to know how to use them.  The same function is used to read both file types so we can't be reading one different from the other.  I've had 250ms offsets using the Pi in the past and had to trim my audio to fix it when I moved for LOR to xLights and that was before data layers existed.

[logandc99]

This question got my interest over at the Falcon forum also because I was experiencing the same thing but nit with imported files. My sequences are entirely done in XL4 abd I noticed that when I ran them from the PC, everything was in sync but when I ran from the Pi, it was out by 180ms for both sequences. I just made the adjustments in the audio offset and all seems to be ok so I "presumed" that it was a function of the Pi. But apparently this isn't the case for everyone.
So for me at least, it's not due to some "importing from LOR thing" so for the future i'll be interested to hear what the cause is. As I can get it all in syn using the offset, I'm happy. The offset is exactly the same for the two sequences that use two different multi-track,chopped up and merged music files in audacity.

[Gilrock]

If I remember correct they said they were going to add the capability to apply an audio offset correction factor in the Pi.  I thought that was added in the last year.

[nmiller0113]

Why didn't they just have you import an LMS sequence that only turns on one node for 1 frame and then you can analyze the FSEQ file to see exactly where the data lands.  They should be experts on the layout of those files.

I could do that for them, but wasn't ever asked.  I think majority felt that it is too close to Christmas at the moment and they'd like to continue troubleshooting this after the holiday season.

[nmiller0113]

And actually data layers are saved in ISEQ files which are basically exactly the same as FSEQ files except we used a different extension to know how to use them.  The same function is used to read both file types so we can't be reading one different from the other.  I've had 250ms offsets using the Pi in the past and had to trim my audio to fix it when I moved for LOR to xLights and that was before data layers existed.

I'm not sure I'm following how this relates, but that may be due to my being new to both xLights and FPP.  I did understand that the data layers were saved in the ISEQ files, but aren't they also saved in the FSEQ file?  I ask because I'm only transferring the FSEQ file to the FPP and it plays the data layer.  Were you mentioning that because the xLights player actually uses the ISEQ file?  Sorry if I wasn't following.

Wouldn't trimming the audio file then make it so the sequence would now play out of sync on the xLights player?  I don't know if you saw this part in my previous message but the sequence played fine in the LOR S3 player as well as the data layer import in the xLights player.  It is only out of sync on the FPP.  is it normal that it would play fine on two other players and not on the FPP?  This leads me to the part that makes me shake my head.  If I build a new sequence in xLights using the same mp3 (unmodified) and don't do a data layer import, I just do sequencing in xLights and then play that on the FPP, it is in perfect sync.

[nmiller0113]

If I remember correct they said they were going to add the capability to apply an audio offset correction factor in the Pi.  I thought that was added in the last year.

Yes, they have it and it works just fine.  This is how I figured out exactly how far ahead my sequence in comparison to the audio.  I'm just trying to figure out why it plays fine in the xLights and LOR S3 players but not on the FPP.  Then, as I mentioned previously, if I make a brand new sequence using the same mp3 that was out  of sync before without doing any data layer import it plays perfectly in sync on all three.  It's puzzling to me.

[Gilrock]

I read your thread on the FPP site.  You were given files from the Captain and they played out of sync for you also so I think you are going off track thinking it has something to do with data layers.  Yes data layers are stored in ISEQ files but they get merged in with all the other effects when you save and the FSEQ is created.  I'm just saying both files are the same format.  You would get the exact same result if you used the Convert tab to bring in the LMS file into an FSEQ format.

[flyinverted]

Interesting thread.

I bought a couple of sequences from Holidaysequences that are in SUP format.  I added the LOR SUP to my tree, while the rest of the elements were already sequenced.  I too noticed a .3 sec offset and ended up adding .3 sec to the beginning of the audio file. That fixed the import, and then I had to adjust the rest of my effects/models where the difference was noticeable.

[dkulp]

Interesting thread.

I bought a couple of sequences from Holidaysequences that are in SUP format.  I added the LOR SUP to my tree, while the rest of the elements were already sequenced.  I too noticed a .3 sec offset and ended up adding .3 sec to the beginning of the audio file. That fixed the import, and then I had to adjust the rest of my effects/models where the difference was noticeable.

I've noticed a bunch of the Holidaysequences stuff are off a bit.  The worst one I've seen from them is about 3 seconds off.  I've been debating adding an "Offset" spinner to the import dialog to automatically offset everything by that amount at import time.   

[Phrog30]

Interesting thread.

I bought a couple of sequences from Holidaysequences that are in SUP format.  I added the LOR SUP to my tree, while the rest of the elements were already sequenced.  I too noticed a .3 sec offset and ended up adding .3 sec to the beginning of the audio file. That fixed the import, and then I had to adjust the rest of my effects/models where the difference was noticeable.

This lag was in noticed on xlights or fpp?

[nmiller0113]

This lag was in noticed on xlights or fpp?

I'm not sure we could call it lag, because on the flip side of that coin you could also call it lead in the sequence.  Not to nit pick, but I'm trying to avoid confusion.  I've been referring to it as out of sync.

The sync issues only presented itself on the fpp, not any other player.

[Phrog30]

This lag was in noticed on xlights or fpp?

I'm not sure we could call it lag, because on the flip side of that coin you could also call it lead in the sequence.  Not to nit pick, but I'm trying to avoid confusion.  I've been referring to it as out of sync.

The sync issues only presented itself on the fpp, not any other player.

I was actually asking Steve about his experience.

[flyinverted]

It's a fixed offset I'd say and not a lag. You can clearly see the effects start just a bit behind the audio peaks. It could be very well that I did not have the exact same song as the author.