Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Keeps crashing when I render … PLEASE HELP, has to b finished by end of day

  • Keeps crashing when I render … PLEASE HELP, has to b finished by end of day

    Posted by Lauraitt on September 14, 2007 at 7:14 am

    Hi Im officially in panic mode, I have tried to render the video the last 3 nights and it keeps crashing. The video is 17 mins long and I am rendering with the following settings:
    Video Rendering quality: Best
    Audio Mode: CBR
    Audio format: Windows media audio 9
    Audio Attributes: 128kbps, 48Khz, stereo (a/v) cbr
    Video Mode: Bit rate VBR
    Format:Windows media video 9
    Image size: High Definition(1440×1080)
    Pixel Aspect Ratio: 1.333(HD 1080)
    FPS: 30.000
    Seconds per Keyframe: 5
    BPS: 8M

    The computer has 2GB ram. The drive I am saving to has 900GB with about 700GB free.
    Is there any other way of rendering ? As it has to be done by the end of the day or 2moro morning at latest.

    This is the error it left this time:
    Bytes at CS:EIP:
    773F74F0: 8B 40 0C 83 E0 0F 3C 0B .@….<. 773F74F8: 75 33 8D 45 F0 50 FF 36 u3.E.P.6 Stack Dump: 0004FEF0: 2B678D08 2B480000 + 1F8D08 0004FEF4: 00050018 00030000 + 20018 0004FEF8: 7E440457 7E410000 + 30457 (USER32.dll) 0004FEFC: 7E4188E0 7E410000 + 88E0 (USER32.dll) 0004FF00: FFFFFFFF 0004FF04: 0004FF94 00030000 + 1FF94 0004FF08: 773F90E7 773D0000 + 290E7 (Comctl32.dll) 0004FF0C: 2B678D08 2B480000 + 1F8D08 0004FF10: 9C010CEE 0004FF14: 0004FFFC 00030000 + 1FFFC 0004FF18: 773F8EA4 773D0000 + 28EA4 (Comctl32.dll) 0004FF1C: 00000000 0004FF20: 0004FF30 00030000 + 1FF30 0004FF24: 7E41BAA4 7E410000 + BAA4 (USER32.dll) 0004FF28: 7E41B96B 7E410000 + B96B (USER32.dll) 0004FF2C: 7E41B933 7E410000 + B933 (USER32.dll) > 0004FF54: 7E41B96B 7E410000 + B96B (USER32.dll)
    > 0004FF58: 5AD718D7 5AD70000 + 18D7 (uxtheme.dll)
    > 0004FF68: 5AD7338A 5AD70000 + 338A (uxtheme.dll)
    > 0004FF74: 773F8EA4 773D0000 + 28EA4 (Comctl32.dll)
    > 0004FF84: 773F8EA4 773D0000 + 28EA4 (Comctl32.dll)
    > 0004FF8C: 7C8025F0 7C800000 + 25F0 (kernel32.dll)
    > 0004FF98: 7E418734 7E410000 + 8734 (USER32.dll)
    > 0004FFAC: 773F8EA4 773D0000 + 28EA4 (Comctl32.dll)
    > 0004FFBC: 773F8EA4 773D0000 + 28EA4 (Comctl32.dll)
    > 0004FFC4: 7E418816 7E410000 + 8816 (USER32.dll)
    > 0004FFC8: 773F8EA4 773D0000 + 28EA4 (Comctl32.dll)
    > 0004FFE4: 7E4188A6 7E410000 + 88A6 (USER32.dll)
    > 0005001C: 7E440457 7E410000 + 30457 (USER32.dll)
    > 00050020: 7E418830 7E410000 + 8830 (USER32.dll)
    > 0005002C: 7E41B4C0 7E410000 + B4C0 (USER32.dll)
    > 00050034: 773F8EA4 773D0000 + 28EA4 (Comctl32.dll)
    > 00050058: 7E4188A6 7E410000 + 88A6 (USER32.dll)
    > 00050070: 7E440457 7E410000 + 30457 (USER32.dll)
    > 00050074: 7E41B4D0 7E410000 + B4D0 (USER32.dll)
    > 00050080: 7E41B50C 7E410000 + B50C (USER32.dll)
    > 00050094: 773F8EA4 773D0000 + 28EA4 (Comctl32.dll)
    > 000500A8: 7C90EAE3 7C900000 + EAE3 (ntdll.dll)
    > 000500C4: 773F8EA4 773D0000 + 28EA4 (Comctl32.dll)
    > 000500C8: 7E41B473 7E410000 + B473 (USER32.dll)
    > 000500CC: 7E41B615 7E410000 + B615 (USER32.dll)
    > 000500D0: 773F9100 773D0000 + 29100 (Comctl32.dll)
    > 000500E0: 773F8EA4 773D0000 + 28EA4 (Comctl32.dll)
    > 000500F8: 7C90E2F1 7C900000 + E2F1 (ntdll.dll)
    > 000500FC: 7C8024B7 7C800000 + 24B7 (kernel32.dll)
    > 0005012C: 0041B5C0 00400000 + 1B5C0 (vegas70.exe)
    00050130: 00000000
    00050134: 00050178 00030000 + 20178
    > 00050138: 74724636 74720000 + 4636 (MSCTF.dll)
    0005013C: 00000013
    > 00050148: 74730455 74720000 + 10455 (MSCTF.dll)
    > 00050160: 7E418734 7E410000 + 8734 (USER32.dll)
    > 00050174: 773F8EA4 773D0000 + 28EA4 (Comctl32.dll)
    > 00050184: 773F8EA4 773D0000 + 28EA4 (Comctl32.dll)
    > 0005018C: 7E418816 7E410000 + 8816 (USER32.dll)
    > 00050190: 773F8EA4 773D0000 + 28EA4 (Comctl32.dll)
    > 000501C8: 74730E71 74720000 + 10E71 (MSCTF.dll)
    > 000501E4: 7E440457 7E410000 + 30457 (USER32.dll)
    > 000501E8: 7E418830 7E410000 + 8830 (USER32.dll)
    > 000501F4: 7E41B4C0 7E410000 + B4C0 (USER32.dll)
    > 000501FC: 773F8EA4 773D0000 + 28EA4 (Comctl32.dll)
    > 00050224: 7E41F94B 7E410000 + F94B (USER32.dll)
    > 00050238: 7E440457 7E410000 + 30457 (USER32.dll)
    > 0005023C: 7E41B4D0 7E410000 + B4D0 (USER32.dll)
    > 00050248: 7E41B50C 7E410000 + B50C (USER32.dll)
    > 0005025C: 773F8EA4 773D0000 + 28EA4 (Comctl32.dll)
    > 00050260: 7E41F819 7E410000 + F819 (USER32.dll)
    > 00050270: 7C90EAE3 7C900000 + EAE3 (ntdll.dll)
    > 0005028C: 773F8EA4 773D0000 + 28EA4 (Comctl32.dll)
    > 00050290: 7E41B473 7E410000 + B473 (USER32.dll)
    > 00050294: 7E4194D2 7E410000 + 94D2 (USER32.dll)
    > 00050298: 7E41B530 7E410000 + B530 (USER32.dll)

    Kolbjørn Hoseth larssen replied 18 years, 7 months ago 6 Members · 12 Replies
  • 12 Replies
  • Mike Kujbida

    September 14, 2007 at 8:00 am

    Try rendering to AVI first and then convert that to WMV.
    It’ll be a lot less strain on your system.

    If it still crashes, break it up into sections and then piece it back together for the final render.

  • Lauraitt

    September 14, 2007 at 8:24 am

    Hi,
    I could do that, but I was just thinking I should be rendering to Mpeg2 to import into DVDArchitect, should I ?
    As soon as I try to render it says ‘An error has occured during the current operation’.

  • Mike Kujbida

    September 14, 2007 at 9:56 am

    If your end product is a DVD, then yes, render to MPEG-2.
    Because it’s so short, use a CBR of 8,000,000.
    You’ll have to scale it down though as you won’t be able to do HD, only SD resolution.

    Your repeated errors have me concerned though.
    I’m wondering if you have a corrupt clip in the timeline somewhere.
    What kind of material do you have on it?

  • Lauraitt

    September 14, 2007 at 10:10 am

    Yeah the end product will be a dvd.
    I had files imported from a server, I have now got them imported locally.

    I am rendering right now as an avi, its at 65% after 1hr20mins which is ok but I need MPEG-2, at highest quality as this dvd is going to distributors worldwide.

    On my timeline I have hundreds of different video clips, photos, WAV files for the voiceover. I know that it is massive in size but I dont see that as a reason for it to repeatedly crash.

    How would I find out if there is a corrupt clip in the timeline?

    Thank you for your help
    Much appreciated,
    Laura

  • Mike Kujbida

    September 14, 2007 at 10:17 am

    The only way I know of finding a corrupt clip is trial and error replacement 🙁

    As far as quality, if you chose “Best” as an AVI render option, that’s as good as it’s going to get (without different render options that would increase render time drastically).

    For an MPEG-2 render, a CBR of 8,000,000 is as good as you can do it.

    Sure hope this works out for you!!
    Keep us informed of your progress.

  • Janet Turner

    September 14, 2007 at 12:16 pm

    Laura –

    I’m sure this is not much help but it does sound like you have some kind of corruption problem with something on your timeline. However, if you can finally get an avi render, then bring that back into Vegas and you should be good to go for the mpg2 or wmv renders. Let us know if it works out.

    Grasshopper

  • Douglas Spotted eagle

    September 14, 2007 at 12:55 pm

    First, I’d not recommend using avi as an intermediate. Particularly DV avi. You’re tossing a significant amount of quality out the window.
    Second, look to your setup.
    Reduce render threads to 1.
    Set Dynamic RAM to a low value, I’d recommend 128 or 256.
    Clear ALL background programs so nothing is running but Vegas. No antivirus, no mail, no Corel, no other background app.
    Be sure heat isn’t getting you. This is a common problem when rendering to CPU-intensive formats.
    Render to MPEG2 for DVD, WMV for web. I’m confused as to how/why WMV has entered the discussion?
    CBR at 8Mbps will provide a very good image (not the best you can do, but you should be worrying about getting an output first).
    Are any of your stills larger than 2K in any dimension? Are they tifs? JPEGS? PNGS? TGA? PNG and TGA work best in Vegas, and no image should be larger than 2K in horizontal or vertical pixel value.

  • Mike Kujbida

    September 14, 2007 at 1:11 pm

    [DSE/Spot] “CBR at 8Mbps will provide a very good image (not the best you can do…).”

    Spot, what are your recommendations for short videos like this?
    I’ve been told (wrongly??) that CBR is the way to go for best quality.
    Should I be using VBR instead?
    If it’s less than an hour, my bitrate calculator says 8,000,000/8,000,000/4,800,000.
    WOuld this give a noticeably better result?

  • Douglas Spotted eagle

    September 14, 2007 at 1:15 pm

    It’s content-dependent. If there are static and then high motion scenes, I wouldn’t use CBR. If it’s fairly static, then CBR is the best option. My bigger point is that she can go to a higher bitrate (I didn’t read the length) which often translates to better quality but not always. Again, it’s content dependent.
    There are many other ways to get better video output from an encode as well that have nothing to do with bitrate, but rather saturation, cropping, etc.

  • Mike Kujbida

    September 14, 2007 at 3:32 pm

    Thanks Spot.
    The content part I understand.
    However, I’ve always burned DVDs with the understanding that the max. bitrate should be limited to 8,000,000.
    This may have even been mentioned in an earlier Vegas/DVDA manual.
    You’re saying that going even higher (like 9,000,000), allowing room for audio, is OK with Sony software and good media?

Page 1 of 2

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