Exporting sequence back into LOR - timing is off

[Phrog30]

I'm seeing it off by about 20% by looking at the images attached.  I was using 25ms.  I just tried modifying the xml to 50ms, opened, saved and I'm seeing basically the same thing.  One timing has a slightly different start time but they are still off by the same amount overall.

Delete the fseq file.

[Gilrock]

Ok yeah I should have tested more.  There does appear to be something wrong I'm just not sure why it didn't show up with my file yet.  I tried with 50ms file and then they were only like 30% of what they should be.

[Gilrock]

Ok scratch my last comment.  It is working correctly for 50ms sequences.  The reason it isn't working for 25ms is we calculate an interval by dividing by 10 so 25 becomes 2.5 which turns into 2 when assigned to an integer so it causes each cell to increment by 20ms instead of 25.  But 50ms is working.  I just had the wrong number in my head where the first effect should have ended so I double checked and its good.  I usually use the Render then Export option.

[jeffl]

Mine are spot on for both 25 ms and 50 ms.  I did the test where I set the MS, deleted the .fseq file, opened sequence, saved and exported.  This time I set each cell to 1 second so it could be seen more clearly.  AutoBeat1 is 25ms and AutoBeat2 is 50ms.

Is there anything else variable wise in the code that could affect it that I could be missing?

[Gilrock]

Your doing something different there is no way the results can be the same for 25ms and 50ms.

Using your original test file:

50ms will begin like this in the lcb file:
      <effect type="intensity" startCentisecond="0" endCentisecond="5" intensity="100"/>
      <effect type="intensity" startCentisecond="5" endCentisecond="10" intensity="80"/>
      <effect type="intensity" startCentisecond="10" endCentisecond="15" intensity="60"/>
      <effect type="intensity" startCentisecond="15" endCentisecond="20" intensity="40"/>
      <effect type="intensity" startCentisecond="20" endCentisecond="25" intensity="20"/>
      <effect type="intensity" startCentisecond="30" endCentisecond="35" intensity="100"/>

25ms will begin like this:
      <effect type="intensity" startCentisecond="0" endCentisecond="2" intensity="100"/>
      <effect type="intensity" startCentisecond="2" endCentisecond="4" intensity="89"/>
      <effect type="intensity" startCentisecond="4" endCentisecond="6" intensity="80"/>
      <effect type="intensity" startCentisecond="6" endCentisecond="8" intensity="69"/>
      <effect type="intensity" startCentisecond="8" endCentisecond="10" intensity="60"/>
      <effect type="intensity" startCentisecond="10" endCentisecond="12" intensity="49"/>
      <effect type="intensity" startCentisecond="12" endCentisecond="14" intensity="40"/>
      <effect type="intensity" startCentisecond="14" endCentisecond="16" intensity="29"/>
      <effect type="intensity" startCentisecond="16" endCentisecond="18" intensity="20"/>
      <effect type="intensity" startCentisecond="18" endCentisecond="20" intensity="9"/>
      <effect type="intensity" startCentisecond="22" endCentisecond="24" intensity="100"/>

[jeffl]

It is my setup. 

I loaded up my wifes computer that had an old copy of LOR, installed xLights and ran the tests again from scratch and 50ms is spot on and 25ms is off as expected.  My previous test were on my desktop and laptop which I use xLights daily.

As usual.  You win. 

Now the next question.  Are there other setting files that are stored outside of the xLights directory that could cause something like this to go off?  How can I exterminate my machine and start over.


Send me your PayPal address.  I owe you.

[Gilrock]

I don't know anything that could cause that.  Did you look at the lcb file and is it exporting incorrectly on that one machine?

I don't want any money for helping.  I chose to help and it did reveal the 25ms issue.

[jeffl]

I'm starting to wonder if I should have shutdown xLights between tests.  So many tests now I'm not sure.  Now that I know better what the XML should look like I'll keep an eye on it and report back if I see something crazy.