Nick White
Forum Replies Created
-
Not promising anything, but you need to post up the settings you are using to render the video.
Try getting a free ap called MediaInfo. You can right click on the video’s icon and see all the details of the video.Choose to see Text of the full data, and copy and post that in your message.
Alternatively post a small snippet of the video somewhere and give this thread a link.
That will go a long way to letting people help. The Youtube version gets so much more done to it that it’s useless as a diagnostic tool.
Nick
-
Thanks very much for the reply.
That was the info I was looking for. I was not sure if the frame was built over the 1/25 second period, or was instant. hmmmm.. No this is not ghosting…… I think. I have seen ghosting , mostly when I do not switch off Vegas’s “resample”. Nearly all action or panning in Progressive stuff shows it at sub 50 fps frame rates, on TV, DVDs and on my own footage (and everybody else’s). I assume it’s there at 50fps as well, but just too fast to see. Well de-interlaced i clips do not show it.
Nick
-
OK. I will just float this idea.
The reason I see objectionable flicker is that the previous frame is being gradually (in frame rate terms) replaced by the new one. So what the eye is watching is both frames gradually melding from one to the other. When I watch 25/30p with lots of action, it really does look as if the frame flickers back and forth, and not just as if it’s the flicker of the new frame (if you take my meaning). Film on the other hand would shutter the old frame, move it one and then open the new frame. the only flicker is shutter time: one single action.
Thoughts appreciated.
Nick
Nick
-
Hey! Never got a heads-up from the forum about your reply. Sorry.
OK. Thanks. That pretty much confirms what I thought.The whole paradigm is just so different.It was just that people who at least _sounded_ good were going on about it. 🙂
Nick
-
Well thanks guys! That option seems to be about confusion than any logic that I could see! 🙂 But yeah that fixed it.
Nick
-
hmmm…darn… Disappointing.
OK.
Things to think about:
* Are you sure you are rendering at the same frame size and bit rate, and in the same format as you were before?
– you may have been using modified formats that you have not kept
– Even if the new machine is more powerful, that could cause the freezing of rendered playbacks (HAH!….The denser the data, the lower the freezing point!)* Have you tried playing old rendered stuff of the same video format and size/quality, either your own or others’, on the new machine, ?
* Have you edited D70 footage on your old machine OK?
– The green bit sounds weird, and there _may_ be an issue with video formats or something. Some proprietary formats are difficult.* Are you importing the clips into the same project all the time?
– I read a blog @
https://www.davecolorado.com/index.php/fixing-sony-vegas-black-preview-window/
about green clips in Vegas, and that this meant the project was corrupt. So either dump that project and start afresh, or, if you have dine a lot of work (it does not sound like it yet) then move all the clips into a new project.* Maybe simply try reinstalling Vegas.
– I know that sounds trite, but it is easy to do, especially if you have not set up too many preferences etc, and has solved some weird stuff for me.Nick
-
I tend to agree with Jeff Schroeder, but can you be a bit more specific? Is this right from istall, whilw working etc?
Nick
-
Thanks for the reply. I take your points and it’s always a fight between ISO and noise and slow shutter.
But I was more wondering about the actual playback, and what causes flicker there. My camera can do 50p and it looks like silk. But if I convert to 25p, there is a noticeable flicker. That is in spite of all the help I have had here to optimise it and including turning off Vegas’s daft “smart resample”.
I still prefer interlaced for any action shots for its smoothness, although I realise it is not quite as good even at its best with still scenes, compared to progressive for detail.
Nick
-
Thanks John, for clearing it up and confirming.
Hehe! After I wrote my last post I _immediately_ thought “woops” and did a VBR render, two pass. I realised that “optimised” was what I wanted and I was was going for “best quality” or at least “most predictable quality”.
So many choices. So many targets. So many…..
And it is hard to make watchable video without lots of data!
-
OK. With a bit of thought I think I got it. The bitrate _will_ set file size, because the smaller frame size will attempt to have more info (less compression/loss) than the larger frame size, for a given CBR. It may not really show it, due to pixellation, but on the other hand there may be some gain….I suppose it depends on the content.