-Eake4- wrote:Seriously? 23.967 to 24 had ghostings? theres almost no difference so i wouldnt expect ghosintgs
mirkosp wrote:It actually makes a lot of sense for it to have a lot of ghosting... the points in time which are represented by 23.976 and 24 do not match at all, since one is float while the other is integer, thus the blend.
But the best thing for you would be to assumefps(24) before editing and going on like that, I guess. Still, seems weird that it won't allow you to do 23.976...
avisource("file.avi")
assumefps(24)mirkosp wrote:Mmmh what formats and framerates do you have at disposal?
Also, do be aware that using assumefps will basically speed up your footage to that framerate, so you'd likely have to re-edit your video for the thing to work out. I meant that as a suggestion for the future because I thought you could export at 24.00 fps from vegas, but that does not appear to be the case...?
mirkosp wrote:It actually makes a lot of sense for it to have a lot of ghosting... the points in time which are represented by 23.976 and 24 do not match at all, since one is float while the other is integer, thus the blend.
But the best thing for you would be to assumefps(24) before editing and going on like that, I guess. Still, seems weird that it won't allow you to do 23.976...
mirkosp wrote:Photoshopping to remove ghosting you introduced with the export? That's all useless work you go through, you could avoid it if you just disabled vegas' resampling.
Also, please do match source, timeline, and export framerate (as well as resolution).
Users browsing this forum: No registered users and 0 guests