Norman Black
Forum Replies Created
-
[dan crossland] “I record in 1080p 60FPS wide and again the quality is flawless until It’s uploaded to YouTube. In addition, my first post has my Photobucket link to some specs I tried out of a tun I used.”
Youtube is 30p of less, so do not bother uploading anything 1080p60. Encode your 60p (59.94) to 29.97 for upload. With resample turned off in Vegas, then every other frame will be removed.
Your photobucket link does not work. It says the library is private.
-
I am with Dave on this one. I have a mountain bike videos where the GoPro is mounted to the bike and the bike is moving and bouncing down the trail with high detail surroundings. Very hard to get high quality with the low bitrates we get from online services. My stuff is on Smugmug.
Another thing, is when you are outside in bright light with a GoPro you get very high shutter speeds. This gives crisp detail. A “normal” video camera would likely have a slower shutter and fast movement would blur the image, and blurry stuff compresses very easily. So the typical GoPro action footage really puts stress on low bitrate encoding.
If what you upload to Youtube does not go blocky or have problems then you are having low bitrate problems. No setting can fix this. Youtube encodes to a certain bitrate no matter how high a bitrate you upload to them.
Something that helped me was to stabilize the video. I use a very light touch and turn off most settings. Handheld or helmet mount would probably leave more settings on than I use. I use Mercalli 3 SAL and my avoid border setting is 10 and my smoothing is also 10. Both very lower numbers. What this smooths is the small quick movements while leaving the “real” moves. With the bike on even a smooth trail there is a micro buzz.
When watching your video I notice it suddenly going blocky and then coming back. The blocky sections are coming from sudden jarring movement while running/moving/bouncing. A bouncy camera. Stabilization can help this. Also it goes blocky on really fast pans. I do not think stabilization can help here. You can probably put a linear or motion blur type effect on fast pans. Blurry stuff compresses better. People understand blur on pans, where blockiness is yuk. Or edit the worst of the pans out.
Just now I am doing a high speed timelapse like thing for an MTB video. I have had to resort to masking off the edges some, with a plain border, to create some invariant pixels which will compress perfectly. This leaves more bitrate for the rest of the stuff and I then get higher quality.
Of course high bitrate stuff never has any issue.
-
[John Rofrano] “You can buy a plug-in like VASST Still Motion for $9.95 USD”
StillMotion is Awesome.
When I did a big slideshow project a while back I wish I had StillMotion for the whole time. I found out about it about half the way through doing the project.
-
Look at your editing preferences. “Automatically overlap multiple selected media when added”. You can only do this at the time you add things to the timeline.
After things are on the timeline, then utilities like Vegasaur have numerous functions to automate all kinds things like this. The kitchen sink really.
-
All DNxHD is 422, unless it says 444.
The 1080p23.976 DNxHD 175 8-bit would be your highest quality to cover the camera output without needless overkill.
DXnHD bitrate varies by frame size and bitrate, so at 1080p29.97 your choice would be 220.You only get 4:2:2 from a 5DMkiii if you recorded via the HDMI output. Files recorded to flash are always 4:2:0. Either way you would still use the same DNxHD setting.
-
You may have hit an internal file size limitation on the video file. Actual file size, or the max number of frames in a file or possibly other things we do not know about.
You never mentioned what your render parameters were.
-
You can target a file size by computing the bitrate.
For example, if you have a video 60 minutes long (3600 sec). 2GB max (2,147,483,648)(2*1024*1024*1024).
2147483648 / 3600 = 596,500 bytes per second (rounded down).
Bits per second (bytes * 8) = 4,772,000.This is the sum of your video and audio bitrate. If audio is 128K bits per second, then you know what your video bitrate can be.
128K = 128 * 1024 = 131,072.There are bitrate calculators around online you can use but the math is simple.
If using Sony AVC or Mainconcept AVC round down a little since they are not perfectly accurate in hitting your target bitrate. Sony AVC is better at this than MC AVC.
However I would suggest using Handbrake, or similar tool using the x264 encoder, to render your final file for best quality. If using Handbrake use two pass, target bitrate mode. The x264 encoder will nail your target bitrate.
-
The custom dimensions in going to be your limiting factor.
Anything MPEG-2 is about as fast to decode as anything. The Vegas smart proxy uses XDCAM which is mpeg-2 but that does not allow custom resolutions. If the file is always intermediate then you could render standard and crop off the excess stuff on entry. Just a guess.
Cineform is free to download and supports custom resolutions. You have multiple bitrate qualities to choose from. The free GoPro studio is how you get this codec. Cineform is found in the Video for Windows render as templates. Fast encode and decode.
You might think of using Mainconcept AVC, with Baseline profile and a suitably high bitrate to be visually lossless. What is suitable all depends on what your source file(s) are. The Baseline profile turns off things that slow down decoding of AVC video. MC AVC can be slow to encode.
Sony AVC does not give you enough control to select Baseline, and it is bitrate limited.
Things like HDCAM SR, XAVC Intra or DNxHD do not let you do custom dimensions.
-
When you have source video in computer full range…
Use a Sony levels fx, with a computer to studio levels preset. You can put this on your Output FX and everything will be adjusted to normal video levels for encoding. In this specific scenario you would only enable the effect when rendering to your 720p MP4 file.
-
From my video, the same as most the recent Vegas 12 Build 770.