If you edit dozens of tracks every week as I do, the answer is a resounding YES!!! The program crashes often and at the most inopportune times.
Simply selecting a section of the audio file using the mouse can cause the program to hang which can only be resolved by Force Quitting the application. Implementing the Noise Reduction or EQ filters can also cause system hangs.
While keyframing and editing with the multi-track editor works great, the Export function that’s accessible from the File menu has a bad programming code error that requires a workaround.
By default, the filename you enter into the Save As dialog box creates a folder that contains the exported track. The Export function automatically appends an .aif extension to the folder name you enter into the selection window, even if you delete the .aif extension manually.
From STP’s File menu, you will notice that you can’t drill down to the exported audio file contained inside the .aif folder.
That’s because Soundtrack Pro has been tricked into thinking that the export folder is an .aif file. The workaround is to open the exported file manually using the Finder.
Another bug involves the saving of Soundtrack Pro project (.stap) files. If you select File>Save (or Command-S), Soundtrack Pro DOES NOT execute your command. That’s right, it ignores your keystrokes and doesn’t save any changes you’ve made to the file. As a result, when I’m working with Soundtrack Pro project files, I make sure I save a copy of the original at frequent intervals [NOTE: File>Save executes the desired result when working with .aif or .wav files].
In years past, I edited audio files using Sound Studio v2 and BIAS Peak DV. I found that BIAS Peak DV had a limited feature set while Sound Studio was also subject to system crashes and lack of support from the developer. I like the fact that Soundtrack Pro is integrated with the rest of Final Cut Studio. I just wish it didn’t crash as often as it does.