Aaron Star
Forum Replies Created
-
As John states above, VASST makes batch rendering add-on for Vegas. Vegas also comes with batch rendering scripts that are not as full featured. The Vegas script basically turns the Vegas timeline into a batch render queue.
Mainly you would just drop a reasonable amount of clips on a Vegas timeline and have Vegas create them for you. There is a Vegas script that will auto add regions by clip event, then the another batch render script will render the regions as separate files. I altered the default script to use the region names as file names. Otherwise the default script uses a weird auto naming with codec type and bitrate for names.
The workflow is very much the like old AVID days when all media was converted to the AVID codec to be worked. In this case you are converting to the Sony/Vegas codec to be edited. If you are not scaling you could render in GOOD quality for better speed, but compare the results on your system to see if this is worth it.
Make sure to do your conversion in FP32 video levels, or you will lose your 10bit video information, and end up with 8-bit files inside broadcast codec.
-
No they will not. The white wire is actually a ground back to the electrical source, and that’s what makes a complete circuit. But since the way AC operates sometimes people can miss wire and make a white a hot wire. You can see this in house wiring with 3 ways switches. The wiring may work, but the colors are mixed up, which is why you want to turn off the power when working on house wiring.
Large metal fixtures are grounded because one loose wire nut could make the entire lamp a hot wire. The next guy to come along and make path to ground gets shocked. Ground wire shorts this out while the guy wiring it is working on it.
If you are in say an old garage that only has 2 wire, you can make a ground wire by adding a green wire to new receptacles, and grounding the green wire to water pipe or a long rebar driven into the ground.
Get a ground check plug from home depot. This will verify the hot leads are wired correctly at the plug, and the ground is functioning. You can put the 2 wire adapter in line with this, but it will show grounding errors obviously. This “pulling the ground” is common with musicians, but also I believe why guys die on stage from grabbing a mic. Someone screws up the hot leads powering the stage, which with proper grounding should just be a blow circuit, and not blown guy.
Bonding straps as I know, them help not only with safety but also help with radio shielding, minimizing static electricity on circuit boards, and minimizing electrical noise in electrical components. The 3 wire does matter more than safety, but things should still work
https://en.wikipedia.org/wiki/Electrical_bonding
https://en.wikipedia.org/wiki/Ground_(electricity)
-
Steve and Danny, what are your system configurations. To not use GPU on a stable configuration is like saying “I am only going to use 3 of 4 CPU processors.” If you are not seeing GPU being utilized, then you have an issue with workflow or system build.
I can tell you on an old system like my i7-870, the GPU works in tandem to offer great time acceleration, and effects and composites rendering improvements.
Back in the i386 days, there was a 386 CPU what did not support higher math functions well, so they marketed a “Math Co-Processor.” This was basically a dual processor configuration, where higher math functions would be handled on the fly by the most capable device. OpenCL and rendering in Vegas works in a similar fashion, though not exactly.
Even if you have no GPU enabled in Vegas, Vegas is still working in OpenCL for timeline acceleration. Your system CPU has virtual OpenCL processor, and Vegas uses this under normal operation. Adding the GPU to the mix allows for a dual OpenCL processor configuration. Vegas then is suppose to handle the pixel math by understanding there are 2 processors available to work the problem. If your GPU is massively faster than your CPU, you GPU will not seem to be utilized much. Conversely if your GPU is to weak, but supports the OpenCL functions, calculation timing issue will look like Vegas is not using the system effectively. Throw on top of that the fact that the GPU and GPU memory is being shared to work the displays.
Working in FP32 mode with GPU, you should see an improvement and greater utilization of GPU with effect. This is mainly due to FP32 math is more complex even for the CPU+GPU combo. The GPU does handle floating point math faster than the CPU alone. If calculations cannot be completed in time, frames are dropped, and the next frames are rendered. This calculation timing issue is why Vegas will drop frames, and do so not seemingly using all system resources.
During “Render As” where all frames are suppose to be handled in full, timing matters here too. A codec choice, 3rd party effect, choice in manner of doing a composite, can slow things down massively. Think of “Render As” as a pipe, where footage is fed in one end and completed out the other end. If the CPU operating under Windows decompresses the video codec, then hands that uncompressed video frame to Vegas’s Engine, there can be a delay factor here. If Vegas is waiting on frames to process and the CPU+GPU get it done in a fraction of second, the GPU monitor may not even show blip. If compression is waiting on more frames, then there is more apparent time to complete the task, which shows up like low system utilization. These processes tee totter back and forth until the render is completed.
Handbrake is better optimized to do just one task, and therefor maximizes CPU utilization. Vegas on the other hand, is continuously changing the math it has to do based on user choices, poor code optimization, or 3rd party fail plugins.
Some things to check on system configurations are:
background tasks – lose as many as possible
CPU – is the CPU the best for the Chipset you have, or is it budget
Memory – are all your memory sticks the same chip timing, and are they the best timing for your chipset.
Memory amount – Windows does massive disk cache, so the amount of memory should around 4GB for Windows OS, 8GB per instance of Vegas editing HD, and 8-16GB for Windows cache.
GPU – must be running at fastest interface speed possible for timing reason, and not so much throughput reasons. There are more communication frames per second at x16 than x8, and more at PCIe 3.0 vs 2.0. The speed of handling requests between the GPU and host system matter.
Disk – You system should be able to provide about 2x the bandwidth of 4 layers of whatever codec you are running. That is the way I look at it. 25-35Mbs codecs are low bandwidth and disk does not matter much with current drives. Work in 4x uncompressed HD and disk IO through your chipset to display can be a problem.
-
Assuming your footage is 1080-60p,30p or 24p in Prores HQ, I would take small sample of your media clips, and convert them to HDCAM-SR-422 (SQ) or HDCAM-SR-Lite.MXF.
HDCAM-SR-SQ (MPEG2) would be the Sony/Vegas = to Prores 422 HQ at around 400mbs.
HDCAM-SR-Lite (MPEG4) would be more than likely acceptable working copy of Prores HQ at 220mbs.
HDCAM is intra-frame like Prores, highly optimized in Vegas, and will not suffer from the file limitations of QuickTime.
Make sure to convert to HDCAM in 32-bit-FP video level mode, then edit in 8-bit, and render in 32FPVL mode. If your system configuration is good with GPU, Vegas will play real-time with effects, even at these high bit rates in 8-bit mode.
I think a lot of people just think HDCAM is some old tape format, but actually it has been updated through the years. SR-Lite is the latest version, which is an Studio Level of MPEG4, and 12 channels of audio.
HDCAM
https://www.shift-4.com/f5-and-f55-sstp-sr-codec-explained/https://en.wikipedia.org/wiki/HDCAM
XAVC would be usable too, but the Vegas implementation does not allow full encoding capabilities of this new codec. Currently Vegas appears to limit the codec to about 10bit video and 100mbs, when the codec is capable of 12bit video and 600mbs.
-
You should be good to go.
Under Vegas preferences>Video tab, you just need to make sure the GPU is selected vs OFF.
When rendering out, say rendering an Sony AVC .mp4, make sure the profile you are using has the Encode Mode set to Automatic or use GPU or OpenCL enable. You may have to save a new template depending on the codec rendering to.
Sony AVC .MP4 does not use the GPU as much as the older Main Concept encoder, but the MC encoder is not supported under newer card. You have to trial and error on your own configuration.
Use AMD System monitor or GPU-Z sensor to verify the GPU is being used during playback and render.
Certain codecs like XDCAM-ex, XDCAM 422, AVC, HDCAM-SR-Lite and XAVC are optimized best under Vegas.
Use GPU sorted effects under plugin chooser over non-accelerated.
-
Actually the iMac 5k with i7,32GB ram, SSD, and M295 GPU is $4268.00 not including tax or anything else.
Not to sure the M290x is a good deal, that is a mobile chip, and it benchmarks 2.57 times slower than the actual r9 290x. So you would be basically having to do CPU only in Vegas with that rig.
-
All this talk and no one has posted system specs, project settings, or workflow details. Really hard to help when flying blind, and just hearing complaints.
Load speccy and share a snapshot.speccy file, that would help us look at the details of your configuration.
Upload a screen shot of your GPU-Z main page.
Run Luxmark V2-LuxBall with CPU+GPU and post the results, and post a screenshot of the speccy summary page a minute or 2 into a render test, but before it completes.
List details of your workflow, like project settings, camera type, any media transforms, and output profiles or types.
-
What is your source footage resolution and codecs? Maybe post a screen shot of your timeline and project settings.
Have you tried the Automatic setting for the “Encode Mode?” You do have Quicksync on that 4790k. What is quicksyc render times.
Check out the comparison between 760 and the now old 7970 on the Luxmark test.
https://www.anandtech.com/show/7103/nvidia-geforce-gtx-760-review/15
and then this comparison showing actual Vegas benchmarking:
https://www.anandtech.com/show/7457/the-radeon-r9-290x-review/18
If you upgrade your GPU, make sure to follow the processes outlined in other posts on switching from Nvidia to AMD drivers.
-
What are your system specs, and what Codecs are you using for audio and video?
-
https://en.wikipedia.org/wiki/Neutral_density_filter
Use a light meter if you are trying to match exposure compensation for a situation like that.