DanRad Posted January 30, 2016 Share Posted January 30, 2016 The new MIDI record regime is really messing me up. I went back to 10.07 and found that it works as expected.. You can punch or loop and record over whatever you want anywhere in a measure. If you choose, you can "wipe" the previous recorded material, punch in and out at will, regardless if it's in a cycle or not. In short, it behaves as expected. Here is the setting I've been using in 10.07. It behaves as it did in LP9. With 10.2.1, this is the new Midi Recording Pref; I've tried every combination of Merge, Merge Current, Replace, Make New Track etc. and I cannot get it to NOT either; Wipe previous or subsequent recorded stuff inside a measure I'm punching into, or Not join things I don't want joined, or NOT create more tracks (messy) or Not wipe regions on either side of cycle or NOT join regions on either side of cycle. Maybe I'm missing something... Is anyone else mystified (and annoyed) by this behavior? How do you have your Record prefs set up and how are you avoiding the above groove killers? Any help is appreciated. Thanks DanRad Link to comment Share on other sites More sharing options...
DanRad Posted January 30, 2016 Author Share Posted January 30, 2016 No ideas from anyone? I'm really wondering how people deal with punching in MIDI. d Link to comment Share on other sites More sharing options...
DanRad Posted January 31, 2016 Author Share Posted January 31, 2016 Still hoping someone can help me with this. I may go back to LP 10.07 because this issue slows me way down. Input needed. What is your process for "punching in" MIDI (not using auto punch) Thanks Link to comment Share on other sites More sharing options...
lologic Posted January 31, 2016 Share Posted January 31, 2016 When I set it to cycle: replace, it behaves as expected.. every new pass overwrites the previous midi lol Link to comment Share on other sites More sharing options...
DanRad Posted January 31, 2016 Author Share Posted January 31, 2016 When I set it to cycle: replace, it behaves as expected.. every new pass overwrites the previous midi Thanks for this... Here's one of the problems with this mode. If you are approaching a cycled area, and start playing even one tick before the down beat of the cycle, the ENTIRE previous measure is wiped out, even though it's not in the cycled area. Not only that... a Command Z WILL NOT BRING BACK THE WIPED PREVIOUS MEASURE. Try it. Also, should you try and punch in on a cycled area for only part of a measure, the entire measure will be replaced, thereby losing events you did not intend to record over . Oddly, Command Z does fix this... This is totally crazy behavior and I really don't understand why they've changed this. In 10.07, it did not behave this way. Any suggestions or methods or workarounds are welcome. Link to comment Share on other sites More sharing options...
DanRad Posted February 4, 2016 Author Share Posted February 4, 2016 Still haven't solved this other than going back to 10.07. Has anyone else noticed the strange behavior with regions being messed up on either side of cycled recording areas, or whole measures being replaced instead of just the punch area? LP9-10.07 works so much better in this regard, but I seem to be a lone voice in the wilderness.... hellooooo Link to comment Share on other sites More sharing options...
Eric Cardenas Posted February 4, 2016 Share Posted February 4, 2016 I can confirm the behavior you are describing. Punching in and out on MIDI tracks is not working correctly. Link to comment Share on other sites More sharing options...
DanRad Posted February 4, 2016 Author Share Posted February 4, 2016 I can confirm the behavior you are describing. Punching in and out on MIDI tracks is not working correctly. Thanks for that. Please tell them to let me out of the Insane Asylum. So, as I mentioned, I've gone back to 10.07 because I can't seem to get clean in and outs without losing parts, leaving parts, or generating copious quantities of tracks and folders...I'm having similar such issues with Audio, though I haven't explored all the possible settings. Any suggestions are welcome... What settings are people using for "Record Overlap"?? Thanks Link to comment Share on other sites More sharing options...
DanRad Posted February 25, 2016 Author Share Posted February 25, 2016 I have been using 10.7 for a while because the overlap situation is a total deal breaker for me. I'm I the only one who finds this annoying. How do others have their "Overlapping" MIDI recording preferences set. Are you experiencing the frustration I am of things getting recorded over that, based on previous behavior should not be happening? Thanks Dan Rad Link to comment Share on other sites More sharing options...
tim57var Posted March 1, 2016 Share Posted March 1, 2016 Yes - Having the same issue here. This is a horrible bug - makes my workflow almost unusable. I have also been having problems with AUDIO - SOMETIMES... punching in on an audio track, the audio after I punch out goes away. I'm in replace mode (not cycling) any ideas?? Link to comment Share on other sites More sharing options...
David Nahmani Posted March 1, 2016 Share Posted March 1, 2016 I have personally given up on punching with MIDI in Logic Pro X. In fact I removed the corresponding section from my Logic Pro X book, which is the official curriculum for Apple Certification, as to me a bug that DELETES data that should not be deleted is critical and should be avoided at all costs. So until this MIDI punching situation is sorted, best to avoid punching on MIDI data IMO. I have also been having problems with AUDIO The problem is not the same, as Audio and MIDI really are completely different beasts. I suggest you start a new thread to detail your Audio issue so that we can give it the attention it deserves. Link to comment Share on other sites More sharing options...
tim57var Posted March 1, 2016 Share Posted March 1, 2016 Thanks David -- glad to know I'm not going crazy. I know it's not for this thread, but what's the easiest way to revert to the older version? Link to comment Share on other sites More sharing options...
David Nahmani Posted March 1, 2016 Share Posted March 1, 2016 Thanks David -- glad to know I'm not going crazy. I know it's not for this thread, but what's the easiest way to revert to the older version? Revert to an older version of Logic? You need to have saved that older version as a backup.... but yes, please start new thread for each new question you have, so that we can keep this forum organized! Thanks. Link to comment Share on other sites More sharing options...
shmorrell Posted March 2, 2016 Share Posted March 2, 2016 There is a key command "capture last take as recording" I use this instead of recording MIDI. SM Link to comment Share on other sites More sharing options...
rAC Posted March 2, 2016 Share Posted March 2, 2016 There is a key command "capture last take as recording" I use this instead of recording MIDI. SM But that limits you to the audio the MIDI device has generated doesn't it? Newbie here and still trying to get my head around configuring Logic especially the MIDI - no doubt I will be starting some threads soon Link to comment Share on other sites More sharing options...
RedBaron Posted March 2, 2016 Share Posted March 2, 2016 "capture last take as recording" Whilst we're on the subject of recorded MIDI not working properly. It fills the last 1-12 takes will junk. It also cuts off long notes at the end of a cycle, instead of splitting the long note over two bars. Link to comment Share on other sites More sharing options...
David Nahmani Posted March 2, 2016 Share Posted March 2, 2016 There is a key command "capture last take as recording" I use this instead of recording MIDI. That's fine, but recording MIDI isn't an issue. Punching in and out is the issue, and you cannot punch in and out using "capture last take as recording." But that limits you to the audio the MIDI device has generated doesn't it? No, it's just another way to record MIDI, independent of what device that MIDI data is then routed to or how that device operates. Link to comment Share on other sites More sharing options...
DanRad Posted March 2, 2016 Author Share Posted March 2, 2016 The problem with 10.2.1 is not only on Midi "Punch In" but in using a cycled area as well. Should you start even one tick before the cycle starts, the previously recorded region will be deleted for the measure before the cycled area. There are other issues as well with cycle which I've forgotten since I've gone back to 10.07 which works more or less as expected in this area. (But still glitchy as heck) I have to say, that this feature makes 10.2.1 unusable for me. How long can I live on 10.07. Where can we make our voice heard that THIS HAS TO BE CHANGED? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.