Aaron Star
Forum Replies Created
-
I would try the following to see if any of it helps:
Use the media match button in the Project Properties window, to make sure the project settings are the same as the media.
Try Sony AVC render vs MainConcept .mp4 encoder.
Verify that your source capture media is actually a true 16:9 “video standard” like 1280×720, or 1920×1080… and 29.97, 30, or 59.94 FPS. Any non-standard capture, especially non standard frame rates will cause encoding problems. Verify that your source media is also not recording as a Variable frame rate. Media Info app can help with this.
https://pacoup.com/2011/06/12/list-of-true-169-resolutions/
Try re-encoding your source captured media to cineform, xdcam-ex , or XAVC-intra depending on resolution. Then use a new vegas project to render those files, and test for the issue.
Verify the memory with memtest86+ from a boot disk. There should be Zero errors, even if you run it over night through several passes.
Uninstall the NVidia software, and pull the NV GPU out of the system. Then make sure you have the latest Intel drivers for the onboard GPU. Next re-run the renders with only the Intel GPU and Vegas options>Video> set to CPU only. Make sure all other slotted in add-in cards are uninstalled for test reasons. Re-run adding back in each card one at a time.
-
You could do VIEW > Windows > Edit details – then select Events > Active Takes.
This would give a list of events in the project, and the file path shown is the list of media in use. This table can be selected, cut and pasted into Excel for further sorting.
There is also Tools > “Clean Project Media” which clear all media not in use on the timeline. Leaving you with project bins that contain only media in use on the timeline.
-
look for a .BAK file of the same name near the original, copy it and and change it to .veg. See if that is what you are looking for.
-
You can right click on the marker and select delete.
You can also find the Edit Details window and filter for markers, then Control+ select and delete a whole lot at once.
If your default project has markers, you will get the markers back when a new project is created. Save a new default project the way you want it.
F1 is your friend.
-
Do you have the same hardware as the original posters?
If you remove your custom audio hardware and drivers from your machine, and use the stock onboard sound card. Do you still have the same issue?
A long while back, I had a top of the line SB Platinum Pro device that had wonderful sound. But SB stopped supporting the device and old drivers were creating a stability issue with editing in SVP. When I removed that device, my editing stability improved greatly.
Have the posters in this thread tried Sony .W64 format or FLAC instead of mp3. Those would at least be uncompressed audio.
I believe pro audio hardware relies heavily on ASIO vs stock sound cards. Is it possible that something has been installed recently that has jacked the ASIO on the machine? Old drivers on new OS or something like that? Googling ASIO tester, there seems to be a utility by centrance, that measures the Audio latency performance. If this runs well, it might be a good thing to check.
You might also check the DPC latency on the machine. There could be another device driver that is causing the issue.
-
There is a large amount of posts on this topic, so search is your friend here.
The quick list for a desktop/non-workstation performance machine is:
CPU: i7-5930 or i7-6700k based system
Chipset: x99 or q170 chipset – I still recommend x99 because of the 4 memory channels, over 2 that most desktops have.
GPU: AMD 7970-Ghz ebay), 290X(ebay), 390x, 480, or r9-Fury-X
Memory: DDR4 around 16-32GB spread across 2 – 4 DIMM modules depending on the board you buy. x99 needs 4, Q170 needs 2.
Disk: 256GB M.2 Samsung Pro line for Boot
1TB Sata Samsung Pro SSD or PCI SSD hard card for working/project storage – on the CPU lanes and not crossing the DMI bridge.
2x 4-6TB HGST Spinning HDD in OS mirror, for longer term project/ back burner storage.
add multiples of the 2x 4-6TB drives for additional storage, or out fit an older PC to be a NAS.OS: Win10 Pro
Display: HP dreamcolor, LG wide gamut, or Dell U-series monitors connected with best Displayport version your GPU supports. If you want 10-bit color, your GPU needed to be an AMD firepro line. But the Dreamcolor will support 100% of the 8-bit video range.
Backup: get backblaze or some sort of extra portable HHD space to backup your important projects long term. You can even just get external bare drive adapters, then just use bare drives and store them back inside the original packaging.
Of course all that is just one mans opinion, at the time of this writing.
-
I would check your disk media for SMART errors, and run a full chkdsk to verify file systems for errors. Then verify your memory has no errors with Memtest86.
Moving the folders, could have re-written something to problem a free area of your file system.
-
There is a well know QT bug with Vegas, where a certain number of QT media files on the timeline or in the project causes QT to stop working. Users have complained for years about how they have troubles editing QT media from phones and other QT generating sources. Most have just passed this off as a lack of Apple updating QT to modern standards, which is now never going to happen for Windows apparently. This why most convert their QT media to a more Vegas native intermediate format for editing.
Vegas 14 has QT native support, but that may only be for Prores content. Other QT media using other codecs may still require QT to be loaded, and then you are back to the problems with QT.
Like John Rofrano always says…it you need to edit QT use a Mac. Makes perfect sense.
-
I notice your media is QT. Is it possible you have hit the ceiling that Vegas has with QT media?
I would try a save as of the project to a new name.
Then render some media to XDCAM-ex, or Cineform.AVI. Then load the save project, pointing the missing media at the new renders folder.
-
If you have more than one GPU that is capable of operating as a compute device, or what Vegas terms GPU acceleration, you can select from your GPUs by going to:
Options–>Preferences–>Video Tab–>Then use the drop down select your GPU.
Verify operation by using a GPU heavy FX like Min/max, and monitoring GPU load during playback.
If you have an AMD GPU. AMD makes a nice “system monitor” application that shows both CPU and GPU in one task manger. You can also use GPU-z, or Windows Performance Analyzer if you are feeling really geeky.