David Alfredo
Forum Replies Created
-
see attached pic, it’s impossible to miss if you have used the plugins at least once.
-
go for the 16 GB, then setup a virtual RAM disk for your Vegas projects, watch editing and rendering speed increasing ten-fold.
-
I heard that NVENC will be finally supported through PhysX and NLEs updates, the reason is simple, the new 7xx cards are based on the same architecture as the 6xx GPUs, at first devs were waiting for new cards which would bring backwards compatibility back, as it’s not the case and 5xx GPUs and lower are discontinued they have to start supporting Kepler architecture now, even Sony intend to do so in Vegas 12-13.
-
[Stephen Mann] “Since the Font Cache loads all of your installed fonts in RAM, it denies that RAM from other programs. Some power-users delete fonts they will never use. Also, if the Font Cache service encounters a bad or damaged font file, it may just keep retrying to load the bad font – forever. (High CPU usage and “not responding” are symptoms). (I guess the programmers at MS never thought that you could have a bad font file?)”
very good observation, this is specially critic if you use Google Chrome before using Vegas, since there’s a Chrome bug if a font is not properly installed or corrupted it would cause high CPU usage (100% load on one core) and weird crashing / issues to whatever software you run after that. I never use Google Chrome when I need to run Vegas, also deleting the fonts cache from time to time does help, very good info.
files to look for and delete from time to time:
fontcache3.0.0.0.dat
fontcache-fontface.dat
fontcache-system.datusually located in bootdrive :Windows ServiceProfiles LocalService AppData Local
-
[Mike Ryder] “I guess its probably an error with Vegas 9, rather than an issue with my specs. Are things like this a common issue?”
since GPU acceleration was added in Vegas Pro 11 the common issues are almost all related to that, GPU acceleration, so it’s just a matter of getting the most compatible card for Vegas (Nvidia GTX 570).
-
the 630 is a very weird card, a modified Kepler GPU aggressively crippled to be placed in the low-budget market segment, its architecture isn’t suited for computing/CUDA, just gaming in medium-low settings environments, what I find annoying is that they are putting 4 GB of VRAM in this board just to make it attractive to casuals, we do know the 630 GPU runs out of rendering power well before it hits more than 1.5 VRAM usage so the extra VRAM is pretty much useless, the most Vegas-friendly Kepler card out there besides the latest Quadros (of course) is the 660 Ti 3 GB, 3-way 192 bit bus working at full speed with 3×1 GB GDDR5 RAM modules and same drivers optimizations as those of the 670s and 680s, the rest of the 6XX cards use different, less-mature, more gaming-oriented drivers.
-
[John Rofrano] “Also WMV is the worst format to be rendering to becasue it’s not GPU accelerated and takes a lot of CPU. I would render to MainConcept AVC using the Internet HD 720p or 1080p template and enable CUDA in the template so that it takes advantage of your GTX 660 Ti GPU.”
a couple of comments, for Vegas to take advantage of the 6XX series GPU, latest Nvidia WHQL drivers are required, and the support for Vegas is in beta, so it’s a bit of hit or miss, using Sony AVC/MVC templates forces Vegas to use the 660 Ti, way quicker renders if you don’t mind AVC instead of Mainconcept.
-
[Tim Neighbors] “I recently installed some new RAM, a PCI to USB3 card, and a eSATA card and that’s when the problem seems to have started. At first it would just shut off without warning”
check if your power supply can deliver for the new hardware installed, also there might be compatibility issues, use latest drivers, contact manufacturers… as for the RAM you should have bought same stick, same manufacturer, same density and same latency (specially CAS)… the problem is not that as it persists without the new RAM but just a suggestion for the future.
-
[John Rofrano] “No. Vegas Pro will only see one card so SLI makes no difference.”
I hacked Vegas Pro 12 to use one card for previewing acceleration and something else for rendering, I believe it’s illegal to share that hack I made to the software since it’s punishable in most countries to modify the software in any way, in my country you can alter the software you paid for and own for research or private use only. I hope next version of Vegas includes native support for multiple GPUs, since 6XX series act so weird I sometimes need to switch over to the GTX 570, but the 660 Ti is much faster with NewBlue Titler Pro 2.0 and Sony AVC templates… Quadro decimates both of them at workplace though.
The hack was easy, just change a couple of pointers, basically use device X when previewing/editing and device Z when encoding. I tried to brute force Vegas to use both cards for encoding but I noticed it would send the same data to encode for both cards and crash immediately, need to split rendering jobs to send to either card and consolidate results after encoding is done, something I don’t have the time to do… for now.
-
only 4 GB ? that would be some old / low-tier motherboard…
the reason behind needing at least 8 GB is for rendering medium-large projects, not 5 minutes clips. Even those need a lot of RAM when multiple plugins / video effects are in use… if Vegas can’t find the physical RAM it would use the hard drive for paging, making the software crawl. If you’re capped at 4 GB you should stick to 720p, low bitrate projects or very short ones.
