There’s a first time for everything. This is not one of those times.
Blame it on entropy or whatever. Things get messed up. Appleâ€™s OS X is no exception.
In the last few months, I started getting this error a lot:
You are opening the application â€Pro Toolsâ€ for the first time. Are you sure you want to open this application?
Except, itâ€™s not true. I open Pro Tools nearly every day. The alert isnâ€™t very important, but it was beginning to get annoying seeing this pop up every time I wanted to record.
So, a little googling and I found an answer on StackExchange. It involves using the command line on your Mac, which can be a bit scary if youâ€™ve never done that before. But itâ€™s a single command, so you should do just fine. Hereâ€™s the quick and dirty summary…
This is where the Matrix is on your Mac. There’s no green falling code or woman in the red dress. There may Agent Smiths lurking though.
- Open the Terminal application (found in /Applications/Utilities/).
- Copy the following command (all of itâ€¦ the whole long line) and paste it after the prompt.
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -all local,system,user
- Hit the Enter/Return key.
- The process will begin. It may take a minute or two to finish. Do not quit the Terminal application while the command is running.
- Eventually the process will complete and another prompt will appear. Now you can quit the Terminal app.
This command resets all of the first run warnings. So any application that requires that will be reset. So you should see the alert one more time for each of those applications and then it will go away for good.
1 Comment >
GarageBand likes to keep MIDI data hidden and inaccessible. Here’s how to extract it anyway.
Appleâ€™s GarageBand makes it relatively easy to sketch out an audio demo, but it does have some severe, intentionally-crippled limitations.
One of the biggest drawbacks is the lack of built-in support for exporting MIDI data.
Performances are stored inside the session file in some sort of MIDI fashion, but Apple doesnâ€™t give users an easy way to get that information out. Major bummer. *looks west towards Cupertino, squints eyes, shakes fist in air, mutters under breath*
However, a nice guy named Lars Kobbe has put together a workaround/hack that extracts MIDI data from the reluctant clutches of GarageBand. You can download his GB2MIDI Apple droplet script from his site: MIDI-Export in Apples Garageband. Here’s the direct download: GB2MIDI.ZIP If that link doesn’t work, I’m providing the file hosted on my site here: GB2MIDI.ZIP
The article is in German, but instructions in English are found near the bottom of the article (just before the comments section). Getting the MIDI data out involves several steps. Hereâ€™s my summary of the process.
How to Extract MIDI Data from GarageBand
- Join (Command-J) regions of a track you want to export
- Convert that region to a loop via Edit > Add to Loop Library (NOTE: In GarageBand 10.1.0 this menu item is now located under File > Add Region to Loop Library )
- Find the newly created loop file (an .AIF with MIDI data hidden inside it) in the folder:
Macintosh HD (or whatever your system drive is named)/Users/(your home folder)/Library/Audio/Apple Loops/User Loops/SingleFiles/
or the abbreviated:
~/Library/Audio/Apple Loops/User Loops/SingleFiles/
- Drop that .AIF file on Larsâ€™ GB2MIDI droplet
- Grab the freshly extracted .MID file, which should appear in the same folder where the .AIF loop was. If not, see the comment section below.
- Import the .MID file into a respectable DAW (basically almost anything other than GarageBand).
- Make next hit record.
That last step is optional, but I say go for it. 😉 Let me know if this helped you.
Locating The Files
If youâ€™re having trouble locating the loop file, it may be because your Library and/or Users folders are hidden, as later OS X versions have been wont to do.
To unhide the Library folder, open the Terminal application, which is found in the /Applications/Utilities/ folder. At the prompt type the following:
chflags nohidden ~/Library/
To unhide the Users folder, type this into Terminal:
sudo chflags nohidden /Users
Then enter your administrator password.
Look for the newly unhidden Users folder in your hard driveâ€™s root folder. It should look something like this:
After running “sudo chflags no hidden /Users” you should see the Users folder (highlighted in red in the image above) appear under the root folder of your hard drive (often named “Macintosh HD” by default).
For more on the hidden Users folder issue check this article from The Mac Observer. It seems the problem was introduced with iTunes 11.2 when Find My Mac is enabled. Another blog suggests that updating to iTunes 11.2.1 fixes the issue.
This GarageBand MIDI article has regularly been one of the most popular posts on my site. That means there are a lot of people using GarageBand and discovering its unfortunate MIDI limitations. The best bit of advice I can give to any musician or audio engineer still using GarageBand is STOP. I know that may sound harsh, but GarageBand is intentionally made to be consumer-grade software. If youâ€™re serious about recording, take the time to investigate other DAWs. Find an alternative solution. There are many to choose from and nearly every one of them is less limited than GarageBand. They range from super affordable to â€œprofessionally priced.â€ Hereâ€™s a list to get you started. (Some links are affiliated.)
Pick any of the DAWs above (or find another â€” this list is by no means exhaustive) and youâ€™ll find it much easier to work with MIDI. Let me know what software you chose.
If you are on OS X 10.15 Catalina or greater on your Mac, then you can only run 64-bit apps. As of the time of this update (May 2020) the app is not 64-bit compatible. This is a known issue. I am not the developer of GB2MIDI, but thankfully the developer Lars Kobbe maintains his app on Github. Here is the link to an open GitHub request for updating GB2MIDI to 64-bit.
112 Comments >