Aaron Star
Forum Replies Created
-
Batch render regions is included with Vegas Pro as a script you can execute. If you go to the Sony Creative forum, under scriping, there are several posts that deal with this script abd how to use it. The script allows you to name the region markers the file names you want, then execute the script which will render each region as a seperate file.
The other add-ons are pretty much just providing front end GUIs to these scripts, and calling it a product.
-
If you do not know the video card in your Sony Laptop, you can use an app like “Speccy” to tell you the details about your system. That app will tell you the exact detail on your video hardware, and you can easily download the correct driver from NV selections.
-
Have you tried using a resolution like 800×600?
Rebooting
Then testing Vegas in the low res to see if the problem persists?
Then switching back to native resolution and testing again?
Are you using the latest video card driver from Nvidia?
https://www.nvidia.com/Download/index.aspx?lang=en-us
-
Love this. What a great solution to a problem.
-
Grazie is nice for helping you with little to go on, other than what you have tried. In the future, listing info on your hardware specs, video media type rendering from and to, and Vegas project settings would help.
You may need to manually update GPU, and other motherboard drivers to the latest version under Win10. Win10 is extremely stable with good hardware, and may not need compatibility settings enabled for a version of Vegas only one step back.
I would run some low level tests like Memtest86+ from a boot DVD/USB, and verify that your system memory is 100% error free.
Process all Win10 updates, Rebooting as many times as it takes, and always run the latest version of Vegas downloaded from Sony/Magix.
Check the Windows System and App Logs for errors with hardware and applications, then hit google for answers.
Do an “SFC /scannow” from an admin command prompt, to verify your Win10 install, then correct any issues found.
Win10 is highly stable with Vegas, and most problems are a between desk and chair problem, with purchasing choice of system hardware leading that list under that topic.
-
There a bunch of gaming sites that will tell say you only need 2 cores for a good gaming rig. This is not the case with Vegas. I feel like Vegas should have a minimum hardware check at startup which would raise peoples overall experience with Vegas. However, it would also mean they would not sell as many copies, and most laptops would be filtered out in this proess.
The P3240 CPU you are running is not a good match for the GPU GFLOPS you are running, and more than likly you are simply hitting the compuation roof of that CPU very quickly. Editing MP4 source material is like editing all your word docs, and email from a zip folder. Every save or open action needs to be decompressed before editing can be done. This process takes a ton of CPU horsepower. Then your edits need to be applied, the series of frames need to be recompressed back to MP4, and written to a file. This cycles over and over. 99% on your CPU simply means your CPU is the bottle neck and not some other point in your system.
You would see much better render times and overall Vegas performance from even an old Gen4 i7, like a 4770 or 4790 system. Remember also the rule of thumb of 4-8GB or RAM per core.
The GPU you have is doing most of the heavy lifting if you are using NV capture encoder. Then in Vegas its all about the CPU, with more than likely no help from your GPU, this due to NV’s poor support for OpenCL. Changing to an AMD 7970, R9 290x, 390X, FuryX or 490X series of GPU would give you a much better experience in Vegas Pro. The X series is nessesary to optimize the amount of compute units, which is different from stream processors. This of course would need atleast a Gen 4 i7 to power it.
Another thing you could try, is to convert all your capture footage to XDCAM-EX 1280×720 in .MXF, then edit that footage on the timeline. When you are done editing, you wold render to that same XDCAM-EX 720 format, and directly upload the file to YouTube or whatever. This may decrease your render times, as XDCAM has less overhead than h.264.
Just some thoughts.
-
It would be wise to just upgrade the Vegas 11 user to VP13 latest build.
Along with the Media files and edit.VEG file, you would want to share your presets for effects in such away they appear on the other computer.
Sony used to make a preset manager, but then changed the location of presets, which rendered it useless and it only works for audio presets.
vegasaur.com/vegas-presets-manager – might work with VP11&13 presets, but I am not positive.
If you know how to work the regedit (registry editor,) you can save your presets out to a .reg file, and move them to the other computer. Presets are under HKEY_CURRENT_USER\SOFTWARE\DirectShow\Presets — Here again, the same version of software may be need, or you would need to verify the presets are moved over correctly.
-
In Masking mode/key-framing, change the Path>Mode setting to Negative.
Negative – will cut out the interior of the selection and leave the exterior.
Positive (default) – will cut the exterior of the selection and leave the interior. -
Under Preferences > General Preferences > Check “Make Spacebar and F12 Play/Pause instead of Play/Stop.
See if that is what you are looking for.
-
“German techs are super from what I can tell. They’ve always been years ahead of everybody else in tech stuff and equipment ”
What planet? What tech exactly? There are very few chip makers in the world and almost all are in Asia.
I just hope the project managers are better at Magix than Sony. I am amazed me how many task items and bugs were dropped or ignored, and people still kept their jobs.