Subscribe to
NSLog(); Header Image

Soundtrack Pro 2.0 – Waiting for Final Cut Studio 3

So, for some reason, Soundtrack Pro has decided to crap itself. Every time I click on a track, it crashes. 100% of the time. I turned off the "sync with hardware" checkbox, I've trashed the prefs, I've even re-installed.

I was going to upgrade ((I have "Final Cut Pro 5.1 Studio", so I'm eligible for the $499 upgrade to Final Cut Studio 2, though you wouldn't know it looking at Apple's site.)), but the tea leaves say "wait" because the ship time is 1-2 weeks, and I have a feeling we're going to see Final Cut Studio 3 in a little while. I can wait - I just won't record any podcasts for awhile.

Crash Log
Process: Soundtrack Pro [16750]
Path: /Applications/Soundtrack Pro
Version: 1.1 (1.1)
Build Info: SoundtrackProProject-2920000~4
Code Type: X86 (Native)
Parent Process: launchd [215]

Interval Since Last Report: 1992 sec
Crashes Since Last Report: 8
Per-App Interval Since Last Report: 314 sec
Per-App Crashes Since Last Report: 7

Date/Time: 2009-07-22 11:24:08.286 -0400
OS Version: Mac OS X 10.5.7 (9J61)
Report Version: 6
Anonymous UUID: AFC663EC-FB27-4C92-B375-B9C524C07203

Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000bf7fffcc
Crashed Thread: 0

Thread 0 Crashed:
0 libSystem.B.dylib 0x016a1310 tiny_malloc_from_free_list + 22
1 libSystem.B.dylib 0x0169a1cd szone_malloc + 180
2 libSystem.B.dylib 0x0169a0d8 malloc_zone_malloc + 81
3 0x00d613d1 _CFRuntimeCreateInstance + 145
4 0x00d791b1 __CFStringCreateImmutableFunnel3 + 737
5 0x00d7a2ce CFStringCreateWithBytes + 94
6 0x02830d2d -[NSPlaceholderString initWithBytes:length:encoding:] + 61

Console Messages
7/22/09 11:23:39 am Soundtrack Pro[16750] *** _NSAutoreleaseNoPool(): Object 0x6925850 of class NSThread autoreleased with no pool in place - just leaking
Stack: (0x2905f0f 0x2812442 0x28181b4 0x39c603 0x371fbc 0xcf028 0xcce64 0x8fe12f36 0x8fe0e7e3 0x8fe0e8c9 0x8fe04102 0x8fe07bcf 0x8fe01872 0x8fe01037)
7/22/09 11:24:10 am[215] ([0x0-0x75b75b][16750]) Exited abnormally: Segmentation fault

5 Responses to "Soundtrack Pro 2.0 – Waiting for Final Cut Studio 3"

  1. This crash started happening to me too, just yesterday. Extremely annoying. It took me twice as long to edit a podcast because I had to work around the crash by right-clicking or using keyboard shortcuts.

    I hate to say it, but Soundtrack Pro is one of the most unstable pieces of software I've ever used. At that price, it should be rock solid.

    If you find a fix for this crash I'd love to hear it.

  2. [quote comment="54812"]This crash started happening to me too, just yesterday. Extremely annoying. It took me twice as long to edit a podcast because I had to work around the crash by right-clicking or using keyboard shortcuts.[/quote]

    Interesting. What software updates have been released since last Wednesday (July 15 is the last time I used Soundtrack Pro)? I know there have been a few - iTunes for one.

    Also, this is interesting:

    9	0x0687053e indexFromPoint + 4691
    10	0x06870580 indexFromPoint + 4757
    11	0x06870580 indexFromPoint + 4757
    12	0x06870580 indexFromPoint + 4757
    13	0x06870580 indexFromPoint + 4757
    507	0x06870580 indexFromPoint + 4757
    508	0x06870580 indexFromPoint + 4757
    509	0x06870580 indexFromPoint + 4757
    510	0x06870580 indexFromPoint + 4757
    511	0x06870580 indexFromPoint + 4757

    You're seeing the same?

  3. Wow, good call on the upgrade - new version today.

    Now if they could just get around to refreshing Aperture... 😆

  4. Erik, I get the same indexFromPoint as well. I've submitted this crash about a dozen times to Apple, hopefully it starts showing up on their radar.

    Both the new Logic and Final Cut Studio look nice, but of course I'd rather this crash just go away. 🙂 It's been reported in the Apple discussions forum as well.

  5. Well, Apple's gone and released a ProKit update which, for me, seems to fix the problem.

    Plus, Final Cut Studio 3 will arrive later today, so I'll be learning Soundtrack Pro 3 soon.