Premiere Pro CS5 and AVI Lagarith - Failed To Import

[Kamaroth]

Hi,

I have 25, half our long clips that were in .mkv format which I converted to .avi usinc the lagarith codec via VirtualDubMod.
The problem is that they import, and play back fine in Sony Vegas 10, yet when I import the same clips into Premiere Pro CS5 I get an error telling me that it is an "unsupported file or format damaged."

My question is, is there any way to fix this? Like, is there an error I could have made in the converting process? I would rather use Premiere Pro CS5 because I am unfamiliar with Sony Vegas.

[mirkosp]

Lagarith is a hit and miss codec depending on the app that tries to decode it and virtualdubmod is more of a miss than a hit converter nowadays. Grab utvideo (install both 32bit and 64bit since you're on a 64bit OS) as codec, and use the latest plain virtualdub for converting your video (tip, when you have to pic the ut codec in the vdub list, choose YUV420).
I assume you were loading the mkv through avisynth, yes? Otherwise, I have to suggest you to Read <a href=http://www.a-m-v.org/guides/avtech31/>ErMaC & AbsoluteDestiny's Friendly AMV Guides Lovingly Overhauled Largely by Zarxrax</a>, though I actually think you might have already read it (although an older version, seeing how you're using lagarith and vdubmod, which are no longer the suggested software).

[Kamaroth]

Thank you. I will do that.
One other question though. I read somewhere that when handling .mkv's it is better to use 'FFVideoSource' rather then 'DirectShowSource', which one would you suggest, or neither?

Sorry. I'm overly proficient when it comes to AVIsynth and the way it handles files and formats.

[Kamaroth]

Oh wait, don't worry. Sorry. I really should have read that guide before posting the question. I should be good now. Thank you for the help.

[Kamaroth]

Lagarith is a hit and miss codec depending on the app that tries to decode it and virtualdubmod is more of a miss than a hit converter nowadays. Grab utvideo (install both 32bit and 64bit since you're on a 64bit OS) as codec, and use the latest plain virtualdub for converting your video (tip, when you have to pic the ut codec in the vdub list, choose YUV420).
I assume you were loading the mkv through avisynth, yes? Otherwise, I have to suggest you to Read <a href=http://www.a-m-v.org/guides/avtech31/>ErMaC & AbsoluteDestiny's Friendly AMV Guides Lovingly Overhauled Largely by Zarxrax</a>, though I actually think you might have already read it (although an older version, seeing how you're using lagarith and vdubmod, which are no longer the suggested software).

VirtualDub doesn't want to open the .avs script that I feed it. It opens fine in VirtualDubMod, but in VirtualDub I'm returned an "AVI Import Filter Error."

Also, the main reason I used VirtualDubMod was because I downloaded the 'AMVapp' and it was contained in there.

[mirkosp]

Newest AMVApp comes with virtualdub and not virtualdubmod anyway, so my guess is that you did download an older amvapp and follow an older guide.
Anyway, I'm assuming the issue you are having is that you are using 64bit virtualdub with 32bit avisynth. Use 32bit virtualdub and you should be fine.
As for mkv, FFVideoSource is better as it is frame accurate, whereas DirectShowSource isn't and can also screw with the frame order.

[Mister Hatt]

FFMS2 isn't always frame accurate unless you enable some really really stupid seeking options (but nobody is using ogv here are they?~)

[mirkosp]

FFMS2 isn't always frame accurate unless you enable some really really stupid seeking options (but nobody is using ogv here are they?~)

It's not frame accurate only with some containers, but it's surefine with at least mkv and mp4, so... and more than frame accuracy itself, I guess it's the frame order that's of concern: directshowsource is able to get the frames in the wrong order, making the motion worse than jerky, whereas something like that will never happen with ffms2.

[TheRyuu]

One thing I'd check is that you have both 32bit and 64bit versions of lags/utvideo/etc... installed because CS5 is natively 64bit now so 32bit stuff like the codecs and avisynth won't work.

Dunno how much this applies in your situation though.