May 2008 - Pro-apps-dev - lists.apple.com

FXPlug and Final Cut interlace
by Steven Meyer 10 May '08

10 May '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=qgOL/y1PhZ61Xz0Pxgt4WMPK47GRG7pRBR/53QPrm9kqtGX7mT3pnXBD3BjOiWtS; h=Received:Message-Id:From:To:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Date:X-Mailer:X-ELNK-Trace:X-Originating-IP; [outputImage fieldOrder] == kFxFieldOrder_PROGRESSIVE [inputImage fieldOrder] != kFxFieldOrder_PROGRESSIVE renderInfo. fieldOrder == kFxFieldOrder_PROGRESSIVE This has confused me some, but I have adapted my code. Now for my question. Steve Meyer _______________________________________________ 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: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… When an interlaced clip is rendered in a progressive sequence, I see the following results for fieldOrder in renderOutput The heights and rowbytes of inputImage and outputImage are the same, i.e not half height for inputImage But, if I call [temporalAPI getInputBitmap], the resulting bitmap has 1/2 height and rowBytes twice of the inputImage, ie half height image and [inputImage fieldOrder] != kFxFieldOrder_PROGRESSIVE but [inputImage fieldOrder] == kFxField_NONE Has inputImage automatically been deinterlaced? In other words, has any deinterlacing processing been applied to the inputImage as a default without the user specifically applying a deinterlace filter. I am working on plugins with conditional deinterlacing code in the filters, and my client is seeing results that appear to indicate the input was already deinterlaced. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Size limitations for custom ui parameters
by Stig Sandø 07 May '08

07 May '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com User-agent: Thunderbird 2.0.0.14 (Windows/20080421) Cheers, Stig On May 6, 2008, at 1:44 PM, Stig Sandø wrote: Hei, A simple piece of example code to reproduce: - (NSView *)createViewForParm:(UInt32)parmId { NSView * view = NULL; [editButton release]; [cfgButton release]; } return view; } Hi, all, - Paul On Mar 10, 2008, at 12:07 PM, Darrin Cardani wrote: On Mar 10, 2008, at 7:56 AM, Steve Christensen wrote: On Mar 10, 2008, at 2:42 AM, Stig Sandø wrote: Darrin -- Darrin Cardani 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: http://lists.apple.com/mailman/options/pro-apps-dev/ses%40vizrt.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: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… Paul Schneider wrote: So to me it seems like FCP keeps/saves the initial size of the view the first time it is created and is using that later, despite the plugin handing over a view with a different size. This seems odd to me. Maybe someone can elaborate? unfortunately, the view dimensions are saved with the project in FCP. If you change your view dimensions, you'll see the change if you add new instances of your plugin, but older instances in saved projects won't update. And apart from doing internal version/size tracking there is no way for an instance to query whether its size has been previously set I presume. It did not seem to be part of the exported xml of a timeline at least, so an external app does not seem able to "change"/"upgrade" the sizes that way either. In our use-case we had hoped to have a dynamic size of this parameter window, both depending on what input options are relevant, as well as giving newer versions of the plugin the opportunity to adapt the view and view-size. In our case we only need one stored parameter that keeps the entire state. Final Cut doesn't allow you to dynamically change the size of your custom view. The user can change the width by dragging the column header, but we don't update our layout if you change dimensions programatically. If you want to provide a dynamic UI, your best bet is to split your UI into multiple custom parameters, which you can dynamically hide and show using -setParameterFlags. We could definitely be more flexible here in the future, but that is your best bet today. In our case that workaround is quite clunky, so we'll have to consider what to do here. When testing in Motion however, it seems to accept and adjust to changes of the size. Allowing a custom UI component with any Cocoa widgets is quite flexible, it's just odd that it hasnt been followed up by allowing a parameter to decide the size too. So we would at least be very happy if we in a (near) future version would be allowed to adjust the size of the parameter ui based on the information it contains. I finally was able to have a look at this issue again after being away for awhile. What I realised was that I had been changing the frame size in -createViewForParm, but was testing on the same plugin instance, ie I used a symbolic link to to the build-dir and tested. So despite recompiling with a different initial size, (initWithFrame) the parameter view remained the same size, but the content within was changing. So eventually I tried a new plugin instance, with code that requested quite a liberal height. And now it got the request height. What had been wrong? So I changed the code to use a more conservative height, recompiled, restarted FCP but the instance kept it's earlier liberal size. So to me it seems like FCP keeps/saves the initial size of the view the first time it is created and is using that later, despite the plugin handing over a view with a different size. This seems odd to me. Maybe someone can elaborate? In our use-case we had hoped to have a dynamic size of this parameter window, both depending on what input options are relevant, as well as giving newer versions of the plugin the opportunity to adapt the view and view-size. In our case we only need one stored parameter that keeps the entire state. if (parmId == (SessionParamID)) { // changing the height here should also update the size of existing/deserialised plugins view = [[NSView alloc] initWithFrame: NSMakeRect(0, 0, 60, 90)]; NSButton *editButton = [[NSButton alloc] initWithFrame: NSMakeRect(0, 0, 140, 25)]; [editButton setTitle:@"Editor"]; [[editButton cell] setFont: [NSFont systemFontOfSize: [NSFont smallSystemFontSize]]]; [editButton setBezelStyle:NSRoundedBezelStyle]; [editButton setTarget: self]; [editButton setAction: @selector(launchEditor)]; [view addSubview:editButton positioned:NSWindowAbove relativeTo: nil]; NSButton *cfgButton = [[NSButton alloc] initWithFrame: NSMakeRect(0, 30, 140, 25)]; [cfgButton setTitle:@"Config"]; [[cfgButton cell] setFont: [NSFont systemFontOfSize: [NSFont smallSystemFontSize]]]; [cfgButton setBezelStyle:NSRoundedBezelStyle]; [cfgButton setTarget: self]; [cfgButton setAction: @selector(launchConfigure)]; [view addSubview:cfgButton positioned: NSWindowAbove relativeTo: editButton]; Paul Schneider skrev: Darrin is right, you *should* be able to tell the host that your view is as large as you want. However, FCP isn't quite that friendly. We will use the initial height you specify, but we will resize the view down to the width of the parameters column. The user can make the parameters column wider or narrower by dragging the column header, and we should dynamically resize your view as the column changes size. You can't specify it programatically, but you can tell your users to resize the column to make your UI more usable - many developers are in this situation currently. We should use the initial height you specify, though. In testing some other plugins (like the SimpleMatte SDK example), it looks like this is working, so the problem may be with your nib or view. we're seeing that in FCP 6 our custom UI parameters seem to be restricted to a certain width, and more worryingly to a height of about 30 pixels. Is there a way to work around this to provide bigger/taller custom UIs? Unless I've been lucky, it sounds like the problem is with your NSView. I have a custom view that contains a 160 x 67 pixel image. The full height of the image is visible in the Viewer window, although the right edge can be clipped if the Parameters column width is reduced. Same behavior in both FCP 6.0.2 and FCE 4.0. That's right. You should be able to tell the host application that your view is as large as you want. Remember though, that users may get annoyed if it's really large and they have to constantly resize their parameter pane to see the whole thing. If you want to post the code from your -createViewForParm: method, I could see if there's anything obviously wrong with it. Are you creating the view in code or using a .nib file? _______________________________________________ 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: http://lists.apple.com/mailman/options/pro-apps-dev/pschneider%40apple.com This email sent to pschneider(a)apple.com ------------------------------------------------------------------------ This email sent to ses(a)vizrt.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: multi-input FxPlugins
by Paul Schneider 06 May '08

06 May '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi, Kaitlyn, - Paul On May 6, 2008, at 3:21 PM, Kaitlyn Kincaid wrote: Kaitlyn _______________________________________________ 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: http://lists.apple.com/mailman/options/pro-apps-dev/pschneider%40apple.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: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… you can use the -addImageReferenceWithName method of the FxParameterCreationAPI to create additional image inputs. This will create an "image well" parameter like BumpMap has. Use [FxParameterRetrievalAPI getBitmap] or [FxParameterRetrievalAPI getTexture] to get an image from the parameter. I am attempting to write a simple shader for FxPlug that adds the value of two inputs together.. I have the ARB code, but I have been unable to find a good example of how to get two inputs in the actual FxPlug code. the example I am looking at: In motion, the Bump Map filter is able to apply a bump mapping to a video from another sourse, however when I look at the Bumpmap.m file I have no idea how it does this... it's not even in an FxPlug style. Does anyone know of any example code that shows how to use two (or more?) inputs in FxPlug? I've tried google, however my google-fu seems to only turn up retail software. This email sent to pschneider(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

multi-input FxPlugins
by Kaitlyn Kincaid 06 May '08

06 May '08

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=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=HPjQT6OFOudBqf4zWLD7a0BTMX+KFpx07Q3KRpPcl8g=; b=Sy9Ky85e58lyFWcEzD/bDVx3iWGMqB1dK0xhwTajG1kZHCwi7Z8+J53K3WPCH6BazqMTiueJ/mVFGL1qG723Dq896I4YFkH9hsNHg2dn9Od/hfdT5WyhiXLCi3+XTwH+FxV5JHIT6TqcKEt1SmlQSA/TbgSoSYjk3DbH+4ZNy2A= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=BlEG4RTOExO9vHVg3I7Di3qS4/3hALKBUFDV0YnNE+Ypux1ZlvGQhtuH9WgvY8qu6EVkiiTgNy+jzwPwKoea1twarMlEx3eOedb7T7UnfU24r5IhceqYnScGX07omVPgt9p/vGL3hvZsEwmtZirfkFX0UYvF+u42l2VPGkh+USA= _______________________________________________ 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: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Size limitations for custom ui parameters
by Paul Schneider 06 May '08

06 May '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi, Stig, - Paul On May 6, 2008, at 1:44 PM, Stig Sandø wrote: Hei, A simple piece of example code to reproduce: - (NSView *)createViewForParm:(UInt32)parmId { NSView * view = NULL; [editButton release]; [cfgButton release]; } return view; } Hi, all, - Paul On Mar 10, 2008, at 12:07 PM, Darrin Cardani wrote: On Mar 10, 2008, at 7:56 AM, Steve Christensen wrote: On Mar 10, 2008, at 2:42 AM, Stig Sandø wrote: Darrin -- Darrin Cardani 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: http://lists.apple.com/mailman/options/pro-apps-dev/ses%40vizrt.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: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… So to me it seems like FCP keeps/saves the initial size of the view the first time it is created and is using that later, despite the plugin handing over a view with a different size. This seems odd to me. Maybe someone can elaborate? unfortunately, the view dimensions are saved with the project in FCP. If you change your view dimensions, you'll see the change if you add new instances of your plugin, but older instances in saved projects won't update. In our use-case we had hoped to have a dynamic size of this parameter window, both depending on what input options are relevant, as well as giving newer versions of the plugin the opportunity to adapt the view and view-size. In our case we only need one stored parameter that keeps the entire state. Final Cut doesn't allow you to dynamically change the size of your custom view. The user can change the width by dragging the column header, but we don't update our layout if you change dimensions programatically. If you want to provide a dynamic UI, your best bet is to split your UI into multiple custom parameters, which you can dynamically hide and show using -setParameterFlags. We could definitely be more flexible here in the future, but that is your best bet today. I finally was able to have a look at this issue again after being away for awhile. What I realised was that I had been changing the frame size in -createViewForParm, but was testing on the same plugin instance, ie I used a symbolic link to to the build-dir and tested. So despite recompiling with a different initial size, (initWithFrame) the parameter view remained the same size, but the content within was changing. So eventually I tried a new plugin instance, with code that requested quite a liberal height. And now it got the request height. What had been wrong? So I changed the code to use a more conservative height, recompiled, restarted FCP but the instance kept it's earlier liberal size. So to me it seems like FCP keeps/saves the initial size of the view the first time it is created and is using that later, despite the plugin handing over a view with a different size. This seems odd to me. Maybe someone can elaborate? In our use-case we had hoped to have a dynamic size of this parameter window, both depending on what input options are relevant, as well as giving newer versions of the plugin the opportunity to adapt the view and view-size. In our case we only need one stored parameter that keeps the entire state. if (parmId == (SessionParamID)) { // changing the height here should also update the size of existing/deserialised plugins view = [[NSView alloc] initWithFrame: NSMakeRect(0, 0, 60, 90)]; NSButton *editButton = [[NSButton alloc] initWithFrame: NSMakeRect(0, 0, 140, 25)]; [editButton setTitle:@"Editor"]; [[editButton cell] setFont: [NSFont systemFontOfSize: [NSFont smallSystemFontSize]]]; [editButton setBezelStyle:NSRoundedBezelStyle]; [editButton setTarget: self]; [editButton setAction: @selector(launchEditor)]; [view addSubview:editButton positioned:NSWindowAbove relativeTo: nil]; NSButton *cfgButton = [[NSButton alloc] initWithFrame: NSMakeRect(0, 30, 140, 25)]; [cfgButton setTitle:@"Config"]; [[cfgButton cell] setFont: [NSFont systemFontOfSize: [NSFont smallSystemFontSize]]]; [cfgButton setBezelStyle:NSRoundedBezelStyle]; [cfgButton setTarget: self]; [cfgButton setAction: @selector(launchConfigure)]; [view addSubview:cfgButton positioned: NSWindowAbove relativeTo: editButton]; Paul Schneider skrev: Darrin is right, you *should* be able to tell the host that your view is as large as you want. However, FCP isn't quite that friendly. We will use the initial height you specify, but we will resize the view down to the width of the parameters column. The user can make the parameters column wider or narrower by dragging the column header, and we should dynamically resize your view as the column changes size. You can't specify it programatically, but you can tell your users to resize the column to make your UI more usable - many developers are in this situation currently. We should use the initial height you specify, though. In testing some other plugins (like the SimpleMatte SDK example), it looks like this is working, so the problem may be with your nib or view. we're seeing that in FCP 6 our custom UI parameters seem to be restricted to a certain width, and more worryingly to a height of about 30 pixels. Is there a way to work around this to provide bigger/taller custom UIs? Unless I've been lucky, it sounds like the problem is with your NSView. I have a custom view that contains a 160 x 67 pixel image. The full height of the image is visible in the Viewer window, although the right edge can be clipped if the Parameters column width is reduced. Same behavior in both FCP 6.0.2 and FCE 4.0. That's right. You should be able to tell the host application that your view is as large as you want. Remember though, that users may get annoyed if it's really large and they have to constantly resize their parameter pane to see the whole thing. If you want to post the code from your -createViewForParm: method, I could see if there's anything obviously wrong with it. Are you creating the view in code or using a .nib file? _______________________________________________ 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: http://lists.apple.com/mailman/options/pro-apps-dev/pschneider%40apple.com This email sent to pschneider(a)apple.com This email sent to ses(a)vizrt.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: Size limitations for custom ui parameters
by Stig Sandø 06 May '08

06 May '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com User-agent: Thunderbird 2.0.0.14 (Windows/20080421) Hei, A simple piece of example code to reproduce: - (NSView *)createViewForParm:(UInt32)parmId { NSView * view = NULL; [editButton release]; [cfgButton release]; } return view; } Hi, all, - Paul On Mar 10, 2008, at 12:07 PM, Darrin Cardani wrote: On Mar 10, 2008, at 7:56 AM, Steve Christensen wrote: On Mar 10, 2008, at 2:42 AM, Stig Sandø wrote: Darrin -- Darrin Cardani 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: http://lists.apple.com/mailman/options/pro-apps-dev/ses%40vizrt.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: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… I finally was able to have a look at this issue again after being away for awhile. What I realised was that I had been changing the frame size in -createViewForParm, but was testing on the same plugin instance, ie I used a symbolic link to to the build-dir and tested. So despite recompiling with a different initial size, (initWithFrame) the parameter view remained the same size, but the content within was changing. So eventually I tried a new plugin instance, with code that requested quite a liberal height. And now it got the request height. What had been wrong? So I changed the code to use a more conservative height, recompiled, restarted FCP but the instance kept it's earlier liberal size. So to me it seems like FCP keeps/saves the initial size of the view the first time it is created and is using that later, despite the plugin handing over a view with a different size. This seems odd to me. Maybe someone can elaborate? In our use-case we had hoped to have a dynamic size of this parameter window, both depending on what input options are relevant, as well as giving newer versions of the plugin the opportunity to adapt the view and view-size. In our case we only need one stored parameter that keeps the entire state. if (parmId == (SessionParamID)) { // changing the height here should also update the size of existing/deserialised plugins view = [[NSView alloc] initWithFrame: NSMakeRect(0, 0, 60, 90)]; NSButton *editButton = [[NSButton alloc] initWithFrame: NSMakeRect(0, 0, 140, 25)]; [editButton setTitle:@"Editor"]; [[editButton cell] setFont: [NSFont systemFontOfSize: [NSFont smallSystemFontSize]]]; [editButton setBezelStyle:NSRoundedBezelStyle]; [editButton setTarget: self]; [editButton setAction: @selector(launchEditor)]; [view addSubview:editButton positioned:NSWindowAbove relativeTo: nil]; NSButton *cfgButton = [[NSButton alloc] initWithFrame: NSMakeRect(0, 30, 140, 25)]; [cfgButton setTitle:@"Config"]; [[cfgButton cell] setFont: [NSFont systemFontOfSize: [NSFont smallSystemFontSize]]]; [cfgButton setBezelStyle:NSRoundedBezelStyle]; [cfgButton setTarget: self]; [cfgButton setAction: @selector(launchConfigure)]; [view addSubview:cfgButton positioned: NSWindowAbove relativeTo: editButton]; Paul Schneider skrev: Darrin is right, you *should* be able to tell the host that your view is as large as you want. However, FCP isn't quite that friendly. We will use the initial height you specify, but we will resize the view down to the width of the parameters column. The user can make the parameters column wider or narrower by dragging the column header, and we should dynamically resize your view as the column changes size. You can't specify it programatically, but you can tell your users to resize the column to make your UI more usable - many developers are in this situation currently. We should use the initial height you specify, though. In testing some other plugins (like the SimpleMatte SDK example), it looks like this is working, so the problem may be with your nib or view. we're seeing that in FCP 6 our custom UI parameters seem to be restricted to a certain width, and more worryingly to a height of about 30 pixels. Is there a way to work around this to provide bigger/taller custom UIs? Unless I've been lucky, it sounds like the problem is with your NSView. I have a custom view that contains a 160 x 67 pixel image. The full height of the image is visible in the Viewer window, although the right edge can be clipped if the Parameters column width is reduced. Same behavior in both FCP 6.0.2 and FCE 4.0. That's right. You should be able to tell the host application that your view is as large as you want. Remember though, that users may get annoyed if it's really large and they have to constantly resize their parameter pane to see the whole thing. If you want to post the code from your -createViewForParm: method, I could see if there's anything obviously wrong with it. Are you creating the view in code or using a .nib file? _______________________________________________ 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: http://lists.apple.com/mailman/options/pro-apps-dev/pschneider%40apple.com This email sent to pschneider(a)apple.com This email sent to ses(a)vizrt.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: New to list & some questions
by Dick Applebaum 02 May '08

02 May '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Troy, Andy, I just went through a complete reinstall of FCS with no problems. But I get mixed results when I run FCP-- see below! I will try to resolve on other lists. Thx Dick On May 1, 2008, at 6:38 PM, Andy Mees wrote: Hi Dick Best Andy _______________________________________________ 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: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com Thanks for the advice-- I didn't think this was the right list. I was surprised that Apple doesn't have a list specific to Pro products, seeing they have lists for QT, QC, AppleScript, etc. Actually this is probably not the right or best place to discuss these specific issues as this list is more focused on third party questions on technical development issues. Your best course of action in the first instance is to is post your questions to the Apple Discusions user to user forums where you may find others who might have faced and already resolved your specific issues. http://discussions.apple.com/forum.jspa?forumID=939 You might also want to consider cross posting at the Creative Cow forums where you'll find a lot of experienced professional users also very willing to help http://forums.creativecow.net/cgi-bin/new_view_posts.cgi?forumid=8 If you can rule out installation specific issues and would like to send some feedback to Apple then you can use the FCP feedback page (which we are assured is read!) http://www.apple.com/feedback/finalcutpro.html And finally, if you have a specific and repeatable bug that you can demonstrate on any FCP system (ie it can be shown to be not installation specific) then you can report the specific bug at Apple's bug reporter page http://radar.apple.com Hope thats helpful Dave even if it doesn;t address your issues specifically ... do come on over to the Apple Discussions and Creative Cow lists and we can try to figure out what's not working and why.

1 0

Re: New to list & some questions
by Andy Mees 02 May '08

02 May '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi Dick Actually this is probably not the right or best place to discuss these specific issues as this list is more focused on third party questions on technical development issues. Your best course of action in the first instance is to is post your questions to the Apple Discusions user to user forums where you may find others who might have faced and already resolved your specific issues. http://discussions.apple.com/forum.jspa?forumID=939 You might also want to consider cross posting at the Creative Cow forums where you'll find a lot of experienced professional users also very willing to help http://forums.creativecow.net/cgi-bin/new_view_posts.cgi?forumid=8 If you can rule out installation specific issues and would like to send some feedback to Apple then you can use the FCP feedback page (which we are assured is read!) http://www.apple.com/feedback/finalcutpro.html And finally, if you have a specific and repeatable bug that you can demonstrate on any FCP system (ie it can be shown to be not installation specific) then you can report the specific bug at Apple's bug reporter page http://radar.apple.com Hope thats helpful Dave even if it doesn;t address your issues specifically ... do come on over to the Apple Discussions and Creative Cow lists and we can try to figure out what's not working and why. Best Andy _______________________________________________ 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: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

New to list & some questions
by Dick Applebaum 01 May '08

01 May '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi, 1) FCP gets the BBOD with increasing frequency-- requires force quit. Everything was fine for months, but now FCP seems very fragile and slow. TIA Dick _______________________________________________ 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: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… I am new to this list and don't know if this is the proper place to post potential bugs/problems in Pro Apps. I use FCS, primarily, for creating content-- though I might write a few plugins (mainly QC). I am using the latest OS X 10.5.2 and FCS 2 with all known updates applied on a iMac 24 2.8 GHz, 4GB RAM. I have been very happy with FCS and have been using FCP and Color several hours per day. Within the last few weeks I've been experiencing some problems: 2) Some simple rendered sequences will not play properly within FCP-- requires quit & relaunch of FCP. 3) Some simple exports to QT movies give garbled or incomplete files-- requires quit & relaunch of FCP or reboot. Thought I ask if anyone else was having similar problems before doing a complete reinstall & application of patches. This email sent to site_archiver(a)lists.apple.com

1 0