Thomas Roell
Forum Replies Created
-
Thomas Roell
February 19, 2013 at 9:32 pm in reply to: Vegas 12 audio skittering, screen buffer (+ bonus crappy Sony Support)SOunds all to familiar to me. In the audio tab you can select the audio device. Per default it’s microsoft’s sourround sound mapper. You might have more success with one of the other 2 entries. The other thing I have constantly been running into is the proper audio driver. Sometimes laptop vendors seem to have some specials somewhere, and you really need to get the right OEM driver for it.
-
The thing I’d do is to first deinstall the NVIDIA driver(s). Lately you get the whole Stereo whatever mess. Then reboot, see what Windows installs as default from the driver store, reboot. Then I’d get the latest off nvidia.com, do a custom install, and install ONLY the graphics driver.
-
A entire compute crash is most likely not the result of using 2 monitors connected to one GPU. On my debugging rig pretty much all the real crashes I am seeing are either recoverable by the graphics driver (meaning only the app crashes), or you’d see a blue-screen (for a stuck IRQ or something). Most times when I see a complete system going down it was either due to a power supply not being big enough (CPU + GPU can draw a lot of power, and depending upon the workload distribution it’s different for every application). Or it’s due to a thermal overload. Latter one can be triggered by an inefficient airflow in your system, or a stuck/bad fan. Worth checking both.
-
I don’t really care about the “again”. I picked Vegas because at the time it worked and did it’s job better than the competition. Vegas Pro 11 is not usable for any real work. I do not see myself subscribing to any religion there. Either it works or not. If not, I’ll pick something else next time around I need to upgrade my HW/SW, right now I can live with Vegas Pro 10.
At the end of the day, if you push out a new product who’s clame to fame is GPU support, and it ain’t working, then in my book you don’t have a new product.
-
The good thing is that one is not forced to switch to Windows 7.
What’s more worrying is that Microsoft seems to force this Metro UI thing onto us throu multiple backdoors, like the upcoming next version of Office.
-
Thomas Roell
February 17, 2012 at 12:30 pm in reply to: Rendering fails in Vegas 11 citing nvcuda.dllAndy,
is there a chance that I can get ahold of a subset of your project ? 0xc0000005 is an access voilation, usually a bad pointer, like a NULL dereference.
285.62 is as far as I understand the recommended, latest driver.
Mind contacting me offline at thomas.roell@earthlink.net ?
-
[Mitch Drummond] “I have been having some odd errors when rendering that I cannot place a pattern to. Quite a few of these have been NVCUDA.DLL errors.”
What driver version (go into the NVcontrol panel, “Help” -> “System Information”) ?
What kind of errors were you seeing ?
-
[Monte Krause] “*** The only thing I can think of people that would be simple to try, is to keep uninstalling and re-installing the application. After each uninstall, clean your PC’s registry and trash any Vegas Pro 11 leftovers to help insure a clean re-installation. ***”
I do exactly that every time Sony Creative comes up with a new update to SVP 11, and after about 30 mins I give up yet again because it’s still too flaky (and slow in many places) compared to SVP 10e.
My theory is that I simply need to always upgrade to the newest version of SVP n, but really wait till SVP n+1 comes out before I can use SVP n.
-
[Monte Krause] “I don’t expect Vegas to perform like Premiere, but for once, I would like a version to be stable.”
Tell me a single reason why Vegas should not perform like Premiere.
-
Thanx for sharing some inspirations with me. Seems like a shared theme. Not a lot of material and not a lot of time.