retep

Dear all, I think I have found the solution to the problem. Today I was in my studio to work on the Logic song. I opened the file and there were no more unwanted folders. I realised that it was a system incompatibility issue. At home I run Logic 10.5.1 but in my studio I run Logic 10.3.3. (because I use an old Mac Pro) Logic always warns when I open a song that wasn´t created using the same version but so far there were no problems. Until now. Thanks for all your input and sorry for having wasted your time.

After struggling with it I think it has something to do with "overlapping" regions. At least Logic thinks they are. Everything is quantised and I can´t see any overlapping. Is there a function to highlight overlapping regions?

As I said the video isn´t good. When I click on an empty track sometimes it creates a folder. Why does it do that if there´s no midi data? Also when joining 2 regions it should create a continuous midi region, not a folder which can´t be unpacked. Don´t you agree?

Sorry. The video is public now. When joining midi regions I use the key "command & J" (join). It´s worked fine for a long time now. The video isn´t good. I have a midi region (bass) that just became a folder all by itself. When I want to unpack it it disappears leaving no data.

I´ve been working with Logic for many years. Logic Pro has some features which I'm not comfortable with. All of a sudden when I want to merge (join) 2 midi tracks Logic Pro creates a folder. When I ask it to unpack this folder nothing happens. I don´t want a folder just a continuous midi track. Is there some sort of preference setting where I can bypass this and return to normal operation? Here´s a video of Logic Pro creating a folder even though the track is empty: