Comments

randyvild wrote on 3/11/2003, 5:04 PM
Had the same problem. Thought it was just me :) Okay, uninstall VV3/4 or whatever. Then go to program files and delete the folders. If you also had the beta (like I did) make sure you delete those files under "Sonic Foundry Beta". In any case, delete all folders/files for VV. Then go to regedit and delete the VV keys in HKey Local Machine/Software/Sonic Foundry. There should be a Vegas key on the left and you should totally blow that away. Also in Software you will see a key for "MainConcept". Be sure to delete that too. Now you shouldn't have to reboot. Reinstall VV4 and there you go .. . Mine worked after that.

Chessmaster wrote on 3/11/2003, 5:35 PM
Actually the solution is to buy a legal copy of the program. The problem you describe is because you have an illegal copy of the program, usually registered with the various key-gens available off the net.

The solution given above is basically another way around so the illegal software users can use VV4 probably registered with the illegal VV4 key-gen that has popped up now.

If this is not the case, then I am sure you will contact sofo with all your serial and registration details so they can validate your copy and give you the correct help.
David_Kuznicki wrote on 3/11/2003, 5:43 PM
I can't say whether or not it's a cracked copy problem or not-- mine works fine, though. I did, however, have to register the MPEG plug-in (as I'm sure everyone did) before using it.

David.
randyvild wrote on 3/11/2003, 6:11 PM
Not so chessmaster. I have a legite copy and proud to say so and I had the same problem.


Randini
Chessmaster wrote on 3/11/2003, 6:36 PM
Thats fine, a quick search of this forum would have revealed this problem come up before, and since it is a big program problem, it would have been easier to send an email off to sofo, unless you want people to give you answers in this forum and try to avoid asking the maker.

People with illegal copies never contact the maker, simply because too many questions about registration are asked before many will help. Sofo are like that.
SonyEPM wrote on 3/12/2003, 9:56 AM
We have found a potential MPEG-1 render problem and will address it in the next Vegas update. This error doesn't appear on every machine, but it is certainly there and we'll do our best to fix it asap.
[r]Evolution wrote on 3/12/2003, 11:13 PM
I too have a LEGIT COPY of VV4 & I also have this problem!

People come to the forums to get answers because if you go to the Manufacturers, of whatever your software is, they will only give you so much support. After that you have to start paying for it. When you have a re-occuring problem such as this, you will use up your tech support within the first week after purchasing. It is always best to go to the forums first. Even the Tech Support tells you that. It has nothing to do with LEGAL or NOT LEGAL copies. Granted, some of the users probably DO have ILLEGAL copies, but the problem also exists in legal copies.

It burns me up when they release a product knowing that it is sub-standard anyway. That's BS! I Love the Sonic Foundry line. I have VV4+DVD, SF6, ACID4, NoiseReduction, BatchConverter, you name it! It is an affordable line with very impressive output. WHEN IT WORKS LIKE IT SHOULD! And if you pay money for it. IT SHOULD WORK!

P4, 2.4Ghz, 512DDR, Asus MoBo, 2x100gig 7200RPM hd's

I am still tinkering with the settings though, cause every sytem reacts differently. -->My render as AVI creates stuttered and skipping files. Here is the error that I just got while trying to render as mainconcept mpeg1.<-- LEGAL COPY!!!

Sonic Foundry Vegas 4.0
Version 4.0 (Build 115)
Exception 0xC0000005 (access violation) WRITE:0xC685D36 IP:0x5327422
In Module 'mpgvout.004' at Address 0x5320000 + 0x7422
Thread: ProgMan ID=0x96C Stack=0x1ABD000-0x1AC0000
Registers:
EAX=00000077 CS=001b EIP=05327422 EFLGS=00010202
EBX=0000073d SS=0023 ESP=01abddc4 EBP=000000c8
ECX=0c685d36 DS=0023 ESI=29639fa2 FS=0038
EDX=00000072 ES=0023 EDI=000000f4 GS=0000
Bytes at CS:EIP:
05327422: 66 89 19 29 C2 29 D3 83 f..).)..
0532742A: C6 02 66 89 59 02 83 C1 ..f.Y...
Stack Dump:
01ABDDC4: 0C673008 0C650000 + 23008
01ABDDC8: 0C772008 0C650000 + 122008
01ABDDCC: 0C673968 0C650000 + 23968
01ABDDD0: 0C673814 0C650000 + 23814
01ABDDD4: 01ABDE40 019C0000 + FDE40
01ABDDD8: 00002D00
01ABDDDC: 000000F0
01ABDDE0: 00000590
01ABDDE4: 00000002
01ABDDE8: 000010E0
01ABDDEC: 00000590
01ABDDF0: 000005A0
01ABDDF4: 00000B40
01ABDDF8: 00000590
01ABDDFC: 0C68D010 0C650000 + 3D010
01ABDE00: 0C68D008 0C650000 + 3D008
> 01ABDE10: 05341F10 05320000 + 21F10 (mpgvout.004)
01ABDE14: 0C673008 0C650000 + 23008
01ABDE18: 0C772008 0C650000 + 122008
01ABDE1C: 295F1240 295F0000 + 1240
01ABDE20: 000005A0
> 01ABDE48: 77F5166A 77F50000 + 166A (ntdll.dll)
> 01ABDE50: 0535CE0B 05320000 + 3CE0B (mpgvout.004)
01ABDE54: 0C673008 0C650000 + 23008
01ABDE58: 0C772008 0C650000 + 122008
01ABDE5C: 0C673968 0C650000 + 23968
01ABDE60: 00000000
> 01ABDE9C: 005CB357 00400000 + 1CB357 (vegas40.exe)
01ABDEA0: 035CCD30 03520000 + ACD30
01ABDEA4: 035CC5D0 03520000 + AC5D0
> 01ABDEA8: 005CB8C3 00400000 + 1CB8C3 (vegas40.exe)
01ABDEAC: 0C67394C 0C650000 + 2394C
01ABDEB0: 0C673968 0C650000 + 23968
01ABDEB4: 029E47F0 02920000 + C47F0
01ABDEB8: 00000000
> 01ABDED0: 0535AD3B 05320000 + 3AD3B (mpgvout.004)
01ABDED4: 0C673008 0C650000 + 23008
01ABDED8: 00000044
> 01ABDEF4: 77F5F485 77F50000 + F485 (ntdll.dll)
> 01ABDEFC: 77F79005 77F50000 + 29005 (ntdll.dll)
> 01ABDF0C: 7C00118F 7C000000 + 118F (MSVCR70.dll)
> 01ABDF18: 7C001194 7C000000 + 1194 (MSVCR70.dll)
> 01ABDF20: 05370D1C 05320000 + 50D1C (mpgvout.004)
- - -
01ABFFF0: 00000000
01ABFFF4: 004E2CC0 00400000 + E2CC0 (vegas40.exe)
01ABFFF8: 006CAC28 00400000 + 2CAC28 (vegas40.exe)
01ABFFFC: 00000000


So how long do you think we will have to wait for a solution?

Lamont
David_Kuznicki wrote on 3/13/2003, 7:45 AM
Talk about sticking my foot in my mouth!

I went home last night & did some longer MPEG 1 renders (still reasonably short-- in the 3 minute range), and lo-and-behold, it stopped after getting around 75% of the way through it with the message 'Vegas has generated errors' (or something to that effect), followed by 'the source of the errors could not be determined.'

This happened twice, before I tried burning straight from the timeline to a VCD, at which point it rendered fine. Strange...

David.
[r]Evolution wrote on 3/13/2003, 8:03 PM
OK....So I left a 12minute roject set to render to VCD, which should be an MPEG1, right? (because I saw a post that said it worked for them) and it hung up at 67%. I left it sitting for 8 hours while I was at work. Started it this morning when I woke up, Ended it just now when I came home.

My task manager showed VEGAS still running fine. It seems as if the program thought it was still going good. I did not get an error message. I hit 'cancel' and it stopped and built an output of what appears to be about 67%, just like it said.

I'm going to render the last part of my video in VV4. Re-Install VV3, then open and sync the files in VV3 for completion. I'm sooo over VV4! (yeah right I LOVE IT! I just wish it would work for me)

EDIT:
For tonight I gave up on SonicFoundry all together. I pieced together 6 chunks of video from "mis-renders" in VV4 and assembled them together in Premiere 6.5 and had NO PROBLEMS WHAT SO EVER. I synced em up and exported timeline as movie. Simple with NO PROBLEMS or CRASHES. I used to use Premiere as my NLE but switched to VEGAS because of the 'real time' editing. But what the hell good is real time editing if you can't output anything?

My fingers are crossed soooo hard that SoFo does something about this. (I love putting the blame on someone else- watch it be some little thing that I am overlooking)

Lamont
arcorob wrote on 10/8/2004, 7:03 AM
Did you guys ever fix this for version 5 ? I have a 100% registered legal paid for Vegas 05 that I bought when it firts came out. Has worked fine BUT this is the first time I tried to render an MPEG1. It hangs half way through.

So what is the fix ?