bboeholt

Hello - experimenting with flex time using raw audio tracks and have everything aligned timing wise where I want it. I’m looking to capture this adjusted audio by using the “export audio to a track” option under the FILE menu and also just focused on a single audio track at the moment to make sure it works before going global with the whole export thing. It’s not working as anticipated of course and to date - no matter what I do with regards to the checkbox options - the resulting audio file is visually reduced in gain in the track lane and in order to play it back I have to raise the gain on the track. I am not normalizing or trying to prevent clipping or bypassing effects….all boxes are unchecked in the export dialog window. Also tried bouncing the individual track and I get the same exact thing….a reduced gain duplicate audio file. I assume I’m simply missing something, but am I CORRECT in that if you export or bounce an audio track and you bring it into a track lane/channel strip with identical settings as the original you should get the same waveform essentially and it should play back at the same “volume” as the original recording or is this reduced gain the way exporting and/or bouncing just works? In full disclosure - in an effort to alleviate always having to adjust faders with my underlying volume automation - I took the advice of another user and changed all my individual tracks to having automated gain in lieu of automated volume so all I have to do is ensure all my faders are at zero and the perceived “volume” is consistent. This seems to work quite well for automating levels w/o the headache of always adjusting faders, but curious if it maybe this somehow played into the gain being reduced for my export files. I don’t think so and don’t see why that would matter, but can’t figure out or think of any other reason why my export tracks are reduced. And while I’m on the subject of exporting audio - can somebody explain the difference between bounce and exporting audio? Seems to be two different ways of doing essentially the same thing. Is there a difference here and is there a time and place to export vs bounce? I don’t see the difference yet, but I’m also just figuring this out so apologize if it’s a stupid question. Any assistance or tips would be greatly appreciated !! Bryan

I have a drum track region that I've smart tempo adapted to get the beats/bars aligned. I've also used this same drum track as the master "star" track and groove tracked all other parts to it to quantize everything to the drum track. In the smart tempo editor it appears the drum transients are perfectly aligned, but only in the editor. My main Beats/Bars/Div display and all track lanes are not aligned and I have no idea how to reflect the smart tempo results to the main program and tracks. My goal is (was) to smart tempo adapt the drums to establish a solid beats/bars/div tempo baseline and then use flex time to make needed adjustments to certain parts. My understanding is you need an "aligned" project that is mapped or quantized to a beats/bars/div tempo reference in order to use flex time. As it is, the measure count in the smart tempo editor and the actual song do not match. The audio transients in the main drum track lane are also not aligned to the main beat/bar/div display, but they appear to be perfectly aligned in the smart tempo editor version of this. I can't figure out how to get my smart tempo editor results to sync or reflect in the actual audio tracks and align the song and I'm assuming if i can do this.....I can then use the flex time to make adjustments. Am I tracking here or am I missing something and/or overthinking this? Super frustrated and I just keep hitting a wall. I've watched every flex time and smart tempo video I can find, but none seem to address this combination of events meaning adapting tempo to a song based on regions and then using flex time to make needed adjustments. I keep telling myself it shouldn't be this hard....but maybe it is Any tips, advice or pointers would be greatly appreciated... thanks in advance !! bryan

Latest Logic Pro running latest OSX Catalina. I recently upgraded my 2014-15 MBP (T2 Connectivity) with a brand new shiny MBP (T3 connectivity). Made sure I had the exact same configuration and then I imported my 2014 MBP over to my new machine. All appears well and the computer and Logic seems to work well with the exception that my MOTU Micro Express and Fastlane interfaces that drive all my external midi instruments have all gone totally bonkers. As logic boots up, about half way thru the boot sequence it sends some sort of MIDI message that from that point forward, triggers random notes on my external instruments driven by my MIDI Interface at every user input screen and the midi interfaces go into a tail spin with indicator lights all coming on, dancing, flashing, etc. Once Logic loads and from that point forward, every mouse click, screen focus change, user move with mouse, space bar start/stop, etc creates a horrific random sound thru my external instruments. Hit PLAY and the all the interface indicator lights go bonkers, the sequence plays and within a minute the whole sequence starts to get all garbled, goes out of sync and the midi interface lights bounce all over the place. Press stop and the lights remain for a bit and then seem to settle down. Hit play - starts all over. There is also something random going on where the lights all come on for a few seconds, blink a few times and then subside...only to repeat meaning there's some sort of pattern being generated some how while Logic is just sitting there doing nothing. MOTU is clueless and hasn't given much help other than to say create a new user profile which is a major pain as I need to share everything and re-register all my plugins, ilok, software instruments, etc. I've tried reloading drivers, erasing profiles, etc and almost want to buy a new interface, but suspect that won't solve my issues as both interfaces are acting exactly the same way so pretty sure there's something going on behind the scenes. The interfaces show up in my Audio/Midi Manager and are defined to proper ports in my environment window as far as I can tell. Truth is EVERYTHING worked flawless until I purchased this new MBP and tranferred my old machine over. I'mkicking myself for it, but reaching out to see if others have any suggestions. Specific Questions I have - This all started after "importing" my older macbook over to my new one. Everything aside from Logic seems to be fine. CAN a corrupt user profile actually cause such an issue. and if so why would it be so specific meaning it's just my midi interface and the external instruments in Logic having problems. I have no other problems with the computer or Logic for that matter. All other programs work as expected. Is there some cache or profile that's maybe corrupted that I can clear that I'm not aware of? Can Logic itself be corrupt and would reinstalling it help? My gut says no as every other aspect of logic seems to be working fine. This is certainly not my favorite idea as I would have to recreate everything and not sure I even remember how I did it all....it's been years! What would cause MIDI to be transmitted randomly and what would cause a midi interface to be all whacked out? Pretty sure I don't have any sort of midi loop as it's pretty straight forward. IN --> OUT to all my boards and that's about it. I keep coming back to some setting in Logic perhaps that I'm not aware of because it's definitely coming from here....every other program and every other function inside Logic works fine. No issues with plugins, effects, software instruments, etc. OK - any assistance or ideas would be very helpful. I've been stuck on this for over a month, have reached out to MOTU and others and no luck. I have videos of what's going on if anybody's interested in tackling it. It's very odd indeed and I certainly have never seen anything like it.

you bring up an interesting point. Logic sees the MOTU Uno Midi Interface as an option to pick under the external instrument plugin MIDI destination menu. Interestingly enough - I had it connected thru a MOTU microexpress 6x4 interface to port 1, but the port did not come up as an option under the external instrument plugin interface, but the Mackie was definitely talking to logic as the faders and transport controls all worked fine. Never did figure out how to make it a target in that scenario and hence I direct connected to the UNO interface. Update: I have firmware 2.1.0 on my Mackie. I was trying to update to 2.1.2 and the midi file would not load under Import MIDI File and hence nothing to playback to the Mackie thru the bootloader mode I downloaded firmware 2.1.1 and magically - the MIDI file did import into the track lane and it's a bunch of sys ex messages which is what I'd expect. However, bypass all controllers and put the Mackie into boot loader mode and hit play - nothing. not sure what I'm missing, but guessing it's stupid simple or a checkbox somewhere buried 10 windows deep any other clues....??

Hello Have an older Mackie Emagic/Logic Universal surface controller that I'm trying to upgrade the firmware on. Found a couple posts that paste the .txt file provided by Mackie for the process, but the problem is I can't get Logic X to import the midi file that's provided with the download zip file from Mackie. It says to make the Mackie controller the midi target - I connected my MCU via a single MOTU UNO 1x midi interface, logic sees it. I created an external instrument track and choose this as the target on Midi Channel 1....and nothing. The boot loader combo keys work on the MCU unit to put it boot load mode, but there's nothing to play because nothing loaded. I am running the latest Logic X under Catalina OSX and while this is totally old school, the controller still works for the most part although some functionality has been lost over the years with Logic upgrades. I'm hoping this firmware update will help as I'm a couple firmware versions back from the 2.1.2 which is apparently the latest. What am I missing ? outside that - anybody using the new Mackie MCU controllers and are they worth the money? They look identical to the older models for the most part so curious what you get that you can't achieve thru the older model? Anybody know??