Norman Black
Forum Replies Created
-
CPU only render as is for the file encoder. Vegas is actually “rendering” the video stream from your sources to show you in your preview and/or send to the file encoder.
So there are two separate things that may or may not use GPU and have their own separate settings to control that use. Vegas (video prefs) and the Sony or Main Concept AVC encoders.
GPUz might still show some load with all GPU in Vegas not used as the video card is being used for some things. Not sure of the specifics of what GPUz is actually measuring for the GPU load sensor.
-
A lot of the Update is back porting various Windows 8 only APIs to the Windows 7 platform. This would allow a program to use the supposedly better APIs available in 8 and still work on Windows 7. Otherwise the application would need unique code paths.
It seems IE 10 is using some of these APIs and wants the platform update.
-
It appears to only affect hybrid graphics setups. It made to change in my setup.
GPU problems on my slideshow project on pan/crop/rotate. Video projects are fine…fingers crossed.
I have a desktop machine and an AMD 7950 card.
Vegas uses OpenCL for GPU acceleration. NewBlue Titler uses OpenGL.
-
I like that idea. I’ll submit the suggestion also.
-
If you want to use something else, plug-in style, then take a look at Boris Graffiti.
-
As usual, it all depends on what is going to play the file. Encode for that playback device capabilities.
I would not worry about USB drive data speed. 20Mbps video is only 2.5MBps data rate. 2.5 megabytes per second is a pretty sedate data speed. It may be possible to buy something insanely slow these days, but I doubt it. Even really cheap drives these days should do 10MB per second.
Of course this says nothing about the devices USB port. Computers are no worries. A TV or Blu-ray. It is conceivable they may not have the speed to saturate the USB 2 bus. But saturating the USB bus means something like 30MB per second.
-
I found that setting preview ram to zero made the GPU hangs go away, but I think I saw some more stuttering. My GPU is an AMD GPU.
My GPU problems have only existed on slideshow projects. Straight video (GoPro MP4) has been fine thus far, but my use is light.
-
I have seen this with GPU enabled in video prefs. Not had it happen CPU only. By CPU only, I mean video prefs GPU option. The MC AVC OpenCL encoder seems to work fine for me…thus far. I am new to Vegas. Same for GPU Sony AVC. So in my mind it is the Vegas actual GPU usage that is problematic.
When the “crash” happens the preview stops showing progress, the CPU goes to idle, the timers keep ticking. Clicking cancel has the system say that Vegas is unresponsive to addition clicks.
It appears to be a thread race condition and threads within vegas have locked each other out. Nothing to do but close Vegas down (task manager). With a race lockout you will never have any error messages, application or system. Also race conditions typically “crash” at random times/positions with the same source material.
-
I have found a difference depending on what sound mapper is used. The standard windows sound mapper or the directsound surround mapper. The directsound mapper was quieter. Vegas lets you choose the mapper and my playback software, Media Player Classic, also allows this. When the two were different I noticed something.
-
I had Vegas Movie Studio 10 platinum, and I don’t remember it having 60fps output capability. My memory could be faulty.