Norman Black
Forum Replies Created
-
[John Rofrano] “[Norman Black] “NVenc outputs AVC/H.264.”
I wonder if you can use a tool like tsMuxeR to re-wrap the MPEG4 video in a new container that Vegas will play better with?”Or maybe even Avidemux, or Cliptoolz convert to rewrap video into to MP4. Audio would need converting to AAC if it is PCM for AVC MP4 files in Vegas.
In an AVI file for AVC I would assume Vegas is going through Video for Windows. Getting Vegas to use the native Vegas decoders may give better performance.
Anyway we still do not have any specs on the source video the OP is having problems with. Hard to comment further without info.
-
NVenc outputs AVC/H.264. Why don’t you give us a MediaInfo report on the file you want to use in Vegas. MediaInfo is a free utility program.
AVC can be time consuming to decode, and the Vegas AVC decoder can be quirky with some AVC output. GoPro AVC files are a well known issue with Vegas decode performance.
-
Norman Black
May 2, 2015 at 7:55 pm in reply to: Custom FX Chains — easy way to apply w/out going thru pulling up the interface?Search the help index for, filter package. Should get you the info you need to know about creating and using filter packages.
Here is a link to the web help info. It should be the same as the Vegas help menu.
-
Speed of upload depends on the size of the file you are uploading and the size is solely dependent on the bitrate you choose.
At very low bitrates MC AVC is probably better than Sony AVC but if you are targeting those low bitrates then neither Vegas AVC encoder is really very good.
If you are targeting 28Mbps (20+) for 1080 video, then that is very high and everything should look the same. Do a test. Trust your eyes. A simple test will show you more than anything anyone on the net can tell you.
Uploading 28Mbps 1080 video to Youtube/Vimeo is massive overkill and will simply make your uploads take a long time. Their re-encoded bitrates are around 7-8Mbps for 1080. They are using a high quality encoder so using the Vegas encoders I would pad that number up some. The Vegas “Internet 1080” templates should be a good choice.
Those templates will probably give you good general quality when you look at them, or even just a little higher.
Camera bitrates are higher because they do not do very much compression at all. They do not have the compute power or time to do such things. They absolutely must encode in real time. With most, but certainly not ALL, source material the bitrates from a PC encode from sources can be dramatically lower due to the better compression analysis they can do.
-
Norman Black
April 30, 2015 at 2:54 am in reply to: Upgraded GPU, cannot render with GPU now (Vegas 11.0 build 511 64-bit)[Anthony James] “Furthermore, Sony AVC is not recognizing my GPU and renders just as slowly as MainConcept.”
My 2x comment is in reference to CPU use. I have only used VP12 and VP13 and in these Sony AVC is about 2x faster than MC AVC, pure CPU.
Also to be clear, these two encoders are the only two in Vegas that might use GPU for file encoding, and the encoders have their own GPU option in the render template which is independent from Vegas video engine use of GPU which is controlled via the video prefs option.
-
Norman Black
April 29, 2015 at 11:15 pm in reply to: Upgraded GPU, cannot render with GPU now (Vegas 11.0 build 511 64-bit)[Anthony James] “So what are my options here?”
Mainconcept AVC is what it is and it is a fairly slow encoder compared to most others. For AVC targets you can try Sony AVC which should be ~2x faster than 1-pass Mainconcept AVC.
-
That is really long. It is very highly unlikely HD speed has anything to do with this.
When you ask a question about rendering, it helps if you provide information about what you are using/doing.
From the speed it sounds like you might be rendering to Mainconcept AVC in two pass mode. Mainconcept AVC is a pretty slow encoder. If AVC is your target then Sony AVC is much faster.
-
Norman Black
April 29, 2015 at 4:37 pm in reply to: Upgraded GPU, cannot render with GPU now (Vegas 11.0 build 511 64-bit)Mainconcept AVC does not support newer GPUs. It is hard coded to specific GPUs and Mainconcept has not updated it for years.
For Nvidia this means 6xx (kepler) and newer are unsupported and for AMD 7xxx (Tahiti) and newer.
-
Norman Black
April 29, 2015 at 5:52 am in reply to: Custom FX Chains — easy way to apply w/out going thru pulling up the interface?[Rob Lindsay] “…but it did not stay on thru the bins”
Not sure what you mean by this.
Did you create a filter package from your FX chain?
-
Norman Black
April 29, 2015 at 3:34 am in reply to: Custom FX Chains — easy way to apply w/out going thru pulling up the interface?You can save a VFX chain as a filter package but you have to bring up the plug-in chooser dialog to apply the filter package to an event.