Re: FCPX, Motion, Compressor Updated, New FxPlug SDK Available
Re: FCPX, Motion, Compressor Updated, New FxPlug SDK Available
- Subject: Re: FCPX, Motion, Compressor Updated, New FxPlug SDK Available
- From: Jon Chappell <email@hidden>
- Date: Wed, 24 Oct 2012 11:57:16 -0700
"However, I believe that TAL apps
will detect if they crashed the last time they tried to restore open
documents, and offer to launch "clean" on the subsequent launch."
Not always. I've found it to be unreliable. You often have to let it crash several times before it will prompt and it will sometimes not prompt at all. I suspect there is a narrow window in the loading cycle in which it has to crash before it will be triggered.
Regards,
Jon Chappell.
CEO, Digital Rebellion LLC.
http://www.digitalrebellion.comOn Wed, Oct 24, 2012 at 11:36 AM, Paul Schneider
<email@hidden> wrote:
On a side note: has anyone on the FCP team thought that perhaps auto-loading the last project is a bad idea in some cases and that the user should at least have an option-click start option in order to choose which project to load upon starting? I can't tell you how many hours of time-suck this has been for us in tech support time.
The convention on OS X is to
a) restore any previously open documents and windows on app startup, unless the "Close windows when quitting an application" checkbox is set in the General System Preferences
b) do the opposite of the preference when the shift key is held down during app startup
We should probably follow suit. I believe that the main reason we aren't currently supporting this is because we still support Snow Leopard.
With the focus on Transparent Application Lifecycle over the past few years, Mac apps are expected to restore all aspects of their previous session when they are relaunched. A design which goes against this is not likely to be successful. However, I believe that TAL apps will detect if they crashed the last time they tried to restore open documents, and offer to launch "clean" on the subsequent launch.
Having said all that, this suggestion seems like it treats the symptom but not the disease. Plugins and apps should handle corrupt or unexpected file data gracefully. Ideally we would be able to separate plugin and app address space so that a crash in one didn't take down the other. But I do understand the desire to solve a customer support issue that is occurring today.
On Oct 24, 2012, at 9:50 AM, Darrin Cardani <
email@hidden> wrote:
You're welcome! I'll pass your feedback on to the FCP team. That does sound like a great idea!
Darrin
On Oct 24, 2012, at 9:26 AM, Peter Litwinowicz <
email@hidden> wrote:
various minor bug fixes.
Major bug fixed: trying to accidentally access frames passed either edge of the clip in time no longer causes FCP to crash (as far as I can tell in my limited hours of testing). Of course once an offending plugin is applied, FCP saves the state, then goes to render, then crashes (in 10.0.5). Upon startup, the NEW state of the FCP project in 10.0.5 is loaded because it was saved just after application of the plugin, then goes to render after loading… crashing again. The user then can't use FCP X because of this infinite loop without knowing where his or her projects are stored and deleting the offending project (which may have had days or weeks of work within it).
So this is good news. Thanks Darrin!
On a side note: has anyone on the FCP team thought that perhaps auto-loading the last project is a bad idea in some cases and that the user should at least have an option-click start option in order to choose which project to load upon starting? I can't tell you how many hours of time-suck this has been for us in tech support time.
Pete
From: Darrin Cardani <
email@hidden>
Date: Tuesday, October 23, 2012 2:08 PM
To: "
email@hidden ProApps" <
email@hidden>
Subject: FCPX, Motion, Compressor Updated, New FxPlug SDK Available
Just a heads-up that Final Cut Pro X, Motion, and Compressor have been updated. You can download the latest FxPlug SDK from <
http://connect.apple.com>. The SDK contains the additions I posted here after the last release for making your OSCs work with the retina display hardware, and various minor bug fixes.
Enjoy!
Darrin
_______________________________________________
Do not post admin requests to the list. They will be ignored.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
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
- Prev by Date:
Re: FCPX, Motion, Compressor Updated, New FxPlug SDK Available
- Next by Date:
Re: FCPX, Motion, Compressor Updated, New FxPlug SDK Available
- Previous by thread:
Re: FCPX, Motion, Compressor Updated, New FxPlug SDK Available
- Next by thread:
Re: FCPX, Motion, Compressor Updated, New FxPlug SDK Available
- Index(es):