are lanes takes accurate?

[sinkmusic]

Hi
I was away and didn't tested several versions (since v1.841 i guess, where the lanes thing were not reliable). It seems that it got improved recently, but when i used it today, i noticed that it doesn't seem very accurate :

http://stashbox.org/19591/reaper_%20lanesbadlenght.png

When i zoom, i see the lenght isn't the same, it is not very noticeable at ear, but I don't understand what is going on...
COuld anyone tell if there is a way to workaround this, as the lane issue apperas to be fixed ?
Thanks

[Dstruct]

recorded as one file? because then only the last take gets a end-marker and (here) each take is sample-correct ...

[sinkmusic]

What do you mean "recorded as one file" ?
In the "recording" preferences, i have enabled "create new files on loop", if that is what you mean, so each take creates a new clip.
And if i open each take in my audio editor, i can see that each take IS indeed a different file.
So i guess the answer to your question is "no", but i didn't know that it could behave differently ;)

[Dstruct]

i have enabled "create new files on loop"

yeah, this still doesn't work "correctly". you have to disable this.

[sinkmusic]

yeah, this still doesn't work "correctly". you have to disable this.

errh... ok, but... how then can i have multiple clips each one of the loop lenght ?
If i disable that, I'll end up only with one big file (with different start/end point on each lane), that's it ?

[Dstruct]

just try it and you'll see how it works ...

[sinkmusic]

just try it and you'll see how it works ...

yes, i have tried it, and that's it : one big audio file with different start/end points for each lane.
I thought it wasn't a big problem because after exploding each take into new tracks, i could render as a new clip, to get single files, but even with efx disbaled i get some annoying and unwanted silence and bad lenght after rendering.
I think i am a bit lost in that...
Do you know if there is any plan to make the other way ("create new files on loop") working fine ?

[xackley]

Been a while, I thought Explode/Glue worked to create a file/take.

[sinkmusic]

Been a while, I thought Explode/Glue worked to create a file/take.

Yes, it works. I think it will be the correct workaround (not too many clicks and a reliable result so far). There also might have a possibility to make a shortcut for it.
(but i'd like to see the "create new files on loop" feature fixed, if possible).

[aldi]

maybe justin can remove "create new files on loop" and instead add a keyshortcut for "split takes to seperate files" and instead of the "create new files on loop" option he can also add "autosplit takes to seperate files after stop" that might do it ?

[sinkmusic]

maybe justin can remove "create new files on loop" and instead add a keyshortcut for "split takes to seperate files" and instead of the "create new files on loop" option he can also add "autosplit takes to seperate files after stop" that might do it ?

Yes i think so :)
As i said above, exploding and then glueing is not so much a pain and at the moment it seem to work fine (tbc), but my first interrogation which made me began the thread was that a feature was here, and not 100% working (i was away and missed some versions, but just quickly rade Justin stating that it was now fixed and "sample accurate" -if i understood correctly, i was reading quick-).

Not really splitting the big file in separate items (as it works now) can be fine in some situations, but the annoyance with it is that when you think you can lay down a looped clip all along your song, and so grab the edge and drag it, it doesn't repeat itself, but you just "unveil" something else (which is the following lane). _I don't know if my explanation is clear_.