On Apr 30, 2013, at 10:01 AM, Paul Miller <paul@fxtech.com> wrote:
On 4/30/2013 11:56 AM, Darrin Cardani wrote:
On Apr 30, 2013, at 7:44 AM, Paul Miller <stelefx@gmail.com> wrote:
Is it possible to fall back automatically to the CPU path if something "goes wrong" when attempting to process the filter in GPU mode?
I tried returning NO from the renderOutput function, but it just put up an alarming screen saying it couldn't render, even though I had CPU mode enabled as well (I expected it to call renderOutput again in CPU mode).
If you can detect that your GPU render failed (and you are then returning "NO" from your -renderOutput: method), you can simply try again yourself instead of returning "NO", can't you? (That is, you can download the input from the card, process it, and upload it back to the card when done.) We assume that you've exhausted your available options if you return NO, hence the red screen saying that we couldn't process.
I suppose so. I figured FCP would just do this for me in the case of the GPU path failing. This implies there is not a good reason to set YES for both GPU and CPU.
Well, for what it's worth, there are paths we take that are CPU-preferred (such as generating thumbnails in FCPX, iirc). In those cases, it can be a win to have a CPU path, as the extra work of upload/downloading to/from the card can slow things down. But we will handle it if you only support one or the other. Darrin _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com