Logic Pro - Macro Megathread (2022)

@fairchilde17, I've edited this to make sure nothing happens if it's already selected.

2 Likes

Oh Wow this is so beautiful..
How did you defined (or noticed) the pop up windows number in MIDI transform window or Functions button as group 1 of group 1 of group 4?
It might be distracting questions but I'm just a guy making music with computer and have no idea which keywords to searching google or the forum.
(Besides that I'm not native English speaker so I spent lots of time to understand the programmers' term XD.)
Lots of help saying this lots, lots of time Thanks, you're my savier.
And I'm going to dig script editor right now.

The front window is always window 1. I tried to specify the window containing "- Transform" but this didn't work (maybe because it's a floating window). It doesn't really matter though, as you'll only be using this when Transform is at the front.

Get the trial of UI Browser. It's being discontinued soon, so it might end up open source (free). If you don't want to wait, there are other ways to get a UI Element path for free, like THIS.

1 Like

Hi there again :slight_smile:

I was trying out the 'bounce all markers' macro but somehow it is getting stuck..

What I would like it to do is the following:

  • Make sure cursor is at 1st marker
  • pop up: ‘how many markers?’
  • rename marker hotkey
  • copy text
  • ‘Set Locators by Next Maker and Enable Cycle’ hotkey
  • cmd+B
  • set checkbox to ‘mp3’
  • Create folder with Project Name
  • Bounce name = paste text from 'rename marker' step
  • press OK
  • repeat

Again I would really like to learn how to make this myself, but for now, I'm just trying to make sense of it all :slight_smile:

Hiya! Yeah that's an old one and needed tweaking. I've updated it above. :+1:t3:

1 Like

Just to clarify for anyone else reading this...

Unless I've missed something else, the V2 version you posted has one Logic Key Command changed, which is an expected part of the setup for each user. The mistake I made was neglecting to tag that one green, and I've corrected it in the original macro above.

@ween This is the new version of the thread. Please see the updated version of the Vocalign Auto macro above. :+1:t3:

Speaking of, we're a few days away from end of life:

UI Browser End of Life: UI Browser will reach its end of life and be retired on October 17, 2022. The current release of UI Browser, version 3.0.2, will not be updated. On the end-of-life retirement date, the PFiddlesoft website will be closed. Thereafter, it will no longer be possible to download or purchase UI Browser, and product support will no longer be available.

So much good stuff here, @noisneil! Thank you!

I've got a couple, similar to your Track Bounce and Marker Bounce, that I might clean up and post. The Track Bounce automatically stops when the track's name is either Output 1-2 or Stereo Out. I'm sure my use cases are similar to yours as well – all-tracks bounce = produce multitracks (in my case with the song title prepended and the track named for the instrument/stem), and marker-delimited bounces = alt mixes. I also have one to create the alt mixes and so-named markers, to be used with the marker-bounce routine.

2 Likes

Does this rely on there being a track for the output channel? (i.e. Show Output Track)

Indeed. I could include an instruction or doc notice to that effect. I wouldn't want to force creation of one; that's ugly.

You could always create one temporarily... I really like it as a solution, as mine relied on there not being any duplicate track names, which is sh*te. Why didn't I think of creating an Output Track?! :man_facepalming:t2:

Annoyingly, you can rename the output channel by right-clicking, but not via key command or menu item.

Does Shift-Return not work for you, for track rename?

Track rename works, but not channel rename in the Mixer pane/window.

Side-note: A quirk of Logic is that it doesn't update the availability of menu items until the menubar is clicked, but double-dippin' seems to do the trick. This is good because using menu items means other users' personalised key commands become less of an issue. Longer-winded, but probably worth it.

So I'll add one of these to the start of the macro and hide it at the end. Job done! :slight_smile:

Cool cool!

And here's this, if it's of interest. It's a demo of my macro to create Alt mixes within the same Project alternative, all the same length (as many publishers require), and delimited by markers named for each typical alt mix. It works hand in hand with my Bounce Alts macro, which uses the markers to name the bounces.

1 Like

@noisneil, I'm sure you can help with this: I've had a macro running just fine to Normalize Gain to -12.0 (Individual Region + Peak) by tabbing into the Normalize Gain window. But it would be a lot cleaner to use AppleScript to directly access the GUI objects.

I've got this, and the two pop-ups work beautifully - but not the slider, which I want to set to -12.0:

activate application "Logic Pro X"
tell application "System Events"
	tell process "Logic Pro"
		
		tell pop up button 1 of window "Normalize Gain"
			click
			click menu item "Individual Regions" of menu 1
		end tell
		
		tell pop up button 2 of window "Normalize Gain"
			click
			click menu item "Peak" of menu 1
		end tell
		
		tell slider 1 of group 1 of window "Normalize Gain"
			set contents of slider 1 of group 1 of window "Normalize Gain" to 12.0
		end tell
		
	end tell
end tell


I've found a lot of people wrestling with the same thing in fora across the land (lol) but not a solution that works here. Clues?

Window Discovery Tool gave me this for the Normalize Gain window:

pop up button 1 
pop up button 2 
slider 1 of group 1 of window "Normalize Gain" of application process "Logic Pro X" of application "System Events", 
button "Cancel" of window "Normalize Gain" of application process "Logic Pro X" of application "System Events", 
button "Apply" of window "Normalize Gain" of application process "Logic Pro X" of application "System Events", 

{group 1 of window "Normalize Gain" of application process "Logic Pro X" of application "System Events", 
slider 1 of group 1 of window "Normalize Gain" of application process "Logic Pro X" of application "System Events", 
static text "1 Region selected" of window "Normalize Gain" of application process "Logic Pro X" of application "System Events", 
static text "Target Level:" of window "Normalize Gain" of application process "Logic Pro X" of application "System Events", 
button "Cancel" of window "Normalize Gain" of application process "Logic Pro X" of application "System Events", 
button "Apply" of window "Normalize Gain" of application process "Logic Pro X" of application "System Events", 
static text "Algorithm:" of window "Normalize Gain" of application process "Logic Pro X" of application "System Events", 
pop up button 1 of window "Normalize Gain" of application process "Logic Pro X" of application "System Events", 
pop up button 2 of window "Normalize Gain" of application process "Logic Pro X" of application "System Events", 
static text "Affect:" of window "Normalize Gain" of application process "Logic Pro X" of application "System Events", 
static text "db" of window "Normalize Gain" of application process "Logic Pro X" of application "System Events", 
static text "Normalize Gain" of window "Normalize Gain" of application process "Logic Pro X" of application "System Events"}

Thanks for any pointers! And sliders!

You'll have to explain what I'm looking at I'm afraid. My powers of deduction are failing me. 🕵🏻‍♂️

Sorry! Should've given a bit of preamble – it's a demo of my macro to create Alt versions within the same Project alternative, all the same length, and delimited by markers named for each typical alt mix. It works hand in hand with my Bounce Alts macro, which uses those same markers to name the bounces.

1 Like

I've updated the Bounce Tracks macro in the main post. I think it's pretty robust now! :grimacing:

That's exactly what I would have tried. I just had a go and couldn't set the slider value I'm afraid. Sorry. :man_shrugging:t2:

Dang! Oh, well. Thanks for trying!