October 2020 - Pro-apps-dev

Re: Avoiding parallel frames processing
by Pierre Jasmin via Pro-apps-dev 31 Oct '20

31 Oct '20

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1 Pierre On 10/28/2020 4:20 PM, Darrin Cardani via Pro-apps-dev wrote: Good to see you around these parts, Dave! Darrin On Oct 28, 2020, at 4:12 PM, Dave Howell <dave(a)avatron.com <mailto:dave@avatron.com>> wrote: Dave at Avatron Darrin Hi ProAppsDev, 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(a)lists.apple.com <mailto:Pro-apps-dev@lists.apple.com>) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com This email sent todcardani(a)apple.com <mailto:dcardani@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 <mailto:Pro-apps-dev@lists.apple.com>) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/dave%40avatron.com This email sent todave(a)avatron.com <mailto:dave@avatron.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/jasmin%40revisionfx.com This email sent to jasmin(a)revisionfx.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 What would work maybe is processing during the equivalent of the analysis pass which will be in frame order and plugin could dump cached rendered frames somewhere - and then revert to just fetching frames from disk when rendering out. To make this clean (would use that too) there should probably be an official plugin cache folder set by host to avoid mac permission issues and what not, even creating an item in project so it can be archived properly. I’m not sure what you mean. Can you elaborate? The timing API returns info about the timing of objects in the project. The temporal image API of FxPlug 3 and earlier can get frames at previous times, but they’re input frames, not output frames. In FxPlug 4, you can schedule frames at other times to be inputs at the current time, but again, they’re input frames, not output frames. Am I misunderstanding what you’re suggesting? Could Bret just use the Timing API to make one frame depend on the contents of a previous frame? Then when handed the previous frame, he could just ignore it and render the current frame. On Oct 28, 2020, at 9:01 AM, Darrin Cardani via Pro-apps-dev <pro-apps-dev(a)lists.apple.com <mailto:pro-apps-dev@lists.apple.com>> wrote: I’m not sure how easy it is to ensure you get them in the proper order, but you can always use a lock of some sort. For example in your -renderDestination: method, you could lock an NSLock at the start. That will prevent 2 calls to the method on different threads from running at the same time. The issue is that the order may not be sequential. (It depends on a number of asynchronous things happening in the host app.) It might be possible to note the time of the last frame processed and if the current time is more than 1 frame later, hold off until a frame closer to the last rendered one gets rendered? It seems like you’d have issues if the user moves the playhead in that case, but that’s the only thing I can think off of the top of my head. On Oct 28, 2020, at 8:57 AM, Bret Battey via Pro-apps-dev <pro-apps-dev(a)lists.apple.com <mailto:pro-apps-dev@lists.apple.com>> wrote: 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…

1 0

Re: Avoiding parallel frames processing
by Darrin Cardani via Pro-apps-dev 28 Oct '20

28 Oct '20

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Good to see you around these parts, Dave! I’m not sure what you mean. Can you elaborate? The timing API returns info about the timing of objects in the project. The temporal image API of FxPlug 3 and earlier can get frames at previous times, but they’re input frames, not output frames. In FxPlug 4, you can schedule frames at other times to be inputs at the current time, but again, they’re input frames, not output frames. Am I misunderstanding what you’re suggesting? Darrin > On Oct 28, 2020, at 4:12 PM, Dave Howell <dave(a)avatron.com> wrote: > > Could Bret just use the Timing API to make one frame depend on the contents > of a previous frame? Then when handed the previous frame, he could just > ignore it and render the current frame. > > Dave at Avatron > > >> On Oct 28, 2020, at 9:01 AM, Darrin Cardani via Pro-apps-dev >> <pro-apps-dev(a)lists.apple.com <mailto:pro-apps-dev@lists.apple.com>> wrote: >> >> I’m not sure how easy it is to ensure you get them in the proper order, but >> you can always use a lock of some sort. For example in your >> -renderDestination: method, you could lock an NSLock at the start. That will >> prevent 2 calls to the method on different threads from running at the same >> time. The issue is that the order may not be sequential. (It depends on a >> number of asynchronous things happening in the host app.) It might be >> possible to note the time of the last frame processed and if the current >> time is more than 1 frame later, hold off until a frame closer to the last >> rendered one gets rendered? It seems like you’d have issues if the user >> moves the playhead in that case, but that’s the only thing I can think off >> of the top of my head. >> >> Darrin >> >>> On Oct 28, 2020, at 8:57 AM, Bret Battey via Pro-apps-dev >>> <pro-apps-dev(a)lists.apple.com <mailto:pro-apps-dev@lists.apple.com>> wrote: >>> >>> 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(a)lists.apple.com >>> <mailto:Pro-apps-dev@lists.apple.com>) >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com >>> <https://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com> >>> >>> This email sent to dcardani(a)apple.com <mailto:dcardani@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 >> <mailto:Pro-apps-dev@lists.apple.com>) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/pro-apps-dev/dave%40avatron.com >> <https://lists.apple.com/mailman/options/pro-apps-dev/dave%40avatron.com> >> >> This email sent to dave(a)avatron.com <mailto:dave@avatron.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: Avoiding parallel frames processing
by Dave Howell via Pro-apps-dev 28 Oct '20

28 Oct '20

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Could Bret just use the Timing API to make one frame depend on the contents of a previous frame? Then when handed the previous frame, he could just ignore it and render the current frame. Dave at Avatron > On Oct 28, 2020, at 9:01 AM, Darrin Cardani via Pro-apps-dev > <pro-apps-dev(a)lists.apple.com> wrote: > > I’m not sure how easy it is to ensure you get them in the proper order, but > you can always use a lock of some sort. For example in your > -renderDestination: method, you could lock an NSLock at the start. That will > prevent 2 calls to the method on different threads from running at the same > time. The issue is that the order may not be sequential. (It depends on a > number of asynchronous things happening in the host app.) It might be > possible to note the time of the last frame processed and if the current time > is more than 1 frame later, hold off until a frame closer to the last > rendered one gets rendered? It seems like you’d have issues if the user moves > the playhead in that case, but that’s the only thing I can think off of the > top of my head. > > Darrin > >> On Oct 28, 2020, at 8:57 AM, Bret Battey via Pro-apps-dev >> <pro-apps-dev(a)lists.apple.com <mailto:pro-apps-dev@lists.apple.com>> wrote: >> >> 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(a)lists.apple.com >> <mailto:Pro-apps-dev@lists.apple.com>) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com >> <https://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com> >> >> This email sent to dcardani(a)apple.com <mailto:dcardani@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 > <mailto:Pro-apps-dev@lists.apple.com>) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/pro-apps-dev/dave%40avatron.com > <https://lists.apple.com/mailman/options/pro-apps-dev/dave%40avatron.com> > > This email sent to dave(a)avatron.com <mailto:dave@avatron.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: Avoiding parallel frames processing
by Darrin Cardani via Pro-apps-dev 28 Oct '20

28 Oct '20

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com I’m not sure how easy it is to ensure you get them in the proper order, but you can always use a lock of some sort. For example in your -renderDestination: method, you could lock an NSLock at the start. That will prevent 2 calls to the method on different threads from running at the same time. The issue is that the order may not be sequential. (It depends on a number of asynchronous things happening in the host app.) It might be possible to note the time of the last frame processed and if the current time is more than 1 frame later, hold off until a frame closer to the last rendered one gets rendered? It seems like you’d have issues if the user moves the playhead in that case, but that’s the only thing I can think off of the top of my head. Darrin > On Oct 28, 2020, at 8:57 AM, Bret Battey via Pro-apps-dev > <pro-apps-dev(a)lists.apple.com> wrote: > > 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(a)lists.apple.com > <mailto:Pro-apps-dev@lists.apple.com>) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com > <https://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com> > > This email sent to dcardani(a)apple.com <mailto:dcardani@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

Avoiding parallel frames processing
by Bret Battey via Pro-apps-dev 28 Oct '20

28 Oct '20

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)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(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