djohnq

This is awesome! I just wanted to add to tjhewers point, in case anyone didnt think of this. I was looking to turn a 16th note pattern into an 8th note pattern by removing all the notes on the off beat. The notes in the pattern were all unquantized and I wanted to keep them that way. so I selected all the notes and 100 percent quantized them with the quantize strength slider. then I did the selection as described above in this thread and removed all the notes I didnt want. Then I selected all the notes I had kept, and moved the quantize strength slider back to 0, and all the notes were back to their original position.

Yeah Im with you Hego. I used Ableton for a while and really liked it but ended up moving away because its video playback did't sync correctly. But Ableton's track bussing and plugin bussing/routing system is so dang awesome, I miss that the most from Ableton. In my head Im just wondering when one of these daws is going to get it all correct haha. I ended up landing on Logic for now because I have been working on a lot of projects with someone who works in Garageband, so it made the most sense, and I have really grown to like Logic a lot. For the PDC, I dont know what your issues are but I ran into that a few times with automation curves being off on timing, making it pretty much impossible to automate the plugin with precise timing. What I ended up doing was making an aux track and moving the plugin I wanted to automate onto that aux track turning the output off on the original track and sending the aux of the original track out at full volume to that new aux track. Then the automation timing cleared up. I dont know if it was a fluke or not though, haha I feel like you never know with Logic.

He Hego just saw this and your PM, figured Id reply here so anyone else reading this thread could see. I guess the only suggestion I can give is that you would want to play around with the timing between actions on your macros, it can make a lot of difference. Also, as great as Logic is, its ridiculously buggy. So I wouldn't be surprised that any macro you end up making will be broken in an update or two anyway haha. I stopped using my macro because I started to realize it was more of a headache than it was worth. Sometimes it would be working just fine in a session for an hour or two, then it would inexplicably stop working. I blame it on Logic because as great as Logic is, I think it has to be the most buggy Daw out there. The reason I wanted to make the macro was because I needed to comp a bunch of midi drum takes. But in the end, if I had to do it again, Id probably just do it in Pro Tools or another DAW then import the midid into Logic. Maybe you can do it in Pro Tools Free version, im not sure. But that would only make sense if you are doing something similar to me. When I'm not doing the midi drum comping described above, if I just want to do some regular midi editing on like a synth part or something, I make a blank midi track (or two, three, etc, or make track alternatives on a blank track) and store a copy of the original midi regions on those blank tracks, then select sections with the marquee tool and drag them down to the actual track that. Again, its not ideal, but its another workaround to try out. Yeah, its a shame that Logic doesn't have non destructive midi editing. So annoying haha. But its so great for so many other things. I think this is the number one bummer for me about Logic. Anyway, hope that helps, and good luck if you are planning to continue on!

Not sure really what you mean but if you are saying take the mouse on one end of the region, drag it, then take the mouse on the other end of the region, drag it, then copy it, then the reason I would avoid that is cause it takes too long haha. but maybe I don't understand what you are saying. At the time I first replied to this thread, I was working on a project with several midi drum takes and I was trying to comp them like you would comp a vocal. In Pro Tools, when you make a midi cut, the cut is non destructive. Just like it is with audio in Logic. If I am understanding your suggestion correctly then that's my whole point. I was trying to avoid having to do what you are suggesting. Maybe im missing something, but thanks for the suggestion anyway!

I ended up taking step one out of the above macro. This means now I need to command click to select where I want to make the cut, *then move the mouse a little bit away from the marquee line but keep it inside the region*, then hit the macro. Still pretty easy. The lack of mouse movement in relation to where the marquee lies graphically is what the problem is with the macro above. sometimes it worked and sometimes it didn't. This extra click and tiny physical nudge of the mouse before hitting the macro make it way more solid.

Okay got a true 1 click solution going. Its pretty fast, the unfortunate side effect is it takes multiple command-z's to undo the macro, but its not horrible. I think three of those undos are due to the "Set Region/Event/Marquee Start to Playhead" bug mentioned above unfortunately. If they fix that the required undos would be reduced. The change from the macro above is that now you can just assign this to a mouse button and click inside a midi region and it will non destructively split it where you click the button. No teeing up required! note: secondary tool needs to be marquee. Im sure you could modify this macro though if that's doesn't fit your workflow. On that note, if you have that "Marquee Tool Click Zones" thing turned on as an option in the preferences, then make sure you only click this macro when the mouse is the regular pointer and not the marquee tool crosshair/plus-sign thing. Here is the improved macro (new stuff is in the first 2 steps): 1. Macro Action: Command-Primary Click (secondary tool should be set as marquee tool) 2. "Go To Selection Start" 3. Macro Action: Primary click down/up 4. “Copy” (command-C) 5. "Drag Mode: X-Fade" 6. “Paste at Original Position” 7. “Nudge Region Event Position right by Nudge Value" 8. "Slip Left by Nudge Value" 9. "Nudge Region/Event Length Left by Nudge Value" 10. "Select Previous Region/Cell/Event of Same Type/Number" 11. "Set Region/Event/Marquee End to Playhead Position" 12. "Select Next Region/Cell/Event of Same Type/Number" 13. "Trim Region Start to Previous Region" 14. "Drag Mode: No Overlap" Also just wanted to mention to me this is totally worth getting a mouse you can assign macros to if non destructive midi editing is as important to you as it is to me. I can't guarantee this is going to work for you if you go out and get one . Its working pretty swell for me though. However even if it doesn't work, having a mouse that can perform macros is really helpful in general.

I really hope they include an option for non destructive Midi cuts some day. In the meantime, here is a macro workaround to split a midi region non destructively. The idea is to place the playhead where you want to split the region, then click the region with whatever mouse button you assign the macro. I would have liked to incorporate the playhead placement into the macro but its just too buggy! Hopefully this inspires a more elegant soution. I am using it rigth now in a session and it seem to be working pretty well, I have some issues here and there. I might refine it or I might abandon it. Figured in the meantime Ill post it so someone can use the ideas if they want. This works on 10.5.1. Several commands are involved in the macro. It will likely not work in specific untested scenarios. It may not fit all workflows. There is a lot of room for error in the setup unfortunately so good luck haha! I used GHUB to set up the Macro and GHub is a nightmare so Id imagine it would be easier somewhere else. I think setting up delays in the macro properly might be pretty important. *Needs a mouse that can run macros or a third party app that runs macros (Logitech GHub works). *no existing overlaps in midi regions that the macro is perfomed on (“Drag Mode: No Overlap” = suggested default workflow) The Logic Pro functions listed below can all be found in the Key Command window. Create the macro below and assign a mouse button to it: 1. Macro Action: primary click down/up (you can take this out but make sure you select the region manually before starting the macro if you do) 2. “Copy” (command-C) 3. "Drag Mode: X-Fade" 4. “Paste at Original Position” 5. “Nudge Region Event Position right by Nudge Value" 6. "Slip Left by Nudge Value" 7. "Nudge Region/Event Length Left by Nudge Value" 6. "Select Previous Region/Cell/Event of Same Type/Number" 7. "Set Region/Event/Marquee End to Playhead Position" 8. "Select Next Region/Cell/Event of Same Type/Number" 9. "Trim Region Start to Previous Region" 10. "Drag Mode: No Overlap" If you create keyborad shortcuts for all the fucntions listed above and play with them one by one you will see how it works out and maybe get an idea for something even smoother. If you are looking at the macro above and thinking, "seems like there are extra unnecessary steps in there", there are. The "Set Region/Event/Marquee Start to Playhead" command only works properly on very short midi files. It doesnt work on super long ones for some reason. So I took that out and replaced it with a multi step workaround within the workaround (steps 5,6,7, and 9).

to recreate bug: Record a few takes of some midi over a few bars to create a midi take folder with at least two takes in it. open the folder to reveal both takes so you can see whats going on better. Use the scissors or marquee to cut the take folder in half. use "Join" (command J) to join the folders back together. It works, but there is a graphical bug where the second half of the first take disappears in the top row of the take folder (the row showing the active take) the second half of the first take appears as it should in the the second row. the second half of the first take is audible upon playback even though it is not showing up in the top row of the take folder. Also notice the divider lines are still present in the two lower rows. But they are not actually real dividers anymore, just graphical/funtional bug I think. to workaround: once you have joined the take folders, use the take folder's pull down menu or a keyboard shortcut to select "unpack to new tracks", then select what you just unpacked with the mouse, use the function "join per track", then right click to "pack take folder". That workaround would be very easy to execute with a macro were it not for the need to select what you unpacked after "unpack to new tracks". Anyone have an easier way to get this bug worked around? (at least im pretty sure its a bug)

Hey Storytime symphony I know its been a while since you posted about this. I read through this thread and it looks like maybe some things were deleted? Do you mind explaining a bit more how this is a solution to the OPs question? Im just not following what you are suggesting to do. I am trying to comp several midi takes that are like 3 minutes long each, and being able to split these takes non-destructively would be super helpful. I would be splitting them many times in many different places and then using the boundaries handles to edit exactly where the cuts are up in the comped track. Does your suggestion help out in a situation like this? Thanks!

Has anything happened on this in the last two years by any chance? Like the OP, I am looking to scissor a midi region and have each of the two new regions retain all the notes of the original region before the scissors. Meaning: midi region has four notes, CDEF. make a scissor on the region between D and E so you have two regions: One with notes C and D and another with notes E and F. drag the two regions away from each other. now take region EF and pull the left edge handle backward. In any other DAW, notes C and D would be there as you pull back the region boundary. But in Logic, they are erased when the cut is made. "Why do you want to do this?" I have a midi performance with several takes that I need to comp and each midi take is about three minutes long. Unfortunately the whole take folder swipe wand thing (which is awesome) only works with Audio, its not available in midi. I have tried using the take folder method without the wand (slicing the take file up instead), the track alternative method, and the plain old method of having several midi tracks. In all of these scenarios, it doesn't really matter. I am finding what would really be helpful is to have the ability to slice a midi region non-destructively.

Here is a video of Streaky talking about a bunch of different sample rates throughout the whole process. The whole video is good, talks about the mix vs mastering and sample rates.

part 2 of George Massenburg talking about when he considered digital to be "good digital"when he started doing session in 96KHz

Here is Tom Elmhirst mentioning that he does 24/96 mixes:

Here is Al Schmidt talking about 96KHz and 192:

Here is George Massenburg talking about 96KHz: