Andreas Lorentsen

Hi, Is there anyone else experiencing problems with key commands/bindings/mapping in Logic Pro 10.8? I use Logic Pro daily, and I've been doing so for the last 13 years, and I've used a LOT of time and effort in customizing Logic in every way I can to make a smoother ride. Enter v.10.8…and everything is just going NUTS all over the place. 😮 I've always used a separate key binding file located in /Users/<myuserName>/Music/Audio Music Apps/Key Commands It has a unique file name, goes without saying... just in case and so on. It has worked flawlessly for the last 13 years, but not anymore. The first thing I noticed when I installed and run Logic Pro 10.8 was that it didn't respond to any of my custom key bindings. So I opened "Key Commands -> Edit Assignments", and I noticed that the correct file was active. Puzzled, I pressed "Intitialize all Key Commands" (…-menu). Lo and behold, there were suddenly 13 conflics that Logic Pro told me I had to resolve. So I did, and they disappeared one by one, and I saved the updated key commands. 10 minutes or so went by…at that point I actually thought it was just a minor passing craziness). All of a sudden, in the middle of a recording, literally, Logic Pro had deactivated my custom file and loaded the one named "U.S". So I switched it back, but I quickly got a new warning about (the same) conflicts that I had to take care of. I repeated the cleanup and saved the logikcs file. I noticed at once that this time, there wasn't a single key command that responded. The thing that made me sure about that assumption, was that the faded text describing each assigned key command in the menus were gone/missing, and the familiar beach balls started rotating more and more in perfect sync with my frustration (48 khz, no dithering please...). After that I tried restarting Logic Pro MANY times. I tried manually deleting every other key command file and even chmodded/locked the permissions of the logikcs file, so it was impossible to change. Every time I save the key command file, it works...like…2-5 minutes, and it randomly switches to seemingly any of the other language specific key command files (US, Swedish, German and so on), and it just refuses 😫 to save my settings and use my file. As I mentioned: I have used it (or any of its predecessors and close relatives 😆) without any hassle whatsoever, for the last 13 years or so. At some point, I even tried creating a completely new key command file (based on the default english) KB file). So I finally had it when Logic refused to load anything but the default "US" key commands, and proceeded to just crash plain and simple, without saving my last changes, or anything else for that mattter. In fact, when I realized that was the case, I was just empty. I had no energy left for debugging, and I just shut down my Mac, giving in and entered hibernation mode for an indefinite period of time (Me, not the Mac. Or I don't know…we're not exactly speaking the same language anymore, to tell you the truth. Any thoughts? I'm kind of desperate, because this is SUCH a creativity killer 🫥😑 Andreas

That was my first thought as well. My second thought was…."Maybe the new driver will unlock some hidden superpowers? Give it a go". Famous last words…. All jokes aside: I don't use the sync stuff either, but I'll hang on to the 2.5 driver a bit more, considering that everything is working properly now

I installed the latest driver, but I had some minor problems. On the "Unitor" tab inside Project settings -> Synchronization, it said "Device Firmware: not recognized", and the device didn't respond to any changes to the SMTP sync options. No lights indicating SMTP/clock either. However, when trashing the v.3 driver and reinstalling v.2.5, it now says "Device Firmware: Ports 1…8 - Version 2.0.4" and the MTC/SMTP is working again. Also, with the latest driver installed, the patch mode was not loading any of my custom patches, and the device didn't respond to program change messages or sysex. Works perfectly with the 2.5 driver. I just wanted to share this in case anyone is having issues with it. iMac 2018 (Intel) 16 GB ram macOS 12.5 Logic Pro 10.7.4 Unitor 8 mkII (USB)

Well, that was..easy. I found myself watching that GIF like 25 times. Extremely impressing party trick. This feels like the time i discovered that an expression pedal is nothing more than a volume pedal with one half of a stereo jack cable connected from the input to the output, and the other half to the expression input. This is much more clever of course. Thanks a bunch, fuzzfilth.

I think I also see the problem with this, and why it's no so easily achieved: As soon as you split that 1 region on a track into many, you can't really expect Logic to automatically "know" how to compare say...125 regions to the "new" single (1) region where you want to duplicate the edit operations from the other (that ended up with 125). The only way to keep track of that would be (I'm guessing here though) by constantly buffering undo history and keeping it in memory all the time, which is madness. I might be wrong, of course, and I really hope so.

Hi! Is there a way to use one track/region as a template for cutting/splitting another region at the exact same places? The obvious answer is Groups, but this is kind of different. I 'll try to explain the diffference in detail: If you set several tracks to be members of a group and mirror the edits with Quantize locked audio, you achieve identical edits on the grouped tracks. But it requires that the edits are done simultaneously (in other words: the group clutch has to be ON and is best achieved with a bit of planning. But if I for instance chopped, split and sliced a snare drum region into tiny pieces with an extreme zoom level and used quite some time to get it precise, and then I record a NEW drum track later (see where this is going?) - the ideal thing would be to just tell Logic: "Split the regions at the same spot and crossfade at the exact same length as I did on the other track.". Use it as a editing template. (Apple? you here?) Well, "ideal world" is the big key word here unfortunately. However, it's not ideal and it's certainly not logical, at least not anymore, and I'm too tired to search anymore. It would be an incredibly boost to effectivity if I just could figure out a way to do this without inventing the wheel 8 times pr hour. I hope I managed to explain what I'm struggling with here. Any suggestions? Andreas

Just guessing: The pre-delay and project tempo values are probably affecting the available decay values. 125 is an odd number while 2000 ms (2s) and 120 (bpm) are not, so it doesn't add up when you divide it. Pythagoras could probably have explained that a lot better than me On a far note, I also noticed that (at least before Logic 10.4.5), it simply wasn't possible to pick 438 Hz from the project tuning properties. Every other increment from 442.0 to 436.0 was possible. It just skipped 438. Same thing with the Hz sweeper plug-in. Based on that, I'm not convinced those algorithms are always right. Best of luck, Andreas

I'll try to capture a couple of screen video recordings later, David.

Turns out that the bug wasn't as predictable as I first described. I've tried to debug more now, and I'll try my best to describe the problem (although there may be some significant x-factors that I'm not aware of): Scenario 1: - If I have a take folder with more than 1 take in it (obviously) and press "mute" on that track in track view (without selecting that track first - i.e. if another track or bus is selected): The track mutes like expected, but the colors of the track/regions will not "grey out" and indicate "Mute" until that track is actively clicked/selected and "unselected" in Track view or the Mixer. The "M" indicator in track is also sporadically unresponsive to the track's mute status until the track is: 1. selected, 2. unmuted and 3. muted again. Oh, and pressing "x" (keybinding for mixer) twice, somehow triggers the mute visual status properly (!) Scenario 2: If I have a "summing" (bus) track stack and... - select any of the regions on a track inside it and mute that/those region(s) only - select any track inside it in track view or mixer, and then mute that track (via the M in track view, control surface, mixer or key binding): - Track is muted, but none of the "usual" indicators will change/toggle state to indicate that mute is active - until I deselect that track (click an "empty space" somewhere in track view or "Select None": Then the track or region color will change to grey (normal mute behavior), and the "M" changes to solid color and starts blinking. This happens in any project/template. I've also checked to made sure it's not a case of "All solo" or "All mute". No hidden channel strips muted or soloed either. These are the situations I've had problems with, but I haven't had a chance to test it further though, so there could be all sorts of x-factors, from control surfaces to preference files). My immidiate "diagnose" from a programmer perspective is that the updating of visual indicators (change state) method/function, somehow fell out of, or simply missed some while/if/for/something loop/catch. But I may be wrong of course. Eventually, if everything goes as expected - the developers will have fixed it by the next version (and introduced at least 3 new bugs in the process) - iMac 27" 5k - macOS 10.14.6 - 32 GB Ram - 3TB SSD - UAD2 Apollo 8P

Since I upgraded to 10.4.6, "mute" doesn't activate until the muted track or region is deselected (or select a region on another track - but generally that's the same thing). Anyone else experiencing this? The bug is easy to spot, because the muted track doesn't "grey out" when you press mute. Applies to region mute and track/channel strip mute. Andreas

It sounds to me like you have enabled "Pickup mode" in the Logic preferences. If it's enabled, Logic will assume that the control surface doesn't have motorized faders. These are my (working) settings for MCU Pro + extenders (btw, does anyone know why Logic keep changing the appearance/icon for the MCU units? Every time I restart Logic, there's some other preview icon for the Mackie controllers):

Apple approved my app, and it's now available on the iOS App Store: https://itunes.apple.com/us/app/reverb-delay-time-calculator/id1444531722?ls=1&mt=8 I just realized that there are probably over 200 apps for iOS with the exact same functionality. Probably better too, but at least I learned a lot while making it. Andreas

Hey, Thanks David! I have now sent it to App Store for review by Apple. If they approve, it will be on App Store soon, but this is the first time I've done this, so I'm prepared for anything. Anyway, it's now also possible to use it from Safari on an iPhone or iPad: http://www.atchoo.net/dev/rdcalc/ Bear in mind that it will look weird on a desktop computer display. I discovered that the version I posted earlier is kind of useless. As soon as you start typing the BPM, the value will go to the roof like a madman, because it "thinks" you're tapping the tempo I'll fix that soon. Andreas

Great feedback everyone, I really appreciate it! I'm working on an iPhone version at the moment, as well as some improvements in the web version (mainly user interface tweaks). I'll update this thread when I publish it. Screenshot: Andreas

Hello, I just made an app/web tool for quick calculation of optimal values (in milliseconds) for reverb decay/predelay or delay time/feedback, based on BPM and note (or bar) value. It also has a convenient "tap tempo" function, so you can tap tempo with any key (doesn't work on smartphones yet, I'm working on that...) The purpose is to find out how long a given note value last. Just wanted to share this, in case anyone find it useful. http://www.atchoo.net/dev/bpmtool