Problems with Feeder, QuickTime 7.2 and Panther
There seem to be problems with Feeder and QuickTime 7.2 on Panther (Mac OS X 10.3) systems. I’ve reported the problem to Apple and will hopefully find out more soon. Feeder will fail to launch and the following messages will be shown in the console log:
dyld: /Applications/Feeder.app/Contents/MacOS/Feeder Undefined symbols: QTKit undefined reference to _OSAtomicCompareAndSwap32 expected to be defined in /usr/lib/libSystem.B.dylib QTKit undefined reference to .objc_class_name_NSAffineTransform expected to be defined in Foundation QTKit undefined reference to .objc_class_name_NSCIImageRep expected to be defined in AppKit QTKit undefined reference to _OSSpinLockLock expected to be defined in /usr/lib/libSystem.B.dylib QTKit undefined reference to _OSSpinLockUnlock expected to be defined in /usr/lib/libSystem.B.dylib QTKit undefined reference to _OSAtomicAdd32 expected to be defined in /usr/lib/libSystem.B.dylib QTKit undefined reference to _ApplicationTypeGet expected to be defined in Carbon QTKit undefined reference to _OSAtomicCompareAndSwap32Barrier expected to be defined in /usr/lib/libSystem.B.dylib CoreMediaPrivate undefined reference to _OSAtomicAdd32 expected to be defined in /usr/lib/libSystem.B.dylib CoreMediaPrivate undefined/usr/lib/libSystem.B.dylib CoreMediaPrivate undefined reference to _OSAtomicCompareAndSwap32 expected to be defined in /usr/lib/libSystem.B.dylib CoreMediaPrivate undefined reference to _OSAtomicOr32 expected to be defined in /usr/lib/libSystem.B.dylib CoreMediaPrivate undefined reference to _OSAtomicXor32 expected to be defined in /usr/lib/libSystem.B.dylib CoreMediaPrivate undefined reference to _OSMemoryBarrier expected to be defined in /usr/lib/libSystem.B.dylib CoreMediaPrivate undefined reference to _vm_purgable_control expected to be defined in /usr/lib/libSystem.B.dylib
For now, reverting to QuickTime 7.1.6 would presumably fix the problem but would be quite a pain. So, I would advise any Feeder on Panther users (yes, all three four of you) who read this to not install QuickTime 7.2 if you want to use Feeder anytime soon.
Update, July 18: Apple has acknowledged that this is a known issue under investigation.
July 17th, 2007 at 11:36 pm
I have a problem with final cut pro after upgrading to quicktime 7.2 . There’s somehting very bad in that code!
July 31st, 2007 at 4:13 pm
My Feeder (registered + purchased) no longer launches under OSX 10.3.9 .
Reinvented, is my purchase for naught? Can anyone straighten this out?
Thanks.
July 31st, 2007 at 10:40 pm
Unfortunately, only Apple can fix it – but as they have acknowledged the problem, I would expect a fix to be included in an update to QuickTime soon.
August 3rd, 2007 at 2:41 pm
I’m not blaming you, but you’re doing nothing to fix the problem, and at the same time making fun of 4 people with the problem. How about a refund?
August 4th, 2007 at 2:29 am
I have done everything I can by researching and reporting the problem to Apple the moment I became aware of it. They have confirmed that this is their bug, to be addressed by them. I am quite serious when I say how many people are affected by this.
Workarounds are:
– Downgrade to QuickTime 7.1.6. I have no instructions on how to do this, you can always seek help in the QuickTime support forums: http://discussions.apple.com/forum.jspa?forumID=932
– Upgrade to Mac OS X 10.4
If you want a refund, bearing in mind that this will be fixed in a QuickTime update, you should write to support@reinventedsoftware.com to tell me your registration code or email address used to purchase Feeder, as I can’t find your details from the name or email used for your comment. Thanks.
August 7th, 2007 at 11:05 pm
Add me to the list of Panther users. We’re bound to OS 10.3.9 due to limitations on a soon to be replaced audio interface (Digi 001 which won’t support Tiger).
There appears to be no simple solution to the uninstall QT dilema and though I don’t hold you responsible in the least, a red flag would have save me (and my four good friends) a ton of grief.
For those others going thru the pain, visit the Apple discussions group mentioned above and know that your tears have company.
September 18th, 2007 at 3:41 pm
Hi! I just encountered the same problem recently in the application I’m developing. When I was looking for solution I found this discussion. That helped me to understand that I was not alone. %)
Now, I’ve localized the reason that caused QTKit to crash and fixed it. Maybe it’ll help you also. In my situation I had a framework linked to QTKit, that had an explicit initialization routine, as soon as I removed that routine (in my case I didn’t need it already) the all went well. I’ve the small example project, that demonstrates exactly the same behavour.
Regards,
Aleksandr
September 19th, 2007 at 4:01 am
Thanks.
My problem is that Feeder uses QTKit and is built as a 10.4 Universal application. When linking for 10.4 (which I have to do to make it a Universal binary) the version of QTKit linked is incompatible with 10.3.9, whereas it was compatible in all versions before QuickTime 7.2. Apple has acknowledged the bug – rdar://5338802.
And unfortunately I can’t produce a PPC-only version of Feeder linked against 10.3.9 without changing code and branching into two versions – the last time I tried, it was looking painful.
September 19th, 2007 at 11:46 am
I’m not sure if I get you right. But as far as I understand, you don’t need to link with 10.3.9 SDK to get app working on Panther, until you don’t use Tiger-only API. So using 10.4u SDK you can get UB that will work fine on PPC under 10.3.9 and Intel.
I’ve just build UB version of the app I’ve send to bugreport.apple.com as an example to the problem and got the same behavior: when I use Initialization routine in framework it crashes and when do not use – it runs fine.
October 24th, 2007 at 9:36 am
After downloading 10.3.9 and Q/T 7.2 I am unable to do any video editing importing or exporting using iMovie. So add me to the list.