site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=DeMontfortUniversity.onmicrosoft.com; s=selector2-DeMontfortUniversity-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=0rc997U77Cow0uLNHTkKhSDYbELBDPaC/bf1cdQSh8c=; b=ERe+iNbf0jgPfJ0+VHVHFbuakN5WmW7hf39o7DmNjcvxOMQCh3YREHoTV2L79Rf6aydxGGgUKvN+2IfrIIXIpELeRPfIiLAKaIqHQ3JZw0TJOy//u3jDElLtvhjRWgEY3ja+/KlTmez9tUaq+/nxhUlfFL0PWzN97nk4ZGorV5M= Thread-index: AQHWrUL6Ahw7q8WRQU2F4o+eQpjDIA== Thread-topic: Avoiding parallel frames processing User-agent: Microsoft-MacOutlook/16.42.20101102 Hi ProAppsDev, In doing my FxPlug 4.X conversions, I understand that now the plugin can and will process multiple frames simultaneously if the GPUs are available to do so, and that there is no longer a switch to control whether this happens. I use FxPlugs for my own nefarious artistic purposes, so sometimes I break rules, since it only needs to work for me. One of my FxPlugs relies on frame-to-frame feedback (a rule-breaker for sure), which the new parallel frame-processing paradigm in turn prevents. I’m just wondering if there might be an underhanded trick available for me to get around this and force sequential processing of the frames for an FxPlug. I might even consider a soft-switch to disable my second GPU if I were truly desperate… Fully understandable if there is not a way. Thanks, -=Bret _______________________________________________ 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