Forum Replies Created

Page 17 of 39
  • Terje A. bergesen

    March 3, 2007 at 6:13 am in reply to: Formatting from FAT32 to NTFS help

    convert X: /fs:ntfs

    Replace X with the drive letter of the drive that you want to convert. This converts to NTFS with no data loss.

  • Terje A. bergesen

    February 22, 2007 at 12:09 pm in reply to: H.264 compression within Vegas

    Don’t use .mov, use the MPEG-4 encoder from Main Concept that ships with Vegas.

  • I assume you are talking about Intel Core Duo vs Intel Core 2 Duo. The latter, the Core 2 Duo, performs *far* better.


    Terje A. Bergesen

  • Just out of curiosity, why Matrox? I know it is recommended by video editing people everywhere, but why? To me it seems expensive compared to cards from nVidia and ATI, and I don’t see what the extra features are.

    I use a dual-head nVidia with S-Video out. It costs nothing compared to the parhelia. What does the parhelia give me?


    Terje A. Bergesen

  • Terje A. bergesen

    February 13, 2007 at 7:59 am in reply to: Rendering a 2.5 hour video…really slowly

    This seems very slow on any computer. There may be many reasons. Do you have effects applied to entire time-lines? Do you do color corrections or similar on a very large number of clips? Since we do not know what you are doing and what type of computer you have, it is a little difficult to know for sure.

    If you can not find why the renders are as long as they are (check effects etc), you can render sections of the time line one by one. Create a loop region of the first 20 minutes, render it. Do the next 20 and render that and so on.

    I’d first try to figure out what slows down your render though. On my PC, a dual-core AMD box, rendering 2.5 hours of video to MPEG-2 started as I go to bed would be done long before I enter REM sleep.


    Terje A. Bergesen

  • Terje A. bergesen

    February 4, 2007 at 5:13 am in reply to: Quick way of doing a J or L audio cut with Vegas?

    Vegas has many ways of doing things, Gary knows most of them. The way I do my audio overlap/video cut cuts is to select a clip, hit ‘U’ to un-group the video and audio, and then I drag the edges of the audio to overlap as much as I want. When done, I select audio and video again and hit ‘G’ to re-group them.

    I like Gary’s way though, but there are always a ton of ways to do the same thing in Vegas. Find your favorite method 🙂


    Terje A. Bergesen

  • Terje A. bergesen

    February 2, 2007 at 12:21 pm in reply to: Sony DVD Architect 4.0

    Just for the record, *.dat files may well be video, but they may be a lot of other things too. They may be a relational database. They may be temporary data from your word processor. They may be a lot of things. There is no formal requirement as to what a .dat file (or a .avi file for that matter) contains.


    Terje A. Bergesen

  • Terje A. bergesen

    January 26, 2007 at 6:45 pm in reply to: Vegas 6 renders out of sync

    Just some background info. There is no such thing as AVI video. AVI is a wrapper format, not a video or audio format. AVI can contain data encoded with many types of codecs. When you encode to AVI you also chose the codec to use. For video editing you should typically use DV-AVI matching your source, for publication you may use DiVX or similar.


    Terje A. Bergesen

  • Terje A. bergesen

    January 26, 2007 at 4:19 am in reply to: Vegas 6 renders out of sync

    If the audio is in synch before you render, it is highly unlikely that it is a hardware problem that makes it out of synch since the “only” hardware involved in rendering is the CPU.

    You say you render to avi, which isn’t really saying much since avi can be just about anything. What codec are you using for video, what codec are you using for sound?


    Terje A. Bergesen

  • Terje A. bergesen

    January 25, 2007 at 12:55 am in reply to: Suddenly Vegas5/6 ‘unresponsive’

    Try this: When the program starts, does there seem to be a large amount of HD activity? Put your ear to the box an listen. Some times you can hear the HD reading the same spot on a disk over and over. Sounds like the drive is “stuck” a little and it goes chug, chug, chug, chug.

    Hard drives do develop problems over time, and the first indicator is usually problems reading certain sectors on the drive. The controller will retry a good number of times before giving up.

    If you hear something like that, take a backup of your stuff and get a new drive.

    Also, do the obvious virus check.


    Terje A. Bergesen

Page 17 of 39

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy