site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Rainer, -eryk On Sep 17, 2009, at 11:11 AM, Rainer Standke wrote: Hello, So here the difference is the rate, and only the rate. Is this a bug? Thanks for any insight you might provide, Rainer Standke XMiL Workflow Tools http://www.xmil.biz _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/evershen%40apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... I looked into this and yes, I think it is a bug. It appears that FCSVR does not accept any DF at 59.94. That is, all 59.94 footage is considered to be NDF timecode. I am seeing what I would call an inconsistency in XMLs output from Final Cut Server. This here is from a clip in 29.97 DF (note the ;): <mdValue fieldName="Timecode Offset" dataType="timecode">01:00:00;00/ (30000,1001)</mdValue> This here is from a clip in 29.97 NDF (note the absence of the ;): <mdValue fieldName="Timecode Offset" dataType="timecode">01:00:00:00/ (30,1)</mdValue> So in parsing these XMLs I assume that analog to how FCP XML work the indicator for DF vs. NDF is the semicolon, rather than the frame rate, as expressed in (30000,1001) vs. (30,1). In FCP XMLs the difference between DF and NDF TCs is expressed in <displayformat>, thus very much independant of <rate>/<ntsc>. However, when I look at FCSvr XML for 59.94 fps clips I get no semicolon at all: 59.94 NDF: <mdValue fieldName="Timecode Offset" dataType="timecode">01:05:26:31/ (60,1)</mdValue> 59.94 DF: <mdValue fieldName="Timecode Offset" dataType="timecode">01:00:42:12/ (60000,1001)</mdValue> Is it safe to assume that in the case of 59.94 there can never be a clip with NDF Timecode running at 59.94? In other words, is it safe to assume that the rate (59.94 vs. 60) is always going to indicate the DF vs NDF? Mind you, in FCP XML it is not, and in 29.97 in Final Cut Server it seems not to be the case, either. This email sent to evershen@apple.com This email sent to site_archiver@lists.apple.com