Will someone please kill Soundtrack Pro?

2008-07-01 - Notes, blog - Trackback - Reply

During the final crunch to present my short film to my thesis’ jury, I once again made the dumb mistake to try to use Soundtrack Pro to sweeten up my films soundtrack. I couldn’t use a professional application like ProTools because a) ProTools is not available to me and b) there were some special effects shots I could only integrate at the very last moment. I couldn’t lock the timeline as I didn’t know the exact timing of said shots.

I tried using Soundtrack Pro 1.0 once before and quickly dismissed it as it couldn’t handle mono tracks. Now, after using Soundtrack Pro 2.0 on a new, freshly installed and fully updated eight-core Mac Pro, I’m convinced that Apple should kill Soundtrack Pro as soon as possible. Here’s what’s wrong with it:

  1. Stability: Soundtrack Pro crashes more than a drunken hooker on iceskates. Version 2.0 is a little better than 1.0, which means that it might stay up for 15 minutes instead of 5 minutes. This is unacceptable for a pro application.
  2. Usability: The default interface is unusable. You can’t view more than a single audio track on a 1440×900 screen and Soundtrack Pro doesn’t know about dual screens. You can tear off most the various tabs, but doing so causes crashes and unhandled exceptions. I got something like “NSCacheImage: invalid image” when tearing of the meters and other unassorted “NSRangeException: invalid range”-exceptions when tearing of the effects tab, inspector and browser. Most of the time Soundtrack Pro just plain crashes though.
  3. Functionality: One of version 2.0s big talking points is the Conform feature. This should make it possible to pull a Final Cut Pro sequence into a Soundtrack Pro project and keep working on both of them in parallel. You’re supposed to send new versions of the Final Cut Pro sequence to Soundtrack Pro and then use Conform projects in Soundtrack Pro to merge updates in Soundtrack Pro and Final Cut Pro into a new Soundtrack Pro project. Soundtrack Pro does the merge for you and gives you a list of changes to approve.

    It sounds nice in theory but I’m convinced no one has ever used it for anything besides a sales demo. I sent my 16-track FCP sequence to Soundtrack Pro and connected the top 4 audio tracks to a bus with some common effects. Next, I changed the volume of one audio clip in Final Cut Pro and sent the sequence to Soundtrack Pro again. Conform projects yielded 200 changes to approve: every single clip on tracks 1-4 (the ones with the bus) was changed according to Soundtrack Pro. I dutily approved every single change and send the result back to Final Cut Pro by using export mixdown with a send-to-Final Cut Pro applescript, as prescribed in the manual. This time, I did nothing in Final Cut Pro but sending the result immediately back to Soundtrack Pro. You might have guessed: I had to approve all 200 clips on tracks 1-4 again.

    The problem is that Soundtrack Pro doesn’t keep track of changes and approvals and cannot send enough metadata back to Final Cut Pro to be usefull. Not keeping any history is fatal for any revision control system, and after all this is that’s exactly what conform wants to be or should be. Worse of all, the approval button is a phony: even the manual tells you that the approval button does nothing but hide “reviewed” changes from the list.

    On top of this, the interface isn’t exactly helpfull: there’s no distinction between changes coming from Soundtrack Pro or Final Cut Pro, and approving 200 changes in a list box with a height of about 7 rows isn’t really helpfull either. You can tear off the tab but then you’re straight into point number 2 hell. You won’t be surprised that Soundtrack Pro isn’t very smart too: moving all clips 2 seconds to the right to make more room for my opening titles marked all audio clips as changed in Soundtrack Pro.

  4. Performance: Somehow Soundtrack Pro (and DVD Studio Pro and Motion and Livetype) feel way more sluggish than Final Cut Pro. I guess this is some kind of Cocoa versus Carbon thing (and I honestly fear the moment Final Cut Pro moves over to the Cocoa camp), but I can live with it on a new Mac Pro. What I don’t get is that I can play 720p25 HDV material with 32 audio tracks over a PAL DV firewire interface in Final Cut Pro without a hiccup, but somehow Soundtrack Pro cannot. It immediately starts complaining about a disk being too slow whenever I enable external video monitoring. (I don’t have to tell that I had problems displaying the video in a standalone — teared off — window too…)
  5. Wrong paradigm: This will mostly likely irk professional audio mixers/editors, but I feel severely handicapped by Soundtrack Pro’s track-based approach. A track-based audio application makes sense in musical environment where you have a limited number of instruments who have a quasi constant presence, but it doesn’t make sense in short movie which might have about 30 scenes with widely different sound characteristics. In this movie, I used 4 tracks for on-location sound (overlapping dialogue, live details) + 2 tracks for room tone. On top of that, I had 4 tracks for extra sounds: these might be dialogue overdubs, foley or precanned sounds from Soundtrack Pro’s library. I also had 4 music tracks.

    Each of the point sounds, ADR, or sound effects might need widely different EQ-ing and reverbation to match the live sound of the scene, and each scene might need widely different compressor and limiter settings. Since Soundtrack Pro only allows me to attach effects to tracks instead of clips (*), I could end up with as much as 10 different plugins on a given track where most of the time only one or two would be active. Or I could put all audio tracks of a given scene on its own tracks, but then I would end up with about 30 * 14 = 420 tracks…

    * I know I can apply individual effects to clips by editing them in Soundtrack Pro’s wave editor, but this is hardly a usefull approach: you cannot see which effects are applied to which clips, nor can you easily copy wave editor effects.

Anyway, here’s my suggestion to Apple:

  1. Kill Soundtrack Pro. Seriously.
  2. Take the Wave Editor part of Soundtrack Pro and put it in a standalone application. The analysis function (click and pops, hum) and noise reduction are pretty nice, and the way you can send individual clips from Final Cut Pro to Soundtrack Pro’s Wave editor is pretty nice too. Perhaps there might be a professional audio mixer who’s glad to have humless clips too (although I suspect most like to have unaltered audio…)
  3. Leave the bad loops and precut music to Garageband.
  4. Make all of Soundtrack Pro’s plugins real Audio Units, usable in Final Cut Pro. This would solve most of my audio troubles with Final Cut Pro (no decent EQ, no decent reverbs) and I would be able to work in a familiar and usable interface. Really, copy and paste attributes + timeline gang sync is all I long for. Busses or submixes might be nice, but I could live without it: I don’t need professional “professional audio”, I need confirmation whether a cut is working or not, whether an off screen sound works or not, whether I might need more room tone or foley,… Being able to shape the sound to a certain degree is integral to this process.

    For me, the biggest strength of Final Cut Pro is the anything anytime spirit: no modes, free form editing, try whether it sticks. I don’t see why audio editing should be any different, and better tools in Final Cut Pro would make the conform thing unnecessary.

  5. Have top notch OMF exports from Final Cut Pro and really good integration with Logic in whatever form. I understand that none of my fancy audio effects might survive the trip to Protools, but then again my professional audio mixer might have way better effects. Perhaps a way to export the same OMF with and without audio effects, or even an OMF with double tracks: one clean, one processed. (I don’t have any experience with OMF and professional audio editors yet).

Sincerely waiting for the kill,
Ben.

11 comments on “Will someone please kill Soundtrack Pro?”

  1. The Editblog » Ben hates Soundtrack Pro says on 2008-07-01 5:27:

    [...] reader Ben De Rydt has written an article called Will Someone Please Kill Soundtrack Pro? A title like that leaves no question as to what Ben thinks of the application. I don’t use [...]

  2. canelson says on 2008-07-01 6:20:

    I’m sorry for reading this post with all this problems, but it’s useful because I think its good to let people know about applications pros and cons.
    Apple has an excellent marketing team and that’s why so many people is moving to Final Cut Studio. I read on one of the latest POST Magazine: Final Cut Studio saves money when you buy it, Avid saves TIME when you are working, and time is money. (Avid hast their own problems too, like the old-school title tool or the way keyframes work on effects).

  3. Ben De Rydt says on 2008-07-01 12:33:

    Truth to be told, Final Cut Pro is pretty stable and can deal with audio quite fine. You can even use a control surface for basic audio levels and pans. It’s just that Soundtrack Pro promises so much more but can’t deliver in the end. The reason I wrote this article is that I spend one and half day fighting Soundtrack Pro and had to go back to Final Cut Pro in the end, but I sure missed the plugins.

  4. Jay Ryan says on 2008-07-01 16:54:

    I hate most bundled audio programs for video guys. My background for the most part was professional audio production and sound design. These programs stink. While Premier CS3 is a stellar video program, Soundbooth stinks. Like FCP, a stellar video program, STP stinks as well. I use separate, and much more user friend applications for my audio work. When coming from a pro audio background, using what comes bundled with our video apps leaves no question as to why a lot of audio even on “professional” work sounds like garbage.

  5. dave says on 2008-07-02 11:37:

    Apple should implement all STP PLUGIN SUPPORT, Visual metering, Editing in FCP.
    I like STP pretty good. It’s not bad. I notice very often that ‘video people’ are allergic to audio applications :P

  6. Joseph says on 2008-07-02 21:38:

    I use STP every weekend to record a podcast, and mos of the time it works fine, although I have given up on a few things. 1) trying to apply the noise removal on files longer than 15 minutes. 2) Multitrack recording. I love the idea, the amount of little bugs when trying to bring the multichannel files back to stereo is unbearable.

    On the whole, though, it works better than garageband, and it does do the job for small projects I finish myself.

    But It’s like Color, great potential, amazing when it works but requires a huge learning curve, and is riddled with bugs.

  7. zeke says on 2008-07-03 20:20:

    I use soundtrack pro on an almost daily basis. This week alone with probably 20 hours editing audio/video files. I heavily use the normalize, repair actions, and dynamic/eq plugins. I love this program, and it rarely crashes on me!! I was shocked to hear it’s crashing so much for you, and to hear of its sluggish performance… maybe it’s time for you to reinstall.

  8. Make Film Work » Timid Icecube - A Linked List says on 2008-07-11 3:30:

    [...] it’s fantastic production-related content. On a recent post Scott linked to a post by a very frustrated filmmaker trying to work with Soundtrack Pro for audio mixing. He lists his grievances and calls for [...]

  9. Stu Mannion says on 2008-08-13 7:14:

    You are so right. Kill STP and put better effects and much more realtime power into the audio editing in FCP! I really wanted to use STP on a short film but it was terrible in so many ways.

    Even Logic needs a bunch of interface improvements. Is there anything on the Mac as easy and powerful for audio editing as Vegas?

  10. Swanic says on 2008-09-14 6:13:

    Soundtrack Pro 1 and 2.0 both SUCK. The program is all marketing hype. I have worked with simple FREE programs that come from Sony turntables that have more functionality than this program. Talk about the learning curve too. It takes months to use the program even on a basic level. You would think a function like TEMPO would be a given for such a “Pro”gram. Forget it, TEMPO doesn’t exist. And Don’t tell me look at the Master track. We “pro”s have already tried it. I even tried converting my files to Core CAF format and thought I was in the bag. Wrong! You use Apple Loops and get your tempo right wear you want it, and think great, I’m all set to go. Drop the file into STP and I’ve heard kids shows with better chipmunks than the crap that comes out of STP. I have both FCS and STP and am begging for a better solution. Half the work I thought I could do on the MBP went back to a PC.

    Of yes, we all love the Humm and “Click Pop” crap. Spend fifteen minutes “removing” the clicks” on a 5 minute audio file. For pete’s sake, the MBP is an Intel Core 2 Duo 2GHZ with 2GB ram. How much more power does it need to “read” a wave file. Even my 386 DX 33 with a Roland ISA sound card had better response.

    Anyone and I mean anyone who says they use STP and love it, are using free copies from an academic institution.

    From a frustrated user waiting like everyone else to be sold on the next miracle in future technology, I throw my hands up in vain.

  11. timeoutofmind says on 2008-10-05 20:21:

    if you need a hammer to beat stp to a pulp, i’m on my way to home depot.

    what a hunk of crap this is ….. i just lost four hours of work, because it decided to crash towards the end of an hour long audio file … after about 200 edits.

    all gone. i’m getting ready to restart, but i’m delirious with rage.

Leave a reply

XHTML: Allowed tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>