Filmy- I'm assuming these are Vegas-generated files. In a fresh, new project, can your render a 24p 2-3 to a new track...without crashing?

SPOT:
Tried the repair with no change. I updated to 4d and no luck. Below is the full error when trying to open 24p project.

SonyEPM:
yes these are VV 24p files. This is the project that you, I think it was you, helped with when I was having the skipping frame issue with 24p 2-3 vs. 2-3-3-2 and PTT. The project has been fine all through 'last year'. I last worked with it in December when I rendered out a little 'intro' and then did a PTT for the Mini-DV festival and at that time it all worked perfect. As for your question - A new project it opens fine. I load one piece of non 24p 2-3 media and I put it on the timeline. I play it. No issues. Now I render to 24p using the 2-3 template. It renders out fine to a new track - all seems fine. I hit play and I get the crash. Again, all of this is only happening with VV rendered 24p 2-3 media.
=====
Sonic Foundry Vegas 4.0
Version 4.0d (Build 205)
Exception 0xC0000005 (access violation) WRITE:0x4D8E000 IP:0x176B139
In Module 'aviplug.dll' at Address 0x1750000 + 0x1B139
Thread: Engine_RenderFromCookedSlices ID=0x9B8 Stack=0x430E000-0x4310000
Registers:
EAX=00000870 CS=001b EIP=0176b139 EFLGS=00010212
EBX=00000870 SS=0023 ESP=0430e3b8 EBP=001d434c
ECX=000000c2 DS=0023 ESI=04c91ee0 FS=0038
EDX=04d8da98 ES=0023 EDI=04d8e000 GS=0000
Bytes at CS:EIP:
0176B139: F3 A5 8B CB 83 E1 03 F3 ........
0176B141: A4 8B 74 24 10 8D 0C 00 ..t...
Stack Dump:
0430E3B8: 01651A10 01630000 + 21A10
0430E3BC: 02B52E98 02AF0000 + 62E98
0430E3C0: 00000000
0430E3C4: 0430E570 04210000 + FE570
0430E3C8: 04C91978 04C90000 + 1978
0430E3CC: 00000000
0430E3D0: 00000001
0430E3D4: 0001D4C0
0430E3D8: 00000028
0430E3DC: 04C90000 04C90000 + 0
0430E3E0: 00000000
0430E3E4: 000000EF
0430E3E8: 00000000
0430E3EC: 00000001
0430E3F0: 001D43D0 00140000 + 943D0
0430E3F4: 0430EB14 04210000 + FEB14
> 0430E424: 77E776AC 77E60000 + 176AC (kernel32.dll)
> 0430E42C: 005D08A8 00400000 + 1D08A8 (vegas40.exe)
0430E430: 00000001
0430E434: 0000000D
0430E438: 00000000
0430E43C: 0430E99C 04210000 + FE99C
> 0430E478: 005D2203 00400000 + 1D2203 (vegas40.exe)
0430E47C: 001D434C 00140000 + 9434C
0430E480: 0430E570 04210000 + FE570
0430E484: 00000000
0430E488: 0000000A
> 0430E9C4: 005D07F0 00400000 + 1D07F0 (vegas40.exe)
0430E9C8: 00000000
0430E9CC: 001D434C 00140000 + 9434C
0430E9D0: 00000000
0430E9D4: 00000000
> 0430E9DC: 005D2690 00400000 + 1D2690 (vegas40.exe)
0430E9E0: 02B52C98 02AF0000 + 62C98
0430E9E4: 0430EB10 04210000 + FEB10
0430E9E8: 0430EA34 04210000 + FEA34
0430E9EC: 02B52E98 02AF0000 + 62E98
> 0430EF64: 005D07F0 00400000 + 1D07F0 (vegas40.exe)
> 0430F6D0: 01114960 01000000 + 114960 (vegas40k.dll)
- - -
0430FFF0: 00000000
0430FFF4: 0054A4B0 00400000 + 14A4B0 (vegas40.exe)
0430FFF8: 03A4FBE8 039F0000 + 5FBE8
0430FFFC: 00000000
======

Now here is the entire project in 4.0d and the full error, as opposed to just one piece of media.

======
Sonic Foundry Vegas 4.0
Version 4.0d (Build 205)
Exception 0xC0000005 (access violation) WRITE:0xBA4E000 IP:0x1B7B139
In Module 'aviplug.dll' at Address 0x1B60000 + 0x1B139
Thread: VideoCache ID=0x8B8 Stack=0x625F000-0x6260000
Registers:
EAX=00000870 CS=001b EIP=01b7b139 EFLGS=00010212
EBX=00000870 SS=0023 ESP=0625f9d0 EBP=001c57fc
ECX=000000c2 DS=0023 ESI=0b951ee0 FS=0038
EDX=0ba4da98 ES=0023 EDI=0ba4e000 GS=0000
Bytes at CS:EIP:
01B7B139: F3 A5 8B CB 83 E1 03 F3 ........
01B7B141: A4 8B 74 24 10 8D 0C 00 ..t...
Stack Dump:
0625F9D0: 001C57FC 00140000 + 857FC
0625F9D4: 01658B70 01630000 + 28B70
0625F9D8: 0625FEFC 06160000 + FFEFC
0625F9DC: 06441910 06260000 + 1E1910
0625F9E0: 0B951978 0B950000 + 1978
0625F9E4: 00000000
0625F9E8: 00000001
0625F9EC: 0001D4C0
0625F9F0: 00000028
0625F9F4: 0B950000 0B950000 + 0
0625F9F8: 00000000
0625F9FC: 000000EF
0625FA00: 00000000
0625FA04: 00000001
0625FA08: 001C5880 00140000 + 85880
0625FA0C: 77F5DD5E 77F50000 + DD5E (ntdll.dll)
> 0625FA18: 77ED60E0 77E60000 + 760E0 (kernel32.dll)
> 0625FA40: 77F5CA4C 77F50000 + CA4C (ntdll.dll)
> 0625FA44: 005BD227 00400000 + 1BD227 (vegas40.exe)
0625FA48: 00000001
0625FA4C: 000000C6
0625FA50: 00000000
0625FA54: 0625FA90 06160000 + FFA90
> 0625FAA4: 0105818F 01000000 + 5818F (vegas40k.dll)
0625FAA8: 0132079C 01320000 + 79C
0625FAAC: 01674390 01630000 + 44390
0625FAB0: 01674370 01630000 + 44370
0625FAB4: 0163A970 01630000 + A970
> 0625FAE8: 77E36418 77DD0000 + 66418 (ADVAPI32.dll)
> 0625FAEC: 77DD8D32 77DD0000 + 8D32 (ADVAPI32.dll)
> 0625FAF4: 77E36418 77DD0000 + 66418 (ADVAPI32.dll)
> 0625FB30: 77132D91 77120000 + 12D91 (OLEAUT32.dll)
> 0625FB34: 77120000 77120000 + 0 (OLEAUT32.dll)
> 0625FB3C: 77F7E5EF 77F50000 + 2E5EF (ntdll.dll)
> 0625FB40: 77E73100 77E60000 + 13100 (kernel32.dll)
> 0625FB50: 77E73124 77E60000 + 13124 (kernel32.dll)
> 0625FB60: 77E778BD 77E60000 + 178BD (kernel32.dll)
> 0625FB68: 77E778B0 77E60000 + 178B0 (kernel32.dll)
> 0625FBDC: 77DD90D7 77DD0000 + 90D7 (ADVAPI32.dll)
> 0625FBE4: 77DD90E0 77DD0000 + 90E0 (ADVAPI32.dll)
> 0625FBEC: 77E36418 77DD0000 + 66418 (ADVAPI32.dll)
> 0625FBF8: 77DD8F17 77DD0000 + 8F17 (ADVAPI32.dll)
> 0625FC34: 77F58B33 77F50000 + 8B33 (ntdll.dll)
> 0625FC3C: 77F58B49 77F50000 + 8B49 (ntdll.dll)
> 0625FC78: 76671538 76670000 + 1538 (setupapi.dll)
> 0625FC8C: 77F516F5 77F50000 + 16F5 (ntdll.dll)
> 0625FCA4: 77F7F3EF 77F50000 + 2F3EF (ntdll.dll)
> 0625FCAC: 77F82402 77F50000 + 32402 (ntdll.dll)
> 0625FCB8: 77F52DBB 77F50000 + 2DBB (ntdll.dll)
> 0625FCBC: 77F52E0F 77F50000 + 2E0F (ntdll.dll)
> 0625FCC0: 77F5180B 77F50000 + 180B (ntdll.dll)
> 0625FCDC: 77F516F5 77F50000 + 16F5 (ntdll.dll)
> 0625FCFC: 77F82402 77F50000 + 32402 (ntdll.dll)
> 0625FD00: 77F75520 77F50000 + 25520 (ntdll.dll)
> 0625FD08: 77F516F5 77F50000 + 16F5 (ntdll.dll)
> 0625FD0C: 77F517CD 77F50000 + 17CD (ntdll.dll)
> 0625FD10: 77F5180B 77F50000 + 180B (ntdll.dll)
> 0625FD28: 77DD8E43 77DD0000 + 8E43 (ADVAPI32.dll)
> 0625FD40: 77DD8E0D 77DD0000 + 8E0D (ADVAPI32.dll)
> 0625FD60: 77DD8DBC 77DD0000 + 8DBC (ADVAPI32.dll)
> 0625FD7C: 7805C23E 78000000 + 5C23E (RPCRT4.dll)
> 0625FD84: 7805C247 78000000 + 5C247 (RPCRT4.dll)
> 0625FD98: 78020CF0 78000000 + 20CF0 (RPCRT4.dll)
> 0625FE28: 77F516B3 77F50000 + 16B3 (ntdll.dll)
> 0625FE50: 0A2DCE5F 0A2C0000 + 1CE5F (extmondrv.dll)
> 0625FE54: 006D2BDA 00400000 + 2D2BDA (vegas40.exe)
0625FE58: 00EBAD14 00D00000 + 1BAD14
0625FE5C: 01674368 01630000 + 44368
0625FE60: 012F0178 012F0000 + 178
0625FE64: 00000000
> 0625FE94: 007A1307 00400000 + 3A1307 (vegas40.exe)
0625FE98: 01674370 01630000 + 44370
0625FE9C: 012F0000 012F0000 + 0
0625FEA0: 0625FCC4 06160000 + FFCC4
> 0625FEA4: 7721045D 771B0000 + 6045D (ole32.dll)
> 0625FEAC: 77F82402 77F50000 + 32402 (ntdll.dll)
> 0625FEB0: 77F75510 77F50000 + 25510 (ntdll.dll)
> 0625FEB8: 77F5180B 77F50000 + 180B (ntdll.dll)
> 0625FEBC: 7C00171F 7C000000 + 171F (MSVCR70.dll)
======

Just a PS - I have tried a few video card related things to see if it changed anything. Lowered the display colors to 16. Lowered the acceleration. Lowered the 'bpp'. Turned off dual monitor. enabled "write combining". Lowered the system memory for 'PCI Mode texures'. Changed the 'mipmap detail' settings. Nothing changed as far as this crash goes.

And one other PS thing - I can still use the capture mod to print out to tape with no issues. To be clear I can load the same file(s) that cause the main Vegas edit module to crash and play them back with no issues, both on the desktop and out via firewire.

Very strange- no repro here.

The computer itself hasn't changed?

Try this: Ctrl+Shift+ restart Vegas (this resets all prefs to the factory defaults). Load one of your 24p clips in this clean, default (NTSC DV)project, play. works yes/no?

Render to new track, 24p DV 2-3, now play this new file. works yes/no?

Hey guess what I found? So I am playing around with Vegas settings. here is what I did - I disabled/unchecked the "Allow pulldown removal when opening 24p DV" and the files load and play fine. (Although they play, read and load at 29.97 and not 23.976) No crash. Now if I put it back on - crash. As a full test I turned off the option and loaded up the full project - no crash. Why this is an issue now and it wasn't a month ago I have no idea.

SonyEPM - to answer your latest question. System wise a few things did change. I installed PhotoshopCS and Acrobat 6. Any known conflict with Vegas and those apps? I can uninstall them although the whole Photoshop activation thing is a hassle. One other thing also changed : I got a USB 2 drive, although none of this media is coming from or going onto that drive. Not sure why that would cause any issues but I will try turning it off just for the heck of it. Nope, turning off the USB drive does nothing to change the problem.

As for your other question - I shut down Vegas. Reopend with the Ctrl+Shift and loaded up one of the 24p 2-3 files. Instant crash. As above if I turn off the "Allow pulldown removal when opening 24p DV" option it loads fine. Also, not sure why, doing this and loading up one piece of media returned a hell of a lot longer error than before.

====
Sonic Foundry Vegas 4.0
Version 4.0d (Build 205)
Exception 0xC0000005 (access violation) WRITE:0x581E000 IP:0x176B139
In Module 'aviplug.dll' at Address 0x1750000 + 0x1B139
Thread: VideoCache ID=0xCF8 Stack=0x2FEF000-0x2FF0000
Registers:
EAX=00000870 CS=001b EIP=0176b139 EFLGS=00010212
EBX=00000870 SS=0023 ESP=02fef9d0 EBP=001b9684
ECX=000000c2 DS=0023 ESI=05721ee0 FS=0038
EDX=0581da98 ES=0023 EDI=0581e000 GS=0000
Bytes at CS:EIP:
0176B139: F3 A5 8B CB 83 E1 03 F3 ........
0176B141: A4 8B 74 24 10 8D 0C 00 ..t...
Stack Dump:
02FEF9D0: 001B9684 00140000 + 79684
02FEF9D4: 0164B068 01630000 + 1B068
02FEF9D8: 02FEFEFC 02EF0000 + FFEFC
02FEF9DC: 001CDA58 00140000 + 8DA58
02FEF9E0: 05721978 05720000 + 1978
02FEF9E4: 00000000
02FEF9E8: 00000001
02FEF9EC: 0001D4C0
02FEF9F0: 00000028
02FEF9F4: 05720000 05720000 + 0
02FEF9F8: 00000000
02FEF9FC: 000000EF
02FEFA00: 00000000
02FEFA04: 00000001
02FEFA08: 001B9708 00140000 + 79708
02FEFA0C: 77F5DD5E 77F50000 + DD5E (ntdll.dll)
> 02FEFA18: 77ED60E0 77E60000 + 760E0 (kernel32.dll)
> 02FEFA40: 77F5CA4C 77F50000 + CA4C (ntdll.dll)
> 02FEFA44: 005BD227 00400000 + 1BD227 (vegas40.exe)
02FEFA48: 00000001
02FEFA4C: 00000373
02FEFA50: 00000000
02FEFA54: 02FEFA90 02EF0000 + FFA90
> 02FEFAA4: 0105818F 01000000 + 5818F (vegas40k.dll)
02FEFAA8: 01320D5C 01320000 + D5C
02FEFAAC: 0164C3B0 01630000 + 1C3B0
02FEFAB0: 0164C390 01630000 + 1C390
02FEFAB4: 01646BC0 01630000 + 16BC0
> 02FEFAE8: 77E36418 77DD0000 + 66418 (ADVAPI32.dll)
> 02FEFAEC: 77DD8D32 77DD0000 + 8D32 (ADVAPI32.dll)
> 02FEFAF4: 77E36418 77DD0000 + 66418 (ADVAPI32.dll)
> 02FEFB30: 77132D91 77120000 + 12D91 (OLEAUT32.dll)
> 02FEFB34: 77120000 77120000 + 0 (OLEAUT32.dll)
> 02FEFB4C: 77120000 77120000 + 0 (OLEAUT32.dll)
> 02FEFBDC: 77DD90D7 77DD0000 + 90D7 (ADVAPI32.dll)
> 02FEFBE4: 77DD90E0 77DD0000 + 90E0 (ADVAPI32.dll)
> 02FEFBEC: 77E36418 77DD0000 + 66418 (ADVAPI32.dll)
> 02FEFBF8: 77DD8F17 77DD0000 + 8F17 (ADVAPI32.dll)
> 02FEFC34: 77F58B33 77F50000 + 8B33 (ntdll.dll)
> 02FEFC3C: 77F58B49 77F50000 + 8B49 (ntdll.dll)
> 02FEFC78: 76671538 76670000 + 1538 (setupapi.dll)
> 02FEFC8C: 77F516F5 77F50000 + 16F5 (ntdll.dll)
> 02FEFCA4: 77F7F3EF 77F50000 + 2F3EF (ntdll.dll)
> 02FEFCAC: 77F82402 77F50000 + 32402 (ntdll.dll)
> 02FEFCB8: 77F52DBB 77F50000 + 2DBB (ntdll.dll)
> 02FEFCBC: 77F52E0F 77F50000 + 2E0F (ntdll.dll)
> 02FEFCC0: 77F5180B 77F50000 + 180B (ntdll.dll)
> 02FEFCDC: 77F516F5 77F50000 + 16F5 (ntdll.dll)
> 02FEFCFC: 77F82402 77F50000 + 32402 (ntdll.dll)
> 02FEFD00: 77F75520 77F50000 + 25520 (ntdll.dll)
> 02FEFD08: 77F516F5 77F50000 + 16F5 (ntdll.dll)
> 02FEFD0C: 77F517CD 77F50000 + 17CD (ntdll.dll)
> 02FEFD10: 77F5180B 77F50000 + 180B (ntdll.dll)
> 02FEFD28: 77DD8E43 77DD0000 + 8E43 (ADVAPI32.dll)
> 02FEFD40: 77DD8E0D 77DD0000 + 8E0D (ADVAPI32.dll)
> 02FEFD60: 77DD8DBC 77DD0000 + 8DBC (ADVAPI32.dll)
> 02FEFD7C: 7805C23E 78000000 + 5C23E (RPCRT4.dll)
> 02FEFD84: 7805C247 78000000 + 5C247 (RPCRT4.dll)
> 02FEFD98: 78020CF0 78000000 + 20CF0 (RPCRT4.dll)
> 02FEFE28: 77F516B3 77F50000 + 16B3 (ntdll.dll)
> 02FEFEA4: 7721045D 771B0000 + 6045D (ole32.dll)
> 02FEFEAC: 77F82402 77F50000 + 32402 (ntdll.dll)
> 02FEFEB0: 77F75510 77F50000 + 25510 (ntdll.dll)
> 02FEFEB8: 77F5180B 77F50000 + 180B (ntdll.dll)
> 02FEFEBC: 7C00171F 7C000000 + 171F (MSVCR70.dll)
> 02FEFEC8: 7C001733 7C000000 + 1733 (MSVCR70.dll)
> 02FEFEE0: 0110214D 01000000 + 10214D (vegas40k.dll)
02FEFEE4: 0164B79C 01630000 + 1B79C
02FEFEE8: 0164C390 01630000 + 1C390
02FEFEEC: 0164B790 01630000 + 1B790
02FEFEF0: 00000001
> 02FEFEF4: 00546715 00400000 + 146715 (vegas40.exe)
> 02FEFEF8: 01102891 01000000 + 102891 (vegas40k.dll)
02FEFEFC: 01646BC0 01630000 + 16BC0
> 02FEFF00: 0047A93B 00400000 + 7A93B (vegas40.exe)
- - -
02FEFFF0: 00000000
02FEFFF4: 00546D50 00400000 + 146D50 (vegas40.exe)
02FEFFF8: 006DE020 00400000 + 2DE020 (vegas40.exe)
02FEFFFC: 00000000
====

search for aviplug.dll...

what version is it?

In Vegas 4.0E (the curent version of Vegas), aviplug.dll is: 1.2.0.1370

LOL! I did that - I mean I got thinking maybe some other program overwrote the file but I could only find the one. I have not gone to the Sony branded version of Vegas so I have been using Vegas 4c until today when I went to 4d to see if that fixed the issue.

Version info is:
Dated: 8/6/2003
File Version: 1.2.0.999
branded Sonic Foundry, not Sony.

System worked, now it doesn't work. We KNOW neither Vegas nor the source files mutated just sitting there and I'm not reproing your issue here. SO:

You'll have to back out your system changes. I'd start with the video display and soundcard. What changed there between the good and not good config- drivers? Settings? I highly doubt the Adobe apps are at fault, I have both. Usb drive- was there some nefarious driver pack that came along with that by chance?

Yes there was...well I mean no there wasn't....sorry. The drive itself just loaded up after Windows detected it and "installed" whatever drivers were needed.

By the way, just as a test I copied over the newer Sony aviplug.dll from the SF 7 folder. I thought to try that and opened the same file and it played fine. So I tired the same dll in the VV flder. At first, get this, I loaded up the exact same file into the media pool and hit play/preview. No crash. Put it on the timeline and hit play - crash.

What has changed since then and now that would affect only 24p 3-2 files? I think that is what the question is. USB 2.0 drive and whatever XP needed to see it. Photoshop CS and Acrobat 6.1. Um...hmmm, my wife installed Yahoo messanger because her father and sister both got webcams at christmas. We already had a webcam installed so nothing changed there - other than the actual Yahoo messenger software. Do you think that would affect 24p 2-3 timeline playback?

I disabled USB 2 adaptec card. No change. I uninstalled same card. Nothing. For the hell of it I also diabled/uninstalled firewire side - nothing. No change. I have been disabling and uninstalling things and nothing seems to matter. I honestly have no clue. Anything flagged with 24p 2-3 pulldown will crash the main vegas window as long as the "Allow pulldown removal..." option is on. Turn it off and everything works fine.

What does this switch interact with system wise? What am I looking for? Is this a memory issue? Every error starts off the exact same - Exception 0xC0000005 (access violation) WRITE:0x4EDE000 IP:0x164A499 In Module 'aviplug.dll'

What else is this dll sharing with in reguards to 2-3 pulldown?!?!?! Sorry, I just don't get it. And you can't repro it so hey - like I said - it is a new 2004 bug.


Sound card - nothing at all has changed.
VIdeo card I have been testing out things left and right. Nothing matters it seems. No matter what setting I choose it still crashes - Vegas I mean.

Lol, now for sure I can say that Vegas crashes faaaaaaaaar more than Premiere ever has. But Premiere 6.5 doesn't have a 24p option so who knows if I would be getting the same results if it did. LOL!

Scuze me, don't mean to stick my nose in, but did you try UNPLUGGING the USB drive to see if this still happened, or did you just turn it off?
I ask this because I was getting crashes all of a sudden in Acid. When I unplugged my M-Audio UNO USB-midi interface, they stopped.

Just trying to help... You sound frustrated, so I figure any help is welcome.

M

Yes I did...but.......read the next post from me...

Okely Dokely - we all overlooked something. SonyEPM try this - install the MainConcept DVCPro 25/50 DV Codec demo. (http://mediasoftware.sonypictures.com/forums/ShowMessage.asp?MessageID=233158&Page=0) Now also uncheck "Ignore third party DV codecs". Load up, and/or create 24p media with the 2-3 pulldown. Now do you get the crash? I bet you will.

After trying everything under the sun I logged on to another screen and loaded up the project fine. I checked the settings there and relized the "Ignore third party DV codecs" option was checked. So I went back to the first desktop and looked - and it was unchecked there. So I checked it and it works. I remembered why I did this - I had downloaded the MC DVCPro demo to try. There was a thread at DMN where someone had asked about how to use it in Vegas and someone had mentioned to get it to read in Vegas you needed to have the "Ignore third party DV codecs" unchecked. (It didn't matter because the codec is seemingly not read by Vegas - http://mediasoftware.sonypictures.com/forums/ShowMessage.asp?MessageID=234566&Page=0)

As a further test I uninstalled it, unchecked it the "Ignore third party DV codecs" and tried again - it works. So it is a combination of things here - conflict with the codec it seems, MainConcept DVCPro 25/50 DV Codec does not do 24p 2-3 but does do 24p 2-3-3-2? I dunno - but it solved the problem. But it also means that vegas was trying to interact with the DVCPro codec, it just wasn't showing up anywhere as an option, nor was it showing up in any of the crash info.

That's what I was going to suggest next if you had tried unplugging the USB drive... glad it worked out for you. ;)
(Notice the winking smiley face.)
M

Glad you figured it out!

>>> Glad you figured it out!<<<
Me too. But now the question is - can you repro the crash?