I'm using the Transmit API to get the timecode of the sequence as it plays. I'm using the inTime and working out the number of seconds from the ticks.
This gets the number of seconds from the start, which is fine if the sequence begins at 00:00:00:00, but if it begins at 01:00:00:00 or some other value then all of the timecode values are wrong. I could not figure out a way of getting the sequence start position - am I correct in assuming that such a function doesn't exist?
Thanks Zac. I'm going to implement a workaround where the user can specify the timecode start in the Setup pane but this feature would be useful because we always prefer zero configuration from the user when possible.
For automation purposes you may want to also implement reading any XMP sidecar file that exists. That has the timecode of the capture in it.
- a good example is to export H.264 in AME/PPro. the resulting xmp/xmpses file has the xmp fields of interest. Open it with WordPad (coz that understands Unicode) and you'll see a XMP:RDP packet like this:
You can read/write/modify XMP embedded in source files or in sidecar xmp files for sources that can't embed XMP using the Adobe XMP Toolkit.
at a higher level - is it even possible for the sequence object to start at non-zero?
if you're making an exporter the sequence start time will be the source start and end times that you can read during exExport.
The sequence start can be set to any timecode value. I'm using the Transmit API so it appears in the Playback menu in CS6 and it sends video to the plugin, which I ignore and just pull out the position in seconds and translate it to a timecode value.
Always great to see new information in the selectors. great work.
But, this does then assume that your plugin will check to see what version it's running on. For current and future this is great but for backward compatibility to CS5, CS5.5, CS6.0.0, CS6.0.1 - which you have to assume is the majority of the market - it won't work. So if your plugin in non-commerical it's fine but if it is commercial you need to check. Will you get back an error when you try to use this new mechanism on < 6.0.2?
thx. my post was more of a cautionary tale for those who have not needed to think about backward compatibility.
For example, betwen CS4 and CS5 the Source frameRate went from float64 fps to int64 ticks.
nothing wrong with the change - in fact it was a good thing - but it does come back to haunt you when you develop against the newest CS and then hope that it'll work on CS n-1 and n-2 etc.
The sames goes the for the Suites. If you blindly use the non-versioned label it'll always point to the current version in the SDK. eg memory suite 2,3,4. If you don't explicitly open them with the version number after detecting the app version in PrSDKAppInfoSuite then you'll fail to get those suites too.
as I said, the only reason I posted was as a cautionary note for those who have not dealt with multiple versions of the App.
Acrobat.com has been updated, so here's the updated link to the header file: