Re: Final Cut 6 and 7 side-by-side?
Re: Final Cut 6 and 7 side-by-side?
- Subject: Re: Final Cut 6 and 7 side-by-side?
- From: Bruce Sharpe <email@hidden>
- Date: Sat, 1 Aug 2009 10:20:40 -0700
Thanks, Paul, moving the SmoothCam plugin took care of it. This will
be a big help.
The only glitch now is that whenever I switch between versions it goes
through the "Profiling for RT Extreme..." step each time. Is there
any way to bypass that?
Bruce
On Sat, Aug 1, 2009 at 8:05 AM, Paul Schneider<email@hidden> wrote:
>
> It's trying to load the SmoothCam plugin. If you don't need that particular
> plugin for your testing, you can move it aside. It's in
> /Library/Application Support/ProApps/Internal Plug-Ins/FxPlug
> The SmoothCam plugin relies on certain shared frameworks which may have
> changed between 6 and 7.
> Disclaimer: as others have noted, what you're trying to do is not officially
> supported by Apple.
>
> On Aug 1, 2009, at 12:57 AM, Bruce Sharpe wrote:
>
> Excerpt from the crash log:
>
> Exception Type: EXC_BAD_ACCESS (SIGSEGV)
> Exception Codes: KERN_INVALID_ADDRESS at 0x00000000295eb5e4
> Crashed Thread: 0
>
> Thread 0 Crashed:
> 0 ...lium.HDominantMotionTracker 0x23abc085 0x23ab8000 + 16517
> 1 com.apple.Helium 0x0ff55a51 HFCreateInstance + 457
> 2 com.apple.SmoothCamFxPlug 0x23a5c7bf getFrameProc(unsigned int,
> void*, char*, unsigned int) + 2283
> 3 ...uartzComposer.FxPlugWrapper 0x0d21ec12 0xd21c000 + 11282
> 4 com.apple.QuartzComposer 0x943c2115 +[GFNode(Private)
> newWithIdentifier:] + 99
> 5 com.apple.ProFX 0x00e941a6 -[PFXNodeManager
> nodeInstanceWithName:] + 74
> 6 com.apple.FinalCutPro 0x004f265c
> MakeEffectsDictForPatch(NSString*, KGFileRec*, long) + 234
> 7 com.apple.FinalCutPro 0x004f36f3
> AddQCPatchAsEffect(NSString*, long) + 41
> 8 com.apple.FinalCutPro 0x004f3850 AddQCPatches() + 266
> 9 com.apple.FinalCutPro 0x004f39a8 RegisterQCEffects + 60
> 10 com.apple.FinalCutPro 0x001bbbb5 KGPlaybackLibAction + 2817
> 11 com.apple.FinalCutPro 0x0023398c CallLibs(KGLibActionCode,
> unsigned char) + 346
> 12 com.apple.FinalCutPro 0x00233b27 KGFinishLibraries + 115
> 13 com.apple.FinalCutPro 0x00233c58 KGInit() + 164
> 14 com.apple.FinalCutPro 0x003ff6bf OpenApplication(AEDesc
> const*, AEDesc*, long) + 75
> 15 com.apple.AE 0x9677e648 aeDispatchAppleEvent(AEDesc
> const*, AEDesc*, unsigned long, unsigned char*) + 144
> 16 com.apple.AE 0x9677e57e
> dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 44
> 17 com.apple.AE 0x9677e425 aeProcessAppleEvent + 177
> 18 com.apple.HIToolbox 0x90383961 AEProcessAppleEvent + 38
> 19 com.apple.HIToolbox 0x903e1d06 AEProcessEvent + 160
> 20 com.apple.HIToolbox 0x903e1c57
> HIStdAppHandler::HandleEvent(OpaqueEventHandlerCallRef*, TCarbonEvent&) +
> 219
> 21 com.apple.HIToolbox 0x903def02
> TEventHandler::EventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*,
> void*) + 70
> 22 com.apple.HIToolbox 0x9035911d
> DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) +
> 1181
> 23 com.apple.HIToolbox 0x9035855b
> SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*,
> HandlerCallRec*) + 405
> 24 com.apple.HIToolbox 0x903583c0
> SendEventToEventTargetWithOptions + 58
> 25 com.apple.HIToolbox 0x90386d34
> ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*,
> void*) + 356
> 26 com.apple.HIToolbox 0x903594d6
> DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) +
> 2134
> 27 com.apple.HIToolbox 0x9035855b
> SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*,
> HandlerCallRec*) + 405
> 28 com.apple.HIToolbox 0x90374eac SendEventToEventTarget + 52
> 29 com.apple.HIToolbox 0x903e1a4c ToolboxEventDispatcher + 86
> 30 com.apple.HIToolbox 0x903de2a2 RunApplicationEventLoop +
> 222
> 31 com.apple.FinalCutPro 0x0014cece KGMainEvent(void*) + 46
> 32 com.apple.FinalCutPro 0x002aae53 main + 59
> 33 com.apple.FinalCutPro 0x00003122 _start + 216
> 34 com.apple.FinalCutPro 0x00003049 start + 41
>
> Bruce
>
> On Fri, Jul 31, 2009 at 10:53 PM, Patrick Sheffield
> <email@hidden> wrote:
>>
>> What's the crash log say?
>> Patrick Sheffield
>> Sheffield Softworks
>> On Jul 31, 2009, at 10:48 PM, Bruce Sharpe wrote:
>>
>> Copied my old version to a new name as suggested, then installed FCP 7. It
>> runs fine but the old one crashes on startup. Sigh... This is going to be a
>> huge pain.
>>
>> Anyone else have any success with installing them side by side?
>>
>> Bruce
>>
>> On Thu, Jul 23, 2009 at 3:33 PM, Darrin Cardani <email@hidden>
>> wrote:
>>>
>>> On Jul 23, 2009, at 2:37 PM, Bruce Sharpe wrote:
>>>
>>>> Can Final Cut Pro 6 and 7 be installed side by side on the same machine?
>>>> They don't have to run at the same time, but it would be helpful to have
>>>> both installed on the same machine in our QA lab for testing.
>>>
>>>
>>> We are moving in that direction. Starting with this release, it will
>>> probably work reasonably well, even though we aren't officially supporting
>>> it, yet. I think you'll need to do what Pete suggests and move the old one
>>> to a different name first, though. We're aware that users and developers
>>> want this functionality, but it wasn't a simple thing to do, which is why we
>>> aren't yet officially supporting it.
>>>
>>> Darrin
>>> --
>>> Darrin Cardani
>>> email@hidden
>>>
>>>
>>
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Pro-apps-dev mailing list (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>>
>> This email sent to email@hidden
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Pro-apps-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden