Wayne Waag
2
COW Coins
Forum Replies Created
-
Tom,
I looked at your YT footage from from the XAVC render which had no artifacts and there are lots of parts that are jerky due to your high motion rates. Since you’re in the UK, your frame rate for 4K footage is only 25 fps . Correct? In NTSC land, it would be a little better at 30 fps, but still very juddery unless your panning movements are very slow, which in your footage, they are not in certain parts. Also I presume that you are judging your playback to be juddery based on your PC playback rather than YT playback which is notorious for momentary pauses, even on the best of internet connections. When you say that your playback from the SD card is smooth, is that from the camera itself or the sd card being read by your PC? I would be very surprised if your results with the Cyberlink software are any better since the x264 encoder that’s part of Handbrake is considered to be the best. You could also try TMPGEnc’s Mastering Works 6, another very good encoder which renders 4K, but it’s not freeware and again, I wouldn’t expect any improvements. Good luck.
wwaag
-
Wrong FX. You need to apply the Computer RGB to Studio RGB level FX.
wwaag
-
Very simple. Your pan rate is much too high for your frame rate. Not knowing anything about your project settings, you can either increase your frame rate or slow down how fast you pan across the still images.
wwaag
-
You can render UHD using Handbrake, which most agree is a better encoder than MC. It’s very convenient if you install the 1-click Vegas to Handbrake script.
https://www.vegasvideo.de/vegas-2-handbrake-en
I also have a 3770K and it took a little over a minute to render a 15 sec project from stills–no FX.
wwaag
Added: With 4K GoPro footage, render time increased to about a minute and a half for a 15 sec clip.
-
i would think this would cause an issue changing the framerate? Or maybe not.
The differences between 59.94 fps and 60 fps are pretty minimal–1 frame per 1000 or roughly 1 frame every 10 sec. You have two options. First, just render at 59.94 fps, making sure that you disable resample. In this case, you drop every 1000th frame. Or, you could adjust the playback rate to .999. Assuming you have Vegas pro, there is a script written by John Rofrano for converting 30 fps to 29.97 fps that I modified to convert 60 fps to 59.94 fps. If you’re interested, I can post that script.
wwaag
-
If you want to change the playback rate and adjust event length at the same time, simply Ctrl-drag the end of your event to the left. E.g. if you ctrl-drag a 1 min event to 30 sec, the playback rate will be 2.0.
wwaag
-
Yes. Please post back.
wwaag
-
Getting the proper levels in Vegas is a bit of a challenge. Here’s a tip I learned from someone on the Vegas Pro forum, although not everyone agrees with this approach. Do all of your editing in Computer RGB making sure you do the proper conversions. Stills, graphics and video from some cameras are already full-range so no conversion is necessary. Consumer camcorders often record at 16-255 so it’s necessary to expand the black levels. If you take this approach, then apply your final computer RGB to studio RGB levels FX on the video output bus and you’re done.
IMHO, bringing back previously rendered files into Vegas for changes is not a good idea because of generational loss, unless you are using a decent digital intermediate. In that case do your pre-renders full-range and then apply the final level FX only on final render to a delivery format.
Since you will be using a laptop to drive a projection display (?), you obviously need to do some pre-testing to make sure the displayed levels are correct. You might consider using a media player that enables you apply such levels conversions. E.g. MPC-HC (Media Player Classic-Home Cinema) has a feature they called Shaders which permit you to do such conversions.
Don’t know if VLC supports such options.
wwaag
-
So I guess my question is…which version of the video is the true correct version – the one I am seeing in the preview window (which is how I want it) or the one that every player seems to want to display?
They are both correct. It’s a matter of differences in luminance levels between computer displays and televisions. Whenever you (correctly) do a render from Vegas, the luminance range should be 16-235, or in Vegas terms, studio RGB. This is the standard for display of video on TV. However, the normal luminance range for a computer screen is 0-255, or in Vegas terms, computer RGB.. So whenever you “play” a “made for TV – 16-235) video on your PC, the software will automatically expand the luminance range to 0-255 or in Vegas terms, apply a Studio RGB to Computer RGB conversion. If you bring your image into Photoshop, you will see that the whites are 255 and the blacks are 0 in your VLC image whereas the whites and blacks on the Vegas preview image are closer to studio RGB.
wwaag
-
Just lower your bit rate when rendering from within Vegas.
wwaag
