Undo function sees midi cycle recording rather than audio

Ok more bug description details.

I have the same. It's not related to Kronos, I don't have it. I use a Saffire56, not SPDIF but plain analog input.

I use logic (currently v10.0.3) since 2009 including advanced stuff and know it(s bugs) pretty well.

Somehow Logic messed up it's internal structure. Audio recording events get flagged wrongly as MIDI recording. But there are more symptoms of messed up internal structure:

- Also it suddenly turns on swipe comp recording whether you want it or not

- A new recording is silent until you open up the track and start swipe comping. At each take you have to do this again.

- If I have two tracks with the same input and output channel, if I record on track 2, the comps of both track 1 and 2 are opened.

- Another thing I suspect to be related: a MIDI drum track suddenly records all notes delayed by 1/16th note yet its track delay is at "none".

Have not found a fix or workaround.

Nothing in the manual about it.

Restarting Logic is useless.

Creating a new clean track and record everything again is useless.

It makes practical professional audio recording useless; I can't afford to make a studio orchestra wait because bugs make it impossible to undo a mistake or even accidentally destroy some other important step and not find out until a few takes later.

The project file can be messed up by the most futile things, which is exactly the problem with all versions of Logic 8 and Logic 9 and Logic X: the internal data structure is was an unreliable mess to begin with and it's never really dealt with by its developer team.

It's even worse!!!

I made a completely new project from scratch.

The very first audio recording I did was not undoable.

New things I tried:

"Initialize all except key commands" did not help.

Rebooting the computer did not help either.

Next I'll go try run Logic 9 see if I can at least continue my recording work...

Ok it seems at least Logic 9 is still usable.

Ok new info, after hanging on the phone with Apple Enterprise Support: It's not fixed when I moved from 10.0.3 to 10.0.4. Even uninstalling and re-installing didn't help. Because it probably is a bug in the software.

But there is news: it's narrowed down: If I record audio, and just one midi note comes in during recording, Logic thinks it's a MIDI recording and can't undo it anymore. I was recording audio from a MIDI controlled analog synth so there you go. If I record other audio (say a mic) no problem. If I record audio and touch my keyboard, only one note is enough, it's a MIDI recording again... its reproducible on my behalf.

Now the supportdesk is busy trying to reproduce this. Haven't heard from them yet, they said they'd call back today... I'll remind them that I'm still waiting.

Don't use undo, but simply delete the take. This will trash the recorded audio file; you will (always) be asked to confirm, and you still need to empty the trash in Finder to reclaim the disk space.

Hi friendly neighbour, thanks for the tip, it could help someone if you're stuck in Logic 10 and have no choice but to go on...

@Logic dev team if you read along: please do not think "ok there's a workaround, case closed", because it ain't. It's either a real bug or a very poor developer decision. I hope you developers agree that it's unneccessary, because the user has to define a track as a midi track before recording so why the autorecognizer if the user chooses to define it as audio.

In practical situations: Imagine what a mindboggler it becomes if I want to go 2, 3 or 4 undo steps back, and always watch your back, having to remember that there may be a midi-polluted audio chunk in it, while focusing on cratively making music. Once you hit that cmd-Z too many times whoops, crack, stuff is messed up and there's no way back anymore.

For now I live with the known and manageable bugs of L9 (like too low mouse event prio during hot gfx from fx windows, and very fragile internal take folder data structure) and hope we end up in a true fix, not in money back.