Aaron Star
Forum Replies Created
-
Are you sure it is camera original footage? What does MediaInfo (https://mediaarea.net/en/MediaInfo) say it is? C100 is just AVCHD at 24MBS, with the options to record in log mode, but you would see an image. What version of Vegas? It could have been recorded to an external recorder in a different format, or converted by someone to another format.
-
That is most likely After Effects, or a particle effect in a 3D app like Blender, Maya, or 4D.
-
No Dual GPU. Vegas OpenCL is coded in a way that it only uses one OpenCL device. A application like Luxmark displays how OpenCL can use multiple OpenCL devices at one, similar to the way Windows uses multiple cores. In Vegas there should be check box selection of devices you wish to use including you CPU (which has opencl capabilities,) but Sony chose to keep that free for other tasks.
The only Dual GPU you can really do with Vegas is dedicate one card for Display, and the other for Compute (OpenCL/rendering.) Maybe Vegas 14 will support OpenCL 2.0 and offer multi-GPU selection, or settings to use things like the Video Encoder (VCE) integrated into most modern AMD cards.
-
Or you could try this.
Go to File Explorer (windows explorer) > Network (formerly Network Neighborhood) > find the server and share you want to render to. Right click on the shared folder, Select Map Network Drive, Give the drive a letter and check if you want it to stay after re-boot. Then try rendering to that drive letter.
-
Have you gone into Shift+Preferences > Internal > type mem in the show only box, then up the OpenCL memory Size filter to 4096. Restart Vegas and retry MC AVC with openCL and Sony AVC with OpenCL and Auto, and see if the numbers improve.
Switch to FP32 mode and see if GPU use significantly improves as a test. Try rendering some XAVC-I and play it back, and note GPU usage. Render some HDCAM-SR-LITE and playback in 32FP mode, and note GPU usage.
Some other things to experiment with might be:
Threads in show only prefs. Experiment with changing the MIN/MAX threads to match your system (16) Experiment with Reader threads at 16.
OpenCL in the show only Prefs. Experiment with OpenCL Per – Thread Command Queue = True
Downloading AMD System Monitor from AMD offers a good view of CPU, GPU, Memory activity.
Luxmark-x64 can be used to verify OpenCL function and shows all available devices.
“gpu_video_x64.log” in your vegas temp will show Opencl device errors
Do each one at a time restarting vegas each time, note results, and see if anything helps.
-
I think that some view the world from one point of view, and others completely different. Vegas tried to leverage at the time what was suppose to be standard. They went down that road, and now Nvidia pulls a Microsoft and creates a J++ out of OpenCL. If you look at OpenCL benchmarking sites like Luxmark, you will see that AMD and even older AMD cards reign over Nvidia’s latest. Luxmark Stats
I believe Vegas’s programming is more elegant than most realize. On my system I have seen playback that the CPU handles with only a blip from the GPU. Switch to 32FP math and the GPU comes to life, apply a GBlur and the CPU comes to life. Is that not what the math co-processor is suppose to do? Optimize your system for number crunching and not how fast some site says it can turn an .mp4. For me I spend more time editing, than rendering and prefer playback optimization.
Laptops are not a good thing when it comes to GPU editing. I used to edit just fine on an I5 Lenovo T410 with SSD and 8GB ram. I just knew the the system was not going to be a super performer, and might have to preview at quarter or half. But the screen was so small that preview window was fine. The 970M in the laptop shown has about the same compute power as desktop gaming card from 2012. The 970 designation is not worthy of that hardware. Laptops also have gimped motherboards generally. You may want to make sure that motherboard has actual dual memory channels, full DMI 2.0, GPU is interfacing at full PCIe spec, and the display is quality enough to fully display the codec you are working with.
-
Have you tried holding CRTL+SHIFT and starting Vegas? This will reset Vegas back to defaults.
After such a major hardware upgrades, you may need to go into Device Manager and clear out hidden old devices, uninstall your video drivers, run ccleaner, and restart. Apply updates and reload the graphics driver for your machine. Fork lifting a motherboard without doing a clean OS install, and application reloads, is not how would have done it. Make sure that something like Luxmark 2.0 or 3.0 can see your CPU and GPU as openCL devices. If you can run Luxmark, you should be good to go in Vegas with GPU.
-
Are you rendering to a UNC named share or mapped network drive? I would try mapped drive and see if the network issue remains.
I think the Main Concept Opencl is separate from the internal Vegas Opencl. There is a separate OpenCL directory for the MC codec. Sony might be leaving updates to that directory up to the third party. I have read from others that CUDA works best with MC, since CUDA will use multiple devices. Sony’s OpenCL will only use one GPU for everything.
-
Yes the advertising is for real. I would recommend i7-4xxx+,32GB ram, with hd5770, hd7970, or R9 290x, and make sure you GPU is interfacing at 3.0. But you can see by the picture even i7-gen1 with 5770 can benefit from the GPU acceleration. Vegas 13’s OpenCL implementation seems to be only 1.1, so no real need for the latest opencl support other than for speed and other apps. Vegas does not support multi cards like the 7990 or 295x, but you can select one of 2 cards and dedicate one to compute functions and other for display. AMD seems to handle OpenCL better than NVidia in Vegas. I recommend the cards listed because they all run AMD XT chips which seem to have the highest compute ratings over other other AMD chips. The chip in the 290x is the chip in Firepro w9100, minus memory and pro features. Since Vegas operates in 8-bitFP and 32-bitFP modes, making sure your system is not Floating Point gimped would give you the best experience.
-
I have noticed that the codec makes a difference in the new versions of Vegas. I have been using Vegas since 2.0 and version 4 did not seem to care much about the combination of codecs on the timeline. AVCHD editing seems to be highly unstable to edit directly on the timeline. I think the fact that AVCHD uses a compressed audio (Dolby digital,) the decompression and sync on the fly causes Vegas to crash. If I convert all my footage to codecs with uncompressed audio, like XDCAM or mpjeg, the stability of Vegas goes way up.
