Edge
8th December 2001, 10:19
Ok. So I've capture a relatively short video clip (not more than 10 minutes) at 720x480 using Huffyuv. File is just about 5 GB in size. I go to Premiere thinking this will be a snap-- merge some video clips together (as well as some still images used for titles and filler) and I'll get the finished product just like that.
Naturally, nothing that SEEMS this simple EVER is.
Instead of working properly, Adobe Premiere 6.0 crashes (hard) with a generic Win32 error dialog explaining that Premiere tried to write to memory it shouldn't have. It happens repeatedly, at the same point, EVERY time. (In this case, it almost always happens at or near frame 6142 of the exporting session.) I've tried doing it on a different system (with WinXP instead of Windows 2000) to no avail (thinking perhaps I had a bad memory module, or perhaps a bad hard drive (pagefile getting corrupted, mebbe?).. but given the repeatability of the situation, it leads me to believe that Premiere 6.0 just has issues with large files (greater than 4 GB anyways).
I've tried using AviSynth to act as plug-in for Premiere, but as was posted by someone else, the AviSynth plug-ins do NOT agree with Premiere 6.0. Instead of showing the frames of video, all you get is black (the audio, however, works fine apperently.. while moving through the timeline I can hear snips of audio that seem in their proper place). So, I tried exporting the timeline as-is, hoping the black frames might be replaced with something meaningful in an exported file.. Whoops. Premiere's inability to deal with the rest of the world rears its head again-- another generic Win32 error dialogue.
Does anyone have ANY advice for using video capped via VirtualDub in Adobe Premiere 6? I've tried everything I can think of, and am convinced that this was a bad idea the whole way around...
Naturally, nothing that SEEMS this simple EVER is.
Instead of working properly, Adobe Premiere 6.0 crashes (hard) with a generic Win32 error dialog explaining that Premiere tried to write to memory it shouldn't have. It happens repeatedly, at the same point, EVERY time. (In this case, it almost always happens at or near frame 6142 of the exporting session.) I've tried doing it on a different system (with WinXP instead of Windows 2000) to no avail (thinking perhaps I had a bad memory module, or perhaps a bad hard drive (pagefile getting corrupted, mebbe?).. but given the repeatability of the situation, it leads me to believe that Premiere 6.0 just has issues with large files (greater than 4 GB anyways).
I've tried using AviSynth to act as plug-in for Premiere, but as was posted by someone else, the AviSynth plug-ins do NOT agree with Premiere 6.0. Instead of showing the frames of video, all you get is black (the audio, however, works fine apperently.. while moving through the timeline I can hear snips of audio that seem in their proper place). So, I tried exporting the timeline as-is, hoping the black frames might be replaced with something meaningful in an exported file.. Whoops. Premiere's inability to deal with the rest of the world rears its head again-- another generic Win32 error dialogue.
Does anyone have ANY advice for using video capped via VirtualDub in Adobe Premiere 6? I've tried everything I can think of, and am convinced that this was a bad idea the whole way around...