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

Re: pixel types in Motion and FCP
by Darrin Cardani 24 Jul '08

24 Jul '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Jul 24, 2008, at 1:25 PM, Micah Sharp wrote: Darrin -- Darrin Cardani 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: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… As I recall, because of a bug, or maybe on purpose, in Motion (3.0 and greater) ARGB buffers are in-correctly marked with a pixel type of RGBA (kFxPixelFormat_RGBA is really kFxPixelFormat_ARGB). This isn't a problem in Final Cut that I'm aware of. Question: Is it possible to EVER actually get RGBA pixels in either Motion or Final Cut? Is support for RGBA ever necessary? In Motion, all textures are RGBA, and in software all bitmaps are ARGB. I believe the bug you're referring to occurred before Motion 3.0 on input bitmaps. And I think in 3.0 output bitmaps are still marked as being RGBA, but the app assumes they're ARGB anyway. I'd have to run a test to verify that, but that's how I remember it. This email sent to site_archiver(a)lists.apple.com

1 0

pixel types in Motion and FCP
by Micah Sharp 24 Jul '08

24 Jul '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.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/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Scope of id attributes
by Bruce Sharpe 24 Jul '08

24 Jul '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:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=PlAYIyPIDqFBZCswQ2HLXjWA+ByeHS9Kfg3SxUFjA7M=; b=dKer9zKDvVWnTglwZsMNbdJp2SEVgOcmJjGHMqY0zriLZQPBqnNKFRSPuT6t4uqRJ9 gDNwpP7uB3Ti45JKJc4bXIo41d91thrhAHO8jfILUkBwA1Vkah1Nq6GqOE48oJ4bStbv nNmGGcZhDpZJyz+W2pyx5lOwq5V3pSZFZ80HY= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=wIsmiA6GD4I9GTypaPe2Vq0C5dYBubFOyIXzrn+YPEGx6Y4mOlLvquf4kZO/cI14NG QdN8AGqy16YboOM9kuBIZSJf5OAuQjz3jmYGKbyWNp6zX3Fb6xQDXoyqqS+G/fjcNAIy TQgT4keouXf8vQAGJXbvrhPs1UWBy1la9M+EY= But if id attributes have no existence outside of the XML, then how do I create an affiliate clip in XML? It needs to refer to a masterclipid. As an experiment, I exported an affiliate clip as XML and sure enough it has a masterclipid value that is not defined anywhere else in the XML. If I export the whole project then I can see the clip with that id value. So, barring some new definitive information about this, my strategy will be to: (1) Either not create any new ids, or (2) examine the project XML and choose id values that are distinct from those already used. (3) In any case, if I want to create an affiliate clip, I will assume that it is safe to refer to the masterclipid that shows up in the export of an existing clip. Bruce On Thu, Jul 24, 2008 at 10:00 AM, Gregory Clarke <greg(a)intelligentassistance.com> wrote: > I agree with you that case 1 is probably true. And here's why: don't forget > that in FCP a clip is not actually a piece of media, but rather a pointer to > a piece of media. Analogous to a QuickTime reference movie rather than a > video file. So my guess is that the id attribute is just an XML > representation of that same pointer "link" and doesn't exist in the FCP > project because QuickTime handles that. > > Of course, we could be wrong... > > Greg > >> Thanks, Greg. I think I get the concept of the id, but my question >> is, if I create one in a component and then import the XML to a >> project, will there be a problem if the id I have created happens to >> be the same as one that already existed in the project? >> >> Case 1: It is possible that there is no concept of id in a project, it >> only exists in XML imports and exports. In that case there is no >> problem. >> >> Case 2: But it is also possible that the id values that I see when I >> export the project do exist in the project regardless of whether it >> has been exported or not. In that case, not only do I need to avoid >> conflicts when I create an id, but I may be able to reference other >> project elements through their id. >> >> Unless I hear otherwise I am going to assume that Case 1 is true. >> >> Bruce >> >> On Thu, Jul 24, 2008 at 9:03 AM, Gregory Clarke >> <greg(a)intelligentassistance.com> wrote: >>> >>> Hi Bruce, >>> >>> The explanation of the id Attribute on p16 of the Final Cut Pro XML >>> should >>> help - it's meant for sharing common info, so it's not meant to be >>> unique. >>> Here's the example from the PDF: >>> >>>> For example, the clip information for a video track in a sequence may be >>>> identical to the clip information >>>> in an audio track in the same sequence. Rather than repeating this >>>> information for both tracks, you >>>> can encode it once and then reference the information using the id >>>> attribute. >>> >>> Hope that helps, >>> >>> Greg >>> >>> On Jul 24, 2008, at 12:23 AM, Bruce Sharpe wrote: >>> >>>> Suppose I am creating a clip, sequence or other object in XML with the >>>> intention of importing it into an existing project. I want to use id >>>> attributes in my object. Do I need to be careful not to conflict with >>>> any ids that are already in use in the project? >>>> >>>> Bruce >>>> _______________________________________________ >>>> 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/greg%40intelligentassis… >>>> >>>> This email sent to greg(a)intelligentassistance.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… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Scope of id attributes
by Gregory Clarke 24 Jul '08

24 Jul '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi Bruce, Hope that helps, Greg On Jul 24, 2008, at 12:23 AM, Bruce Sharpe wrote: Suppose I am creating a clip, sequence or other object in XML with the intention of importing it into an existing project. I want to use id attributes in my object. Do I need to be careful not to conflict with any ids that are already in use in the project? Bruce _______________________________________________ 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/greg%40intelligentassis… _______________________________________________ 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… The explanation of the id Attribute on p16 of the Final Cut Pro XML should help - it's meant for sharing common info, so it's not meant to be unique. Here's the example from the PDF: For example, the clip information for a video track in a sequence may be identical to the clip information in an audio track in the same sequence. Rather than repeating this information for both tracks, you can encode it once and then reference the information using the id attribute. This email sent to greg(a)intelligentassistance.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: Scope of id attributes
by Andreas Kiel 24 Jul '08

24 Jul '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Andreas On 24.07.2008, at 09:23, Bruce Sharpe wrote: Suppose I am creating a clip, sequence or other object in XML with the intention of importing it into an existing project. I want to use id attributes in my object. Do I need to be careful not to conflict with any ids that are already in use in the project? _______________________________________________ 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… Good question, I thought about this several times: what does FCP do with the id attribute on import. But it was never needed with my projects. There never had been that issue - all stuff was unique. So I didn't give it a test drive. If you do mean the UUID node entry, it only matters in conjunction with the "replace" set in the XML. If there not such an instruction or just an "add" FCP will assign a new UUID on import. Bruce _______________________________________________ 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/andreas.kiel% 40spherico.com This email sent to andreas.kiel(a)spherico.com This email sent to site_archiver(a)lists.apple.com

1 0

Scope of id attributes
by Bruce Sharpe 24 Jul '08

24 Jul '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:content-transfer-encoding :content-disposition; bh=nsCmqJ1f0cgigb8JZE/o0x7egzRxkw6aSMwVcbm9nQ4=; b=ZMeNpdFU3K7vYdUEPNHf2r7GTri2R/FRhioQPs0wYVwxMahuxJxSGd3/DndelAEamE /qfEI3Tx1P+UmRggKK3RfP08TMo3J1ZkfUMvHz+umpw0t7KG1tXkLBkriCZgxofQckob IOZeOpNt23K1To+lWALigRu7ibBV7DsCQJUgM= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=eo6dmhfwaX4Nx+St+XadMGCn7WA+C/W63+F0VBejU2rL/k3Oycj3e/1pGw6TnCN0kQ UFxuaXqTS/kyc9WEWkvyaqSCb1O0Bc932aVWo/9/RjvrXO2yrZnKNwcoM86e+AEcDbCV p1NQwW1EEf6vSNvr49k7iRIdxbdtQXI/yO6mM= Suppose I am creating a clip, sequence or other object in XML with the intention of importing it into an existing project. I want to use id attributes in my object. Do I need to be careful not to conflict with any ids that are already in use in the project? Bruce _______________________________________________ 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: note on problem reports
by Steve Christensen 24 Jul '08

24 Jul '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Jul 22, 2008, at 3:42 AM, Kristian Harms wrote: steve _______________________________________________ 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… Den 21. juli. 2008 kl. 18.32 skrev Darrin Cardani: The third problem is only in Motion: If an FxPlug effect generates pixels that are fully transparent, but have the R, G and B channels set to some non-zero value (e.g. 127 if we're talking UInt8), then Motion won't treat these pixels as fully transparent, but will instead show any underlying layer as "washed out", and the black default background will shine through as grey. This is with the normal blending modes. (Apple guys, the problem ID is #6079465.) As Steve mentioned, this is a problem on your end (and you're not the first person to have this problem). You just need to premultiply your pixel values, and everything will work as expected. Okay, but it seems that to provide consistent output for both Motion and FCP, I'll have to premultiply in one host but not the other. No. If you look in FxImage.h in the comment right above the declaration of the FxImageInfo struct, it says: "isPremultiplied YES if the RGB values are premultiplied by the alpha. Should always be YES." Can you confirm that this is the normal way to do this? Also, since I don't seem to get any information with which I can differentiate between the two cases, except -hostIsMotion et al. See above, but I just assume that I always have premultiplied pixels, and don't check for which host application is currently running the plugin. Anyway, isn't half the point of making a generator instead of a filter that I should simply include an alpha channel and leave it to the host app to blend with lower layers? No, the point of a generator is to produce an effect that isn't dependent on a source image. The blending occurs with all the layers, taking into account the alpha values at each pixel location within the frame, irrespective of the type of effect plugin that was applied to a particular layer. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Marker question
by Helena Ju 23 Jul '08

23 Jul '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.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/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

MooV atoms for MPEG1 Layer 2
by Michael Miller 23 Jul '08

23 Jul '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=Om4O94uZXgeXAKdRQO50p27rQJ2sh+RsqU9IeOWgCqM=; b=VqN0vUDYb76WdiyRSXeKK9mHli9QvnMukpHDs7k0Es9LCfU6ayap5aWMg0JOETpJ0X 1bgldO6KKFVYmHjD7571Xz1d2KhqzLIrGVEMQhKWNzCHVh9Tn4yWMxWvgmOfAB/mv6TO KCA6NAE+y6ABm87ot2o/2PmnKucqsU7XsX7AI= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=nniGvkPgsZFKSBI3beQspKNPgXuwYujSBuuMtA88T3h4CuvOevG2aSWMiTtaitOaMv dOOu+gcHS9lQpg2xJXIMt+He8aOHr7XERkA4kvYsHk3wIapYIVfb9mOadHrfKrKaVT2N WE+acbh2TvtSgVJW239HK8mNVm5jLDvxGC1NE= _______________________________________________ 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: note on problem reports
by Gary Oberbrunner 22 Jul '08

22 Jul '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080421 Lightning/0.9pre Thunderbird/2.0.0.14 Mnenhy/0.7.5.0 -- . . . . . . . . . . . . . . . . . . . . . . . . . Gary Oberbrunner garyo(a)genarts.com GenArts, Inc. Tel: 617-492-2888 955 Mass. Ave Fax: 617-492-2852 Cambridge, MA 02139 USA www.genarts.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: One reason why many compositing applications prefer working premultiplied is that the typical "over" operation is so much simpler; The other big reason is it allows for emissive foreground images (bright but fully transparent, like a lens flare). Many optical effects never look their best in a non-premult compositing system. This email sent to site_archiver(a)lists.apple.com

1 0