[Mark Barton]

GPU: NVIDIA GTX570
Drivers: 306.23
OS: Windows 7 64-bit
Status: Working

[Mark Barton]

I had this happen earlier in the year. For me it turned out to be when I uninstalled Adobe Photoshop Elements. Apparently Adobe was sloppy in the uninstall and did not remove the codecs they registered. So Windows thought they were there according to the registry, but the files were uninstalled. GraphStudio and Codex Tweak Tool helped out to detect where the problem was. Like you, Vegas and Media Player were impacted by the list of codecs that Windows presents as registered. That is why you see a lot of comments in this forum about not installing just any codecs, especial free ones, as they may be preferred by Windows over the better ones you already had working.

Good luck,

[Mark Barton]

I don’t have an AMD video card but according to Sony, you should have Catalyst driver 11.7 and I found 12.4 on the AMD site. It could be we are just reading different version numbers (Catalyst vs the driver).

https://www.sonycreativesoftware.com/vegaspro/gpuacceleration

AMD/ATI

Requires an OpenCL-enabled GPU and Catalyst driver 11.7 or later with a Radeon HD 57xx or higher GPU. If using a FirePro GPU, FirePro unified driver 8.85 or later is required.

The release notes for Catalyst 12.4 states you have an older driver:
The AMD Catalyst software suite 12.4 contains the following:

AMD display driver version 8.961
HydraVision™ for Windows Vista® and Windows® 7
Southbridge/IXP Driver
AMD Catalyst Control Center version 8.961 / AMD Vision Engine Control Center version 8.961

https://support.amd.com/us/gpudownload/windows/Pages/radeonaiw_vista64.aspx?type=2.4.1&product=2.4.1.3.43&lang=us&rev=&ostype=Windows%207%20-%2064-Bit%20Edition

[Mark Barton]

I have no problems with the Sony glow effect, so maybe it is video driver related. I’m using the same build 683 of SVP 11. I have an Nvidia GTX 570 with the 301.24 drivers. I have the GPU option turned on under Tools/Options/Video. Check the following directory for the GPU and other logs to see if any additional error information was logged.

“C:Users…AppDataLocalSonyVegas Pro11.0gpu_video_x64.log”

[Mark Barton]

I confirmed that I also have a problem with the 32 bit pixel format. See below for the results I got.

I just tried a render at 32 bit pixles with the MainConcept AVC Internet 720p and SVP 11 stopped (crashed). I tried again at but change back to 8 bit and it worked fine. I restarted SVP 11 again and tried at 32 bit once more and got the crash again.

I tried 32 bit again with Render -Customize template and setting the encoding to just CPU (NO GPU). Result was still a crash

Tried again same settings, but now turned off GPU in Tools-Options-Video and left it in 32 bit pixle and Render no GPU. The result was a good render.

This was with the SVP 11 Build 683 with NVidia 301.24 (beta)

[Mark Barton]

I just downloaded the update and tried the same steps you listed. I could not get it to crash. I tried the eyedropper on the video preview window and also within the Media Generator window. I would suspect a video driver problem if it is related to the eyedropper. I’m running 301.24 of the NVidia drivers for the GTX 570. I’m just providing this information so it may help troubleshoot the problem if we know what works.

[Mark Barton]

I usually make the Window bigger or choose BEST-half or BEST-quarter to get it to fit. I have not found a way to select which section of the video you see in the screen. Although recently I hooked up a second monitor and it makes this a non issue.

[Mark Barton]

I am running the latest NVidia BETA drivers with my SVP 11 and can render. If you had chosen the Microsoft update recently, then you may need to select the advance option in the Nvidia Installer to perform a clean installation.

[Mark Barton]

I can’t tell from your reply if you tried setting the Preview RAM and threads. Did you try Best vs Preview for the quality settings of the preview dialog? Did you match the source settings and turn off scaling?

[Mark Barton]

I tried to paste a screenshot of the properties. AVCHD from a Panasonic TM900 1920x1080x32, 60fps progressive.

I am using SATA 2 drives, nothing too fast, but I try to have the source on one drive and render to another.

Operating System
Platform: Windows 7
Version: 6.01.7601 (Service Pack 1)
Language: English
System locale: English
User locale: English

Processor
Class: Intel(R) Core(TM) i7 CPU 970 @ 3.20GHz
Identifier: GenuineIntel
Number of processors: 12
MMX available: Yes
SSE available: Yes
SSE2 available: Yes
SSE3 available: Yes
SSSE3 available: Yes
SSE4.1 available: Yes
SSE4.2 available: Yes

Display
Primary: 1920x1080x32

Memory
Physical memory: 12,279.1 MB
Paging memory available: 12,277.3 MB

It could be related to codecs installed on your system. I googled that a while ago when things stopped working and it turned out it was related to uninstalling Adobe Photoshop Elements 8.0 when I had decided to just use Gimp and Picassa instead. Adobe did not remove the registry entries properly, so the system still was referencing a codec that Adobe installed, but removed. By reinstalling Adobe again, things started working again. I used graphstudio and CodecTweakTool to get additional information to find out that Adobe was the culprit in that case. I built my system speced to the NVidia card, so I have a 800W gold standard power supply to handle the current that card needs and followed many of the recommendations from the VideoGuys.com DIY section as to motherboards that work well with the i7-970 processor. Good luck and if there is anything I can help test with, I would be happy to try and post the results.

In the above screenshot, you can see I set Dynamic RAM Preview = 200MB and have 16 threads. Search this forum showed that setting the RAM too high would impact the preview, even if you have 24GB of RAM available. I also seem to get better results with BEST rather than Preview quality and I can only guess that maybe BEST utilizes the GPU.