I don't know if anyone has reported this yet...
 
Personally, I'm still uncomfortable with the reversed stacking (new on top) for Lanes, but with that said. I've just encountered an anomaly... Has anyone else seen this happen? It just happened twice in a row...
 
I'm recording a vocal track. I'm in sound on Sound mode and I have lanes open... track in Record, monitored via zero-latency at the board... There are three pre-existing  Lanes stacked in the new order (most recent on top) and muted...
 
I have set up a loop of a "verse" area in the song...
 
Enable record
record until it starts a second loop
stop
 
Expected, small piece of second loop to be uppermost Lane
 
Actual, Small piece is the lower Lane of the two just recorded...
 
If anyone can confirm this I'll bug it up... Or else for now I'm gonna think... fluke?
 
Keni
 

I'm guessing it's something unique to the project state. If you can get the project into a condition where you can save it and reproduce the issue after re-opening it, then it would be worth submitting to the Bakers. Otherwise, there won't really be anything for them to investigate. Chances are the issue is due to the current state of the program in RAM that won't be saved with the project.
 
One thing I've found that that can lead to issues like this is using Undo to recover deleted lanes. I try to avoid using Undo in this case.
 
 

Everything seems to work fine here, but I am not sure I understand the problem.  Are your takes numbered correctly (e.g., T1 at bottom, T2 above it).
 
Are you sure you didn't start the recording at the very end of a loop?  That would create a short clip in the first new take.

Thanks brundlefly...
 
I think you're last line nailed it... But with a caveat...
 
I had clicked on the uppermost lane to delete the little piece as I could have sworn it was there, but it left me with the full clip (first loop) deleted and the little piece (second loop) remaining. So I did an undo which brought the first loop back to the uppermost position... So I'm not quite sure what went on. I thought I deleted the little piece and turned out wrong (deleting the uppermost lane), then after the undo the second loop was below the first loop... Something wasn't right there. At first I thought I must have deleted the wrong lane, but if that was the case, the second loop ended up beloe the first loop before I did the undo command... Something fishy here for sure...
 
Thanks neirbod too... but no, I started a fresh recording at the start of the loop and it returned to the beginning to start a second loop... that much I'm sure of...
 
Keni