Problems with vegas 10

[John Rofrano]

[Christoffer Widegren] “Ive got two problems with sony vegas. The first is that I cant use the effects cause only half of the effect screen is showing, the other half is grey :S “

Check that you haven’t enabled the split screen view:

[Christoffer Widegren] “And the second problem is that I cant render when i use like 10 clips, cause it says ‘ your system is running low on memory ‘ but thats not the case cause i have 8 gb of RAM so it shouldnt be a problem. Please help!”

Are you using the 64-bit version of Vegas Pro 10?

What codec do the 10 clips use?

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Christoffer Widegren]

It wasnt the preview button.. I think I uploaded a picture with the problem..

ehm, sorry for beeing a noob but whats codec?

Christoffer

[Christoffer Widegren]

I dont know if my response was posted ( Im new here so i dont know how this forum works ) so i make a new post.

To: John

It wasnt the preview button, its the effects screen. Hard to explain, how can i show u a screenshot?

Im using the 64-bit version, and sorry for being a noob, but whats codec?

Christoffer

[Stephen Mann]

“but thats not the case cause i have 8 gb of RAM so it shouldnt be a problem.”

I’ll let John continue to address the half-screen problem, and I’ll address the Windows “low memory” warning.

Here’s my boilerplate response (recently updated):
Low Memory or Out of Memory does not mean “Not enough RAM”, though adding RAM can sometimes fix a “Low Memory” waning. A “Low Memory” warning usually means that you have exceeded your commit limit. You need either a bigger page file, more physical memory, or both.

One of the biggest sources of confusion over Windows memory usage is the whole concept of virtual memory compared to physical memory. Windows organizes memory, physical and virtual, into pages. Each page is a fixed size (typically 4 KB). To make things more confusing, there’s also a page file (sometimes referred to as a paging file and dynamic RAM). Many Windows users still think of this as a swap file, a bit of disk storage that is only called into play when you absolutely run out of physical RAM. In versions of Windows starting with Vista, that is no longer the case. The most important thing to realize is that physical memory and the page file added together equal the commit limit, which is the total amount of virtual memory that all processes can reserve and commit.

All Windows since XP (and Unix/Linux for that matter) always wants to have page space. Always. Programs (including drivers and codecs) like to and are allowed to pre-allocate as much memory as they want. Even if they are never ever going to actually use it. Sometimes those programs properly deallocate memory, sometimes they don’t (resulting in “memory leak”). Sometimes, programs leave parts of themselves in allocated memory just in case you are going to run that program again. (MS Word, Excel and other Office programs are particularly adept at this). If you have no page file and a program wants to commit some for itself, your PC will crash (AKA, BSOD, or Blue Screen of Death).

Paging file configuration is in the System properties, which you can get to by typing “sysdm.cpl” into the Run dialog, clicking on the Advanced tab, clicking on the Performance Options button, clicking on the Advanced tab (this is really advanced), and then clicking on the Change button. I would suggest a value of 1.5X the currently allocated value. The old advice of 2X or 3X your RAM is, well, old advice when a few MB of RAM was normal. The largest paging file that you can select in Windows is 4,095 megabytes (MB).

Also, Windows supports up to 16 paging files, but each must be on a separate volume, so if you have more than one internal disk drive you could try enabling a Paging File on your second hard-disk. DO NOT put a paging file on an external drive because if it’s not present when Windows boots, then Windows will crash.

For more information, see https://support.microsoft.com/kb/237740 and https://support.microsoft.com/kb/2267427

Steve Mann
MannMade Digital Video
http://www.mmdv.com

[John Rofrano]

[Christoffer Widegren] “It wasnt the preview button”

OK, are you having trouble with the FX window being cut off? This is usually a font DPI problem. Try setting all of your windows font sizes back to normal. There are several places this can be changed.

[Christoffer Widegren] “Hard to explain, how can i show u a screenshot?”

You can embed a screenshot right into your post. Just use the Image Upload button above the area where you type your reply. This this:

Then fill in the popup window:

But it sounds like it may be a font DPI problem on Windows or perhaps your graphics card driver?

[Christoffer Widegren] “Im using the 64-bit version, and sorry for being a noob, but whats codec? “

CODEC stands for enCOder / DECoder which is the way a video gets encode and then later decoded. Some codecs don’t work well in Vegas and can cause memory problems. Where did the files come from? What extension do they use? You can use a free utility like GSpot to determine which codec they use:

Also make sure that your Dynamic RAM preview is not set too high. This will steal memory from your render. Use Options | Preferences | Video and check the Dynamic RAM preview max.

I have mine set to 1024 and I have 8GB of memory.

~jr

http://www.johnrofrano.com
http://www.vasst.com