December 2012 - Pro-apps-dev

Floating point param display
by Peter Litwinowicz 14 Dec '12

14 Dec '12

_______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Rogue upside down frames
by Paul Miller 14 Dec '12

14 Dec '12

On 12/14/2012 10:12 AM, Paul Miller wrote: On 12/6/2012 5:36 PM, Darrin Cardani wrote: It's currently still open. I believe we have a fix for it, but it didn't make it into this release. Any news on this? I have a customer who is being bitten by this a great deal. Is there a recommended work-around, either on the plugin or user side? _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com I just heard privately from another user that 10.0.7 is out and fixes the weird rectangle corruption problem (but the full-frame random corruption is still there). I passed that along to my customer - none of us knew there was a new version out (and this particular fix wasn't mentioned in the update notes in the App Store).

1 0

Re: Rogue upside down frames
by Paul Miller 14 Dec '12

14 Dec '12

On 12/6/2012 5:36 PM, Darrin Cardani wrote: It's currently still open. I believe we have a fix for it, but it didn't make it into this release. _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com Any news on this? I have a customer who is being bitten by this a great deal. Is there a recommended work-around, either on the plugin or user side?

1 0

Re: Rogue upside down frames
by Darrin Cardani 06 Dec '12

06 Dec '12

_______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Rogue upside down frames
by Martin Baker 06 Dec '12

06 Dec '12

_______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: FCPX flickering 1080P H.264 with CPU-only FXPlug?
by Darrin Cardani 04 Dec '12

04 Dec '12

We have some reports of it and are looking into the cause. Darrin On Dec 4, 2012, at 1:05 PM, Paul Miller <paul(a)fxtech.com> wrote: > I'm seeing some weird flickering on various machines, but different results (may depend on the speed of the machine - all MBPs so far) when rendering a sequence with a H.264 1080P clip (about 10s) and a software-only FxPlug applied. > > Throughout the rendered clip, randomly, there will be weird purple blocks - it looks like partially undecoded compressed frames. I can't reliably reproduce it on my machine but it's happening consistently on other, older machines. I've boiled down my effect to simply copy the input bitmap to the output bitmap and it's still happening. > > Any ideas? > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com > > This email sent to dcardani(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

FCPX flickering 1080P H.264 with CPU-only FXPlug?
by Paul Miller 04 Dec '12

04 Dec '12

Any ideas? _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com I'm seeing some weird flickering on various machines, but different results (may depend on the speed of the machine - all MBPs so far) when rendering a sequence with a H.264 1080P clip (about 10s) and a software-only FxPlug applied. Throughout the rendered clip, randomly, there will be weird purple blocks - it looks like partially undecoded compressed frames. I can't reliably reproduce it on my machine but it's happening consistently on other, older machines. I've boiled down my effect to simply copy the input bitmap to the output bitmap and it's still happening.

1 0

Re: Backwards compatibility
by Martin Baker 04 Dec '12

04 Dec '12

Thanks for the explanation Darrin. I think we'll stick with 10.0.6 minimum requirement after all. Martin www.digital-heaven.co.uk www.twitter.com/digitalheaven www.videospaceonline.com www.finalcutters.com ------------------------------------------------------ Digital Heaven Ltd is registered in England and Wales Company registration number: 3628396 Registered address: 55 Lynwood Drive, Worcester Park, Surrey KT4 7AE VAT registration number: GB 736 0989 03 On 4 Dec 2012, at 18:13, Darrin Cardani wrote: > Martin, > > In general when we rev the version number of the document, we have changed the file format. (Usually only slightly.) But that means that older versions of the app will not be able to understand the data in it properly. > > In this specific case, we did not change the file format in any way except for increasing the version number from 5.2 (I think?) to 5.5. The higher version number signals to FCPX to properly handle parameter supervision. In older versions of FCPX, parameter supervision in FxPlugs had some bugs, which meant you couldn't properly enable and disable or hide and show parameters on-the-fly. They would sometimes not update properly. We fixed this in 10.0.6, but several developers requested that we keep the old behavior for existing templates. We do that by checking the version number of the template. If it's < 5.5, we act in the old broken way. If it's >= 5.5, then we properly enable and disable parameters. > > So you can change the version number back to 5.2 (or whatever Alex mentioned in his email), and older versions of FCPX will be able to read it, but newer versions will continue to exhibit the bug with parameter supervision. If you keep it as 5.5, newer versions will work properly, but older versions won't be able to open the file. In all other cases, you should never change the version number of a template manually. > > Darrin > > On Dec 4, 2012, at 3:32 AM, Martin Baker <martin(a)digital-heaven.co.uk> wrote: > >> What's the deal with backwards compatibility with FxPlugs/Motion Templates and earlier FCPX releases? We have a generator product which has just started beta testing. The Motion template was created on Motion 5.0.5. >> >> All works fine on FCP 10.0.6 but one of the testers is on 10.0.5 and is reporting a red error screen when dragging the generator to the timeline, also no generator parameters are shown and "parsing error" is logged in Console. >> >> thanks >> >> Martin Baker >> www.digital-heaven.co.uk >> www.twitter.com/digitalheaven >> www.videospaceonline.com >> www.finalcutters.com >> ------------------------------------------------------ >> Digital Heaven Ltd is registered in England and Wales >> Company registration number: 3628396 >> Registered address: 55 Lynwood Drive, Worcester Park, Surrey KT4 7AE >> VAT registration number: GB 736 0989 03 >> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com >> >> This email sent to dcardani(a)apple.com > _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: changes in fcpxml 1.2
by Darrin Cardani 04 Dec '12

04 Dec '12

Thomas, Please file a bug about the documentation for this component. I know that some documents we use internally will have change markers on them. It might be possible to do the same for public documentation. (I don't know for sure, but it seems like it might be.) But without a bug, nobody will work on it, so please file one! Darrin On Dec 4, 2012, at 11:51 AM, Thomas - Mindtransplant <thomas(a)mindtransplant.com> wrote: > Hi all, > > I hope Apple reads this message too. > > It would be really nice for us developers to have some type of "Changes Log" which gives us a detailed description about the changes made in fcpxml 1.2. I´m aware of the Notes in the fcpxml 1.2 documentation but it´s tedious to scroll through the whole PDF to find these Notes (and further changes not mentioned in Notes). > By accident I noticed some new attributes here and there which mess up the parsing process in my app. I only came across these changes because some beta testers reported bugs about features behaving strange and in my opinion this is a "no-go" and much too late! > > Why is this so annoying? The review process in the Mac App Store currently takes 20+ days. 10 days passed since I´ve submitted an update (which makes my app 10.0.6 compatible) when a tester reported a bug that was related to the new "rateConform" attribute in the <timeMap> Node (not mentioned in any kind of Note but has it´s own paragraph). As a result I had to "developer-reject" my app, bugfix it, submit it to the Mac App Store and start from zero with waiting for getting reviewed in 20+ days. That´s a lot of time for the customers to wait for an update! > > Ok, some might say: rtfm. Well, I´ve completely read the docs for version 1.1. I have a basic understanding what´s going on. Do I have to read the docs from front to back again (40-50 pages) and compare it with the prior version just to make sure not having missed a new attribute or a new node? > > So please Apple, give us some type of changes log or some kind of overview from where we start and make our way to the detailed description in the docs. Thanks. > > > Thomas > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com > > This email sent to dcardani(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

changes in fcpxml 1.2
by Thomas - Mindtransplant 04 Dec '12

04 Dec '12

_______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0