Aaron Star
Forum Replies Created
-
After looking up your system specs, your laptop supports DDR3-1333 (PC3-10600.) At the time the manufacturer created the specs, 8GB so-dim were not likely available. 8GB dims will likely work, however, if you want to play it safe 4GB per dim will work per the manufacturers specs.
Something like this on amazon:
G.SKILL 16GB (2 x 8G) 204-Pin SO-DIMM DDR3 1333 (PC3 10600) Laptop Memory F3-10600CL9D-16GBSQSearch YouTube for a how to video on upgrading your specific laptop model memory. Some laptops have a memory slot under the keyboard, and only one slot on the bottom.
Once you upgrade, make sure to run memtest86+ from a boot disk and verify the chips and controller have 0 errors.
-
The specs on the laptop are not that bad. I would add the following:
Up the RAM to 16GB if possible, 8GB if that’s all you can manage. Rule of thumb is 4GB per internal CPU core. If you upgrade, research the best ram for your motherboard chipset, as you want to max the bandwidth between the CPU and RAM.
In Vegas 11 – 13 under preferences make sure to disable GPU acceleration, if the GPU is even recognized in the 1st place. The 240 is only 174 GFLOP capable, and Vegas recommends a GPU that is 1300 GFLOPs minimum with 1GB VRAM. Keeping Vegas CPU only will keep the GPU calculations from holding you back. But my guess is you will not even see if in the preferences to use.
-
You know Win10 with Vegas 13 B473 is probably more stable and feature rich.
With some huge number of files, you may be hitting the memory ceiling for 32-bit Vegas. Upgrading to Win10-64 and Vegas 13 may solve this if this is the issue. Not sure what type a project would require a huge number of source files to hit that ceiling. If you are trying to do timelapse, use image sequence import vs dropping on the timeline.
Here are a few things to try with such an old system:
Clean it out top to bottom, and reseat cards and memory
Run CCleaner – Reboot
Run Malware Bytes and check for bugs.
Check HDD for surface errors or failures.
Then test RAM for failing blocks with Memtest86+ outside of windows, and run a complete set of tests. Any errors found at all mean you need new ram in that slot.
Upgrade the machine to something modern
-
If you post “mediainfo” (its an app) on your source MOVs, there might be a way to convert them to a format with out re-rendering them.
Vegas can be a horizontal batch render tool, by using a script that comes with Vegas, and renders regions to individual files. That way you just place a region around each clip, give the region a name, and render to any codec that Vegas supports.
You best codecs to work with in Vegas, for the smoothest timeline scrubbing and real-time playback:
HD Project Size – Largest bitrate to lowest.
Cineform-High.AVI
HDCAM-SR-LITE.MXF
XDCAM-422.MXF
Cineform-Low.AVI
XDCAM-EX – Good for 90% of general YouTube and client work.4K projects – Best to worst
.EXR
REDCODE.r3d
XAVC-I.mxf
XAVC-S.mxfThese suggestions assume you have good recommended system specs to be running Vegas with GPU enabled.
-
I would read up on Ripple Edit in the help file and see if that is what you need.
-
4GB of RAM is really low first off.
For laptops, that for obvious reasons do not have a the power of desktops, you might converting all h264 media to an intermediate codec like XDCAM.mxf or cineform.avi. These codecs have less decode overhead than h.264.
The overall compute power of the laptop will determine the limits of improvements. i5 and AMD processors in laptops are generally not optimal for Vegas editing. Even laptops with “good” processors and a state of the art NV mobile GPU, will be half of what a i7 desktop with discreet GPU will give you. Mobile compute performance sucks, because they are trying hard to limit heat, and max battery life.
-
How many .MOVs are on the timeline? There is a limit to the amount of .MOV QuickTime will support in Vegas.
I would recommend not working with MOV in Vegas, and convert mov footage to an intermediate like xdcam.mxf, cineform.avi, XAVC-I.mxf, or hdcam.mxf. You can do this proxy style in another project, then re-open your main project, and point to the new media.
Just some thoughts.
-
DV25 comes with Vegas, do you have a legit copy of Vegas? Have you tried Vegas 13 with the latest build?
If you have installed certain codec packs, you may need to do a clean install of windows, and reload Vegas. Codec Packs are generally crapware designed to own your system.
If FFPLAY will not run your capture, then there might be something wrong with your captured file.
Vegas was known for how good the DV25 codec support was back in the day. DVCPRO is more of a tape format than a codec.
-
” I remember a time when Premiere was so bad I’d have never guessed it would eventually become so huge.”
+1 to that. I know people fought to keep using Lotus 123 vs switching to Excel too however.
-
Good to know. I guess I always used Track motion scaling down for PiP type things, and never noticed this before.