another bug! avi error

Back to post

Comments

Grazie wrote on 6/12/2003, 10:30 AM
Yess DD - I referred to this in my post - about 1 metre above this. I agree, that we need to have a procedure when we wnat to "register" an anomaly - outside proven User Error - yes?

Hey, I guess we all want the same thing - a better, more elegant NLE - there is place for continuous improvement. So here's to us all!

Grazie

SonyEPM wrote on 6/12/2003, 12:10 PM
Weasel: After poking at this further, I can repro your problem. An uncompressed 720x480 file rendered in Vegas opens back up in Vegas or AE 5.5, no problem, file size doesn't matter all is good. We can eat our own dogfood, so can AE.

(updated 6/11/03): Uncompressed 720x480 from AE opens ok in AE and opens in Vegas...BUT if bigger than 2gb it goes black in Vegas ~ the 2gb mark. This is what you are running into. The next Vegas update (4.0d, no timetable yet) will be able to open big uncompressed AE .avi files- we're testing the changes right now. Thanks for bringing this to our attention.

Immediate workaround for you would be to render a still image sequence from AE- that works no matter what the AE sequence length. QT uncompressed also works just fine.

mikkie wrote on 6/12/2003, 12:22 PM
OK, from my point of view, wf might have posted to complain, troll, or seek a solution.

If 1), then the complaint is noted and an attempt made to help dx the prob. if wf was/is interested. So far in the 3 posts made by wf, little if any info can be gleaned, so one could justifiably feel that wf was not interested in a solution.

If 2), (& this certainly seems the reaction if not the intent), ignore the person.

If 3) So far I've been able to determine from the 3 posts by wf, there is a video file that Vegas didn't like, it was in an uncompressed format, approx 3 gig in size, approx 1.5 minutes long, at 720 x 480. This video played in wmplayer 9, in prem, and in ae 5.5. Changing the file's attributes, encoding it to uncompressed qtime the file was playable in Vegas.

I have not read in wf's posts if the qtime file was in avi or mov format if rerendered thru the qtime player, or if rerendered in ae. If I assume the file was re-rendered in qtime format (thru either prog), then logically the problem is/was either a glitch on wf's system, or a prob. resulting from the software used to render the avi in the first place, in this case not ae, but rather whatever directshow filters were involved as ae would use these to render the file in windows, and/or possibly those used by default to render the file to screen. As an avi is just a container, there are a few possibilities, Vegas incompatible data that could have been included in the file or omitted.

I created an avi a frame or two short of 1.5 minutes, saving it as uncompressed avi, and the file behaved as well as could be expected using the quartz.dll packaged with winmedia 9 to play back an rgb file.

Of course someone else might have better questions to ask, or logic to apply. That said, I'd ask if the original file that would not play contained any other info, alpha channels etc., was in rgb format, used quartz.dll v. 6.5.1.900 as the avi splitter and video renderer. I'd also ask for confirmation that the file that would play was re-rendered to the mov and not avi format. Otherwise, as an experienced alpha tester, wf should as a matter of course provide all the other data normally accompanying prob. reports in general - if it helps, MS recently released a new tool to gather that info for wf and package it in a form that could be transmitted to SOFO tech support.