David Alfredo
Forum Replies Created
-
as I suggested above try running Vegas with just one GPU, swap if it fails again, maybe one them is not working well in Vegas with latest Forceware drivers.
-
ok
– go to your Windows drive:\Users\YOURUSERNAME\AppData\Local\Sony\Vegas Pro\12.0\Media Pool Thumbnails
example C:\Users\David\AppData\Local\Sony\Vegas Pro\12.0\Media Pool Thumbnails
-delete the content inside that folder
restart Vegas, check again.
-
hold down ctrl+shift and click the Vegas shortcun icon, wait until it open the user interface and release the keys, now Vegas should be in default settings…
btw with your system specs Vegas should be running quite smooth… and you should have GPU acceleration enabled for whatever card you want to use, you can even access the Nvidia Control Panel and specify which card will be used as a CUDA renderer (use the one with more CUDA cores) accelerator and which will be accelerating Vegas editing (use the one with largest VRAM buffer and memory bandwidth).
[Larry Brewer] “BTW, the ProType titler issue seem to begin with the update to build 563.”
well so here we have the root of the problem, guess we don’t need to look further, have you tried reverting to the former version you were using and trying Titler there? in case it is then I’d try to uninstall that build, perform a registry clean (Google CCleaner, it’s a free tool) restart Windows and perform a fresh install of the latest build (563)…
there’s no reason it shouldn’t work for you, but I have a feeling it could be GPU drivers, some drivers don’t behave well with different GPUs… make sure you’re using latest Nvidia drivers, WHQL 314.22, if the problem with titler goes on I’d try using only one GPU (uninstall the oldest one, turn off your PC, unplug from mains, open the case, unplug the card from the Power Supply Unit) and check Vegas again, if you already have 314.22 installed try reverting to some older drivers such as 314.07 and check again.
-
[Robert Mathison] “No special video cards, just what was installed onboard.”
taking for granted GPU acceleration is disabled in Sony Vegas, it should be by default.
non-common pixelated renders could come as result of poor CPU performance or incorrect overclocked CPU, poor GPU performance or buggy compatibility, corrupt RAM, corrupt codecs (try reinstalling Vegas)… start by re-installing Vegas, disabling GPU acceleration, checking RAM performance and stability with Windows Memory Diagnostic, checking CPU performance and stability with Prime (Google it)… this is an issue not easy to trace back to the root of the problem. At the end of the day it could very well your source material not being high quality and rendering compressed videos, thus exhibiting artifacts.
-
please more details like… operating system ? graphics card ? GPU drivers ? DirectX versions installed ? KB2670838 update installed ? .NET Framework 3.5 and 4 working and updated ? running overclock or stock hardware ?
to begin with, try starting Vegas while holding down SHIFT+CTRL (reset settings to default) then disable GPU acceleration if it’s enabled, try Titler again, keep us posted.
-
excellent post Norman, and yes, Vegas Pro 12 invokes its own codecs as I was able to identify running a process monitor showing files opened by software, I encoded some mp4 on Adobe Media encoder while rendering a mainconcept template on Vegas (thanks 3770K multithreading) and different x264 codecs in different folders were being using by each, so pretty much as long as you install Vegas after you installed your codec pack you’re mostly fine.
-
does installing Vegas after installing the codec pack replace those with the high quality ones from Sony ?
a while ago I tested with a fresh and “clean” install of Windows 7 Ultimate 64 and one with the latest K-Lite Codec Pack, installed Vegas Pro 12 afterwards and perform some testing, got same results on both computers, so that’s why I think Sony replaces back the codecs if you install Vegas after the codec pack is already installed.
edit: after some file activity monitoring it seems Vegas Pro 12, contrary to Pro 11, invokes its own codecs installed in a different folder than those for general use installed by Windows or whatever codec pack.
-
also, these Sony AVC templates are the first to properly support the GTX 6xx series for rendering with latest Nvidia drivers installed, but the new renderer is still beta, that’s why the rare bug working with the 1080p template, the first step in the good direction is the greatest step.
-
[John Sieber] “But has anyone noticed that the file size created from both new (old) Sony AVC render templates is the same? In fact, I’m getting a slightly larger file from the 720p as I am from the 1080p (using the default settings in those templates). Should it be?”
Internet 1080p template using Sony AVC renderer is glitched-buggy on some systems, it skips a lot of frames, that’s why the size is smaller than 720p which works nice. I’d recommend using CPU only if you run into this bug.
-
I observed that every track you add, even if empty, gets some amount of CPU time and RAM reserved that get increased when actually filled with “content”.