I have taken it upon myself to test out the latest updates to GarageBand on iOS and Logic on Mac. Specifically, I have been pushing this new feature where you can prepare a Logic file you have started on the Mac for use on the GarageBand app on iOS.

This feature is compelling to me because a lot of my audio editing these days requires the power tools of Logic, but also the ease of simply booting up a project and making lots of light edits. For example, when I podcast, I usually only manage 2-6 tracks, not 30+. I need Logic for the control over my plugins, quick workflows, etc… but I also need a light and efficient way to make small edits on the go. I am constantly moving around between a busy schedule of public school, private lessons, concerts, gigs, and other miscellaneous commitments. It is nearly impossible to get any editing done on a Mac alone. The iPad is the perfect platform for this. Press the wake button, launch the app, and make a couple of quick cuts. There has not been a great way to work with Logic projects on the iPad, at least until this recent feature announcement.

Testing the First Project

Here is how I ran my first test of this feature. I created a Logic file on my Mac and added some software instrument tracks and audio tracks. I tried two audio tracks and two software instrument tracks for the first test. I wanted to keep it simple for the OS to handle and simple for me to keep track of how precisely it was syncing my edits (or not). 

After recording some MIDI notes and audio into these four tracks, I went to the File Menu and selected “Share->Project to Garage and for iOS.” This act creates a GarageBand version of the file in the “GarageBand iOS” folder which is stored within the iCloud Drive folder.

File Management is Messy as Usual

Ok, so this is where things get weird. It saddens me that Apple’s iCloud Drive model continues to overcomplicate the file syncing process. In my book, Digital Organization Tips for Music Teachers, I ponder why iCloud Drive does so little to compete with file services such as Dropbox, which has been simpler, more intuitive, and more reliable since the start. The same issue I describe in my book is at play in this Logic->GarageBand workflow. 

It is still weird to me that iCloud Drive has container folders within itself that are app specific. It seems to me that this is an unwelcome abstraction for users who are accustomed to putting files in whatever folder they want. You can do this in iCloud Drive, by the way, but then the counterpart apps on iOS do not practice the syncing the same way. For example, if you sync a Keynote file from a Mac to an iPad by placing it in the “Keynote” folder, you can instantly see it when you boot up Keynote on the iPad. However, if you save it somewhere else in the iCloud Drive folder, it will not appear in the file viewer on iPad. You have to manually go looking for it by clicking the “new” button and then selecting it from within iCloud Drive. I wrote more precisely and clearly on this topic a few years back.

Things get murkier when you consider that iCloud Drive has two GarageBand folders. One for iOS and one for macOS. I get why they did this. Projects made on an iPad and shared with an iPhone are automatically saved to the iOS folder which makes that process less convoluted. And the same is true of two Macs working on the same project that was started on macOS. Mac projects have to do some prep work to get files ready for iOS so it is important to make the distinction. But since macOS is capable of this prep work, why can’t it happen automatically when the Mac version of a file is closed? And why, if iCloud is capable of syncing complex GarageBand projects, does the Mac version still try to save projects to a local folder called “GarageBand” that is stored within the “Music” folder by default? 

This process only gets more complicated with Logic thrown into the mix. Here is why…

Back to the Story

Ok, so I prepped my Logic file with four tracks to be worked on from an iPad and it saved it as a GarageBand project and placed it into the “iOS GarageBand” folder within my iCloud Drive. Now I go to my iPad and boot up GarageBand. Hooray! The file is already waiting for me in the file browser when I launch the app. I tap on it, and it opens, reliably! Except my two audio files have been compressed into one track. I can understand this because audio tracks take up far less processing power when they are collapsed. But what if the audio part is what I wanted to edit on my iPad? Shouldn’t this be an option when I prepare the file for GarageBand? The iPad version can definetely handle more than one audio track at a time.

Next, I fool around with this project on iPad for a bit, adding audio effects to the vocal track I recorded. In this case, I am adding the effect that makes the voice sound like a monster and the audio track is just me saying “YAAAAAAAAASSSSS” over a funk beat. So my wife is now rolling her eyes from the couch. 

This is the only edit I make, because again, I am trying to keep this simple. I go back to my Mac and find the “GarageBand iOS” folder. Certainly, I can open this file right back up in Logic, right? Wrong. I double click the file and it opens in GarageBand. Fair enough, but wait, now GarageBand wants me to save the file to another location because it has to reformat it for the Mac. So I have to create a duplicate copy elsewhere? Doesn’t that sort of defeat the point of this new feature? Ok, fine. I click “Save As…” Where does GarageBand want to save the new version? The “GarageBand” folder within my “Music” folder. Seriously? Not even the “macOS GarageBand” folder in my iCloud Drive? Ok, I get it. Most users have only 5GB of iCloud space. Apple is making the right decision here. So now I have two versions and have already interacted with four different folders just to manage this one file. 

1. The Logic file was originally stored in the “Logic” folder from within my “Music” folder.

2. The “macOS GarageBand” that I saved the GarageBand version of that Logic file to.

3. The “iOS GarageBand” folder that I had to send the iOS version of the file to.

4. The local “GarageBand” folder that I am now being prompted to save my GarageBand for Mac file within.

“Sigh.” Am I done yet? Nope, because I have to open the local copy and prepare it to go back to Logic, which then offers me to save a third copy of the file. Where? In my local “Logic” folder, also located in the “Music” folder… Are you keeping up? My original Logic file was created in that folder, so now I have four copies.

I am not really sure what I expected. If GarageBand and Logic can do all of this heavy lifting, it seems some of the file management stuff could be automated. My dream scenario would have been that I could save the Logic file right to the iCloud Drive from the Mac, open it from the same location on iOS (using GarageBand) and then just seamlessly go back and fourth between the two, but who am I kidding. I guess we just aren’t there technologically. 

Conclusion

It seems like this feature is just laying the ground work for a future where either Logic exists on the iPad and can sync projects over iCloud (my iPad Pro is certainly powerful enough for it). Or for a feature much like I just described above, where the iOS never gets Logic but the two become closer and closer in feature parity until it doesn’t matter.

That second scenario is what happened with a lovely app Apple used to make called Aperture. Aperture was to iPhoto what Logic is to GarageBand. iPhoto and Aperture became so compatible that at one point, you could even direct both apps to edit the same photo library. Want to know what happened to Aperture? Apple discontinued it a few years back. Now we have the Photos app to replace both iPhoto and Aperture. And while I miss some of my pro photo editing tools from Aperture, photos are an area where I can get by with most of the features that are still left over in the Photos app. But Logic is NOT an application that I could get by with if it were ever dissolved into GarageBand. So lets hope Apple is not following down that same path…