Really big problem with Vegas and Premiere exporting and imp

[x_rex30]

First I decided to drop a project of making a nicer looking version of one of my videos because I wanted to make it an mp4 but the lossless copy of the video was too small and I had to upscale it which is something I'm not going to do and also I noticed scenes were moved around in the Vegas Project file that were created using Avisynth and Vfapi so I couldn't really go back to Vegas to make the aspect ratio bigger(could of easily fixed the aspect ratio to be bigger because I could alter the script). I didn't want to go over frame by frame to look over the whole thing even if I fixed those areas. I tried fixing the script and settings in Vegas, even restore older project files, but the problem still persisted, I even remade the fake avi. In the script it was set to 23.976 frames a second and the "Project Properties" in Vegas were also set at 23.976, so different frame rates weren't the problem of this. I started to blame Vfapi, but problems I'll explain latter make me think it's something else. I didn't even mess with the script or project settings at first so getting frames not in the right place really baffled me. So I dropped the project, blamed vfapi, then went on my merry way.

Then today I found out that I had a higher res/bigger aspect ratio version saved. I guess I could of just used this but there was this one scene I wanted to fix, so I brought that in Vegas with vfapi(had to use avs to change the aspect ratio) and that one small bit was fixed. I then exported it and noticed these frames(whaa.. what the fuck!?)

Here are some frames when I export it with Vegas and Premiere using the original avi, the avs or the fake avi
http://img158.imageshack.us/img158/3539 ... putve0.jpg
http://img158.imageshack.us/img158/4711 ... puttv3.jpg
http://img158.imageshack.us/img158/4937 ... putqb4.jpg

Here it is actaully when I import the avs, fake avi, or original avi into Vegas and Premiere.
http://img158.imageshack.us/img158/4885 ... ut2xe8.jpg
http://img158.imageshack.us/img158/4614 ... putca5.jpg

I again started to blame Vfapi because I made another fake avi with it, avisynth and the higher res legarith avi (used avisynth because I had to change the aspect ratio of the legarith file). I reopened Vegas to see if the specific messed up frames wasn't from the export, it was showing up in the project file as well, so I definetly thought it was vfapi. Then I tested the vfapi in Virtualdub and it was showing up fine.. so I was wondering if it really was vfapis fault or not. So I tested it again in Premiere, and it was showing up in there as well. I then tried it again with avisynth without vfapi and the problem was still there, so I know it wasn't vfapi now and that it's possibly only avisynths fault. I then Just used tried importing the legarith file by itself and I'm still getting those weird frames with it, so now I think it's legariths fault. Decided to do more tests, took the flawless original higher res legarith file and convert it to huffyuv in virtualdub. The huffyuv came out just fine, didn't notice any messed up frames viewing the huffyuv file in virtualdub, so I then tried that out in Vegas and Premiere and the problem was there and now I don't know what to blame. Maybe all my codecs are f***ed up, maybe just vegas and premiere(don't think that's the case, vegas was something I started to blame before I tried the videos in premiere, but after trying it premiere as well, the thought of having to reinstall vegas went away).

So what the fuck is going on here!? I thought maybe because I tried the amvapp beta was the cause of this, but the very first issue I brought up was happening before I messed with that, I also set a system restore point before trying the app, the app did mess up a few things but after the system restore I noticed those things started working like normal again. Later in the day yesterday I tried a program called DVD43 3.9.0 located at the doom9 forums and noticed that was messing things up. Did system restore because of that and things seemed to get fixed, though when I did the restore I had a pop up for program crashes, when it asks you if you would like to send a report. After cleaning some things up I restarted the computer and that error didn't pop up again, still don't know if anything is messed up still because of it. So I'm not sure if that's to blame here, I didn't try to remaster the video with the lossless legarith till today.

Can anyone help me here figure out what is going on? Are the codecs messed up, the video editors, a driver maybe, what do you think? Any help here is greatly appreciated.

[Corran]

I'm not sure I exactly follow but something I was having problems with when I installed the amvappbeta was that my old lagarith encodes would cause errors in media player classic when I frameserved them in avisynth with the avisource command. Re-encoding them in virtualdubmod with the newest laragith with "always suggest RGB for output" fixed my problem... I don't know if this is the case for you since you were having issues prior to the new app but if you had a newer version of the laragrith codec or other software, it may be a similar issue.

[x_rex30]

Thanks Corran. I did what you said but also changed the mode in the Legarith settings from YV12 to RGB as well then remade the legarith file in Vdub. Tried the new one in Vegas and two messed up frames side by side that I noticed showed up, kinda like the last two pics in my last post. I guess that was a mistake. I put it back to mode YV12 and it went away, then exported in Vegas and watched the whole thing through and didn't notice a single frame that was messed up. So that fixed it, I guess AMVappbeta is to blame, maybe. I do want a more understanding of this though and really dig deep just to avoid this happening again. What could cause such issues to pop up? I guess it has to do fully with Colorspace. I never ran into such an issue like this before when exporting and importing media, even if I didn't set a color space in my media through avisynth or a codec setting. I found one additional problem though.. some things are off by a frame when I exported, maybe I didn't place the clips right or some other odd setting. I compared the frames of the original export with the new export in vdub. Know anything that could cause that? If not, that's cool, I could probably figure that out. Kudos to you if you could. I did go back and check. Everything seemed to be placed right. I'll double/triple check to make sure though.