GTAStunting

General => Video Editing/Compression => General Discussion => Video Editing Tutorials => Topic started by: Daffy on November 19, 2006, 07:09:00 AM

Title: Tutorial: Xvid/LAME High Quality Render
Post by: Daffy on November 19, 2006, 07:09:00 AM: Disclaimer: This tutorial does not guarantee you great quality.
It's only a good tool in the fight against bad quality.[/i]

This tutorial will hopefully learn you how to achieve the best possible quality with the Xvid video codec and the LAME audio codec.[/b]

Step 1: First we have to grab some software in order for this to happen, use the links below.
• Xvid (Nic's Version) (http://www.codecs.com/download/Nic_XviD_Codec.htm)
• LAME Encoder (http://www.codecs.com/download/Lame_Encoder.htm)
• LAME ACM Codec (http://www.codecs.com/download/LAME_ACM_Codec.htm)
• The Huffyuv Codec (http://neuron2.net/www.math.berkeley.edu/benrg/huffyuv.html)
• Virtual Dub (http://prdownloads.sourceforge.net/virtualdub/VirtualDub-1.7.0.zip?download)[/b]

Step 2: Now you're gonna have to render your movie uncompressed.
I will be guiding you through this in Vegas, don't hit your head if you're using another editing program since this should pretty much be the same regardless of what you use.
Lets start.
[img]http://img.photobucket.com/albums/v92/Indiana_Jonas/Tutorial/1.jpg\" border=\"0\" alt=\"IPB Image\" /]

Step 3: I have no idea why this is even an option but select Best on the Video Rendering Quality option.
[img]http://img.photobucket.com/albums/v92/Indiana_Jonas/Tutorial/3.jpg\" border=\"0\" alt=\"IPB Image\" /]

Step 4: Now lets go to the video options.
It's important that everything is like it is in the screenshot except for the framerate if it's a San Andreas movie, then it should be 25 fps instead of 30.
It's also very important that you use the 2.1.1 version of the Huffyuv codec and NOT version 2.2.0
[img]http://img.photobucket.com/albums/v92/Indiana_Jonas/Tutorial/4.jpg\" border=\"0\" alt=\"IPB Image\" /]

Step 5: Go to the audio options and make sure "Include Audio" is unchecked, we will render the audio separate from the video and merge the together later.
[img]http://img.photobucket.com/albums/v92/Indiana_Jonas/Tutorial/5.jpg\" border=\"0\" alt=\"IPB Image\" /]

Step 6: The video options are as good as they can get, render the video now.
Keep in mind that this may take a little time and a lot of space so make sure you render it on a fast hard drive with a good amount of free space on.

Step 7: Now you have hopefully finished rendering the video, it's time the for the audio.
Press render again and choose .wav as the output format and press custom.
[img]http://img.photobucket.com/albums/v92/Indiana_Jonas/Tutorial/6.jpg\" border=\"0\" alt=\"IPB Image\" /]

Step 8: Make sure everything is like in the screenshot, especially the Bit Depth
Render the audio after this is done.
[img]http://img.photobucket.com/albums/v92/Indiana_Jonas/Tutorial/7.jpg\" border=\"0\" alt=\"IPB Image\" /]

Step 9: Time to close whatever you were editing with and open Virtual Dub.
Now we're gonna import our audio and video before we do anything else.
Press Ctrl+O and locate the video file you rendered with Huffyuv and import it.
Now Press Audio at the top menu and follow the steps in the screenshot.
When you press WAV Audio you be asked to select the .wav you wanna use, use the one you just rendered.
[img]http://img.photobucket.com/albums/v92/Indiana_Jonas/Tutorial/8.jpg\" border=\"0\" alt=\"IPB Image\" /]

Step 10: A pop-up should now have opened after completing the last step.
This is where we how much our audio shall be compressed and the codec we wanna use to compress the audio with.
Select LAME and choose 128kbps if you're rendering a Medium Quality version or 192kbps if you're render a High Quality version.
[img]http://img.photobucket.com/albums/v92/Indiana_Jonas/Tutorial/9.jpg\" border=\"0\" alt=\"IPB Image\" /]

Step 11: Time to configure Xvid which is the codec we're using to compress our video.
Press Video which is next to Audio on the top menu and follow the steps in the screenshots.
[img]http://img.photobucket.com/albums/v92/Indiana_Jonas/Tutorial/10.jpg\" border=\"0\" alt=\"IPB Image\" /]
[img]http://img.photobucket.com/albums/v92/Indiana_Jonas/Tutorial/11.jpg\" border=\"0\" alt=\"IPB Image\" /]

Step 12: Enter the settings shown in the screenshots below.
The button with the light blue glow indicates which button you have to press to acces these options[/u].
[img]http://img.photobucket.com/albums/v92/Indiana_Jonas/Tutorial/14.jpg\" border=\"0\" alt=\"IPB Image\" /][img]http://img.photobucket.com/albums/v92/Indiana_Jonas/Tutorial/12.jpg\" border=\"0\" alt=\"IPB Image\" /][img]http://img.photobucket.com/albums/v92/Indiana_Jonas/Tutorial/13.jpg\" border=\"0\" alt=\"IPB Image\" /]

Step 13: Now it's time to open a brilliant tool that's included in Xvid called the Bitrate Calculator.
Here you enter how long your movie is and what you want the final file size to be.
Make sure you configure the options so the bitrate is somewhere between 2250 and 3000kbps.
You must also make sure the audio bitrate is the same as the bitrate you select earlier with the LAME codec.
[img]http://img.photobucket.com/albums/v92/Indiana_Jonas/Tutorial/15.jpg\" border=\"0\" alt=\"IPB Image\" /]

Step 14: You can now render your movie.
Keep in your mind the quality may not turn out great on first attempt so i would like to encourage you to try different settings to achieve the best possible quality.[/font]

I hope you found this tutorial helpful and educational.[/i][/font]
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Spoofy on November 19, 2006, 07:10:07 AM: Thank you dearly for this Daffy, will test out immediatly.
Title: Tutorial: Xvid/LAME High Quality Render
Post by: sony on November 19, 2006, 07:24:46 AM: Thank you
Will try it out.
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Brainkiller on November 19, 2006, 08:03:56 AM: I rendered my video and it was 350mb, 5mins 31 seconds. help
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Spoofy on November 19, 2006, 08:39:37 AM: Step 13, Simon
Title: Tutorial: Xvid/LAME High Quality Render
Post by: _Hiei_ on November 19, 2006, 09:46:51 AM: Ohh my eyes! my EYES!
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Brainkiller on November 19, 2006, 10:12:24 AM: Yea, there's nothing to change on step 13
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Makrame on November 19, 2006, 11:42:48 AM: Thanks for re-writing this Daffy I'll try to use this nex time I edit a video.
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Raskal on January 02, 2007, 07:23:17 PM: When I click Render As on my vegas... It doesn't come up with the options your screenshot shows....

Help...
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Makrame on January 02, 2007, 07:28:26 PM: When you click "Render As" you have to click "Custom" in the window that opened ;) Then you'll see the same things as the screenshots.
Title: Tutorial: Xvid/LAME High Quality Render
Post by: BoBsaget on February 28, 2007, 01:02:27 PM: Well, probably a noob question, but I want to use this render but I don't know where to place Huffyev codec etc.. Could anyone explain me where I need to install these files, it would help me a lot! Thanks.
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Aries on February 28, 2007, 04:09:51 PM: Put them in any folder, right click one of the files.....ddl maybe? And there is a 'Install' option, click it
Title: Tutorial: Xvid/LAME High Quality Render
Post by: BoBsaget on February 28, 2007, 09:51:48 PM: Thanks, but it does ask, where to install it then... And I don't know where that is.
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Daffy on February 28, 2007, 11:15:50 PM: Chose the .inf
Title: Tutorial: Xvid/LAME High Quality Render
Post by: BoBsaget on March 01, 2007, 08:37:50 AM: Ah thanks, it works now!
Title: Tutorial: Xvid/LAME High Quality Render
Post by: boxXx on March 25, 2007, 02:25:31 AM: where is the render button in VDub ? *shames*

nvm rendering
Title: Tutorial: Xvid/LAME High Quality Render
Post by: VaNilla on April 29, 2007, 01:18:16 PM: Decided to upload the processing settings incase people don't like setting up Vdub xD.
EDIT - Place Untitled.avi and Untitled.wav in Desktop on a Drive C: btw .
Title: Tutorial: Xvid/LAME High Quality Render
Post by: KillaMarci on May 06, 2007, 07:48:37 AM: When i try to install Huffyuv it always says 'Can't find HUFFYUV.DLL'

EDIT// Never mind , fixed
Title: Tutorial: Xvid/LAME High Quality Render
Post by: KillaMarci on May 06, 2007, 12:19:29 PM: Ok i just rendered the 5min video , with 2600Average Bitrate , it was 289MB big . Then i rendered it with 2312 Average Bitrate and its still 289MB big , what can i do so the video is smaller?
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Link on May 07, 2007, 01:23:09 PM: I dont have that bitrate calculator and i installed "Nic's XviD Codec 1.1.0 b2 build 6.04.2005" and there's only some shit called minicalc and avic ??
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Daffy on May 08, 2007, 01:19:17 PM: There's a bitrate calculator included in it, if you can't find it you can download it separately as well.
Title: Tutorial: Xvid/LAME High Quality Render
Post by: FIGHTER on May 12, 2007, 12:24:41 AM: i try and BTW Thanks
Title: Tutorial: Xvid/LAME High Quality Render
Post by: KillaMarci on May 12, 2007, 09:02:39 AM: I tried it and got awesome quality But whats better ? This or the x264 .mp4 tut?
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Daffy on May 12, 2007, 09:29:16 AM: x264 by far.
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Link on May 12, 2007, 10:02:33 AM: Are there any other/better settings for just one stunt on 30 sec or less ?
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Daffy on May 12, 2007, 03:40:09 PM: For small clips with just one stunt i usually go for 3ivx with a half resolution filter and some mediocre settings so they don't take ages to send or render.
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Link on May 12, 2007, 04:14:17 PM: thanks will try that
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Torque on May 23, 2007, 09:02:19 PM: Has that disclaimer always been there...
Title: Tutorial: Xvid/LAME High Quality Render
Post by: VaNilla on June 08, 2007, 06:19:57 AM: Error Initializing audio stream decompression: the requested conversion is not possible.
Check to make sure you have the required.
Then you can't see the rest of the error, halp .
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Daffy on June 08, 2007, 06:23:39 AM: Render the audio again to make sure it didn't get corrupted, make sure all the projectfiles are avaiable and make sure it has the right bit depth and hz frequenzy.
Title: Tutorial: Xvid/LAME High Quality Render
Post by: VaNilla on June 08, 2007, 06:25:57 AM: Did all that before, just restarted I'll try again.
EDIT - Still not working! .
Title: Tutorial: Xvid/LAME High Quality Render
Post by: VaNilla on June 26, 2007, 08:04:06 AM: Sorry for the double post but I know what the problem is now, Vdub doesn't recognize LAME audio, I've tried re-installing and stuff but it wont work, :/.
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Labiloute on June 26, 2007, 10:06:54 AM: Just one question this tutorial render the same quality to Unbroken
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Ostits on June 26, 2007, 10:30:21 AM: Quote from: Labiloute
Just one question this tutorial render the same quality to Unbroken
I used this tutorial to render Unbroken...
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Labiloute on June 26, 2007, 11:42:50 AM: Quote from: Ostits
I used this tutorial to render Unbroken...
Thank you very much Ostits

Just how many bitrate have you write ?
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Ostits on June 26, 2007, 01:50:23 PM: I had something like 3500. Just test how far your willing to go in file size.
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Juan on June 26, 2007, 01:52:18 PM: HAHA, i cant view movies with these settings in WMP, i have to open them in VLC.
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Labiloute on June 27, 2007, 09:26:09 AM: Yeah but read with VLC is little bad where as the quality of WLM is better
Title: Tutorial: Xvid/LAME High Quality Render
Post by: boxXx on July 31, 2007, 08:38:30 AM: i got the k-lite codec pack do i need to download "XviD (nic's version)" still ?
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Daffy on July 31, 2007, 08:40:51 AM: Dunno, i don't use a pack where i don't need 90% of what it contains.
Title: Tutorial: Xvid/LAME High Quality Render
Post by: boxXx on July 31, 2007, 08:48:32 AM: Quote from: Daffy
Dunno, i don't use a pack where i don't need 90% of what it contains.

Thats true

i'll just install the one you linked

(btw the thing you sended yesterday looks fucking awesome allready !)
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Ev0x on August 10, 2007, 04:31:33 PM: My render have a problem:

Help me
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Souzuk on September 11, 2007, 11:52:41 AM: that is awesome but i have my Own Codec and mine is Ownage
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Daffy on September 12, 2007, 02:12:48 AM: Ev0x: Re-install the codec and re-render the source.
Souzuk: x264?
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Eddeman on September 12, 2007, 02:41:22 AM: I have the same thing as Ev0x except mine pops up when I've finished rendering in virtual dub, and doesn't seem to do shit
Title: Tutorial: Xvid/LAME High Quality Render
Post by: KoreaBank on September 24, 2007, 05:41:47 AM: maybe hard ..
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Ev0x on November 18, 2007, 06:33:00 AM: Quote from: Daffy
Ev0x: Re-install the codec and re-render the source.
Souzuk: x264?

I find my problem. My problem was because i had installed K-Lite Codec. so I uninstalled the codec and re encoding with 4000BitRate and no problem.

7minutes - 203Mo - Great Quality
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Dogger on March 22, 2008, 04:53:00 AM: Woah ! The best off...
2:00, 800x600, HQ Audio, 15 mb
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Willzyyy on July 16, 2008, 09:31:41 AM: I know I've asked this before, but Daffy? Have you used these settings in any WH vids or Solos at all?

EDIT: I can't find the bitrate calculator.
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Mythic on July 16, 2008, 10:49:13 AM: He used these in Post Mortem's HQ if im right.

C:\Program Files\Xvid\MiniCalc.exe is the calculator he means I think.
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Willzyyy on July 16, 2008, 11:14:28 AM: Quote from: Mythic
He used these in Post Mortem's HQ if im right.

C:\Program Files\Xvid\MiniCalc.exe is the calculator he means I think.
^^Thanks, I rendered it, but the quality looks kinda like the normal replay and no where near as good as Post Mortem. It is more like a normal WMV render (HQish) I recorded my stunts at 25fps. Shall I click 25(PAL) instead of 30fps?
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Mythic on July 16, 2008, 11:48:39 AM: No, always record and render at 30fps. I think the color corrections are what you're speaking of, try out Daffy's tutorial.

Color Optimizing (http://www.gtastunting.net/forums/index.php?showtopic=17934).

They're not exactly same as Daffy's ones from Post Mortem, but they should give it a bit better look.

1) Record your stunts using Fraps (Full Size, 30fps)

(http://xs229.xs.to/xs229/08293/help2fraps750.jpg)

2) Import them into Vegas and apply Daffy's tutorial's filters to Track's FX.

(http://xs229.xs.to/xs229/08293/help1904.jpg)

3) Render using this tutorial. It should look better.
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Willzyyy on July 16, 2008, 12:00:02 PM: Quote from: Mythic
No, always record and render at 30fps. I think the color corrections are what you're speaking of, try out Daffy's tutorial.

Color Optimizing (http://www.gtastunting.net/forums/index.php?showtopic=17934).

They're not exactly same as Daffy's ones from Post Mortem, but they should give it a bit better look.

1) Record your stunts using Fraps (Full Size, 30fps)
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Mythic on July 16, 2008, 12:16:46 PM: Yes, they'll look floaty. Use 30fps at rendering and recording in VC (in SA, both at 25fps).
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Willzyyy on July 16, 2008, 12:28:58 PM: OK thanks. I have done daffy's Color correction. It ownz, but it is the player model and bike. The edges of the bike and player have bad graphics. I'll send a pic.
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Daffy on July 17, 2008, 03:40:10 PM: Turn on some anti-aliasing and use BK's FPS tutorial.
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Willzyyy on July 18, 2008, 01:45:10 AM: I've done it. Thanks man, but the problem was that I was recording my stunts at one of the lowest resolutions. I have now made the resolutions in the game high and now the quality is clean, smooth and looks great. Cheers guys for all you help.
Title: Tutorial: Xvid/LAME High Quality Render
Post by: DeadlyExterior on August 26, 2008, 05:32:58 PM: Hey, how do i get the lame encoder running?
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Daffy on August 26, 2008, 08:41:08 PM: If you could be a little more detailed about where you're stuck and what you've tried i might be able to help.
Title: Tutorial: Xvid/LAME High Quality Render
Post by: DeadlyExterior on August 27, 2008, 09:06:03 AM: Sorry lol, im stuck at step 13, i cant find where the bit rate calculator is.
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Mythic on August 27, 2008, 09:18:35 AM: Quote from: Mythic
C:\Program Files\Xvid\MiniCalc.exe is the calculator he means I think.
Title: Tutorial: Xvid/LAME High Quality Render
Post by: bluedagger on October 17, 2008, 04:12:55 PM: Is it the same to render DIRECTLY from vegas in the MPEG-4 Xvid quality? I did that and got shit quality, low filesize though.
Title: Tutorial: Xvid/LAME High Quality Render
Post by: KillaMarci on November 08, 2008, 04:45:53 PM: Hey Daffy

Tried out yer tutorial for the second time , did everything like you said but when I click on "render as .avi" in VDub it say "Oops Vdub has crashed" and it gives me this crash report..

Quote
VirtualDub crash report -- build 25854 (release)
--------------------------------------

Disassembly:
62680e60: 40 inc eax
62680e61: 89c1 mov ecx, eax
62680e63: d1e9 shr ecx, 1
62680e65: 29cb sub ebx, ecx
62680e67: 895c2408 mov [esp+08h], ebx
62680e6b: 8b742430 mov esi, [esp+30h]
62680e6f: 8b7c2428 mov edi, [esp+28h]
62680e73: 8b54242c mov edx, [esp+2ch]
62680e77: 8b6c2448 mov ebp, [esp+48h]
62680e7b: 8b5c244c mov ebx, [esp+4ch]
62680e7f: 09db or ebx, ebx
62680e81: 741b jz 62680e9e
62680e83: 31db xor ebx, ebx
62680e85: 29c3 sub ebx, eax
62680e87: 29c3 sub ebx, eax
62680e89: 29c3 sub ebx, eax
62680e8b: 29d3 sub ebx, edx
62680e8d: 895c2410 mov [esp+10h], ebx
62680e91: 89e8 mov eax, ebp
62680e93: 83e801 sub eax, 01h
62680e96: 52 push edx
62680e97: f7e2 mul eax, edx
62680e99: 5a pop edx
62680e9a: 01c7 add edi, eax
62680e9c: f7da neg edx
62680e9e: 8b44243c mov eax, [esp+3ch]
62680ea2: 8b5c2434 mov ebx, [esp+34h]
62680ea6: 8b4c2438 mov ecx, [esp+38h]
62680eaa: 0f6f3d60816a62 movq mm7, [626a8160]
62680eb1: 892c24 mov [esp], ebp
62680eb4: 8b6c2404 mov ebp, [esp+04h]
62680eb8: 0fefe4 pxor mm4, mm4
62680ebb: 0fefed pxor mm5, mm5
62680ebe: 0f6e07 movd mm0, [edi]
62680ec1: 0f6e1417 movd mm2, [edi+edx]
62680ec5: 0f60c4 punpcklbw mm0, mm4
62680ec8: 0f60d5 punpcklbw mm2, mm5
62680ecb: 0f6ff0 movq mm6, mm0
62680ece: 0ffdf2 paddw mm6, mm2
62680ed1: 0ff5c7 pmaddwd mm0, mm7
62680ed4: 0ff5d7 pmaddwd mm2, mm7
62680ed7: 0f6fe0 movq mm4, mm0
62680eda: 0f6fea movq mm5, mm2
62680edd: 0f73d420 psrlq mm4, 20h
62680ee1: 0f73d520 psrlq mm5, 20h
62680ee5: 0ffec4 paddd mm0, mm4
62680ee8: 0ffed5 paddd mm2, mm5
62680eeb: 0fefe4 pxor mm4, mm4
62680eee: 0fefed pxor mm5, mm5
62680ef1: 0f6e4f03 movd mm1, [edi+03h] <-- FAULT
62680ef5: 0f6e5c1703 movd mm3, [edi+edx+03h]
62680efa: 0f60cc punpcklbw mm1, mm4
62680efd: 0f60dd punpcklbw mm3, mm5
62680f00: 0ffdf1 paddw mm6, mm1
62680f03: 0ffdf3 paddw mm6, mm3
62680f06: 0ff5cf pmaddwd mm1, mm7
62680f09: 0ff5df pmaddwd mm3, mm7
62680f0c: 0f6fe1 movq mm4, mm1
62680f0f: 0f6feb movq mm5, mm3
62680f12: 0f73d420 psrlq mm4, 20h
62680f16: 0f73d520 psrlq mm5, 20h
62680f1a: 0ffecc paddd mm1, mm4
62680f1d: 0ffedd paddd mm3, mm5
62680f20: 52 push edx
62680f21: 0f7ec2 movd edx, mm0
62680f24: c1ea08 shr edx, 08h
62680f27: 83c210 add edx, 10h
62680f2a: 8816 mov [esi], dl
62680f2c: 0f7eca movd edx, mm1
62680f2f: c1ea08 shr edx, 08h
62680f32: 83c210 add edx, 10h
62680f35: 885601 mov [esi+01h], dl
62680f38: 0f7ed2 movd edx, mm2
62680f3b: c1ea08 shr edx, 08h
62680f3e: 83c210 add edx, 10h
62680f41: 881406 mov [esi+eax], dl
62680f44: 0f7eda movd edx, mm3
62680f47: c1ea08 shr edx, 08h
62680f4a: 83c210 add edx, 10h
62680f4d: 88540601 mov [esi+eax+01h], dl
62680f51: 0f6fc6 movq mm0, mm6
62680f54: 0ff53570816a62 pmaddwd mm6, [626a8170]
62680f5b: 0ff505 pmaddwd mm0, [ebp]
62680f5e: 68 db 68h
62680f5f: 81 db 81h

Built on KOS-MOS on Sun Nov 05 13:25:45 2006 using compiler version 1400

Windows 5.1 (Windows XP build 2600) [Service Pack 2]

EAX = 00000710
EBX = 076a74a7
ECX = 077374a7
EDX = ffffec50
EBP = 00000002
ESI = 074acb0e
EDI = 0832bffa
ESP = 0914dbf0
EIP = 62680ef1
EFLAGS = 00010202
FPUCW = ffff027f
FPUTW = ffffaaaa

Crash reason: Access Violation

Crash context:
An out-of-bounds memory access (access violation) occurred in module \'xvidcore\'...

...reading address 0832C000...

...while compressing frame 0 from 07e20020 to 08330020 using codec "XviD MPEG-4 Codec" (w32videocodecpack.cpp:671)...

...while running thread "Processing" (thread.cpp:151).

Pointer dumps:

EBX 076a74a3: 80808080 00000000 00000000 00000000 00000000 00000000 00000000 00000000
ECX 077374a3: 80808080 00000000 00000000 00000000 00000000 00000000 00000000 00000000
ESI 074acb0a: 10101010 00000000 00000000 00000000 00000000 00000000 00000000 00000000
EDI 0832bffa: 00000000
ESP 0914dbf0: 0000041a 00000690 00000040 00000080 ffffd8a0 80000000 000013b0 00000000
0914dc10: 00000690 6262ff2c 07e20020 000013b0 074ac480 076a7160 07737160 00000710
0914dc30: 00000388 00000690 0000041a 80000000 00000000 00000000 00000000 00000000
0914dc50: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

Thread call stack:
62680ef1: xvidcore!xvid_plugin_ssim [62600000+73e30+d0c1]
6262ff2c: xvidcore!xvid_encore [62600000+12860+1d6cc]
6260fa77: xvidcore!0000fa77
6df0c0f2: xvidvfw!DriverProc [6df00000+bd40+3b2]
7c920833: ntdll!RtlAllocateHeap [7c910000+105d4+25f]
7c920833: ntdll!RtlAllocateHeap [7c910000+105d4+25f]
7c80b5b8: kernel32!GetModuleHandleA [7c800000+b529+8f]
7c80b58c: kernel32!GetModuleHandleA [7c800000+b529+63]
7c80b5a1: kernel32!GetModuleHandleA [7c800000+b529+78]
7c925041: ntdll!bsearch [7c910000+14ffb+46]
7c925233: ntdll!bsearch [7c910000+14ffb+238]
7c9255c9: ntdll!RtlHashUnicodeString [7c910000+15465+164]
7c92554a: ntdll!RtlHashUnicodeString [7c910000+15465+e5]
7c9253f5: ntdll!RtlFindActivationContextSectionString [7c910000+15319+dc]
7c925af1: ntdll!RtlDosApplyFileIsolationRedirection_Ustr [7c910000+157a3+34e]
7c925b4f: ntdll!RtlDosApplyFileIsolationRedirection_Ustr [7c910000+157a3+3ac]
7c925707: ntdll!RtlHashUnicodeString [7c910000+15465+2a2]
7c925a00: ntdll!RtlDosApplyFileIsolationRedirection_Ustr [7c910000+157a3+25d]
7c925a65: ntdll!RtlDosApplyFileIsolationRedirection_Ustr [7c910000+157a3+2c2]
7c924859: ntdll!RtlGetLongestNtPathLength [7c910000+147df+7a]
7c923212: ntdll!LdrLockLoaderLock [7c910000+13171+a1]
7c923281: ntdll!LdrUnlockLoaderLock [7c910000+13229+58]
7c923288: ntdll!LdrUnlockLoaderLock [7c910000+13229+5f]
7c92664e: ntdll!LdrGetDllHandleEx [7c910000+165a7+a7]
7c923288: ntdll!LdrUnlockLoaderLock [7c910000+13229+5f]
7c9266f1: ntdll!LdrGetDllHandleEx [7c910000+165a7+14a]
7c92657e: ntdll!LdrLoadDll [7c910000+161ca+3b4]
7c92657e: ntdll!LdrLoadDll [7c910000+161ca+3b4]
7c92657e: ntdll!LdrLoadDll [7c910000+161ca+3b4]
7c92659e: ntdll!LdrGetDllHandle [7c910000+16586+18]
7c80e693: kernel32!GetModuleHandleW [7c800000+e63c+57]
7c80e6a3: kernel32!GetModuleHandleW [7c800000+e63c+67]
7c80e693: kernel32!GetModuleHandleW [7c800000+e63c+57]
7c80e6a3: kernel32!GetModuleHandleW [7c800000+e63c+67]
7c80e6a3: kernel32!GetModuleHandleW [7c800000+e63c+67]
7c925041: ntdll!bsearch [7c910000+14ffb+46]
7c925233: ntdll!bsearch [7c910000+14ffb+238]
7c9255c9: ntdll!RtlHashUnicodeString [7c910000+15465+164]
7c92554a: ntdll!RtlHashUnicodeString [7c910000+15465+e5]
7c9253f5: ntdll!RtlFindActivationContextSectionString [7c910000+15319+dc]
7c925af1: ntdll!RtlDosApplyFileIsolationRedirection_Ustr [7c910000+157a3+34e]
7c925b4f: ntdll!RtlDosApplyFileIsolationRedirection_Ustr [7c910000+157a3+3ac]
7c925707: ntdll!RtlHashUnicodeString [7c910000+15465+2a2]
7c925a00: ntdll!RtlDosApplyFileIsolationRedirection_Ustr [7c910000+157a3+25d]
7c925a65: ntdll!RtlDosApplyFileIsolationRedirection_Ustr [7c910000+157a3+2c2]
7c91d4ea: ntdll!NtAllocateVirtualMemory [7c910000+d4de+c]
7c9280ff: ntdll!RtlReAllocateHeap [7c910000+179fd+702]
7c921bff: ntdll!RtlInitializeCriticalSection [7c910000+11b2d+d2]
7c92825d: ntdll!RtlReAllocateHeap [7c910000+179fd+860]
7c921538: ntdll!wcsncpy [7c910000+10a8f+aa9]
7c921596: ntdll!wcsncpy [7c910000+10a8f+b07]
7c9206eb: ntdll!RtlAllocateHeap [7c910000+105d4+117]
7c923212: ntdll!LdrLockLoaderLock [7c910000+13171+a1]
7c923281: ntdll!LdrUnlockLoaderLock [7c910000+13229+58]
7c923288: ntdll!LdrUnlockLoaderLock [7c910000+13229+5f]
7c92664e: ntdll!LdrGetDllHandleEx [7c910000+165a7+a7]
7c923288: ntdll!LdrUnlockLoaderLock [7c910000+13229+5f]
7c9266f1: ntdll!LdrGetDllHandleEx [7c910000+165a7+14a]
00575567: ValidateScopeTableHandlers()
00575701: _ValidateEH3RN()
7c920833: ntdll!RtlAllocateHeap [7c910000+105d4+25f]
00568da9: _except_handler3()
7c9137bf: ntdll!RtlConvertUlongToLargeInteger [7c910000+3745+7a]
7c91378b: ntdll!RtlConvertUlongToLargeInteger [7c910000+3745+46]
7c947860: ntdll!LdrAddRefDll [7c910000+37619+247]
7c91d4ea: ntdll!NtAllocateVirtualMemory [7c910000+d4de+c]
7c9280ff: ntdll!RtlReAllocateHeap [7c910000+179fd+702]
75ec18a8: MSVFW32!ICSendMessage [75ec0000+187d+2b]
75ec4c09: MSVFW32!ICCompress [75ec0000+4ba6+63]
00557938: VDVideoCompressorVCM::PackFrameInternal()
00557dbc: VDVideoCompressorVCM::CompressFrame()
004bee06: AVIOutputFile::init()
00538391: VDPixmapBlt()
004720a9: VDDubProcessThread::WriteVideoFrame()
7c9205c8: ntdll!RtlFreeHeap [7c910000+1043d+18b]
7c92056d: ntdll!RtlFreeHeap [7c910000+1043d+130]
7c9206eb: ntdll!RtlAllocateHeap [7c910000+105d4+117]
005672f6: malloc()
0050530b: VDFileAsyncNT::FastWrite()
00475382: VDStreamInterleaver::PushStreams()
00475389: VDStreamInterleaver::PushStreams()
0047294f: VDDubProcessThread::ThreadRun()
7c81eb33: kernel32!RaiseException [7c800000+1eae1+52]
7c91d919: ntdll!NtDuplicateObject [7c910000+d90d+c]
7c80e07b: kernel32!DuplicateHandle [7c800000+e016+65]
0046290b: VDThreadInitHandler()
004fddf6: VDThread::StaticThreadStart()
0056ca28: _callthreadstartex()
0056cacd: _threadstartex@4()
004bc491: AVIOutputFile::FastWrite()
7c80b50b: kernel32!GetModuleFileNameA [7c800000+b357+1b4]
004bc491: AVIOutputFile::FastWrite()

-- End of report

hopefully you understand some of it

I tried to render without the audio to see if its the audio or the video and it crashed again and I got this

Quote
An out-of-bounds memory access (access violation) occurred in module \'xvidcore\'...
...reading address 074AC000...
...while compressing frame 0 from 06fa0020 to 074b0020 using codec "XviD MPEG-4 Codec" (w32videocodecpack.cpp:671)...
...while running thread "Processing" (thread.cpp:151).
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Daffy on November 09, 2008, 09:32:33 AM: http://www.gtastunting.net/forums/index.php?showtopic=27396 (http://www.gtastunting.net/forums/index.php?showtopic=27396)
Title: Tutorial: Xvid/LAME High Quality Render
Post by: KillaMarci on November 09, 2008, 10:04:12 AM: That's just too complicated :|
Title: Tutorial: Xvid/LAME High Quality Render
Post by: Daffy on November 09, 2008, 11:18:49 AM: Not really, you haven't even tried.
Title: Re: Tutorial: Xvid/LAME High Quality Render
Post by: bluedagger on March 31, 2011, 01:43:00 AM: EPIC BUMP!

The pics need updating :)