Norman Black
Forum Replies Created
-
GPU load…
There are two separate GPU uses in Vegas and each has its on on/off setting.
As for the encoders, Sony AVC and Mainconcept AVC are the only ones that can use GPU.
Sony AVC does not use GPU very much but you should get a small performance boost from my experience. I do see some GPU load in GPU-z on my system. I cannot comment on Nvidia use as I am a AMD GPU person.
The Quicksync option in Sony AVC is another matter. It is actually a separate encoder. It is an interface to the hardware encoder built into Intel chipsets. Sony AVC code is really bypassed in this mode.
Vegas can use the GPU for creating the video stream but that use depends on what you are doing on your timeline. In other words, Vegas may or may not use GPU depending on which features you are using. If Vegas is using GPU here you should see some load during playback as well. If you want to test this then use “full” for your preview to get more work on the GPU so measurements are the most apparent.
-
Define slow? In other words, what are you getting and what were you expecting?
Have you rendered on the same machine with the same template and got something not slow?
Are the sources the same (camera+settings) as previous file renders of acceptable performance?
Are your project settings the same as your sources and template?
-
Track motion. Everything gets the same crop.
However, if your source files are larger than your project size, like stills, then the image quality is typically better when using pan/crop.
Track motion is done after any scaling is performed to the project size. Pan/crop is done before/during the sources being scaled to project size.
If you want to apply the same pan/crop to a bunch of events should be able to use paste event attributes.
-
Interesting. The update frequency. I wonder if Sony is opting for a more frequent update schedule, with a resulting fewer number of items in updates list.
-
Your source file(s) probably have a range of 0-255. You can use the video scope to see this. “Proper” levels are 16-235 for REC.709 which is HD color levels.
So when you playback on a computer the player expands the 16-235 range to 0-255 which is what computer monitors expect. This increases contrast, crushing the blacks and blowing the whites.
The Vegas preview system does not assume any kind of input levels and so does nothing to the input data when displaying. This is unlike a typical video player.
So on Vegas preview a 16-235 input source would look washed out in preview, and the resulting playback would like fine. A 0-255 input would look fine on preview and boosted on playback.
For my GoPro video input (0-255) and jpegs (always 0-255) I put a computer to studio preset levels effect on the output. I leave it there always, and I know the preview will be a little washed which I don’t care about unless I am judging color and then I can turn it off. I leave it there always so I don’t forget to put it there when I encode.
-
When you say 59.94 does not exist as an option, exactly what were you looking at?
59.94 does exist in project properties.
“render As” templates…
It(59.94) does not seem to exist for Mainconcept AVC as a drop down option but you can enter the numeric value.59.94 does exist for Sony AVC as a preset option.
I don’t know how you can render Xvid directly from Vegas. What render template? I do not see one.
-
No need to go higher than the source bitrate when staying in the same codec.
GoPro files are AVC. If you are encoding to an MPEG-2 format, then there is a use for a higher bitrate than the GoPro source file bitrate. This is because AVC compresses better, and can give more detail at the same bitrate than MPEG-2.
I also have a GoPro Black and at the high bitrate AVC the Black can do, it is amazing the fine detail that “cheap” little camera can give. 35 Mbps VBR XDCAM and 50 Mbps XDCAM cannot quite preserve the fine detail of the source. Both are mepg-2. Only AVC at the same settings and high bitrate intermediate formats like DNxHD preserve the source.
My videos are on my mountain bike and I have a lot of fine brush along the sides of the trail and this is the fine detail I speak of.
-
Which GoPro and what is the video mode you recorded your video in on the GoPro.
I have a GoPro 3 Black and have not had any problems. I have recorded 1920x1080p60, 1920x1080p30, 1280x720p60 and 1280x720p120. I have always rendered as AVC (Sony or Main concept). I watch my vids on my TV as output from a nettop PC via HDMI. I always let Vegas match project properties to the first video stream. I always changed the project back to 30p since the higher rates were recorded for a little better slo-mo when applicable.
The GoPro does have 4:3 aspect video modes, and my Black actually defaults to one of these modes.
When I say 30p I technically mean 29.97. 60p is 59.94.
-
HD 1080 is actually about 2MP.
If you are not doing any crop/pan/zoom then resizing the stills to your project size, say 1920×1080, makes sense. Otherwise leave some room so your crop size never goes below your project size. Otherwise you are magnifying which loses detail.
This is why I sized to about 4.3MP (2400×1800). It left room for crops and no crop goes smaller than a 1080 height which was my project size. Vegas performs well with this image size on my 2.9Ghz machine, and I had more than enough room/freedom to do what I wanted with crops.
On Best quality render setting, Vegas uses Bicubic interpolation which is the same general algorithm Photoshop uses, and Vegas does a good job IMO. Good quality uses Bilinear interpolation. Of course saying the algorithm is the same is not to say they are identical. Only quite similar.
When resizing in Irfanview or Photoshop or whatever, use a very high quality setting. In Photoshop setting 10 or 11. Irfanview 92+ percent, and disable chroma subsampling. You are just trying to keep the compression level similar to that of the digital camera source, which is very minimal compression.
-
Jpeg sizes?
Project properties: full resolution rendering quality?If your stills are larger than your project then full resolution rendering quality must be Best. It defaults to Good. The only difference between Good and Best is image interpolation quality and this(interpolation) happens with large stills being resized down to the project dimensions. Also, having GPU enabled can greatly enhance preview video quality since you get a higher quality interpolation with GPU than the preview level normally gets.
On a side note. Vegas performance can slow down with large stills with pans/crops/zoom. On a stills project I did with 12MP stills I batch resized them to about 4.3MP. A few were left full size as they had big zooms. You can use Irfanview or I used Photoshop to easily do a batch resize.
I have only ever rendered an 1440×1080 24fps progressive stills project. My edit/playback window is set to preview(half) and it is sized to exactly half. I turned preview window scaling off. This just minimized the number of interpolations for best quality preview. It does not affect render as. My render as, was to AVC (Sony or MC) and anywhere from 8Mbps an up bitrate looks great.