It has been well documented that despite all appearances to the contrary in the CS4 Media Encoder that cuepoints simply do not work in the f4v format.
For reference see Lee Brimelow's blog entry.
The workaround he gives is not frame accurate as 'if you create a navigation cue point on an F4V file, it does not add a keyframe into the video file at that point''
As I need the video acceleration capabilties of h264 encoded material that f4v houses, and frame accurate cuepoints in my work, I am completely at a loss. Has this been fixed in Premiere CS5?
Retrieving data ...