Rainbow Warrior

The behaviour changed, I think around November of last year and I believe it was a bug, but it has now been fixed.

I've been having this problem, but only with certain projects. Using capture recording creates mutiple regions on separate tracks, not always in the the right place. There's also problems moving the captured recordings to different tracks and generally, once it starts happening it's impossible to stop it. Several times I've had to painstakingly recreate projects region by region. The record enable problem seems to have no logic to it and it has been driving me nuts! Have reported it to Apple several times

For what it's worth (considering the original post was 9 years ago) I just had the same problem. Looking at the notes in the event list they were different MIDI channels. (As they were in the original post) Once I changed them to the same channel the feature worked as expected.

Hi Jak - which version of Logic did you use to create the project? I saw the video, and that's exactly what was happening before, but then they released 10.6 and now 10.6.1. I was getting something similar happening in 10.6, but less regularly. Now I'm unable to reproduce it. I downloaded your project file file and it worked perfectly on my system. It's certainly much better than it was - but I don't think it's completely fixed.

Many thanks for this - I'll let Apple know right away!

Nope. Been testin it out and sure enough still got the bug Hi Garry, I thought the bug was fixed, but then it happened again. I reported to Apple and they got back to me asking me to send a file and explain how to reproduce the problem. Unfortunately, now I can't reproduce it (maybe it was happening in a specific project?) Can you reliably reproduce the bug? If so, please can I refer Apple to you so they can follow it up?

Further to my last post, I've loaded a different project and the problem has started again!

Nope. Been testin it out and sure enough still got the bug Hi, The upgrade certainly works for me. All I can think is that you are missing something. It is a bit convoluted. In the preferences you can set the default behaviour when you open a new window, but if you right click the playhead button in each window you get extra options specific to that window. The upgrade has fixed the issue for me. PS - I loaded a different project and the problem has returned. !!!!!!

It fixed it for me

Subsequent to my post earlier: This is not user error. I have checked this out on an older operating system and I can't reproduce it. However, I can reproduce it consistently on my new machine and the latest version of Logic - 10.5.1. It appears to happens when the playhead is visible in the piano roll and the end of the region is also visible. It doesn't happen if you extend the end of the region so that it disappears out of sight, and neither does it happen if you loop the region or if there is another region following on the same track that is also selected (empty or containing data - it doesn't matter). I'll report it to Apple - in the meantime I hope this helps.

It's driving me nuts too - I've been on Logic since it was C-Lab Notator, so I know my way around pretty well. This hasn't happened before. Maybe it's a new setting and I'm missing something??

I'm having trouble using an external controller (Oxygen 88) with smart controls. Logic appears to learn the assignment, but nothing happens when I push the fader on the Oxygen 88. However, I set up a new user account with nothing else running and it works just fine in this account, but I would really like to get it working on my regular account. So, there appears to be some kind of conflict - but how would I go about resolving it? Edit: I'm not sure what I did, but it seems to be working now - though as others have pointed out, not inside a stack.

Thanks sambosun - I'll have a look at Breeze, though I do like Moom. We've resolved the issue with Logic - no one else could replicate the bug - so it's not actually Moom that's causing it.

I've been in contact with the Moom team - they say Moom couldn't do this and that it must be interacting with another application. In any event, they were very helpful and we have now found a solution so that I can still use Moon , and the score editor works properly. Thanks for your help. I'll have a look at Better Snap Tool now.

Thanks Eric - so if you can't reproduce the behaviour it would suggest that the problem is not in the Logic project, but is a fault somewhere else in the system. I have disabled the audio interface, but the problem persists. I trashed the preferences, opened Logic, enabled advanced tools and created 5 tracks, each with a region, but without a plug-in. I noticed that nearly always whatever note I select, the tooltip displays the information for the first note in last track in the score. If I rearrange the tracks in the main pane then the tooltip information changes to reflect the information of the first note for the track which is now at the bottom. I added a new track at the bottom, with an empty region. Now the behaviour is really weird, with very large bar numbers (279611 2 1 64) sometimes indicated as a negative number. If I hold the note for a few seconds the display sometimes changes to something more believable - such as -3 1 1 1, but still incorrect. A lot of the notes on the different staves have the same position information (279611 2 1 64) but some do not. I have just solved it! A few weeks ago I installed an app called Moom - which is a great little app for automatically resizing windows - I do recommend it. But, I have closed it down and now everything is working as expected. Thanks for your help! Also check out this: Have a great day!