colacola

EDIT: To clarify, I mean if you import ANY tracks. Not the Melodyne'd ones (Importing Melodyne'd tracks has always been broken, but even importing a random Midi track will reset all my Melodyne edits) IME, any session (new or old) in Logic 10.7.7 with latest Melodyne Studio (ARA instance/5.3.1) will lose ALL Melodyne edits, session wide, if I open the Right Pane and import some tracks from another Logic session. I'm on Monterey 12.6.5 MacBook Air M2. I suspect though that this DIRE bug is not unique to me. I've emailed Celemony and Apple. If you use these softwares/functions, can you tell me if you face the same repeatable bug? And if so, please email the respective companies also so they take note and prioritize this, please 🤞

Thank you for taking the time -- that makes good sense (I've been doing simple sessions in the past without using SMPTE-Lock, but someone suggested that I use for the problematic sessions. I didn't analyze that this wouldn't affect anything about the content of the region but rather only ensure the start-point is maintained). That was kind of you to go out of your way to break it down, I appreciate the extra effort. So in closing, we're not aware of any way to Logic to convert more complex sessions to a different sample rate? (Yes, 99% of the time I do as you outline.. just print stems etc). But there are scenarios I'm facing right now with back and forth collaborations between old (but very important) sessions being revisited of which there is multiple versions (production, tracking, etc) and a lot of 'Import' going on). The regular methods are slow and limiting; it would be ideal just to convert all sessions to the intended SR to get a more streamlined flow going. But I realize I may be out of luck on this...

[EDIT: oops gotta eat my words] With all due respect, you've totally misunderstood/ignorant of how important using SMPTE lock is when changing the SRC of all the audio files used in a project. Thank you for your input but none of it is relevant (or correct) with regard to my workflow.

Just curious, is it a reliable method to: 1) Select-all in the Arrange and SMPTE lock the regions 2) Switch session Sample Rate (eg from 44.1khz to 48k) 3) Go to the Audio Bin and select all and choose 'Convert Files' to do SRC This works fine for simple sessions, I'm curious if there's any known caveats as sessions become more complex (aka large)? Do audio Take Folders survive this process, or are they an aspect that is prone to break?

Yes, just press J (or choose Edit > Bounce and Join > Join Per Tracks: join-regions.gif Thank you! Always happy to be the fool if it means the answer is in my favor

It appears there is no way take the marquee tool and select an area (inclusive of both silence and an audio region) and 'consolidate' it to instantly (and destructively) create a new region that includes the full selection? This is a quick command in PT or Cubase, but I've never located it in Logic (even though Logic is the DAW is know best, making worry that the functionality doesn't exist). I'd love to stop doing work-arounds...

It's been years and with every iteration I pray they have addressed this behavior.. Is there anyone who has been able to use this function with it always causing the entire project to reload? Incredibly time consuming and painful -- Im sure there's some peopel who rarely need this function, but I find myself needing it all the time and I'm driven absolutely mad (If you're not familiar and want to test, right-click and audio region with an imbedded tempo and choose from the Tempo submenu 'Remove Original Recording Tempo') I have been filing bug reports, but like most of my reports, they go unaddressed for years (or maybe forever). I'm used to this. I personally filed *over* 100 individual reports over the years about Logic's broken PDC and only last year did they *begin* to address it (10.7.2 still has PDC dysfunction even now) Does anyone have any tips or insight that might help me mitigate this behavior? Unfortunately, using 'Write Project Tempo to File' doesn't seem to function consistently, so I must first 'remove' embedded tempo to get a clean slate.

The amount of people in this thread who are downplaying these bugs or seem unaware of them is crazy (one such response from a 'certified trainer' even.. ??!). I realize we all use Logic differently, but anyone that mixes songs has run into it, and anyone that mixes song Professionally has simply moved to PT, Cubase, etc because these bugs are fatal and have existed forever and continue to exist (Logic 10.5.1 currently) Here's a quick summary: 1. Automation in Logic (Pro X 10.4.8 at time of writing, but is still the case I believe in 10.5.1) is not plug-in delay compensated on audio/instruments tracks (but on aux tracks/summing stacks). In other words, once you're working with latency-intensive plug-ins, even instruments (e.g. VPS Avenger) or just being an UAD user, your automation is basically out of order. This is also true for Logic's own Linear Phase EQ for example, no additional 3rd party plug-ins needed. Just automate a low or hi-cut, the automation will be nearly around 100 ms out of time in this case. 2. Plug-ins that depend on beat-time information (MIDI synced to the host) are simply not compensated on aux tracks/summing stacks (but on audio/instrument tracks) In other words, if you are using something like Output's Movement, LFO Tool, Pumper, Effectrix, Cableguys plug-ins... , you name it, on an aux track/summing stack - timing of the beat-time based plug-ins will be out of order. I know several producers using a ducking or gate-effect bus for such effects - timing won't be correct then. This is also true for Logic's own Phat and Step FX for example. 3. Side chain signals aren't compensated correctly The external side chain signal isn't compensated when introducing latency generating plug-ins after the side chain receiving plug-in on audio/instrument tracks (e.g. limiter after compressor with external side chain). The external side chain signal isn't compensated when introducing latency generating plug-ins before the side chain receiving plug-in on aux tracks/summing stacks (e.g. tape simulation plug-in before compressor with external side chain). If you are using the FabFilter Pro-L 2 with external side chain triggering for stem mastering for example, the side chaining will be completely out of time moreso when using one of the oversampling options. This is also true when working with Logic's own Linear Phase EQ and Compressor on one track using external side chaining. 4. Bounce in Place is not compensated correctly at all Bounce in Place does not take automation and plug-in delay compensation correctly into account especially when bouncing aux tracks/summing stacks (see above). Pure chaos, depending on what is going on on your tracks and busses. External side chaining is ignored when using Bounce in Place as well. So you have to use the export track or bounce to disk function and drag your files back again into Logic, cubersome.

Is there a way to route the output of a track (typically containing the a stereo 'rough mix' I've been provided) so that I can solo it and hear it played back without being routed through the regular Stereo Out, which contains various bus processing? Obviously, the answer (maybe the only answer) is to change my template for Stereo Out has no processing, and instead if fed from pseudo-master bus where that processing is happening). I'm curious though if there's another way. While still having the audio coming out my standard monitor outputs (1-2) on the interface. Thanks for any input!

Self confirmed. It's now decided to play the audio. I'm unsure what was causing that behavior and why it's decided to switch back with no apparent change on my behalf.

Ok. Can you confirm I'm not crazy, and that at one point (logic 7/8/9 for sure, but X as well I thought) would play audio prior to bar 1?

Can I change a setting somewhere so that audio, midi, or input monitoring will output sound in the measures preceding bar 1 of the arrange? I would like to be able to hear audio regions at 0 1 1 1 or -1 1 1 1 and my input monitoring when tracking. But only silence, until bar 1, at which point all sound out resumes. I hope this was a silly question with a simple answer; I'm convinced Logic didn't always behave like this and I've accidentally changed a setting or something

Ways? Plural? I'm not dismissing the work around (it was my remedy approach for years -- it's hardly some esoteric idea). No one was offended that that was suggested, it was wording like "current insert and send capacity is more than sufficient if you know what you're doing" that comes off as intentionally condescending. I work in multiple DAWs -- and Logic was the only straggler that didn't allow 12 sends on a bus while all others have for eons.

Thanks for the condescending replies.. But I guess there was so many other people like me who "don't know what they're doing", so Apple has blessed us with 4 more sends in this 10.4.5 update, putting Logic on par in this department with other DAWs. Horay!

Love it! You love it? You love blatant misinformation being shared as if it's gospel? That TH-U isn't miles and miles ahead of Amp Designer? That Adlimiter isn't borderline worthless compared to FabFilter L2? That depth, function and versatility of Superior Drummer 3 is the reason the base product (before all the extras you can get) fetches $400, twice the cost of the daw itself? I never said there wasn't a use for the Logic's internal things -- I've used them a ton since I bought Platinum in at version 4.7.2 and continue to today. But anyone encouraging this kind of misinformation should be ashamed. Logic is literally the best value DAW ever, by a long shot, ever since Apple re-packaged it from Emagic. And the value keeps growing with each new version. But I refuse to let misinformation like the things SomeMusicKid44 says be championed, he's borderline trolling and should be ignored.