Sorry, just amended my previous post, I am not out of the woods yet, I had - inadvertantly - reset VP15 to the alternate aviplug.dll which allows that file to load, but no encoding available for AVI, ala "Video for Windows," Sorry for any confusion. Trying every conceivable combo, and I did, even before you had mentioned it, load the Cedo DV, but how does Vegas find that, utilize that via the aviplug.dll, that is what is not happening and above my pay grade to understand why or why not or if it is even possible.

OK, now, something new, it load with original aviplug.dll, and it is utilizing the Cedocida codec (I unchecked "ignore 3rd party codecs" -- something I did in the past as well, but now works) but it took a long time to load, and still I've got encoding available via "Video for Windows." So, son of a gun, but I am now afraid to shut down for thinking this load time is always going to be horrendous again. Pretty decent quality.

Are you talking about Vegas loading time or project loading time?

It might be that you have a lot of 3rd party codecs installed in the system so Vegas need to check them all.

In my case I have not installed any codec packs and just a few 3rd party codecs installed: the DV codec (not sure if I still need it as I have not worked with DV sources quite a long time already), Cineform, Huffyuv, Lagarith (will not use to encode any longer, however still have some encoded stuff), MagicYUV (just bought, never used yet but will try soon), x264vfw (I'm not using the last one, should uninstall it). Probably that's it. Vegas loading quite fast.

My point? I'd try to rid off from the system some codecs that is not needed.

Project load. I think that since the Cedocida works so well, I will probably get rid ot ffdshow, I do have logarith and Avid and Cineform and MagicYUV for extra muscle when needed. Thanks for your ideas.

The only codecs you need on your system are the ones native to Windows and Vegas. There are a few individual vfw codecs that are sometimes used as digital intermediates that have withstood the test of time. Lagarith and x264vfw are not among them.

Codec "packs" are insidious, like a case of bedbugs dwelling deep within your registry, except harder to get rid of.

You came here after finding yourself stuck in a hole -- and a brand new one for most of us. Only thing was, you decided not to tell anyone how you got down there. Now that we all know, the full solution is simple -- stop digging!

Going forward, you should consider posting your hobbyist disussions in the Off-Topic area, lest they be confused with a request for support. You disable a .dll by renaming it, not deletion. You uninstall third-party codecs in Control Panel. As far as Windows 101, we're pretty much agreed here that school is out.

Also, your responses seem disingenuous, and not a productive use of decades of combined experience and time being given freely by your peers. There seems to be a crossed purpose with social media agendas, and I will resist that trend until I have gone the way of johnmeyer and a few other pioneers of post production in the nonlinear millieu.

Watch for a new tutorial on logical troubleshooting protocol, using sequential, conditional steps, including ruleout and indirect proof to isolate possible solutions. Translation: "We need all the information up front."

That said, welcome to the forums, and best of luck going forward.

Are you the resident a$$ hole...policing the "professional" app forum.....lest it be taken over by wank pretenders...???.I don't need the brow beating, so keep your backhanded "welcome." thanks.

I have a legitimate issue, and I am a longtime user. It was unknown to me that the dll switch was anything but a boon and a "solution" as it did work, and worked well..for a long time.... (and I did 'rename' that file, thank you very much, and I posted about that as a "solution" in a separate thread some time ago, well before this thread.) It was employed only in desperation after much consternation with AVI generally. Of course, AVI is a wrapper, and so it is YMMV, of course, and that is well understood.

I don't have the coding depth to perhaps connect that "Video for Windows" is directly tied to the same DLL that provided my solution, and which I rarely access anyway, or have need of, especially as the other two "Windows" options don't disappear in the "Render As" list. Sorry about that, my profuse apologies.

I have had similar issues, over the course of the years tinkering with this adult toy known as Sony Vegas, come up with QT files, just as another example of the weirdness of Vegas. (these same problems you don't have with Premiere, at least that is my experience) Which ver. QT one used was always a iffy situation, so it is not just Vegas, it is the PC world generally and the sometime Mac dominance in that arena, which is/had been changing. All of this represents a lot of "moving targets."

I did not know, for example, till just yesterday, that if you let the computer just sit, vegas will load that AVI problem file after an hour or so. Was that always the case? I don't think so, but who knows, and who has an hour to watch the program "not load" - I mean it sits and sits at the same 58% loaded - doesn't progress slowly,

You sound like a lot of fun, let's go have a beer together sometime.

Please post the exact steps necessary to replicate your legitimate issue on a clean install.

I see on closer inspection that you have an 11GB file? If by chance you are importing files stored on a FAT32 formatted drive, which includes virtually all portable storage, usb sticks and SD cards, the 4GB size limitation is your operative limiting factor. I know of no corrective possibilities once the fat tables are corrupt except to reimport from source to an NTFS media.

What's on G:\\ ? Maybe a smoking gun?

Then, it's easy enough to split your monster into 2GB chunks using VirtualDub et al that any OS, even Windows 98 and Mac pre-OSX, should handle uncorrupted and uninterrupted when butted correctly on any timeline.

http://www.techfleece.com/2012/06/11/how-to-split-an-avi-file/

Or using a DOS batch-split command, which I forgot before you were born.

(Don't deconstruct or concatenate mp4 files in DOS if you plan on editing them later).

Vegas, for full backwards compatibility, captured all my Type 2 interleaved VFW in 2GB chunks.

So is it possible that legacy OS issues are more responsible for your (not our) endless frustration with AVI than are Vegas and it's users? I mentioned we try to avoid Windows questions, but if your school district raised you on Apples, you truly have my unconditional understanding and forgiveness. The Windows OS can even seem somewhat aboriginal to such users.

Also, 32 khz audio sampling in a video is a real oddball, the spec being 16/48.

As far as my previous post, which I've left up, did it seem righteously miffed to you?

Ok, smarm master, I catch your legit attempt to unravel this can of worms, and you may have something on your hunch that a large file may have something to do with this. It is not now stored on FAT 32, nor do I believe that ever happened, although this is an older file, but it always resided on XP and then Win7 going forward, I far as I remember, and certainly has been the case for a long time. As I mentioned, this file opens immediately in Premiere, Immediately in Vegas with the "hack" aviplug and after about an hour with the normal plug. So, it might be "weird" in some fashion, but certainly not beyond any sort of ability of video programs, in general, to handle it just peachy.

I have always been a PC person, I am just noting that some of these formats were more natively Apple in the semi pro video world.

I will absolutely take under advisement your suggestion that this file be broken into chunks, and VirtualDub is one I was considering anyway, so thanks for that.. much appreciated.