Vegas timeline and 23.976 frames a sec questions.

x_rex30 · Post by **x_rex30** » Mon Feb 26, 2007 5:29 am

For the first time I've tried editing in 23.976 in Vegas and days later when I went back to the project, it would show frames that I didn't put in it, and they would mainly be noticeable by cuts because I'd insert a scene that was right after a previous scene in the original source.

Everytime it was a previous frame in the timeline that showed up, not the one after or some other random frame, it was always the one just before the intended frame.

So what caused this? What causes this? I'm thinking it may be because I'm editing in 23.976 frames a second because I've never had this happen before.

Help's appreciated.

CrackTheSky · Post by **CrackTheSky** » Mon Feb 26, 2007 3:13 pm

Are your project settings set at 23.97 fps? Did you change your project settings after you started ediitng?

x_rex30 · Post by **x_rex30** » Mon Feb 26, 2007 3:30 pm

CrackTheSky wrote:Are your project settings set at 23.97 fps? Did you change your project settings after you started ediitng?

Settings are the same as the import.

Oh, should of mentioned I'm using Vegas 6.0d(build 210)

I'm sure I've been using the same build for quite a while and I just now noticed problems but also the first time I've edited in 23.976 frames a second. Normally I edit in 24 fps or 29.970.

The source is the same frame rate as the project settings, 23.976 and I'm editing vobs directly using avisynth, dgindex and convincing the program to use it using vfapi. Also have been editing with vfapi for a year and it has always been working just fine.

Just tried Vegas 7.0d and it seemed to fix it, but it turns out it reversed the problem. Take the pic above and reverse it, now the problem is happening before the cut, the last frame before the slice is suppose to be cut off and the correct frame is to the left of that frame.

CrackTheSky · Post by **CrackTheSky** » Mon Feb 26, 2007 3:39 pm

I dunno then :/ I use Vegas 6.0c and I've always edited in 23.97 fps without any problems (problems similar to this have cropped up when I changed my project settings as I edited, but that's obviously not the problem with your project here). My only suggestion, until someone can figure out what's really wrong, would be to not edit in 23.97 fps or not edit with VOBs (as I myself have always made clips).

Sorry I can't be of more help :/

x_rex30 · Post by **x_rex30** » Mon Feb 26, 2007 3:56 pm

I want to put full blame on 23.976 frame editing, It may be because I tested the amvapp beta and did system restore expecting everything would go back to normal, and I'm not going to stop editing vobs because I've been doing it for 2 years and never ran into this problem. Everything was fine, I can prove that through the original export. And I noticed this I think sometime after I tried AMVapp beta. Some codecs weren't even working right but I thought they were all fixed. Maybe it's not a vegas problem it could be vfapi, but I checked the exact frames from avisynth and the fake AVI I made and they were in the same place. It's odd how the frames shifted when trying vegas7, man this is all soo confusing and no one seems to understand what the main source of the problem is. I haven't seen it brought up in the guides that it's risky to edit vobs using avisynth and shit.. :sigh:

x_rex30 · Post by **x_rex30** » Mon Feb 26, 2007 3:57 pm

CrackTheSky wrote:Sorry I can't be of more help :/

It's alright, at least you tried.

x_rex30 · Post by **x_rex30** » Mon Feb 26, 2007 4:01 pm

Also, not knowing the main source, I'm even afraid to edit in 24 at this moment, and think it may even come up using lossless clips.

Willen · Post by **Willen** » Tue Feb 27, 2007 4:51 am

I suspect that VFAPI has something to do with the inaccuracies. It's also a possibility that an updated/changed codec is doing something different (dropping, or not dropping frames where it used to (not)). Did you also change your version of DGMPEGDec (DGIndex/DGDecode)?

x_rex30 · Post by **x_rex30** » Tue Feb 27, 2007 3:41 pm

Willen wrote:I suspect that VFAPI has something to do with the inaccuracies. It's also a possibility that an updated/changed codec is doing something different (dropping, or not dropping frames where it used to (not)). Did you also change your version of DGMPEGDec (DGIndex/DGDecode)?

VFAPI if it is messing up, it's not because it's bad, I would say it's codec or DGIndex or something got f'ed up.

I did change the version of dgindex because of the amvapp and did system restore. I thought it fixed it but maybe it didn't.

I'm probably going to have to run more tests. Remaking the dgindex is an idea then creating the vfapi and convincing vegas it's the same file might fix it. Still, like I said about VFAPI, I've been using it for a year and never encountered this problem so I don't think the solution is to stop using it because it's defective. Maybe it is but after a year of using it, I would conclude that something just got F'ed up. Maybe I should reinstall Vegas. I'll try that and see if it does anything, also try remaking the file and also try some other things.

x_rex30 · Post by **x_rex30** » Wed Feb 28, 2007 7:32 pm

I fixed it. I don't know if I may have added this at some time to screw it up, but the thing that was causing it to be messed up was having AssumeFPS(23.976) in the script. Even when I take it away, when I put info() in the script, it still is 23.976 frames a second, though it comes up as 23.9760 frames a second(ok, know pointing out that 0 may be pointless, though I want to give the entire info that I can.)

Does this problem make sense? Anyone here of this happening before? I put AssumeFPS and set it at the same frame what the source originally is.. so why would there be a problem from adding this in the script? I'm so HAPPY I've figured this out.. somewhat. I want to know what I did to make it do that by adding the AssumeFPS(23.976).. in detail please.