timing mark issue in mac version of .17

[scuba]

I've tried several Audacity label files imported into Xlights as timing marks and it appears to off 25ms (to the left) or so from the audio track.  the audio file is 44100hzs; 16-bit PCM and128kbps.  I check the Audacity files and it appears to right on in its window.

Can on manually offset the timing marks as a group?

[dkulp]

The bigger question is whether the import of the marks is off or if the display of the waveform is off. 

Basically, does an effect that starts at the timing mark actually match up with the actual audio if played from various players (would try FPP and xLights)?  If so, that would suggest the rendered wave form is off.

[flyinverted]

Just a hunch that the sequence was configured for  100ms or 50ms timing. 

The timing "resolution" will need to go to 25ms in your sequence to get the imported marks to match.

Even with 25ms timings,  the imported marks will still be adjusted to the closest 25ms interval. This is still a huge improvement over 3.x where we had a 50ms skeleton.

Go to Settings, Sequence settings, bottom left will have the Sequence Timing resolution.

[Gilrock]

Timing marks get rounded to the nearest 25ms.  Actually they should be rounded to the nearest multiple of the sequence frequency but I think it's hard coded to 25ms at the moment.

[scuba]

For example: just started a new sequence with imported timing marks from audacity.  The timing mark format audacity should be at 0.046; round up to .05 and that matches  the timing mark on the display...the no set in the audio track is at ~.025. That offset carries throughout the song.

Therefore it appears the Music track is off.