Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Midi capture recording creates take folder instead of overlapping regions

This is a very weird glitch that happens under a very specific set of circumstances, that I believe is caused by a bug in Logic. If anyone could shed light on it, it would be much appreciated.


I normally record midi using the Capture Recording tool, which I find far more convenient (and less pressure) than actually hitting Record. I routinely record multiple passes on a single track, with Cycle both on and off. I'll often record different midi CC's on different passes, then merge the regions afterwards. Usually, this works with no issue.


Today, for some odd reason, recording a second pass created a take folder. After doing some investigative work, it seems that this only happens, at least initially, when a midi controller is mapped to a specific control in the instrument. (I'll get back to the specifics in a bit.) Bizarrely, though, once that's happened, it seems to open the floodgates, where it starts randomly occurring on other tracks (both Instrument tracks and Midi tracks triggering external instruements), including on the first pass, which will randomly be split into multiple takes. (Even more infuriating, flattening those takes only preserves a section, making it almost impossible to retain the performance without extra work.)


As for the details, this started happening using Heavyocity libraries (it happens with Evolve, Evolve Mutations 1&2, and Damage), loaded in Kontakt 5.1. When I use a midi CC that is mapped to one of the parameters on the instrument (e.g. CC74) and capture the recording, a take folder is automatically generated. If I use a controller that does nothing (e.g. mod wheel), a normal region is created. However, if I remap the parameter to the mod wheel, that then generates a take folder as well.


Once this happens on one track, it starts happening on other tracks, including Stylus RMX, EXS24, and even midi tracks sending to a slave machine over ipMidi, including when recording just notes, and no controller data. Quitting and relaunching Logic usually fixes it for a little while, but then it will start happening again.


I've verified that it's not caused by file corruption, which I initially suspected, by recreating it in a fresh empty template. I've also deleted and reset the Logic preferences to no avail.


Under Project Recording Settings, MIDI Overlapping Regions is set to "Merge only in Cycle Record". (On a side note, how is there no option of "Record Normally" or "Do Nothing" here?!) In any event, I've tried switching this, but it doesn't resolve the issue.


There is no complex routing going on in the Environment on any of these tracks.


At this point, I've run out of ideas on how to fix this issue.


Reuven


Logic Pro 9.1.8

OS X Mountain Lion 10.8.2

2012 Mac Pro 12 core 3.06 GHz

64 GB RAM

RME HDSPe Raydat

Logic Pro, OS X Mountain Lion (10.8.2)

Posted on Feb 8, 2013 8:10 PM

Reply
16 replies

Midi capture recording creates take folder instead of overlapping regions

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.