Hi All, I checked the forum and other sites as well, but could not find reference to this. Frequnetly, but not always, when merging audio regions in Logic 9.1.1 on my MacBook, I get time shifts of the order of 2500 samples. I first noticed this while comping vocals and then using "Flatten and Merge". The result was noticeably but not hugely off. Doing some troubleshooting, it seems related to the merge step. When in this state, if I create two simple regions, each one bar long, where I record a stick click on 2/4 to the click track, the sample editor shows that I hit the 2/4 at least as close is Igor could :-), but when I merge the two regions, the clicks are shifted by about 2500 samples. This is repeatable with the undo command. I have tried playing with the merge cross-fade preference settings, snap to absolute, snap to zero crossing, etc., but cannot make it work, EXCEPT if I save the project with my 2 test bars, quit Logic, and then restart and merge them, in which case the timing of the merged audio file is right-on. Not sure if this is a known bug out there, but there is at least this work-around, cumbersome as it is and not sure if it will work 100% of the time. The trouble is that the effect is small enough that it might go unnoticed on a cursory listen, but will definitely disrupt the groove to anyone who is in critical listening mode. I can't take it for granted that I can trust the timing of merges, particularly in swipe editing. What a huge pain to have to spend the extra time to QC this. I am suspicious that swipe editing followed by "Flatten and merge" might trigger this state. Again, it is intermittant, but once in this state where merge operations cause the timing error, I seem stuck in it until I restart Logic. Any experience or thoughts with this? Settings? Other work-arounds? Cheers ricardo

Hi Ricardo, Thanks for this! I haven't come across this to the best of knowledge - although from what you're describing I may well have missed it anyway! Personally, I prefer bouncing in place (or plain bouncing) regions rather than merging them... it's just the way I like to work in Logic: bounce the track in place or bounce regions to a new file and then mute and hide the original track. Do send this to Apple as feedback: [url]http://www.apple.com/feedback/logicpro.html[/url] It's the best way to let them know... I'll test this out over the weekend. Rounik

Hey Rounik Thanks for the quick response. I will try the bounce in place in lieu of the merge to see if that helps. I will also forward this to Apple as you suggest and let you know if I learn anything else. Yes- it is a bit insidious and could be missed depending on the program material. Cheers ricardo

Hey Rounik, Problem Nailed If the low latency button is clicked-in to orange, then either a merge or a bounce-in-place will insert a timing error of order 2500 samples in my case (at 44.1 KHz). This is a smoking gun that Apple can probably fix in 5 minutes. When we see it is another question. Cheers ricardo PS Perhaps you can double check me and if verified, please consider how to best inform the community. I am new to these forums.

Hi Ricardo, Interesting... low latency mode on caused this... Many thanks again for pointing this out. The best thing to do (which you've done) is to inform Apple directly. A future update may well fix this issue. The next best thing I can do is turn this post into a sticky and/or begin to assemble "common bugs" into a thread... In fact that might be better... ...I'll create a sticky thread (always at the top of the list) in the Logic forum called 'Logic Bugs and workarounds'. This will be open to anyone to post into and add to. Please could you copy and paste your findings from here to the new thread. It'd be great to have this finding & solution attributed to you. :) Rounik