Aaron Star
Forum Replies Created
-
“Intel Core i7-3770 CPU @ 3.40GHz
16 GB RAM
Nvdia GeForce GGTX 660
Windows 7 – 64-bit
Vegas 10.0”The “x”77 series chipset (i7-3770) was a good rig at one point. Assuming you have that chipset. Upgrades are going to not do a whole lot unless you are running really slow RAM and no SSD. That chipset was the end of PCIe2.0, and the next generation came with PCIe3.0. 3.0 has not only improved bandwidth, but also comes with less overhead for even more bandwidth. Your GPU will appreciate the 3.0 improvements.
GPU upgrade, you could go up to an RX480, 390x, or Fury-x. This would work much better with Vegas.
16GB of ram is good, but you want to make sure you have not fully populated the DIMM slots. If your board has dual channel, that means work 16-32Gb of ram out of 2 sticks of memory. Adding more will cause most motherboards to drop back to single channel operation. Memory bandwidth is very important to Vegas, encoding, and general operation. Test your memory bandwidth with Winsat mem, or memtest86+.
Windows 10 pro has a much improved memory controller. I recommend moving to Win10-64.
Motherboard design type could matter with regards to SSD SATA drives. Try and get an M2 slot NVME Samsung 950 Pro. With SSD drives you are placing a lot of load on the DMI bridge. Look up DMI bridge. So a motherboard like the x99 will give you more options for high bandwidth devices like SSDs.
Z270 chipset with the latest processor would be a good upgrade choice for a modest configuration. This would upgrade you to PCIe3.0, and DD4 memory the latest evolution. Also the CPU would give you the longest service life since it comes with the most contemporary instruction sets. X99 still has more memory bandwidth, but the memory controller speeds of the z270 are reaching a point where they are almost neck and neck these days. We are still waiting on an x99 class motherboard for the latest generation of CPUs.
I would upgrade to VP 14, as 10 is not going to take advantage of any GPU upgrades.
Vegas may work just fine with the .MOV encoded material. Try VP14 with that format, .MOV may not use QT and may use native mode of operation for certain codecs like Prores and AVC. You can determine this by looking at what .dll is being used under the Vegas media properties. That format sounds alot like XAVC-intra in a .MOV container. FFMPEG may be able to re-wrap without re-encode, if you have a problem with playback.
-
Hard to say how you can do this. Post the “media info” (See the FAQs) on the file format.
That camera records in several different formats and file types.
https://pro.jvc.com/prof/attributes/specs.jsp?model_id=MDL102268&feature_id=03
I would try the MP4 (XDCAM EX), or .MTS record modes, and not the .MOV settings.
-
Did you try any other codecs like XDCAM or Cineform? Those work different from the way AVCHD decodes.
The issue does seem odd. Have you tried different monitor outputs off the card for the 2nd monitor? On my system, I output to full preview HDMI via a Displayport adapter. While two other desktop monitors are on the DVI ports.
You are certainly CPU bound. Have you tried playback with other Preview settings? Draft Half, auto, or Preview Auto?
Do you need full quality playback while editing? I tend to favor FPS over image quality, knowing that the quality will be there in the final. Switching to best/full temporarily when placing graphics, or others things that need it.
-
1) Take all the ABC.mpg files and put them in an MPG sub folder.
2) Put all the ABC-2017.mp4 in an MP4 subfolder.
3) Open vegas and when prompted to find the files, point vegas at the abc-2017.mp4 files.
4) Then adjust your project settings to match the new file format.
5) verify placements of L3 graphics and any pan/crops.
Your new ABC-2017.mp4 files will need to be frame for frame duration accurate as the originals. If they are not, you will need to sort that out before you attempt step 3.
This is a pretty standard “Proxy Editing” technique.
-
If you want help with that configuration, here are some things to look at.
- download Speccy, and post a snapshot or at least the summary section from save as text output.
- Post your project settings
- Post the media info on your timeline source footage.
- 8GB on a 4 Core CPU is a bit low, as you generally want 4GB per core.
There are reasons that Vegas recommends i7 hardware vs i5. Vegas dedicates 8 threads to AVCHD decode alone, then it has all the other processes too along with Windows threads. A HyperThreaded CPU really does help with all of this.
Here is a link to where your CPU sits in comparison with i7 class hardware, and 1000 points here is significant.
https://www.cpubenchmark.net/cpu.php?cpu=Intel+Core+i5-3570+%40+3.40GHzDetermine how fast your memory is operating at with Memtest86+ boot disk, or Winsat Mem. If your memory bandwidth is below 12GB/s you need to figure out why. This might be due to low cost memory being installed by the manufacturer, or you are not operating in dual channel mode.
If you upgrade your memory, pull out all of the existing memory, and upgrade with only 2 identical DIMMs of the desired total memory. I would do at least 16GB if not 32GB since the remaining extra memory goes into disk cache, which is what you want for multi-cam work. 12-24GB/s is much faster than accessing a HDD at 100MB/s. According to the Intel Ark specs on your CPU, you can handle DDR3-1600MHz but your motherboard memory controller might handle faster speeds. Memtest86+ any memory configuration, especially speeds above the stock 1600Mhz. There should be Zero errors no matter how long you run it, even overnight.
Since your motherboard likely only capable of PCIe2.0, I would verify with GPU-z that the device is actually interfacing at 16X speeds. 8X PCIe2.0 is pretty gimp when you compare it to the system memory speeds. You want to be able to move data as fast as possible between the System memory and GPU memory. The 6970 is an XT GPU, so you are already maxed on the compute units for that series. OpenCL (GPU accell) should work well with Vegas, but the CPU might be holding things back. Hard to tell. I would make sure to disable the Intel GPU in BIOS if possible.
Codec in use on the timeline, test Cineform or XDCAM-ex material for multi-cam projects. Make sure audio is uncompressed only, no MP3/AC3 audio.
Just some thoughts on things to try.
-
Well with motherboards. I look at the chipset block design 1st and try and max the interfaces like 4 memory channels on the x99 board. The 7700 uses the Z270 chipset so its design is laid out, so then you are down to choosing what is important to you. Here is a link to a review of different z270 boards:
https://www.techspot.com/review/1316-asrock-z270-motherboards/page3.html
‘>https://www.techspot.com/review/1316-asrock-z270-motherboards/page3.htmlIf you look at the different benchmarks, I would value the LatencyMon score 1st, then maybe consider the fact that the Gigabyte board comes with a really good audio chip.
Here is another review that offers some insight into other boards. They found in testing that 3200MHz was a stable DDR4 RAM speed on their configurations. That is a significant performance boost in memory bandwidth to try in your own testing. Use Memtest86+ and run it over night, and a stable speed should show zero errors no matter how long you run it.
https://www.extremetech.com/extreme/241950-intels-core-i7-7700k-reviewed-kaby-lake-debuts-desktop
“All of our CPUs were configured with four 8GB sticks of DDR4-3200 courtesy of GSkill (F4-3200C14Q-32GTZ). We had no trouble running the RAM at 3200MHz with Skylake, Kaby Lake, or Broadwell-EP, even though the maximum clock speed was substantially higher than anything these chips are formally rated for.”
There are only 2 memory channels on the Z270, so verify with Memtest86+ or Winsat Mem that you are still operating at dual channel speeds if you populate beyond 2 DIMMS. If the board drops back with 4 chips, then you will need 2 higher density DIMMs.
-
The 6700 and 7700 are identical practically speaking. The 7700 just comes with a higher stable clock speed, which gives it a performance boost over the stock 6700.
The Z270 motherboard for the 7700 also has improvements, mainly the upping of the stock memory bandwidth. The other improvement is the addition of more PCIe lanes, but they are not off the CPU and cross the DMI bridge. Basically the additional PCIe lanes are so they can add more high bandwidth accessories.
Video editing tends to need dedicated bandwidths, where as most of the accessories they hang off the z170/z270 chips are meant for intermittent use or solo use. An M2 drive and a Blackmagic capture card will overload the DMI bridge pretty fast. Desktop/gaming boards have this flaw, whereas Xeon workstation boards have bandwidth improvements to keep this from happening. When you compare the design of the z270 and X99, you see that the X99 is practically a Xeon class design.
-
Maybe post a photo of what you are talking about?
Are you over saturating the colors? Skin tone starts to look really red when you over saturate it.
-
Some else recently was complaining about rendering on Xeon. I wonder if there is an issue/bug there?
GPU acceleration enabled, or software only? NV cards are not great with Vegas.
Having you run your machine through clean up steps listed in other posts? Verified your memory is not overclock and 100% free of errors?
-
Pick an AMD card from this list sorted by performance:
RX480 – 5100 GFLOPs
R9-290/390x – 5900 GFLOPS
Fury-X – 8600 GFLOPsFor Vegas, always choose an X series card, or a card with an XT GPU chip. These have the most compute units and performance is the best.
AMD Vega GPU line is due out in the next couple months.