Hi everyone,
As all my work now is in UHD 4K, I have to upload many videos to Youtube.
From what I see in Vegas Pro 14, it is still the same as was in 13: the MainConcept mp4 is very slow to render and does not support my GPU. On the other side, Sony AVC might be faster but maximum bitrate to choose from it too low (26Mbps).
Is there any other option to render 4K 50Mbps in mp4?
Thank you.
I guess we don't have alternative option for this, only able to use Mainconcept's MP4.
As YouTube does not (yet?) accept H.265 HEVC, the only workaround I could offer and which I use for my own YouTube videos is to use HandBrake. Its H.264 output is superior to MainConcept AVC especially in details.
There is a workflow which takes some time for installations and configs but then will allow to use HandBrake almost as if it'd be a Vegas Pro plug-in: Vegas2HandBrake
What you get there works fine in Vegas Pro 11, 12, 13. To use Vegas2HandBrake within Vegas Pro 14 it would need three additional modifications described in this posting.
Thank you Marco.
Marco, have you considered crowd sourcing to make development of V2HB more sustainable as if a product?
Haha, nice idea but even a million bucks would not make me a coder. I'm glad this workflow seems to work for most who tried it but actually it is only a very, very rough and awkward conjunction of tools of others, once made for my personal use. I have zero idea how I could further improve it from here (I was so glad to see there is an easy way to make it work in VP14).
I wish Magix would see how poor quality of both MainConcept AVC and Sony AVC is compared to x264 delivered by tools like HandBrake and offer better ways from within Vegas Pro itself. Build-in frameserving could help a lot (if the frameserve file could be read by tools like HandBrake).
"Build-in frameserving could help a lot (if the frameserve file could be read by tools like HandBrake)."
Since I did the testing on the last iteration of Debugmode Frameserver, I've found it fascinating that DVD Architect reads the output file but Vegas itself can not / does not.
WRONG...
#1. YouTube Quality is 2.5Mbps, or 2500Kbps... at FullHD 1920x1080 4:2:0 YUV
it was higher long ago, but now because the volume of videos uploaded,
YouTube down converts all files to 2.5Mbps, aac 128kbps.
if you Upload at higher bitrate,
A. You are loosing time uploading...
B. You are loosing time waiting for Processing...
Is better to encode as slow as possible with a 3-pass at 2.5Mbps, to keep as much detail as possible in the highs and shadow areas, also fast moving scenes/objects.
#2. Sony XAVC S allows 100Mbps at 4K,
or 50Mbps at 24p FullHD.
24p has higher quality than 30p at same Mbps.
working at lower frame rates gives higher quality with same bitrate.
"Build-in frameserving could help a lot (if the frameserve file could be read by tools like HandBrake)."
Since I did the testing on the last iteration of Debugmode Frameserver, I've found it fascinating that DVD Architect reads the output file but Vegas itself can not / does not.
Unfortuantely, only 32bits application can read frameserved files
Meanwhile the open source Frameserver code is begging for someone to go and fix the audio glitch and make a 64-bit version.
Would that "someone" be Satish or Marco? They have given so much...
Would that "someone" be Satish or Marco? They have given so much...
That's a "negative" I'm afraid.
"Sorry Nick, never found the time and I've basically given up on it by now :( The only hope I have is someone would take up the open source code and improve it going forward." - Satish
"Haha, nice idea but even a million bucks would not make me a coder." - Marco
IMO it would make sense for Magix to fund it, or write their own.