Norman Black
Forum Replies Created
-
Vegas also supports Quicksync via the Sony AVC encoder. Most of us have video cards installed so to get Intel video working without a monitor connected AND also have an AMD/Nvidia card takes a little work but it can be setup. Of course if you have two monitors and one is connected to Intel and the other to you video card then there is no setup.
-
Proxies in Vegas are automatic. Nothing to do other than create them. The proxy will be used whenever your preview mode is Preview or Draft. In Good and Best the original files are used.
You say “mp4” like that means anything. MP4 files are just a generic container and they can contain just about any video and audio codecs in combination. Vegas only supports a few of them. AVC and XDCAM mpeg-2.
Vegas proxies are XDCAM EX video in 720 resolution. This is an mpeg-2 codec which always edits better than AVC/H.264 video in my experience.
-
If what you render from Vegas looks good on playback and the Youtube result does not, then there is NOTHING you can do.
Youtube re-encodes everything uploaded to their own spec. Their spec is very low bitrate and very often game material does not compress well enough to maintain a certain visual quality. This has nothing to do with some magic encoding setting. It is entirely dependent on exactly what is going on in the video at at every instant in time.
Again, if your encode looks good, then how is it possible that giving Youtube something different can possible help. The loss of quality is entirely from the Youtube re-encode. If someone elses game video looks better then the the specific sequence of frames in their video just compressed better into the low Youtube bitrate than yours did.
https://support.google.com/youtube/answer/1722171?hl=en
-
Sony AVC should be about 2x the speed you are getting from Mainconcept.
If you want to do other things on your machine while Vegas is rendering just set the Priority of Vegas in Task Manager from “Normal” to “Below Normal”. Then anything else you do on the machine will get priority and if you are not doing anything then Vegas will still get all the CPU time.
-
GPU crashes can happen in any Vegas version and for dozens of reasons. There is no “A” reason. A lot depends on the driver is this regard.
That said, most have found that Vegas 13 is more stable for them than previous versions with regards to GPU.
-
Wayne: Thanks for the conversion settings. I do have Vegasaur but I think I can easily enter those values. I don’t think I need a 709 to 601, but I guess it couldn’t hurt to have it.
Grazie: The issue with 601 matrix being used is well known thing that can happen on with libavcodec/ffmpeg and certain encode conversion. t Prodad is using this code for encoding. That code defaults to 601 and you have to change to 709. Prodad is apparently running with default. The color shift is so small that they probably don’t realize it is happening.
-
Can you describe this 601 to 709 conversion filter mentioned. What are the channel blend settings?
-
What specifically is wrong with the video? I watched it and it plays fine.
-
[John Rofrano] “The last time I checked, the M-JPEG files created by 2.6.8 can’t be read by Windows or Vegas Pro.”
Just tried 2.6.10 in MJPEG. VLC plays it, but with an error of some sort. Vegas does not like it.
-
Once upon a time 2.6 was new, and less stable, and the internal structure of Avidemux was changed from 2.5 to 2.6. The last 2.5.6 version was 2011.