site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Andreas, regards, -eryk On Jan 28, 2008, at 5:18 AM, Andreas Kiel wrote: Hi all, Maybe somebody can shed some light here - thanks. Kind regards Andreas Andreas Kiel Spherico Nelkenstr. 25 D-76135 Karlsruhe Tel.: +49 (0)721 183 9753 eFax: +1 650 897 8094 eMail: kiel@spherico.com http://spherico.com/filmtools -- workflow tools for FCP P Please don't print this e-mail unless you really need to. _______________________________________________ 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... Since the <timebase> element is required to have an integer value, the <ntsc> element's only purpose is to indicate whether that integer should be modified by the (much loathed) NTSC multiplier - i.e. 1000/1001 - in order to arrive at the true rate. As far as I understand it the <ntsc> element doesn't really have any meaning within the <timecode> element since any timecode is intrinsically integral. The <displayformat> should be NDF except possibly when the <timebase> is 30, in which case it could be DF. So, in the first example, the file has a rate of 29.97 and is using 30 NDF timecode. In the second example the file has a rate of 23.98 and is using 24 NDF timecode. I'm working on application which does some kind of analyzing media in a project or sequence. While working on that I may have come to a point where do have a lak of understanding. Within the XML an audio node may look like the below: <file id="TD26 L016 Gwen"> <name>TD26 L016 Gwen</name> <pathurl>file://localhost/RAID/TDI/TDI-026/026_Lines/TD26%20L016%20Gwen.wav </pathurl> <rate> <timebase>30</timebase> <ntsc>TRUE</ntsc> </rate> <duration>674</duration> <timecode> <rate> <timebase>30</timebase> <ntsc>TRUE</ntsc> </rate> <string>03:09:22:25</string> <frame>340885</frame> <displayformat>NDF</displayformat> <source>source</source> </timecode> <media> <audio> <samplecharacteristics> <samplerate>48000</samplerate> <depth>24</depth> </samplecharacteristics> <channelcount>1</channelcount> </audio> </media> </file> So the timecode information says that this file is NTSC(True) 30 frames per second NDF. From my understanding there can't be this kind of TC in FCP as the current handling of 30 NDF is not NTSC - at least for video. Or is there a hidden handling which do match the options of current audio HDRs? It's even more confusing for me if I look at media using 24 frames per second which won't show the "NTSC" node for the rate: <file id="TDI_FULL_OPEN_REVISED"> <name>TDI_FULL_OPEN_REVISED</name> <pathurl>file://localhost/RAID/TDI/TDI%20Final%20Theme/TDI_FULL_OPEN_REVISED.WAV </pathurl> <rate> <timebase>24</timebase> <ntsc>TRUE</ntsc> </rate> <duration>1461</duration> <timecode> <rate> <timebase>24</timebase> </rate> <string>23:58:33:10</string> <frame>2071522</frame> <displayformat>NDF</displayformat> <source>source</source> </timecode> <media> <audio> <samplecharacteristics> <samplerate>48000</samplerate> <depth>24</depth> </samplecharacteristics> <channelcount>2</channelcount> </audio> </media> </file> This email sent to evershen@apple.com This email sent to site_archiver@lists.apple.com