Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro vegas pro 11 crawls then stops.

  • vegas pro 11 crawls then stops.

    Posted by Peter Heap on March 8, 2012 at 4:52 am

    Hi

    I’ve been using Vegas since version 4 but have been largely absent from editing for the last 5 years or so.

    Until recently I owned a woefully underpowered Gateway laptop with a Celeron chip (and not much RAM) that I did a little bit of editing on. And since I was only editing SD material it worked surprisingly well. And that was using an external USB drive for my video storage.

    My new laptop is much more powerful (but still modest for editing) but can barely cope with a project with about 3 hours of rushes. They are proxy files from a Sony XDCAM PDW-700 so not huge but they are located on an external drive(USB).

    As an experiment I’ve put some of them on a partition on the sole drive on my computer (which I know isn’t recommended) but no improvement.

    Has Vegas Pro got to the point where it can only run on a powerful computer even when only running a relatively small project? I always used to boast about how stable it was and how it never crashed. But now I’m worried I won’t be able to even view my rushes from within the project let alone edit them.

    Any helpful thoughts?

    PS This one of the messages I get when the program freezes….What’s a FileIOSurrogate.exe?

    Just spent 20 minutes trawling the web for an answer but none the wiser:)

    Description:
    A problem caused this program to stop interacting with Windows.

    Problem signature:
    Problem Event Name: AppHangXProcB1
    Application Name: vegas110.exe
    Application Version: 11.0.0.595
    Application Timestamp: 4f47704d
    Hang Signature: 59b3
    Hang Type: 6464
    Waiting on Application Name: FileIOSurrogate.exe
    Waiting on Application Version: 11.0.0.595
    OS Version: 6.1.7601.2.1.0.768.3
    Locale ID: 3081
    Additional Hang Signature 1: 59b38dd4fa5b2809d4c02d33d37785c4
    Additional Hang Signature 2: 7674
    Additional Hang Signature 3: 7674f32f3906bd31a0e9205596fc8a93
    Additional Hang Signature 4: 59b3
    Additional Hang Signature 5: 59b38dd4fa5b2809d4c02d33d37785c4
    Additional Hang Signature 6: 7674
    Additional Hang Signature 7: 7674f32f3906bd31a0e9205596fc8a93

    If you’ve made it this far, here are my computer specs

    Vegas Version 11 (build 595) 64-bit
    Operating System
    Platform: Windows 7
    Version: 6.01.7601 (Service Pack 1)
    Language: English
    System locale: English
    User locale: English

    Processor
    Class: Intel(R) Core(TM) i5 CPU M 460 @ 2.53GHz
    Identifier: GenuineIntel
    Number of processors: 4
    MMX available: Yes
    SSE available: Yes
    SSE2 available: Yes
    SSE3 available: Yes
    SSSE3 available: Yes
    SSE4.1 available: Yes
    SSE4.2 available: Yes

    Display
    Primary: 1366x768x32

    Memory
    Physical memory: 3,946.1 MB
    Paging memory available: 7,890.5 MB

    Peter Heap
    Sydney

    John Rofrano replied 14 years, 2 months ago 2 Members · 5 Replies
  • 5 Replies
  • John Rofrano

    March 8, 2012 at 3:07 pm

    [Peter Heap] “Has Vegas Pro got to the point where it can only run on a powerful computer even when only running a relatively small project?”

    Well… 3 hrs of HD footage is not a small project, but yes, Vegas Pro 11 requires more resources than Vegas 4 did. The world of video editing has gotten a lot more complex in the past 5 years since Vegas 4. HD has 5x the information that SD had. SD was pretty much a single format (DV) while HD supports a variety of formats, some of which are extremely difficult to edit. By your own admission, your laptop is modest for HD editing. In fact, Sony was recommending a minimum of a 2.8Ghz dual core and you only have a 2.5Ghz. Also if you bought that laptop for video editing you should have gotten a high end Core i7 not the midrange Core i5 with a minimum of 8GB of memory. But still, you should be able to do modest editing with a Core i5.

    How does it perform with only a few clips in the project (not 3 hrs of footage)? I suspect that you may be reaching a memory limit with only 4GB of memory and 3 hrs of footage. Start with one clip and see if it’s something about your computer that is bogging things down or just the sheer number of clips. Then add more clips. If it starts to get slower, it may be a resource issue with all the HD footage. You may have to work with several smaller projects.

    ~jr

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

  • Peter Heap

    March 8, 2012 at 9:25 pm

    Hi John

    Thanks for your reply. I have done as you suggest and you are correct. The computer is getting bogged down by too much material.

    However, (and it always amazes me that I don’t include enough information in my original post to make myself clear:)) what I should have said was that I have only loaded the lo-res (MPEG-4) Proxy files into the project with the idea of conforming to HD at the last moment. So I have 3 hours (actually a little less) of lo-res footage, no HD footage at all. I shot the project on XDCAM HD discs.

    I’ve just compared one of the proxy files with it’s HD equivalent and it’s only 5.62MB vs 146MB for the HD version of exactly the same shot. The files are 352 x 288 rather than 1080 x 1920. Could it be that Vegas doesn’t like MPEG-4 files?

    Do you think that installing more RAM could be the answer?

    Thanks again for your help.

    Peter Heap
    Sydney

  • John Rofrano

    March 8, 2012 at 9:41 pm

    [Peter Heap] “The files are 352 x 288 rather than 1080 x 1920. Could it be that Vegas doesn’t like MPEG-4 files? “

    Well… if your project is set to 1920×1080 then Vegas is rescaling the 352 x 228 to 1920 x 1080 for playback. That’s a lot of work for each and every frame and MPEG4 is not the easiest codec to decode. This could cause slower playback.

    [Peter Heap] “Do you think that installing more RAM could be the answer?”

    If you think you are getting low on resources then it might help. Check your memory usage in the Task Manager and if you are getting close to the limit on physical memory, then more RAM should help. I have 8GB of RAM but I never work on projects that are more than an hour.

    ~jr

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

  • Peter Heap

    March 9, 2012 at 1:55 am

    John Rofrano Check your memory usage in the Task Manager and if you are getting close to the limit on physical memory, then more RAM should help.

    The Task Manager says that I’m only using 60 to 70% of memory and 2% of cpu. So adding RAM doesn’t sound like the answer.
    John Rofrano if your project is set to 1920×1080 then Vegas is rescaling the 352 x 228 to 1920 x 1080 for playback.

    Following your advice, I’ve changed the project from 1920×1080 to 352 x 228 and while I’m not out of the woods yet, (if I may mix my metaphors) there’s light at the end of the tunnel. Playback is improved but still far from ideal.

    2 Hours Later…

    Well I finally installed Vegas on my other (faster) computer and it fared no better. So I decided that the common denominator was the USB drive. It looked fine in Device Manager and it wasn’t until I did a bit more testing that it failed a “Random Seek Test”. I’ve copied all the material to another USB drive and everything’s back to normal. My mid-level laptop computer is editing just fine, playing 352 x 228 mpeg-4 files in a 1920 x 1080 project with no difficulty at all.

    Phew, I can’t tell you how happy I am after wasting a whole day trying to figure out what was wrong.

    Thanks again for your help John. I know how difficult it is to diagnose computer problems from afar and I appreciate your suggestions and help.

    Peter Heap
    Sydney

  • John Rofrano

    March 9, 2012 at 2:41 am

    Peter, I’m glad you were able to figure it out. I had ruled out the USB drive when you said that you copied a few files to your internal drive and had the same slow results but maybe you still had files on the USB drive that Vegas was referencing. Anyway, it looks like you’ve found the problem. Good detective work! 😉

    ~jr

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

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