This content has been marked as final. Show 5 replies
PAL uses 25 fps. Your source footage is 50 fps. It would make sense that half those frames will need to be dropped. Whether they're interlaced or progressive is incidental. Your source footage has twice as many frames as allowed by the DVD specification, hence they must be dropped.
Jim, I agree with you, PAL uses 25 frames-per-second. But every frame is splitted into 2 fields wich means you get 50 fields-per-second. If I use PAL 25 frames progressive every frame is plitted, too, because PAL ALWAYS uses interlaced fields. But in that case the two fields are always the same so you got in fact one frame.
These terms fields-frames-50i-25i are often mixed up, so I'm sorry if I made it not clear enough in my first post.
Again, my source clips are in 50 fps (frames), the destination should have 25 fps interlaced which means 50 fields. AME encodes it as 25 fps progressive wich misses the information of every second frame.
Other encoders convert 50p to 25i correctly in 50 interlaced fields and you got smooth horizontal movements.
btw, this AME behavior is not depended on DVCProHD, I tested other 50p-formats, too (exept ntsc sources).
I'm afraid I don't know enough about the programming of AME to offer an explanation of why it does things the way it does. All I can say is that Premiere doesn't have the greatest track record when it comes to things like this. The general recommendation has been to use outside software for the conversion.
Too sad that no frameserver-plugin is working anymore, so we have to stick with AME...
What about the link for premiere bugreports to adobe, I can't find it anymore. Can anybody post it, please?