F4V cuepoints now working in Premiere CS5?

Question

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?

Answer 1

Well, there's really no rationale for the project conversion to somehow drastically alter the appearance of footage, particularly something like DVCPROHD. Adobe changed the way its software handles pixel aspect ratios between CS3 and CS4, but that affects SD footage, not HD footage. There may be some degree of weirdness since in CS3, you had a project that was set to a specific format/frame rate/codec/whatever, whereas in CS4 and later the project is just a container for sequences of any and all types.
Instead of opening the original project and going through the conversion, try creating a new project and importing the old project as if it were any other media file. Premiere will reconstruct the old project within the new one; this probably is not going to have any change, but it's worth a shot.
Can you describe (or better, show) the pixelation you're referring to? It's hard to visualize without, well, a visual, and that might help better pinpoint the issue. Also, is the pixelation only during playback, or is while the clip is paused in the sequence, as well?