August 2014 - Pro-apps-dev - lists.apple.com

Re: Black Mac Pro
by Christoph Vonrhein 29 Aug '14

29 Aug '14

Darrin, The console doesn't show any errors. The plugins also don't crash or have any other strange behavior besides that they just render a white image. I did not set any multi-gpu properties. This behavior can even be seen with older versions of my plugins. I'll try the trick with the two identical graphics cards. Maybe I can trigger it here on my MacPro2,1 in some way. Thanks! Christoph On Aug 29, 2014, at 3:00 PM, Darrin Cardani wrote: > Christoph, > > The most obvious difference would be that it has 2 GPUs and that rendering happens on both of them (simultaneously if you’ve set the property that allows it). It’s probably going to be difficult to debug without actually having a machine to test with. > > Note that you don’t actually need a new MacPro for a test like this, though. If you have an older MacPro and can find 2 identical video cards, you can put them both in it and get the multi-threaded rendering. > > Are there any errors printed to the console? If you have a customer that has a dual GPU setup, you could send them a version with some extra logging and see if you’re getting any OpenGL errors. > > Darrin > > On Aug 29, 2014, at 11:56 AM, Christoph Vonrhein <chv(a)chv-electronics.de> wrote: > >> Hello, >> >> I'm having a few issues with my plugins on the new black round Mac Pro. They only render a white image... I don't have the new Mac Pro because of it's price. My plugins are using a lot of vertex and fragment shaders. I suspect that there is a difference between any other Mac and the black Mac Pro, because my plugins run everywhere else. >> >> Does someone know about any significant thing that I should take a look at? >> >> Thanks! >> Christoph Vonrhein >> >> >> _______________________________________________ >> 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: Black Mac Pro
by Darrin Cardani 29 Aug '14

29 Aug '14

Christoph, The most obvious difference would be that it has 2 GPUs and that rendering happens on both of them (simultaneously if you’ve set the property that allows it). It’s probably going to be difficult to debug without actually having a machine to test with. Note that you don’t actually need a new MacPro for a test like this, though. If you have an older MacPro and can find 2 identical video cards, you can put them both in it and get the multi-threaded rendering. Are there any errors printed to the console? If you have a customer that has a dual GPU setup, you could send them a version with some extra logging and see if you’re getting any OpenGL errors. Darrin On Aug 29, 2014, at 11:56 AM, Christoph Vonrhein <chv(a)chv-electronics.de> wrote: > Hello, > > I'm having a few issues with my plugins on the new black round Mac Pro. They only render a white image... I don't have the new Mac Pro because of it's price. My plugins are using a lot of vertex and fragment shaders. I suspect that there is a difference between any other Mac and the black Mac Pro, because my plugins run everywhere else. > > Does someone know about any significant thing that I should take a look at? > > Thanks! > Christoph Vonrhein > > > _______________________________________________ > 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

Black Mac Pro
by Christoph Vonrhein 29 Aug '14

29 Aug '14

Hello, I'm having a few issues with my plugins on the new black round Mac Pro. They only render a white image... I don't have the new Mac Pro because of it's price. My plugins are using a lot of vertex and fragment shaders. I suspect that there is a difference between any other Mac and the black Mac Pro, because my plugins run everywhere else. Does someone know about any significant thing that I should take a look at? Thanks! Christoph Vonrhein _______________________________________________ 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: memory leak when rendering with Compressor from FCPX
by Darrin Cardani 29 Aug '14

29 Aug '14

On Aug 29, 2014, at 11:40 AM, Paul Miller <paul(a)fxtech.com> wrote: > On 8/29/2014 11:28 AM, Darrin Cardani wrote: >> Paul, >> >> Can you give us any more information? How are you sending the project to Compressor? How complex is the sequence? Does it happen if your plug-in isn’t applied? >> >> Obviously Compressor is a different app and has different memory characteristics, but beyond that, it’s hard to do more than speculate. If you want to send us a project and a plug-in, we could try it out and see what we can find. You can probably run Compressor in the Leaks tool with Instruments and see if it gives you a common stack trace for where the leaked memory is coming from. If you do that, feel free to send me the results and I’ll take a look. > > Darrin - I was going to try that, though I don't know how to use Compressor yet. When I render through Compressor, does Compressor actually do the rendering? ie. does it have the Motion effects engine built into it? Is there a way to send a project to Compressor, then quit Compressor and re-launch it from Instruments, and have it pick up the rendering? Or can I "attach" Instruments to it like I can with the debugger? I don’t remember off the top of my head if Compressor renders things directly or has a daemon which does that. I will look into it. You can definitely attach instruments to a running process, though. There’s a popup near the top of the window next to the start/stop buttons that lists current processes and allows you to attach to one. Darrin _______________________________________________ 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: memory leak when rendering with Compressor from FCPX
by Paul Miller 29 Aug '14

29 Aug '14

On 8/29/2014 11:28 AM, Darrin Cardani wrote: Paul, Can you give us any more information? How are you sending the project to Compressor? How complex is the sequence? Does it happen if your plug-in isn’t applied? Obviously Compressor is a different app and has different memory characteristics, but beyond that, it’s hard to do more than speculate. If you want to send us a project and a plug-in, we could try it out and see what we can find. You can probably run Compressor in the Leaks tool with Instruments and see if it gives you a common stack trace for where the leaked memory is coming from. If you do that, feel free to send me the results and I’ll take a look. Darrin On Aug 29, 2014, at 6:27 AM, Paul Miller <paul(a)fxtech.com> wrote: We found a situation when rendering a long sequence with one of our plugins applied, USING COMPRESSOR, eventually we get a weird out of memory/force-quit message. If we render the same sequence from within FCPX, without using Compressor, all is well. Can anyone shed any light on this? _______________________________________________ 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 Darrin - I was going to try that, though I don't know how to use Compressor yet. When I render through Compressor, does Compressor actually do the rendering? ie. does it have the Motion effects engine built into it? Is there a way to send a project to Compressor, then quit Compressor and re-launch it from Instruments, and have it pick up the rendering? Or can I "attach" Instruments to it like I can with the debugger?

1 0

Re: memory leak when rendering with Compressor from FCPX
by Darrin Cardani 29 Aug '14

29 Aug '14

Paul, Can you give us any more information? How are you sending the project to Compressor? How complex is the sequence? Does it happen if your plug-in isn’t applied? Obviously Compressor is a different app and has different memory characteristics, but beyond that, it’s hard to do more than speculate. If you want to send us a project and a plug-in, we could try it out and see what we can find. You can probably run Compressor in the Leaks tool with Instruments and see if it gives you a common stack trace for where the leaked memory is coming from. If you do that, feel free to send me the results and I’ll take a look. Darrin On Aug 29, 2014, at 6:27 AM, Paul Miller <paul(a)fxtech.com> wrote: > We found a situation when rendering a long sequence with one of our plugins applied, USING COMPRESSOR, eventually we get a weird out of memory/force-quit message. > > If we render the same sequence from within FCPX, without using Compressor, all is well. > > Can anyone shed any light on this? > _______________________________________________ > 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

memory leak when rendering with Compressor from FCPX
by Paul Miller 29 Aug '14

29 Aug '14

Can anyone shed any light on this? _______________________________________________ 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 We found a situation when rendering a long sequence with one of our plugins applied, USING COMPRESSOR, eventually we get a weird out of memory/force-quit message. If we render the same sequence from within FCPX, without using Compressor, all is well.

1 0

transitioning from FxPlug2 -> FxPlug3 - issues?
by Paul Miller 18 Aug '14

18 Aug '14

_______________________________________________ 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 Has anyone had any trouble when transitioning effects or effect templates from FxPlug2 to FxPlug3? I haven't had any trouble with a "new" set (an upgrade) but when doing a "minor" update to fix a bug I moved over to FxPlug3 and my effect templates broke. Worse, projects with the "old" effects applied have all their parameters reset when opened with the "new" effects. I'm still trying to track down why this is happening. I don't think my parameter IDs have changed - so it's got to be something else.

1 0