November 2013 - Pro-apps-dev

FCP X: Problem with Drop Zone and Text Generator
by Eberhard Ammelt 15 Nov '13

15 Nov '13

Hello, we experience a problem with text generators as image input to a drop zone. What we're trying is: Create a generator template with a drop zone. Place the generator in the timeline of a fresh FCP X project. Below this generator add a text generator, e.g. "Clouds". Then specify the text generator as source of the drop zone. The drop zone accepts the text generator, but the text is not rendered. Is this expected to work this way, or is there any workaround? Thanks, Eberhard _______________________________________________ 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: Mavericks/XCode and Intel compiler issues
by Paul Miller 15 Nov '13

15 Nov '13

On 11/15/2013 11:21 AM, Darrin Cardani wrote: On Nov 14, 2013, at 3:48 PM, Paul Miller <paul(a)fxtech.com> wrote: On 11/14/2013 5:04 PM, Darrin Cardani wrote: On Nov 14, 2013, at 1:09 PM, Paul Miller <stelefx(a)gmail.com> wrote: I recently installed Mavericks, and am having trouble getting XCode 3.2, the Intel compiler, and XCode 5 working properly. I did a clean install of Mavericks to an SSD, then Migrated my Lion system over to it. That went smoothly - everything came over and runs as before. BUT: XCode 3.2 projects that use the Intel 12.0 compiler won't link - they complain about a missing libstdc++. I reinstalled the compiler and that didn't make a difference. I tried installing the latest Intel 14.0 compiler (with XCode 5 and Mavericks support), but that doesn't show up in XCode 3.2. After attempting to make an intel 14 plugin for XCode from the existing 12.0 plugin, now XCode 3.2 won't open the project properties window - even after removing all of the Intel plugins. XCode 3.2 is now hosed. Giving in, I tried opening my 3.2 projects in XCode 5.0 - XCode crashes while trying to open the project. I understand your frustration. I’m told that Xcode 3.2 is not supported under Mavericks, so you’ll probably want to get things working on Xcode 5. Is there a reason you can’t move to Xcode 5? Well, right now it crashes when I load my XCode 3.2 projects. ;-) I'm hoping I may be able to migrate projects through XCode 4.x if necessary. The big thing holding me off from XCode 5 has been lack of OpenMP support, and I've been waiting for Intel to come out with a version of their compiler that supports 5. Why XCode 5 ships without OpenMP I have no idea. Paul, Can you send me a crash log from when it crashes opening your 3.2 project in 5.0? We may be able to figure out the issue and save you a step. _______________________________________________ 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 will once I reinstall Mavericks in a clean configuration (no Intel compiler, no migration) and see if it still happens while loading my good backups of the projects.

1 0

Re: Mavericks/XCode and Intel compiler issues
by Darrin Cardani 15 Nov '13

15 Nov '13

On Nov 14, 2013, at 3:48 PM, Paul Miller <paul(a)fxtech.com> wrote: > On 11/14/2013 5:04 PM, Darrin Cardani wrote: >> >> On Nov 14, 2013, at 1:09 PM, Paul Miller <stelefx(a)gmail.com> wrote: >> >>> I recently installed Mavericks, and am having trouble getting XCode 3.2, the Intel compiler, and XCode 5 working properly. >>> >>> I did a clean install of Mavericks to an SSD, then Migrated my Lion system over to it. That went smoothly - everything came over and runs as before. >>> >>> BUT: XCode 3.2 projects that use the Intel 12.0 compiler won't link - they complain about a missing libstdc++. I reinstalled the compiler and that didn't make a difference. >>> >>> I tried installing the latest Intel 14.0 compiler (with XCode 5 and Mavericks support), but that doesn't show up in XCode 3.2. After attempting to make an intel 14 plugin for XCode from the existing 12.0 plugin, now XCode 3.2 won't open the project properties window - even after removing all of the Intel plugins. XCode 3.2 is now hosed. >>> >>> Giving in, I tried opening my 3.2 projects in XCode 5.0 - XCode crashes while trying to open the project. >> >> I understand your frustration. I’m told that Xcode 3.2 is not supported under Mavericks, so you’ll probably want to get things working on Xcode 5. Is there a reason you can’t move to Xcode 5? > > Well, right now it crashes when I load my XCode 3.2 projects. ;-) > I'm hoping I may be able to migrate projects through XCode 4.x if necessary. > > The big thing holding me off from XCode 5 has been lack of OpenMP support, and I've been waiting for Intel to come out with a version of their compiler that supports 5. > > Why XCode 5 ships without OpenMP I have no idea. Paul, Can you send me a crash log from when it crashes opening your 3.2 project in 5.0? We may be able to figure out the issue and save you a step. 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: Mavericks/XCode and Intel compiler issues
by Paul Miller 14 Nov '13

14 Nov '13

On 11/14/2013 5:04 PM, Darrin Cardani wrote: On Nov 14, 2013, at 1:09 PM, Paul Miller <stelefx(a)gmail.com> wrote: I recently installed Mavericks, and am having trouble getting XCode 3.2, the Intel compiler, and XCode 5 working properly. I did a clean install of Mavericks to an SSD, then Migrated my Lion system over to it. That went smoothly - everything came over and runs as before. BUT: XCode 3.2 projects that use the Intel 12.0 compiler won't link - they complain about a missing libstdc++. I reinstalled the compiler and that didn't make a difference. I tried installing the latest Intel 14.0 compiler (with XCode 5 and Mavericks support), but that doesn't show up in XCode 3.2. After attempting to make an intel 14 plugin for XCode from the existing 12.0 plugin, now XCode 3.2 won't open the project properties window - even after removing all of the Intel plugins. XCode 3.2 is now hosed. Giving in, I tried opening my 3.2 projects in XCode 5.0 - XCode crashes while trying to open the project. I understand your frustration. I’m told that Xcode 3.2 is not supported under Mavericks, so you’ll probably want to get things working on Xcode 5. Is there a reason you can’t move to Xcode 5? Well, right now it crashes when I load my XCode 3.2 projects. ;-) I'm hoping I may be able to migrate projects through XCode 4.x if necessary. Why XCode 5 ships without OpenMP I have no idea. _______________________________________________ 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 The big thing holding me off from XCode 5 has been lack of OpenMP support, and I've been waiting for Intel to come out with a version of their compiler that supports 5.

1 0

Re: Mavericks/XCode and Intel compiler issues
by Darrin Cardani 14 Nov '13

14 Nov '13

On Nov 14, 2013, at 1:09 PM, Paul Miller <stelefx(a)gmail.com> wrote: > I recently installed Mavericks, and am having trouble getting XCode 3.2, the Intel compiler, and XCode 5 working properly. > > I did a clean install of Mavericks to an SSD, then Migrated my Lion system over to it. That went smoothly - everything came over and runs as before. > > BUT: XCode 3.2 projects that use the Intel 12.0 compiler won't link - they complain about a missing libstdc++. I reinstalled the compiler and that didn't make a difference. > > I tried installing the latest Intel 14.0 compiler (with XCode 5 and Mavericks support), but that doesn't show up in XCode 3.2. After attempting to make an intel 14 plugin for XCode from the existing 12.0 plugin, now XCode 3.2 won't open the project properties window - even after removing all of the Intel plugins. XCode 3.2 is now hosed. > > Giving in, I tried opening my 3.2 projects in XCode 5.0 - XCode crashes while trying to open the project. I understand your frustration. I’m told that Xcode 3.2 is not supported under Mavericks, so you’ll probably want to get things working on Xcode 5. Is there a reason you can’t move to Xcode 5? 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

Mavericks/XCode and Intel compiler issues
by Paul Miller 14 Nov '13

14 Nov '13

I'm about to go buy a gun and several clips of ammo. Anyone have any experience with any of this? Kidding about the gun, but you get the idea. _______________________________________________ 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 recently installed Mavericks, and am having trouble getting XCode 3.2, the Intel compiler, and XCode 5 working properly. I did a clean install of Mavericks to an SSD, then Migrated my Lion system over to it. That went smoothly - everything came over and runs as before. BUT: XCode 3.2 projects that use the Intel 12.0 compiler won't link - they complain about a missing libstdc++. I reinstalled the compiler and that didn't make a difference. I tried installing the latest Intel 14.0 compiler (with XCode 5 and Mavericks support), but that doesn't show up in XCode 3.2. After attempting to make an intel 14 plugin for XCode from the existing 12.0 plugin, now XCode 3.2 won't open the project properties window - even after removing all of the Intel plugins. XCode 3.2 is now hosed. Giving in, I tried opening my 3.2 projects in XCode 5.0 - XCode crashes while trying to open the project.

1 0

Re: C++ name collisions between plugins
by Paul Miller 12 Nov '13

12 Nov '13

On 11/12/2013 11:47 AM, Darrin Cardani wrote: Paul, Did you ever get this resolved? If not, I’ve got some questions below. I had this kind of structure: PLUGIN SET 1 <bunch of C++ code> FxPlugInterface (objective C class) filters are subclasses of FxPlugInterface PLUGIN SET 2 <bunch of C++ code - possibly slightly different from set 1> FxPlugInterface (objective C class - slightly different from 1) filters subclasses of FxPlugInterface To fix it I had to actually make a "FxPlugInterface2" for PLUGIN SET 2. _______________________________________________ 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 It wasn't actually a C++ collision, but the wrong C++ code ended up being called (even though it was all statically linked and stripped) because the wrong FxPlug class was getting called. I had it set up to only "export" (via the symbols.txt file) only the list of per-filter Objective C classes, which are all unique. But despite all that, when filters from either set were instantiated, it was randomly choosing the FxPlugInterface class from either one, which resulted in crash dumps down in the "wrong" C++ code. I had forgotten that even though symbols may be "hidden" or stripped, once the code is loaded all bets are off if they are Objective C classes (what a lovely feature). The upshot is I'll have to rev my "FxPlugInterface" class with a version number every time I change it, either in an updated or new set of filters.

1 0

Re: C++ name collisions between plugins
by Darrin Cardani 12 Nov '13

12 Nov '13

Paul, Did you ever get this resolved? If not, I’ve got some questions below. On Nov 6, 2013, at 1:52 PM, Paul Miller <stelefx(a)gmail.com> wrote: > >> Have you run >> nm -a >> On the resultant binary to make SURE that the requisite structures/classes are hidden? >> >> I've found that symbols are not necessarily hidden unless you hide the symbols upon compile (using the hidden flag for visibility), and THEN also strip the binary afterwards. > Coming back to this again - now I have another plugin that has the same strip settings (and related symbols file) as the previous one that appeared to work, although now the two new ones are colliding. I’m still confused on how C++ code is having name collisions. Did we ever determine why that’s happening? Normally, C++ doesn’t have this problem, just Objective-C. > > These are the settings I am using: > > Linking: > Exported Symbols File: symbols.txt > > symbols.txt contains an entry for each filter class initialization function: > > [FilterClass1 initWithAPIManager:] > [FilterClass2 initWithAPIManager:] > > However, when I run "nm" on the resulting binary, these symbols are marked "t", which I believe is internal. “t” indicates the symbol is local and part of the “Text” section. > Pete mentioned also running "strip". I tried running it with -u -s symbols.txt and that didn't help. > > Assuming I have this symbols.txt file with the blessed list of filter class entry points, is there a single "strip" command that will hide everything else? I don’t know a lot about how strip works, so I’ll have to ask internally about it. 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: Building fxplug with shared libraries and static libraries
by Darrin Cardani 11 Nov '13

11 Nov '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: any way at all to auto-generate FCPX templates
by Paul Miller 11 Nov '13

11 Nov '13

On 11/11/2013 4:20 PM, Stephen Bash wrote: ----- Original Message ----- From: "Darrin Cardani" <dcardani(a)apple.com> Sent: Monday, November 11, 2013 4:46:12 PM Subject: Re: any way at all to auto-generate FCPX templates On Nov 11, 2013, at 11:25 AM, Paul Miller <stelefx(a)gmail.com> wrote: Anything that makes dealing with the templates easier would be a big difference for GenArts. With 250+ effects in Sapphire, the Motion templates are the #1 reason we aren't supporting FCPX. When/if I do commit suicide, FCPX templates will be #1 on my list of reasons why. This is obviously a very important issue to you guys, but I don’t see any Radars in my queue regarding this issue. Please let us know when something is causing this much of a problem for you by filing a Radar: <http://bugreport.apple.com/> Done: Full FxPlug support in FCPX: 15441263 Automated Motion wrapper creation: 15441318 Thank you Stephen. _______________________________________________ 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