Found this out after a lengthy render, and spent some time testing this am... VV4c.
If you have a 24p video clip on the timeline in a 24p proj, Do Not render to winmedia 9.
The wmv 9 plugin does not give a choice for 24 fps - only 23.976 in the drop down box. The render will introduce a telecine/interlace effect with ghosting on images in individual frames.
Likewise, Do Not use the winmedia 8 plugin if you have a 23.976 proj., as you can only go to 24 fps, with the same result of introducing severe ghosting.
23.976 to 23.976 wmv 9 seems OK, as does 24 to 24 wmv 8.
Don't have timed results yet - wanted to get this posted - but it also seems in this situation the plugin for wmv 9 (peak vbr 2-pass) is a bit slower then the stand alone encoder, perhaps because of generating these tweener frames (which has to have some cost timewise).
I suppose one could ask: "Why does this surprise me"? Well, if you encode to wmv using the MS encoder this doesn't happen - in fact with vbr you have to be careful of your settings so it doesn't drop too many frames (it considers irrelavant) in the interest of compression. The MS encoder treats desired frame rates kind of flexibly, as a target. Encode a 23.976 file to 24, and it records key (I) frames & the requisite number of frames in between. Do the reverse, and it just records fewer (as mentioned, it's a bit too good at that). At any rate the result of the conversion & resultant ghosting in VV4c is not cool IMO.
If you have a 24p video clip on the timeline in a 24p proj, Do Not render to winmedia 9.
The wmv 9 plugin does not give a choice for 24 fps - only 23.976 in the drop down box. The render will introduce a telecine/interlace effect with ghosting on images in individual frames.
Likewise, Do Not use the winmedia 8 plugin if you have a 23.976 proj., as you can only go to 24 fps, with the same result of introducing severe ghosting.
23.976 to 23.976 wmv 9 seems OK, as does 24 to 24 wmv 8.
Don't have timed results yet - wanted to get this posted - but it also seems in this situation the plugin for wmv 9 (peak vbr 2-pass) is a bit slower then the stand alone encoder, perhaps because of generating these tweener frames (which has to have some cost timewise).
I suppose one could ask: "Why does this surprise me"? Well, if you encode to wmv using the MS encoder this doesn't happen - in fact with vbr you have to be careful of your settings so it doesn't drop too many frames (it considers irrelavant) in the interest of compression. The MS encoder treats desired frame rates kind of flexibly, as a target. Encode a 23.976 file to 24, and it records key (I) frames & the requisite number of frames in between. Do the reverse, and it just records fewer (as mentioned, it's a bit too good at that). At any rate the result of the conversion & resultant ghosting in VV4c is not cool IMO.