Cinema Tools 4.0.1 Crashing in Lion 10.7.1

Question

Cinema Tools 4.0.1 Crashing in Lion 10.7.1

Hi all:

I'm not sure who else may be having problems, but I cannot get my Cinema Tools 4.0.1 to open in Lion 10.7.1. It continues to crash every time I click on the software program to open and launch. I understand there are some compatibility issues regarding Final Cut Studio 2 running in Lion 10.7, however I am able to open the rest of the FCS 2 suite without any problems (Final Cut Pro 6.0.6, Motion 3.0.2, Compressor 3.0.5, Color 1.0.4, DVD Studio Pro 4.2.1, LiveType 2.1.3, Soundtrack Pro 2.0.2). All these programs, except for Cinema Tools 4.0.1, work just fine so far in Lion 10.7.1.

Has anyone else had any problems trying to open and work Cinema Tools in Lion? I've seen a few threads in the internet already about users having similar problems, however I haven't seen any solutions. Perhaps somebody may have a solution or work-around to get the program functioning in Lion.

Thank you

iMac, Mac OS X (10.7), 2.4 GHz Intel Core 2 Duo

Posted on Sep 7, 2011 11:02 AM

Reply

Answer 1

aviel740

Level 1

0 points

Sep 9, 2011 3:20 PM in response to Madridfanatic

I have the same exact problem and cant figure out how to fix it and its really ******* me off because every time i want a slowmo clip, i have to open up after effects and do it which takes like 5 times longer.

Reply

Answer 2

Nick Holmes

Level 7

30,018 points

Sep 9, 2011 3:38 PM in response to Madridfanatic

Have you tried using Disk Utility to repair permissions on the system drive?

I know it gets posted as a catch all, but it can sometimes help.

If that does not help, post the Crash Log for CT.

Note: the Crash Log will contain a lot of info. The useful bit is from the beginning up to "Thread (number) crashed" and then the section with details of the crashed thread. No need to post the entire thing.

Reply

Answer 3

Sep 12, 2011 12:52 AM in response to Nick Holmes

Here is my particular crash log:

Process: Cinema Tools [529]

Path: /Applications/Cinema Tools.app/Contents/MacOS/Cinema Tools

Identifier: com.apple.CinemaTools

Version: 4.0.1 (4.0.1)

Build Info: CinemaToolsApp-710301148~9

Code Type: X86 (Native)

Parent Process: launchd [126]

Date/Time: 2011-09-12 00:49:45.527 -0700

OS Version: Mac OS X 10.7.1 (11B26)

Report Version: 9

Interval Since Last Report: 406799 sec

Crashes Since Last Report: 1

Per-App Crashes Since Last Report: 1

Anonymous UUID: BB45EB0C-3E9E-4032-B9B1-57CDCC6166F4

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGBUS)

Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000084

VM Regions Near 0x84:

--> __PAGEZERO 0000000000000000-0000000000001000 [ 4K] ---/--- SM=NUL /Applications/Cinema Tools.app/Contents/MacOS/Cinema Tools

__TEXT 0000000000001000-0000000000148000 [ 1308K] r-x/rwx SM=COW /Applications/Cinema Tools.app/Contents/MacOS/Cinema Tools

Application Specific Information:

objc_msgSend() selector name: retain

/System/Library/PrivateFrameworks/ProKit.framework/Versions/A/ProKit

objc[529]: garbage collection is OFF

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0 libobjc.A.dylib 0x957b5d47 objc_msgSend + 23

1 com.apple.CoreFoundation 0x9364f868 CFRetain + 136

2 com.apple.CoreFoundation 0x9369db7d +[__NSArrayI __new::] + 189

3 com.apple.CoreFoundation 0x9369da42 -[__NSPlaceholderArray initWithObjects:count:] + 530

4 com.apple.CoreFoundation 0x9368d0c3 CFArrayCreate + 195

5 com.apple.CinemaTools 0x00008fcf 0x1000 + 32719

6 com.apple.prokit 0x003ac517 _DoProSplashWithPath + 151

7 com.apple.prokit 0x003ac5ef DoProSplash + 143

8 com.apple.prokit 0x0021d66a _EarlySplash + 18

9 dyld 0x8fef515b ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 251

10 dyld 0x8fef4cc0 ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) + 64

11 dyld 0x8fef2220 ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) + 256

12 dyld 0x8fef21b6 ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) + 150

13 dyld 0x8fef31c0 ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) + 62

14 dyld 0x8fee7656 dyld::initializeMainExecutable() + 214

15 dyld 0x8feebef2 dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**) + 2238

16 dyld 0x8fee52ef dyldbootstrap::start(macho_header const*, int, char const**, long, macho_header const*) + 637

17 dyld 0x8fee5063 _dyld_start + 51

Thread 1:: Dispatch queue: com.apple.libdispatch-manager

0 libsystem_kernel.dylib 0x97b8a90a kevent + 10

1 libdispatch.dylib 0x93c39ccc _dispatch_mgr_invoke + 969

2 libdispatch.dylib 0x93c3871b _dispatch_mgr_thread + 53

Thread 2:

0 libsystem_kernel.dylib 0x97b8a02e __workq_kernreturn + 10

1 libsystem_c.dylib 0x97d5bccf _pthread_wqthread + 773

2 libsystem_c.dylib 0x97d5d6fe start_wqthread + 30

Thread 3:

0 libsystem_kernel.dylib 0x97b8a02e __workq_kernreturn + 10

1 libsystem_c.dylib 0x97d5bccf _pthread_wqthread + 773

2 libsystem_c.dylib 0x97d5d6fe start_wqthread + 30

Thread 0 crashed with X86 Thread State (32-bit):

eax: 0x00148014 ebx: 0x00148014 ecx: 0x95593d30 edx: 0x00000064

edi: 0x00148014 esi: 0x9364f7ed ebp: 0xbfffeae8 esp: 0xbfffeac8

ss: 0x00000023 efl: 0x00010206 eip: 0x957b5d47 cs: 0x0000001b

ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f

cr2: 0x00000084

Logical CPU: 0

Reply

Answer 4

Nick Holmes

Level 7

30,018 points

Sep 12, 2011 12:58 AM in response to Madridfanatic

ProKit Framework

This crash seems to have been caused by the ProKit framework. A common cause for this crash is a mismatched framework version.

If you upgraded to Snow Leopard from Leopard, you may have still have the Leopard pro user interface elements installed instead of the Snow Leopard ones. If this is the case, you will need to either update ProKit (if an update is available) or reinstall Final Cut Pro from scratch.

Suggested Actions

Update Final Cut Studio and ProKit.
Remove Final Cut Studio and reinstall.

Relevant Line

6 com.apple.prokit 0x003ac517 _DoProSplashWithPath + 151

Report generated by Crash Analyzer in Pro Maintenance Tools

Reply

Answer 5

Sep 12, 2011 1:04 AM in response to Nick Holmes

Actually, the Final Cut Studio 2 suiete was working just fine under Snow Leopard. Unfortunatey, it is when I updated to Lion 10.7. As a result, I cannot uninstall and reinstall FCS 2 without having to uninstall Lion 10.7 and reinstalling Snow Leopard again, as Rosetta is no longer supported in Lion (and as such FCS 2 installs using Rosetta).

I've already performed a System Update for ProKit, and installed whichever was the latest patch. As I mentioned previously, the rest of my programs start and load just fine; it is only Cinema Tools that crashes. I will have to try the Disk Utility as another option to see if that may fix my issue ...

Reply

Answer 6

wiatt

Level 1

0 points

Sep 22, 2011 10:17 AM in response to Madridfanatic

Any luck? Same issue here.

Reply

Answer 7

Sep 22, 2011 3:16 PM in response to Madridfanatic

It happens whenever you update your OS. You need to update ProKit.

Also, Final Cut Studio 2 is not supported on Lion.

Reply

Answer 8

Sep 22, 2011 8:03 PM in response to Jon Chappell

No such luck. I tried Verify and Repair Disk Permissions, but that did not help. Alas Cinema Tools does not work on my Lion iMac. I did update the ProKit when in Snow Leapord, but upgrading to Lion I do not see any new ProKit update you speak of. I click on Software Update, but no new ProKit update shows up. Is there somewhere I can download the ProKit Update? Otherwise, my Cinema Tools does not work in Lion.

The rest of the FCS 2 Suite works just fine, except for Cinema Tools 😢

Reply

Answer 9

Nov 4, 2011 9:15 AM in response to Madridfanatic

I have exactly the same issue. I migrated from OSX Snow leopard to lion and all my programs and FS2 run smoothly. (There is an issue in installing FS2, but not in running). Only Cinema Tools crashes. I also do not see ProKit, so i downloaded Prokit 7.0 and when I try to install it says: a newer version of this software is already installed.

For the moment I´ve ran outof ideas. It seems not to be supported??

regards

Sunshine

Reply

Answer 10

Sordal

Level 1

0 points

Nov 28, 2011 8:47 AM in response to Madridfanatic

Hello there

I have the exact same problem as the thread starter, but i got the FCS 3 (Guessing cinema tools might be the same version). I scoutet the internet for solutions but i cant seem to find any fix. Has anyone heard anything from apple, will there be a update anytime? IS there a fix? I'm really not keen on reinstalling the last osx..

Reply

Answer 11

wiatt

Level 1

0 points

Dec 2, 2011 10:42 AM in response to Sordal

Talked with a friend that works at Apple he does not think there will be an update ever. FCS 3 Cinema Tools (4.0.1) does not work with Lion. Only solution is to get Cinema Tools 4.5.1 or go back to snow leopard.

Reply

Answer 12

Apr 2, 2012 1:37 AM in response to wiatt

That just seems so absurd! I have used cinema tools to conform 60fps clips to 24 for agggeeess and now there is no simple replacement?!

I cant seem to find anyone with a more reasonable fix than go back to leopard....

N

Reply

Answer 13

Studio X

Level 7

27,229 points

Apr 2, 2012 7:06 AM in response to nickdamoose

This is all part of Apple's grand committment to a consumer/web based video future.

Unless you work in film, you don't need Cinema Tools. Compressor will do everything you need with video to video conversions.

x

Reply

Answer 14

wiatt

Level 1

0 points

Apr 2, 2012 8:03 AM in response to nickdamoose

The only option I know of is to get Cinema Tools 4.5.1. it works in Lion (for now).

Reply

Answer 15

tristanw

Level 1

4 points

Apr 18, 2012 8:03 AM in response to Madridfanatic

The best alternative for conform, that we've found, is using MB Grinder during transcode. This is only for fcp7 workflow as premiere pro and fcp x can conform on the timeline. It lacks a 30p or 29.97 option but does the trick of 30p > 24p and 60p > 24p.

Reply