Stephen Mann
Forum Replies Created
-
I am the same as Mike, ‘cept everything, including any original media, is in a folder in my “projects” folder. From time-to-time I sync this folder to a separate hard disk drive. When the project is done, the I do one final sync to the external drive and it goes into a drawer for long-term storage.
At any time in the next few years, all I need do is drop the HDD into an external dock and open the VEG file, and the project is as I last used it.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
What format and how are are you downloading from YT?
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
-
[Jim Murphy] ” In the Vegas preview screen it looks really good–a nice blue sky with some clouds showing. I thought I had it fixed. I then rendered this to MPEG2, and brought it into DVDA. In DVDA the sky again looks white”
I would bet a lunch that you didn’t bring the new MPPEG file into DVDA. Try encoding it in the Render As menu to a new name. Just to make sure you don’t accidentally pick up an older copy.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
Steve, here’s a couple of other things to do.
From the start menu, run DXDIAG. This will test your DirectX components
Also from the start menu, run SFC/SCANNOW. This will test all of your Windows system files, including the .net stuff.Steve Mann
MannMade Digital Video
http://www.mmdv.com -
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, 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 -
Not prefect? What would you have done differently? The lighting looks great, the colors didn’t shift between cameras, the audio levels were great. What would have made it perfect?
On YouTube – The final resolutions that YouTube “processes” is a black art. No one really knows how the “processing” software decides. I have uploaded an AVCHD 1080i file and when YouTube finished processing it, 1080i was in the list. I made some changes to the project and encoded another AVCHD 1080i file and uploaded it to YouTube and this time the YouTube “processor” resulted in only a 720p resolution. A few hours later, I uploaded the SAME file and this time I got 1080i.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
Uncompressed AVI is fail-safe. I have ten year old AVI files that still open in Vegas. I personally avoid MOV because it is the most abused container in the video world. You never really know what’s in there. And you may find that when you do want to use the media later, you have to cross your fingers and hope that whichever version of Quicktime you have installed likes the format of your media.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
Looks good – I would like to know more technical details. What did yo shoot with?
BTW, if you put a link in the forum post, you have to highlight it and hit the “L” box above.
https://dl.dropbox.com/u/1421565/Cow%20links.jpg
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
That’s a C# error. I would reinstall Vegas and try again.
Steve Mann
MannMade Digital Video
http://www.mmdv.com