Stephen Mann
Forum Replies Created
-
GPU support is something that Vegas users screamed for for years, “because Premiere has it”. No one listened when I said, “be careful what you wish for, you might get it”.
GPU support is good for people with last year’s processors. At some point your processor can render the video just as fast if not faster than with GPU because it takes the processor longer to prepare the data for the GPU than to do it without the GPU.
In my opinion, GPU should default off, and only turned on when you are satisfied with everything else working correctly.
Glad you got your project done.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
I think the best source is nVidia. However, if it works, don’t fix it.
I don’t recall which processor you have, but I am running the latest i7 and nVidia cards. I really don’t see that much difference in render times with GPU on or off, so I generally leave it off.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
The file opencl.dll is installed by your display adapter card. The prefix nv likely means that Nvidia owns this.
I think that you mean “nvopencl.dll”, not nvoo…
This is strange. My PC’s have NVidia cards, but there is no nvopencl.dll.
But if you turned off GPU in both places, why would opencl.dll be called in the first place? You *did* turn off GPU in both places? Also, have you tried updating your nVidia drivers?
If you are crushed for time, how big is your project (in Gb)?
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
The “Send” to Sony is only an aggregate collection, it only alerts them to patterns or trends. We need to know what the error is *before* this window.
If it is an unmanaged exception then you have a driver problem. I asked you in another thread where are you located? There may be another Vegas user nearby who can help you get the DVD finished.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
-
The other thing that can cause a render time to increase (and the estimate is simply an estimate with little connection to reality) is the use of F/X. Some F/X will greatly increase render time because the encoder has to render every pixel of every frame. For example, bumping the opacity from 100% to 99% will be imperceptible to the eye, but it will add hours to the render time. Did you buy Vegasaur? It has an audit feature that may help – it will at least alert you to suspicious settings. Here is a screenshot of a test project I have on my desktop. I intentionally bumped the opacity of one event to see if Vegasaur Audit would see it.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
What Steve said. If your expected render time goes up like that, then DVDA is re-encoding the video file (and should have told you that it was going to). Did you adjust the bitrate in the “Render As” menu to get the MPEG file down to 4.3Gb? The default encoding parameters are good for about 75-minutes of DVD.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
Here’s a quote from Jan Ozer, a compression guru:
Finally, though it’s not technically related to B-frames, consider the number of Slices per picture, which can be 1, 2, or 4. At a value of 4, the encoder divides each frame into four regions and searches for redundancies in other frames only within the respective region. This can accelerate encoding on multicore computers because the encoder can assign the regions to different cores. However, since redundant information may have moved to a different region between frames—say in a panning or tilting motion—encoding with multiple slices may miss some redundancies, decreasing the overall quality of the video.
In contrast, at the default value of 1, the encoder treats each frame as a whole, and searches for redundancies in the entire frame of potential reference frames. Since it’s harder to split this task among multiple cores, this setting is slower, but also maximizes quality. Unless you’re in a real hurry, I recommend the default value of 1.
Here’s the full article.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
I took their word for it – techSpot is usually pretty reliable. It *was* too good to be true… But I wonder if they let the horse 2.0 out of the barn?
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
The reason I ask is because you described what happens when a CF card maximun file size is 2Gb. The raw video has to be divided into 2Gb chunks. The download software that comes with the camera (I am not familiar with the one you have) stitches those segments into one file.
Then I realized that the camera uses tape. Duh!
Try using HDVSplit to capture the video from the tape in the camera. It’s free and HDV capture is all it does. That’s what I used for a few years before buying some HVR DR-60 hard drive recorders.
Steve Mann
MannMade Digital Video
http://www.mmdv.com
