Aaron Star
Forum Replies Created
-
Back in the day when H.264 was as new as h.265 is now, most machines and NLEs struggled with it. Here is what I understand, and maybe the suggestions will help. I have not tried them myself.
Vegas 11-14 pretty much required the best OpenCL capable GPU, at that time it was AMD series. If you are using Vegas 14 or less, you should be building for optimal cards for that era. Effects that required the higher math that OpenCL provided saw great acceleration when compared to CPU only. A great number or people I believe had heat and other problems with their machines, which made the GPU acceleration unstable. I found GPU acceleration unstable until I figured out what was causing it.
The coders working on Vegas 11-14, made no effort to support things like VCE built into the AMD GPU. https://en.wikipedia.org/wiki/Video_Coding_Engine
With Vegas 15+ the new coders integrated NVIDIA support for NVENC, while also seemingly supporting OpenCL for the higher math capabilities. Formats that are compatible with NVENC will see an acceleration with decode and encode. Effects that require OpenCL for the higher math will be limited on how well NV GPUs support the OpenCL standard. I think NV has improved their support of OpenCL, so with the newest cards there might not be such a wide gap as there once was.
https://en.wikipedia.org/wiki/Nvidia_NVENC – Make sure to read through the generation differences and understand how they may factor into your workflow. For example if you are trying to do 4K HDR material, then a Generation 1 NVENC card will not be utilized. HEVC or H.265 is not supported until generation 3 and above.
Since Vegas has no “compatibility applet” or capabilities function tests built in, you are on your own to make sure your system supports the software features that Vegas claims to support.
Make sure to test your configuration for support of the different standards. Also periodically check for memory errors, heat issues, and DPC latency issues that might come up over time with other software installs or dirt build up.
If you are going to try 2 GPUS in your system, make sure the motherboard will supply 2 16X lanes of bandwidth. Most cheap, non workstation motherboards only support one 16x card in the system.
Hopefully that make sense to someone out there.
-
You may need to give the forum more info to help you. That question is not detailed enough to determine what the problem is.
-
There are plenty of other posts, that discuss cards types that people are seeing an NVENC benefit from. I would try one of those, if that is main factor you feel you should choose a GPU by.
-
Sounds like there is a problem with your workflow from source to render.
Start with a video standard project setting. 1280×720, 1920×1080, or UHD.
if your photos are not at least the resolution of your project file, the photos will look less resolved.
If your photos are much larger than the project settings, make sure to scale them correctly with pan crop. You can see the scaled resolution in pan/crop>position display. The height and width should not go below your project resolution.
Render to a video profile that matches your project settings. Make sure the render profile>project setting is set to use “video rendering quality: BEST” This will use the better image scaler in Vegas.
Also make sure to use enough bit rate for the changes in your content. Assuming AVC/MP4, for example 16Mbs-22Mbs for HD, or 50-100 for UHD.
The flicker thing with RAYS sounds like it could be RAYS, since RAYS will flicker with changes in the background material. If you want static rays, you may need to render to a an intermediate layer. Rendering to PNG sequence such that you only end up with the text and rays, and the rest of the image alpha. Then you can layer the PNG sequence on top of the other media. Try rays with just text on a black background and see if it still flickers. This is hard to tell what is going on without seeing the composite.
-
Probably just a bug that needs to be fixed by Magix.
Are you on the latest version of build Vegas 12?
Does the issue still happen on the latest trial version?
-
This has been a long standing issue with Vegas and MOV format. The best thing to do is one of two things:
1 – render your material to an intermediate format like cineform, XAVC-intra, or XDCAM (HD). Work in small groups of files.
2 – change the container type from MOV to MP4 using a utility app or FFMPEG. This process will not re-render the the media, it will only re-write the information from one container to another. Vegas will read your footage in .MP4, .AVI, or .MXF much better and not have the file limitation.
-
I would check for postings for issue with the polaris line and Vegas. https://www.vegascreativesoftware.info/us/vegas-pro-forum/
Polaris is a significant architecture change, and both drivers and Vegas need to support the changes to get the performance from the system. AMD drivers are always being updated, but Magix is moving much slower with support of AMD GPUs right now. Magix seems to be focusing on Intel quick sync and NVidia GPUs in the latest release of VP15. The most recent versions of Nvidia GPUs seem to support OpenCL better, which is the main thing Vegas Users wanted from their AMD GPU.
Your core system is getting pretty old to put such a new GPU on it, and it may hold the GPU back. What I would do is upgrade the core system to something that supports PCIe3 x16 slot, and increase your system memory to 16-32GB (4-8GB per core.)
-
I would make sure your windows updates are all fully processed.
I would consider using only Windows defender for AV and junking anything else. Then occasionally run MalwareBytes to verify the system is clean.
Run the following:
https://www.memtest.org/ — Create a boot disk, and run a a full pass of tests with ZERO errors.
Check out: https://www.sweetwater.com/sweetcare/articles/solving-dpc-latency-issues/ — this will verify that you do not have a bad hardware driver that is actiing up.
I wrote the following back in Dec-2015 but it still applies to the latest hardware and OS.
You may also want to run the following on your machine and verify a few things, generally in this order:
“chkdsk /f” from a command prompt, choose yes on next reboot. Reboot
Verify that all disks have no found.00x folders on them. If they do replace the storage media.
Verify storage disks have no SMART errors, or are at least green in SMART state.
Apply all windows updates, including any .NET updates.
Make sure GPU driver is latest.
Uninstall any old applications or utilities no longer used.
Run CCleaner Registry cleaner and repair issues. Reboot.
Run a Windows defender scan, and Malware Bytes scan, and repair issues found, reboot if issues found and re-run scans.
“dism /Online /Cleanup-Image /RestoreHealth” from an admin command line. You should get:
[==========================100.0%==========================]
The restore operation completed successfully.
The operation completed successfully.sfc /scannow from an admin command prompt. Verify you get:
“Windows Resource Protection did not find any integrity violations.”
repair any issues here. Reboot and re-run if issues repaired until you get the message above.
Make sure Vegas is running the latest build for your version, reboot if upgrade is needed.
Verify Hardware temps are ok during playback and rendering with something like Speccy or another program like it. Repair clogged heat fins or cooling issues if high temps are present.
This process will ensure the foundation of hardware and software you are running Vegas on is functioning correctly.
-
Blu-ray is HD. Architect supports blue-ray encoding formats.
The latest 4K Blu-ray, architect does not support the encoding format since its a whole new codec. Same disc media, but different video and audio codecs.
Its really surprising how long the 4K DVD has been out, and there are no updates to the DVD architect to support it. Vegas 14-15 support the codecs, but the lawyers must be the hang ups on updating the DVD authoring tool.