Aaron Star
Forum Replies Created
-
Yes. It would seem like a messed up program, but you said you are getting blue screens? BOSDs are straight up hardware and driver failures. Try and find out what the BSOD says, this can help track down the offending hardware.
Recommend making sure your hardware is up to minimum specs, not over clocked/stable, memory error free, and not overheating before calling blame on Vegas.
- Make sure your drivers for each device is up to the latest version, as well as the system BIOS.
- Make sure to fully update your windows along with any .NET updates.
- Make sure you are running the latest build of your Vegas version.
- Make sure you are not working with .MOV media from a phone. If you are, re-wrap the media using FFMPEG to .mp4, .avi, or .mxf.
- Uninstall any AV/security suites that maybe causing direct hardware access issues. Use windows defender that comes with windows, then scan periodically with Malware bytes as a verification.
- Use Memtest86+ from a boot disk and complete a full 10 pass memory scan with no Errors.
- Run SFC /scannow from an admin command prompt, and verify that your system requires no windows system file repairs.
- Verify DPC latency on your system with DPC Latency checker, you should see a flat line in the green or yellow. Spikes in red are bad driver and hardware.
List your system specs and media info so the community can help you better.
-
Peoples attachment to this MainConcept mp4 GPU encoder is a dated point of view. That encoder was “neat” and improved things back when our CPUs were much slower. There have been improvements in CPU instruction sets and other things that make the GPU encoder not necessary any more.
” bad decision to lock this plug-in to GPUs was MainConcept’s nasty way of getting their licensees to pay extra for new versions. ”
This is true about licensing, but what happened about 6 years ago is that most every encoder manufacturer decided that running the encoder on the GPU was not thing to do. Mainly because so much of the benefit of LGOP codec happens outside the extreme parallel operation of the GPU. If you do not believe me, watch some YouTube videos by AMD and Mainconcept on the subject around 5 years ago. Our PCs simply do not need the GPU to do this task anymore.
OpenCL on the other hand improves math functions far beyond what the CPU can do alone. This is still beneficial to the encode process on many levels.
If encoding your final render is your biggest pain, then your CPU and overall system are likely to blame, and not so much your GPU encoder.
Just because your GPU is not “loaded” up during render, does not mean it is is not being utilized when needed. If you have a slow CPU, and fast GPU, your GPU could waiting on the CPU for more calculations. Most GPU utilization graphs are averages over long interval, while your GPU could hitting 100% for fractions of a second. But since the average shows a low percentage, people blame the software for not utilizing the GPU effectively. While in fact it’s the general user that thinks his budget choice in hardware is infallible.
-
I would try converting your source cineform media to .AVI from .MOV. Then point your project at the .AVI files at startup when vegas asks for missing media.
This would rule out Quicktime fail on Windows, as any Apple product is rubbish on Windows by Apple’s design.
If you do some research, FFMPEG should be able to re-wrap your media with no recompression.
-
“GPU is not utilized at all, if multicam enabled, and output to secondary monitor is enabled too”
Are you saying the OpenCL benefits of the GPU are disabled in this mode? Because the secondary monitor is a function of GPU operation.
I had not noticed this while multicam editing on my system. Could it something to do with the source format you are editing? I only do multicam with an intermediate format in .MXF like xdcam, hdcam, or AVC-intra. Cineform would be a good choice too because it’s an intra frame format.
-
Yeesh. .MTS… Its probably ac-3(mp3) audio too.
I would try converting some clips to xdcam-ex.mxf, HDCAM-sr-lite.mxf, or cineform.avi. Then trying some multi-cam editing again, see if that makes any difference.
Since you have an old NV k2200 GPU, keep GPU disabled in preferences. The k2200 barely meets the Vegas minimum GFLOPs, and comes from the era of NV not supporting OpenCL well. Use it only for display.
If that stuff does not work, I would starting checking for system errors in windows logs, running SFC /scannow, make sure all your .NETs are updated, and the last revision of your BIOS, and GPU drivers. Memtest86 thru a full 10 pass, to check for errors or mem controller errors. Check DPC latency is good, which should show if you have a bad driver that is acting up.
-
Aside from making sure your project settings match your media format 1280x720P@23.97FPS, there does not appear to much wrong with that media format. The format is generic and the frame constant. The frame rate being variable is what is seen often with game capture media, and this has caused render issues.
You may want to save as a new file name, and replace the media file where the render stops with some other footage. This will rule out possible errors with that specific media.
Then disable tracks above the source media one by one to rule out effects, or some composite issue.
Make sure there are no windows updates pending, install any .NET windows updates, uninstall any Anti-virus that is not windows defender, and reboot everyday before going to work in Vegas. Make sure you have the latest release of the Vegas you are running.
-
” 20+ layers consisting of many samples that are different formats ( mp3, WAV, OGG, AIFF and FLAC) ” — I would start by converting all your samples to WAV(PCM/Uncompressed), at whatever smaple rate you are trying to use in your project, then see if your problem persists. In my experience with Vegas several layers of varied compressions is where the stability goes down.
I have also seen with an older version of Vegas where AC-3 audio from a camcorder that recorded .MTS caused all sorts of issues. Once I converted the footage to a format that used uncompressed audio, my problems went away.
-
Well the render time is due to the “Intel Celeron N2840” system you are trying to work on. Fast computers are expensive, but the $300.00 rig you are running is just to low powered to make vegas work well.
I would advise you to get a PC tower and monitor with the following components:
i7-6700
16GB of RAM <–4GB per CPU core = 4 core CPUx4GB=16GB
256GB Boot drive
1TB 2nd drive
AMD RX480 GPU <–this AMD card is important to Vegas Pro software, just trust the forum on this one.
Windows 10 Pro
20″+ monitor with Display Port, connect monitor to displayport on GPU
Install the latest version of Vegas you have.That system spec would be a low end Vegas editing machine, with out getting Ebay involved and buying a used older good system. Laptops just do not have the power to work Vegas very well, but if you really need a laptop, get one with similar specifications. The GPU in a laptop would be an RX480M, which is the best laptop chip, but much less powerful than the desktop GPU with the similar name.
Please go to https://mediaarea.net/en/MediaInfo and get a copy of “Media Info”. Use Media info on one of your main visual media files, switch the view to TEXT, and cut and paste that info to a reply. That is the type of info we are looking for.
-
John is right. That story is pretty much why I stopped buying good sound blaster cards about 5 years ago. There was really no other reason to stop supporting the Audigy 2 card that supported relevant formats, other than to obsolete hardware and sell more hardware upgrades to end users. The lack of good driver support lead to playback and stability issues in vegas. Once I removed the audio interface and used the more contemporary onboard audio interface stability improved in Vegas. Of course the signal to noise is a lot less, but few have really quiet / dampened listening environments.
Your latency is likely due to the poor audio implementation on the webcam to USB. Ironically, some programmer probably spent time aligning the audio to the video on the webcam by adding delay to the audio.
-
You can control the slope of the transition by adding more points. Then moving those points to create whatever slope/fade you need, whether that be sharp, stepped, or long and drawn out.
Is that what you are asking, or are you asking about some default setting to make all future edits the same?