MrSnickers

Adding my own experience to the thread because I was searching for an answer to this as well in 2023 on Logic X. On my system, when using any method to create a loop from a MIDI region, Logic will create a GREEN Apple Loop - but it's also recorded as an .AIF file using the sounds from whatever software instrument is present on the track you are creating the loop from. I guess this is done to provide preview audio when browsing loops. This happens with both 3rd party instruments (TAL-Drum) and Logic instruments (Ultrabeat). Oddly, even if there's no instrument present on the track, Logic still creates an .AIF of... nothing... and adds the file to my User Loops folder. I replicated the same behavior in a completely empty new project with no plugins, nothing on the Stereo Bus, no software instrument presets loaded, etc. Ultimately this process still creates the thing I'm after -- a GREEN MIDI loop that lives in my User Loops library -- but it's definitely annoying (mostly from a disk storage capacity standpoint) to have Logic creating .AIF files of a MIDI region when you are explicitly trying to avoid it.

Replying here to say THANK YOU - I was searching for an answer to this problem as well and *this* fixed it for me on Logic 10.7.4

Alex - thanks for posting this. I've been wondering about this myself for months and thought I was going crazy. It's such an inconsequential thing that it's difficult to troubleshoot because you can't know what changed or what to call the issue you are troubleshooting! I concur with David that there doesn't seem to be a rhyme or reason why the piano roll does what it does at this point. Posting here just to keep an eye on this to see if anyone else has any other workarounds

Thanks for the reply, Des. Absolute / Scaled modes result in the Playhead jumping to a set position 20 secs or so before 1.1.1.1. However I was able to figure it out (for my purposes) through trial and error. Here are the steps I took to program the Maschine MK2 Control Encoder (Master Knob) to serve as a Playhead control in Logic Pro X. With the Maschine in MIDI Control Mode... In Native Instruments Controller Editor, I set the Control Encoder (Master Knob) to: MCU Wheel In Logic Pro X, Controller Assignments, I created 2 separate assignments - one to control the Playhead moving forward (Value Change = B0 3C 01), one to control the Playhead moving backward (Value Change = B0 3C 41) Here are the assignment values they both share: Min/Max: 0/127 Format: Unsigned Mode: Relative The key difference here was to assign different Multiply values for each assignment: Playhead moving forward, Multiply = 1.00 Playhead moving backward, Multiply = -1.00 This solved it for me - the playhead now moves forward and backward 1 bar with each step of the knob, depending on if its moved clockwise or counter clockwise. Hopefully it helps some others down the line

I'm attempting to control Logic's Playhead with a MIDI assignment to a stepped knob on my Native Instrument Maschine MK2. I'm trying to use the big knob on the Maschine to move the Playhead forward and backward a bar depending on if the knob is turned right (forward) or left (backward). I've gotten it to work moving forward but can't figure out how to make it go backward when turning the knob left. I've attached my MIDI assignments for reference. Is this possible - if so what am I missing?

You can save a Drum Machine Designer instrument / set of samples by using the Library browser and saving it as a Patch. When you have the DMD instrument selected, open the Library and in the bottom right of that pane you can click "Save..."

In doing some quick experimenting - it looks like you can create an Alias to a folder located on an external drive and drop it in the default Patches location (Mac HD > Users > [user] > Music > Audio Music Apps > Patches > Instrument). This would allow you to store your Patches / kits on an external drive but still access it via the lefthand Library browser. AFAIK, the samples can live anywhere regardless of the patch file location. Hope that helps

Just a quick update - I figured out how to make the assignments universal across all the pads. By default, when assigning via Learn Mode, the Channel Strip parameter for the assignment is set to Fader Bank but if you change it to Selected Track, it will work. Once you have the samples loaded, with this workflow you can start hitting a pad on the controller to select it and then start sculpting the sound by using assigned knobs to control the Quick Sampler controls - amazing! Note: you have to have both "Select Pad by Key" and "Select Channel Strip by Pad" checked off for this to work.

Not quite the same topic but related, I've been trying to figure out how to map universal controller assignments to a Maschine in MIDI Control mode (i.e. just using the pads and knobs as CC data). Automation would follow. My goal is to replace Battery 4 with the new DMD/Quick Sampler for all my custom drum kits / samples. One thing I haven't figured out yet is if it's possible to make controller assignments universal for all pads in a DMD kit vs. for individual pads/tracks. For example, a knob mapped to control the decay of a sample, a knob mapped to control pitch, etc.. of whatever sample is currently highlighted / selected. From what I can tell so far, you can set a controller assignment to individual pads/tracks but not as a universal assignment that knows what sample/pad you're trying to change. I'm considering doing all the assignments for the decay, pitch, and HPFs for each pad.... god help me. In Battery 4, there was a way to do all the mapping / automation control in a single macro - you could highlight all the pads/tracks at once and drag the MIDI assignment and it would map them all in one task. Right now I haven't figured out if thats possible with the new DMD.

You can save them as a .patch (the standard Logic instrument preset / instrument file type) by using the Library. I'm working on converting all my custom Battery kits and sample banks over to DMD as the Quick Sampler essentially gives us everything Battery could do - been waiting for this moment!

It looks like adjusting the Velocity settings downward before recording via Inspector - in both the Region OR the Track sections - successfully alters the velocity as its played back but does not affect the actual data coming in as recorded / performed. In this sense, it seems to work the same way as using the MIDI FX Velocity Processor. For my purposes, I imagine it will get confusing fairly quickly... seeing one velocity but hearing another across a number of drum tracks/regions. I suppose I'll have to fix myself rather than trying to find a Logic workaround . To be clear, I wasn't expecting a "solution", I was mostly curious if others had run into a similar situation and how they dealt with it. If NI ends up updating the firmware on the A61 to allow for various velocity curves, I'll try to come back and post here for future reference.

Thanks for the responses all. Yes - I was pretty surprised to find that adjusting a velocity curve would be a "feature" only reserved for the significantly more expensive S61... especially considering it's got to be a purely software "feature"... They recently updated the Firmware on the A-series keyboards to allow for re-mapping of the knobs and buttons... no, this was not a "feature" that was offered for this keyboard either, until a month or 2 ago... so maybe that bodes well for a future update to give us control over the velocity curves. I'll try to offset the velocity on the track via Inspector to see if that works, I hadn't tried to do that AHEAD of recording a performance. Thanks for the thoughts and comments.

So after using my beloved M-Audio Keystation 61es for a decade, I had to move on as the pitch wheel now sends errant CC data. I picked up a Native Instruments Komplete Kontrol A61 to replace it only to find out that the A series keyboards do not offer the ability to change the set velocity curve (!?) - good one, Native Instruments. The pressure and force I'm accustomed to playing with on the Keystation translates to way higher velocities on the A61. As a result, I lose a ton of feel and dynamics because most everything hits a max 127 velocity value. I'm wondering if there is a Logic solution to this problem that does not involve instantiating a Velocity Processor MIDI FX on every channel. Likewise, while the Velocity Processor would be a partial solution, what I'm really looking for is something that will automatically knock off about 10-20 in velocity as the MIDI data is recorded but still maintain the velocity relationship / dynamics as I've played them. Over time I'm sure I will get used to the A61 and adjust my playing habits but I'm curious if anyone knows a solution in Logic that would help in the meantime. Thanks in advance.

This forum never ceases to amaze - here I am in 2018 looking for exactly this - so helpful

With the addition of the Percussion Drummers in 10.3.2, I'm using Drummer A LOT more now - what a great add on. I'm wondering if anyone knows where the default Drummer channel strips are saved / if they are accessible to re-save new Channel Strip Settings... I love the Percussion Drummer feature but would like to eliminate the bulk of plug-ins that are loaded automatically when you pull it up (e.g. the Channel EQ, Distortion II, St-Delay, and ModDel) ... Is there a way to change this? If so, how? Thanks in advance,