Norman Black
Forum Replies Created
-
A productivity tool like Vegasaur has a “presets manager” you can use. I am sure other productivity tools have this as well. Sony has a free one, and its features may be enough for you. Search for “sony preset manager”.
As for where the files are saved, I think on Windows 7 they are in the one of the hidden “appdata” folders. In this case, roaming.
C:/users/yourusername/appdata/roaming/sony/vegaspro/12.0
The other main appdata folder (local)
…/local/sony/vegaspro/12.0has stuff for internal vegas use specific to the current install.
-
Action safe is the outer box.
title safe is the inner.These are defaulted to 10 and 20% and you can change them in your video preferences. These are historical values from the CRT tube era.
In the modern digital era you can probably go to 5% for TV safe viewing. Actually my TV has a mode than completely drops the overscan and I must use this when viewing my nettop PC output on the TV. I’ll bet others have this as well.
No doubt others know tons more than me about why you have two safe settings. Is one safe and the other extra safe?
In my mind safe is safe and therefore you should only need one safe setting.
-
This is a known bug in Vegas titles and text. They say it is known, and will be fixed in a future update, but nothing ever happens over 2-3 updates while I have known about it.
For me the problem seems to be with OpenType fonts that contain postscript outlines/glyphs. OpenType fonts with Truetype outlines and Truetype fonts seem to work fine.
My problem fonts are those that Adobe Photoshop installed.
-
Update: Blu-ray levels 4.1 and higher require 4 slices.
In Vegas the Sony AVC encoder cannot go to bitrates high enough for level 4.1. The Mainconcept AVC encoder is allowed to go that high and the high bitrate MC AVC Blu-ray templates default to 4 slices.
-
A slice divides the frame into multiple independent pieces. Each encoded independently. So with more slices you lose some compression efficiency.
AFAIK, Blu-ray requires 4 slices in its specification. My only info on this is from years ago when the x264 encoder was not Blu-ray compatible until it supported slices.
It is easier to implement multiple slower very simple decoders in hardware than a faster more complex one. Blu-ray allows for very high bitrates and this (slices) was one way to lower cost of Blu-ray player decoders.
-
-
To me more CPU speed may be your key. RAM is easy to detect, and change, when you need more if your projects need it.
My machine is a Core i7 860 2.9Ghz. 8 logical cores, 4 physical.
8GB ram, AMD 7950 video card.My videos are from my GoPro Hero3 Black I attach to my mountain bike. They are MP4 AVC(H.264) files at 20-30 Mbps bitrate.
The videos are typically 1080p30 (20Mbps) or 1080p60 (30Mbps). I did test 720p120 (30 Mbps) once for 4x slow mo at 30p.
As I said, my machine just does run out of gas with AVC 1080p60 files, preview quality half size. This is in a 30p project. They only gas out just barely. As stated mpeg-2 or Cineform proxies decode with room to spare. I briefly did a test of a 3.4Ghz machine and it handled the 1080p60 GoPro files.
I only have a single monitor so the max I view at is half 960×540. Everything has played real time with what little effects and transitions I have done. Some titles and text animations slow down.
With jpeg sources for slideshows I do get playback performance issues in various circumstances. jpeg size being the biggest concern.
-
You need to give detailed information for any response.
Project settings.
Source file(s) formats. mpeg-2, h.264, ?The hard disk is very unlikely to ever be a bottle neck for HD 1080 video.
If task manager says you still have free RAM you are probably okay there.
With CPU percent utilization you have to be careful. When most people say they have 8 cores, what they have are 4 real physical cores with with logical cores. Hyperthreading is the common term. Logical cores really only give you an extra 0-20% boost. So when you are at 50% you are pretty close to maxxed out in a real sense.
Even with less than 100% CPU, if the task of a single program thread, which runs on a single core, is the bottleneck you are typically screwed no matter how many more cores or threads you have or add.
For example. Decoding an H.264 video stream appears to be single threaded in Vegas. If I take a 1080p60 file from my GoPro Hero3 Black, Vegas has stuttery playback on my machine with only 15% CPU utilization. Vegas is not really using 3 of my four physical cores. A 1080p30 file works fine. If I proxy the 1080p60 files it works fine. Vegas 12 smart proxy files are mpeg-2 which is easier to decode than AVC/H.264/mpeg-4.
-
Interesting, and sad, thing is that Vegas actually has to support the multiple video bus mechanism internally because of support for nested projects (veg). Each project (veg) has it’s own separate single bus that video tracks are mixed into. So a veg with an imported veg effectively has two buses. A shame that Sony does not expose this to us in a more general manner with user video buses.
-
I have a Hero3 Black. I am not sure what you mean by “best”.
I have viewed 1080p24 and 1080p30 from a Nettop via HDMI to my TV. I did try viewing a 1080p60 briefly from the nettop. Mostly for curiosity, as I wondered if the nettop could handle it.
As for “best” I would say go with 1080 as this is typically the native resolution of TVs. My 1080p60 files are typically dropped to 30p for my final render to keep file size down. 30p is enough IMO and I only filmed in 60p in case I might want to do a little slow mo. The one 24p file I did was a slideshow of stills.