Trouble Rendering - SFTRANS1.DLL error

addu786 wrote on 10/17/2003, 7:53 AM
Hi,

Trying to render a project (DV project to DVD NTSC Template) with the latest build of Vegas 4.0 -- it starts off rendering but crashes when it reaches the first *fancy* transition (I have a plugin chain with NOISE and BORDER). Error message is a bunch of numbers complaining about "SFTRANS1.DLL" crash. I removed the transition and tried re-rendering, this time it passed the first *crash* point and crashed again after rendering around 500MB saying "An unexpected error has occured" with absolutely no details at all (not sure if it was at another transition effect in the timeline, will confirm).

Has anyone of you seen this before or know anything about the reason behind this error? please write back, I have worked real hard (a few overnight sessions) creating this 1hr 40 mins project and anxious to burn a DVD out of it.

Comments

jetdv wrote on 10/17/2003, 8:26 AM
Sounds like you need to reinstall.
addu786 wrote on 10/17/2003, 8:33 AM
Thanx! .. re-installing Vegas was next on my list -- I am sure something corrupted my .DLL file(s). Thanks for your post JetDV!

addu786
addu786 wrote on 10/17/2003, 9:18 AM
Re-installed Vegas but it still crashing, here is the exact error message (PLEASE HELP!):

Sonic Foundry Vegas 4.0
Version 4.0d (Build 205)
Exception 0xC0000005 (access violation) READ:0x251C368 IP:0x1BE0990
In Module 'sftrans1.dll' at Address 0x1AF0000 + 0xF0990
Thread: Engine_RenderFromCookedSlices ID=0xD54 Stack=0x241C000-0x2420000
Registers:
EAX=0003ffff CS=001b EIP=01be0990 EFLGS=00010206
EBX=0003ffff SS=0023 ESP=0241c15c EBP=0241c220
ECX=00000001 DS=0023 ESI=0251c368 FS=0038
EDX=00000001 ES=0023 EDI=0251c368 GS=0000
Bytes at CS:EIP:
01BE0990: 66 0F 6E 06 66 0F 6E 17 f.n.f.n.
01BE0998: 66 0F 62 C2 66 0F 6E 14 f.b.f.n.
Stack Dump:
0241C15C: 0241C234 02320000 + FC234
0241C160: 00000000
0241C164: 00000000
0241C168: 0241C234 02320000 + FC234
0241C16C: 0618F3B0 05CE0000 + 4AF3B0
0241C170: FFFCFFFC
0241C174: 00000000
0241C178: FFFCFFFC
0241C17C: 00000000
0241C180: 77F84C1C 77F50000 + 34C1C (ntdll.dll)
0241C184: 77F84FD6 77F50000 + 34FD6 (ntdll.dll)
0241C188: 00000000
0241C18C: 01327B40 01320000 + 7B40
0241C190: 00000000
0241C194: FFFFFFFF
0241C198: 00000776
> 0241C224: 01BDB9EE 01AF0000 + EB9EE (sftrans1.dll)
0241C228: 00000000
0241C22C: 00B40000 00B10000 + 30000
> 0241C230: 004E0000 00400000 + E0000 (vegas40.exe)
0241C234: 0241C36C 02320000 + FC36C
> 0241C238: 01BDB9EE 01AF0000 + EB9EE (sftrans1.dll)
0241C23C: 11225C08 11110000 + 115C08
0241C240: 0241C38C 02320000 + FC38C
0241C244: FFFFF4C0
0241C248: 0241C394 02320000 + FC394
> 0241C27C: 01BBDD7D 01AF0000 + CDD7D (sftrans1.dll)
0241C280: 0000001C
0241C284: 0241C2B0 02320000 + FC2B0
0241C288: 00000000
> 0241C28C: 01C4FB70 01AF0000 + 15FB70 (sftrans1.dll)
0241C290: 0241C3B8 02320000 + FC3B8
0241C294: 00000000
0241C298: 00000004
0241C29C: 00000000
> 0241C2A4: 01BA9D1E 01AF0000 + B9D1E (sftrans1.dll)
- - -
0241FFF0: 00000000
0241FFF4: 004E3AC0 00400000 + E3AC0 (vegas40.exe)
0241FFF8: 006D3FE0 00400000 + 2D3FE0 (vegas40.exe)
0241FFFC: 00000000
DGrob wrote on 10/17/2003, 10:08 AM
I had a similar episode with the sftrans1 error code. Even sent in the veg file to SF Support, but it went fine with them.

I zoomed 'way in and discovered a single frame where a PIP image was missing. The background, text, even the "border" behind the missing image were all there. My render would crash at exactly that frame each time. Ultimately I discovered 2 other screwy frames in the project. BTW, it was a slideshow with plenty of pan/crop activity throughout over 20 minutes.

I believe, and I think SF agreed, that the track had become corrupted.

I wound up deleting the event(s) but leaving the time slots open. Duplicated the track to a new track and deleted the old.
Re-inserted the media (stills in this case).
Zooming in and voila, no missing image-frame.
Rendered successfully.

Oh yes, I was V4c, XP Home. I had "uninstalled" V3, but all the folders were still present in Explore. SF had me go through and delete the actual folders of V3 and V4, and do a clean reinstall of V4.

Never happened again. Good luck, DGrob
addu786 wrote on 10/17/2003, 10:57 AM
Thanks a lot DGrob .. I will try this solution and let you know =) .. greatly appreciated!

addu786
--