Rendering problems

ahfoon wrote on 11/2/2002, 6:46 PM
I'm running an AMD Athlon with xp 2000+ (with Windows xp pro sp1) 1.67 Ghz processor, 1 Gb of RAM. I'v utilized only 19% of my recources, yet I'm unable to render down (even dynamic ram previews) at a high resolution. SF tech support has had me delete, uninstall, re-install, yada yada yada. I currently can't even get 20 seconds into a 30 second project when rendering or building a preview. any Ideas?

Comments

Tyler.Durden wrote on 11/2/2002, 6:55 PM
You might try setting your ram to max..

Are you rendering to default DV template?

More info might be helpful:

Full System Specs
Project specs & folders
What exactly happens or messages you get (or not)
Video hardware
How video captured
Stuff like that


MPH
philfort wrote on 11/2/2002, 7:01 PM
You don't have a pitch shift effect in an audio track, do you? I encountered a problem where my machines virtual memory would be completely used up after about a minute (video time) of rendering. I usually had to reboot to recover.
In this case you'd see the Total Commit Charge going up and up on the Performance tab in Task Manager, till it reaches the limit. I removed effects one by one, and finally found the culprit... pitch shift.
ahfoon wrote on 11/3/2002, 4:21 AM
It really doesn't matter what I'm using (mpeg, avi, mov...) as source material, it always dumps out. I have several projects (with different sources) and it happens with all of them. I've tried using varying degrees of RAM between 16 & 896. I always get the same error message:

Sonic Foundry Vegas Video 3.0
Version 3.0c (Build 138)
Exception 0xC0000005 (access violation) READ:0x10B12000 IP:0x167365E
In Module 'sftrans1.dll' at Address 0x15D0000 + 0xA365E
Thread: Engine_RenderFromCookedSlices ID=0x5D0 Stack=0x1A9D000-0x1AA0000
Registers:
EAX=000001e0 CS=001b EIP=0167365e EFLGS=00010216
EBX=00000b00 SS=0023 ESP=01a9d104 EBP=01a9d170
ECX=000000da DS=0023 ESI=10b12000 FS=0038
EDX=10c80020 ES=0023 EDI=10c807b8 GS=0000
Bytes at CS:EIP:
0167365E: F3 A5 8B CB 83 E1 03 F3 ........
01673666: A4 8B 75 10 8B 4D F0 03 ..u..M..
Stack Dump:
01A9D104: 01A9D1D8 019A0000 + FD1D8
01A9D108: 109C0068 109C0000 + 68
01A9D10C: 10DCA020 10C80000 + 14A020
01A9D110: 00230000 00140000 + F0000
01A9D114: 00000000
01A9D118: 00000000
01A9D11C: 000001E0
01A9D120: 01A9D160 019A0000 + FD160
01A9D124: 77E9BB86 77E60000 + 3BB86 (kernel32.dll)
01A9D128: 77E81890 77E60000 + 21890 (kernel32.dll)
01A9D12C: 00029561
01A9D130: 0014B000 00140000 + B000
01A9D134: 77E71754 77E60000 + 11754 (kernel32.dll)
01A9D138: 00230008 00140000 + F0008
01A9D13C: 77E716EF 77E60000 + 116EF (kernel32.dll)
01A9D140: 0014B000 00140000 + B000
> 01A9D144: 01E1A350 01DF0000 + 2A350 (Indeo4.qtx)
> 01A9D148: 77E733FB 77E60000 + 133FB (kernel32.dll)
01A9D14C: 000001DF
01A9D150: 00000000
01A9D154: 10C80020 10C80000 + 20
> 01A9D16C: 77E9BB86 77E60000 + 3BB86 (kernel32.dll)
> 01A9D174: 01673E13 015D0000 + A3E13 (sftrans1.dll)
01A9D178: 10DCA020 10C80000 + 14A020
01A9D17C: 01A9D1D8 019A0000 + FD1D8
01A9D180: FFFFF500
01A9D184: 10B11868 109C0000 + 151868
> 01A9D1A4: 01674F46 015D0000 + A4F46 (sftrans1.dll)
01A9D1A8: 10C80020 10C80000 + 20
01A9D1AC: 01A9D1D8 019A0000 + FD1D8
01A9D1B0: 000002C0
01A9D1B4: 10B10D28 109C0000 + 150D28
> 01A9D240: 00808000 00400000 + 408000 (vegas30.exe)
01A9D244: 00000000
01A9D248: 000002C0
01A9D24C: 00000000
01A9D250: 000001E0
> 01A9D26C: 005D8000 00400000 + 1D8000 (vegas30.exe)
01A9D270: 003E4000 003E0000 + 4000
> 01A9D27C: 005D8000 00400000 + 1D8000 (vegas30.exe)
- - -
01A9FFF0: 00000000
01A9FFF4: 004E9EC0 00400000 + E9EC0 (vegas30.exe)
01A9FFF8: 006592E0 00400000 + 2592E0 (vegas30.exe)
01A9FFFC: 00000000

It's crazy!
ahfoon wrote on 11/3/2002, 4:29 AM
I'm an audio producer by trade, so I tend to work with solid 44,100 hz wav mix downs (I don't do any audio adjusting in vegas at all) so the pitch problem wouldn't apply. I noticed the problem while I was using alot of video fx though... I tried removing fx one by one like you suggested... but no such luck. ARRGGHHH!

thanks for your help, though
BillyBoy wrote on 11/3/2002, 7:10 PM
My first AMD had a similar problem. Only Vegas would crash. Turned out just dropping the clock speed down a tad cured it. Still don't know why. I've build several AMD's since with the same and different chipsets and had no problem at all expect that my latest refused to be stable with the 133 DDR memory the IWill MB claimed it supported. I booted, then just dragging the mouse across the desktop would corrupt the kerrnel over and over. I was pulling my hair out copying the corrupt Windows files from one machine to the new one over and over. The new box would sometimes work for a few minutes, maybe up to an hour, then crash all over again. Finally I put in slightly slower memory after trying a repacement with the same speed memory, been rock solid since.

Also, be aware that Windows XP is much more fussy about memory. In other boxes what worked fine on slower PC's with Windows 98 or W2000, crashed and burned under XP if using a fast AMD.