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

Re: C++ name collisions between plugins
by Darrin Cardani 26 Aug '13

26 Aug '13

On Aug 26, 2013, at 1:34 PM, Paul Miller <paul(a)fxtech.com> wrote: > >>> Yuck. I already have visibility override #pragmas around the Objective >>> C functions I want exposed. It would be a lot easier to just have >>> "hide EVERYTHING *except* these 5 things). >>> >> I completely agree, but I was happy there was at least a workaround. Currently our list is about 400 entries long, and it's a pain to maintain. In this case nm is your friend (though it still requires hand editing). >> > I wanted to mention what I think I got to work (at least it seems to be working). > > I ran "nm" to get the names of my FxPlug filter entry points: > > [FilterClass1 initWithAPIManager:] > [FilterClass2 initWithAPIManager:] > [FilterClass3 initWithAPIManager:] > > I put those lines into a symbols.txt file, then pointed the Linker option "Exported Symbols File" at it. > > After building, if I run "nm" on the resulting plugin, I still see tons and tons of symbols, but it now loads up without conflict with my older plugin which previously conflicted. > > I expected to see only those few initWithAPIManager: symbols in the nm results. Can someone explain why I'm still seeing everything? Can I get rid of the rest of the symbols some other way? When you run “nm” what is in the first column of the results? Any symbols which get linked at runtime should have a “U” in front of them. The man page for “nm” (like all man pages) is fairly hard to understand, but it appears that nm lists these symbols as being in an “undefined” code segment, since they don’t exist in your binary. They’re always visible because the system has to connect them up once it loads whatever library contains them. The lines that start with a “T” are symbols that you defined that are being exported. I think there are a few other types of symbols, but I don’t remember all the details. Feel free to post the output here and maybe we can help you decipher it all. 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: C++ name collisions between plugins
by Paul Miller 26 Aug '13

26 Aug '13

Yuck. I already have visibility override #pragmas around the Objective C functions I want exposed. It would be a lot easier to just have "hide EVERYTHING *except* these 5 things). I completely agree, but I was happy there was at least a workaround. Currently our list is about 400 entries long, and it's a pain to maintain. In this case nm is your friend (though it still requires hand editing). I ran "nm" to get the names of my FxPlug filter entry points: [FilterClass1 initWithAPIManager:] [FilterClass2 initWithAPIManager:] [FilterClass3 initWithAPIManager:] _______________________________________________ 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 wanted to mention what I think I got to work (at least it seems to be working). I put those lines into a symbols.txt file, then pointed the Linker option "Exported Symbols File" at it. After building, if I run "nm" on the resulting plugin, I still see tons and tons of symbols, but it now loads up without conflict with my older plugin which previously conflicted. I expected to see only those few initWithAPIManager: symbols in the nm results. Can someone explain why I'm still seeing everything? Can I get rid of the rest of the symbols some other way?

1 0

Re: FxPlug parameter doesn't show up in FCPX *sometimes*
by Paul Miller 23 Aug '13

23 Aug '13

On 8/23/2013 11:37 AM, Darrin Cardani wrote: If you open the template in a text editor, what does it say the version is? It should look something like 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 Sorry guys false alarm. I had a chicken-egg related problem with that first parameter that was related to how many times the effect instance was created.

1 0

Re: FxPlug parameter doesn't show up in FCPX *sometimes*
by Darrin Cardani 23 Aug '13

23 Aug '13

If you open the template in a text editor, what does it say the version is? It should look something like this: > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE ozxmlscene> > <ozml version="5.5"> > Is the "ozml version" attribute 5.5 or something lower? If it's lower, and you change it to 5.5, does the problem go away? If so, you're seeing some compatibility fixes we put into Motion 5.0.5. This is intentional for backward compatibility, but seems odd if you aren't expecting it. Given that Motion is up to version 5.0.7, and all updates have been free, it shouldn't be too bad to tell your customers to update to 5.0.7. (Assuming that's the issue.) If that's not the issue, please send us an example so we can debug it. Darrin On Aug 23, 2013, at 9:01 AM, Paul Miller <stelefx(a)gmail.com> wrote: > Let me describe what I'm seeing and maybe this will jar a memory with someone. > > In Motion all parameters show up fine and I have created a template for FCPX. > > The first parameter has an ID of 400 - and parameters after that start at 100 and go up. > > In FCPX, the *FIRST TIME* I apply the template to a clip, that first parameter doesn't appear. If I UNDO and then apply the template AGAIN, it then shows up (so it's working the *SECOND* time). > > If I have effects already applied when I save, even after applying it in the state where that first parameter is not visible, when I restart FCPX that first parameter is now visible. > > I have verified in the debugger that in all cases the code which adds that first parameter is getting called. > > What's going on? > _______________________________________________ > 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

FxPlug parameter doesn't show up in FCPX *sometimes*
by Paul Miller 23 Aug '13

23 Aug '13

What's going on? _______________________________________________ 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 Let me describe what I'm seeing and maybe this will jar a memory with someone. In Motion all parameters show up fine and I have created a template for FCPX. The first parameter has an ID of 400 - and parameters after that start at 100 and go up. In FCPX, the *FIRST TIME* I apply the template to a clip, that first parameter doesn't appear. If I UNDO and then apply the template AGAIN, it then shows up (so it's working the *SECOND* time). If I have effects already applied when I save, even after applying it in the state where that first parameter is not visible, when I restart FCPX that first parameter is now visible. I have verified in the debugger that in all cases the code which adds that first parameter is getting called.

1 0

Re: Building and running sample plugins in FCPX
by Andreas Kiel 21 Aug '13

21 Aug '13

_______________________________________________ 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: Building and running sample plugins in FCPX
by Darrin Cardani 21 Aug '13

21 Aug '13

_______________________________________________ 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

Question about CurrentVersion SQLs
by Andreas Kiel 21 Aug '13

21 Aug '13

Maybe it is stupid question or the wrong place to ask. If I rename an Event in FCPX the media paths are not saved in the SQL (still .../OldEventName/...) But it works since FCPX obviously does a double check and looks for the media folder inside the Event folder and everything looks fine (even in the XML which shows the correct path). This applies to the Projects which use these Events as well. Finally the question is: Are there any reasons not to update Events and Projects in case of a simple name change? -Andreas _______________________________________________ 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: Building and running sample plugins in FCPX
by Andreas Kiel 21 Aug '13

21 Aug '13

_______________________________________________ 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: Slider Min Max Delta Question
by Darrin Cardani 20 Aug '13

20 Aug '13

_______________________________________________ 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