DoItFast4U and Hybrid Movies (Jay and Silent Bob)

[rkorkie]

I used an older version of the software (1.09) on Jay and Silent Bob Strikes Back, and it created multiple .m2v files with multiple .avs files so I could encode the interlaced and progressive parts of this movie separately and rejoin them (I assume). With 1.10, it doesn't seem to auto-detect the different hybrid parts of the movie anymore and create the separate .avs and .mpv files. Any advice or guidance would be great. Thanx.

Ryan

[Mechannibal]

Hey,

I had encoded the main movie in XviD a while back and kept the avs script i used.

This movie has been telecined, and it appears that the credits use a different method than Force Film, but they can still be IVTC'd successfully with Decomb. I did _not_ use Force Film.

For the _entire_ movie I used Decomb with the following settings:

Telecide(post=false,guide=1)
Decimate(cycle=5)

I basically told Decomb not to post process because there are no combed frames sneaking through, and set guide to 1 to speedup the field matching process.

The movie came out great.

Mechannibal

[rkorkie]

ok, great, I'll give it a try. But, this doesn't explain why DoItFast4U didn't detect the hybrid parts and process accordingly. Do you think it's a bug or simply a feature that was removed?

[Eyes`Only]

You made sure to have the autodetect button checked? I can't see this feature working incorrectly in any of my tests...

[waldok]

Could this be related to the problem I mentioned before about DIF4U trying to rename the files to the same name over and over, thus rename fails and only it ends with the first file created ? (By the way, Eyes, shame on me, I coudn't find the time to try this with the latest version...I'm a bad tester :p
Rkorkie watch you destination folder carefully during the process and see if the files are created then deleted at rename time.

Waldok:cool:

[rkorkie]

yes, I did have the auto-detect option checked, as always. I will keep my eye on that folder and see what transpires. Thanx for the tip. Eyes, I will get back to you on this after the weekend!

[adam]

Perhaps this can just be attributed to the very bizzare method that this DVD was encoded with. Everything on the first layer is pure film with pulldown flags, except the studio logo of course. Everything on the second layer is NTSC (29.97fps interlaced) with the ending credits using a different telecining pattern than the movie. I can only conclude that Jay and Silent Bob must have decided to encode the DVD themselves.

I made a SVCD of this movie a while back. I just ripped it by chapter and processed all chapters from 1st layer in dvd2avi with forced film and made it disk 1. For the 2nd layer I used decomb and got good results. Maybe not the best way to do it but probably the fastest.

[Eyes`Only]

I can only conclude that Jay and Silent Bob must have decided to encode the DVD themselves. BALLS! Hahaha you crack me up!

[MickeyNBK]

Noinch, Noinch, Noinch, Schmokin Weed, Schmokin Weed, Doin Coke, Making DVDs..."

[rkorkie]

Ok, I realized that what produced the multiple .m2v files with this movie was processing it by VOBID. It created 6 separate .avs files, 3 for each angle I think. Needless to say, it included decomb lines for the interlaced parts of the movie. Case closed on that point.

Next, I went back to doing regular processing on the movie in DoIfFast4u v.1.1.0.6 on Angle 1. I modified the resultant .avs script to include the decomb to look like this:

LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\MPEG2Dec3.dll")
LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\decomb.dll")Mpeg2Source("VTS__01_P01A1.16~9_1.d2v")
Telecide(post=false,guide=1)
Decimate(cycle=5)
AddAudio()
ConvertToYUY2()

When imported into CCE 2.67, I get the error "Frame rate 11988/625 is not supported...". Keep in mind I am using AVISynth 2.51 and Decomb for v2.5. So I experiment with the decomb lines, and find out that the problem is the Decimate line. Apparently it doesn't like the parameter cycle=5. Is this an AviSynth 2.0 feature only? Because I changed my script to this and it imported and worked just fine.

Decimate(mode=1,threshold=50)

Any ideas here? I want to make sure I am using the right parameters on all these things as I'm sure each affects quality and time overhead in a different way. Thanx guys.

[Eyes`Only]

making dee vee dees, buyin movies, making dupes, Who got da skillz? We got da skills.

I modified the resultant .avs script to include the decomb to look like this: There's an avs editor built-in so you don't have to post-modify the scripts.

No idea with 2.51.. and/or that new decomb.dll. I experimented a bit with it but wasn't impressed enough to stick with it. The idea of not being able to preview my avs in wmp (or anything else) just doesn't appeal to me, which is what happens when you add that addaudio() line. yuck! If someone comes up with a way to make it work and still allow previewing, I'll take another look.

ironically, I was about to add avisynth 2.51 support to my beta.. and i don't remember having decomb.dll issues as long as i used the latest one. But that inability to preview just bites ass!

[rkorkie]

I modified the script because the tool didn't understand that at layer 2, the movie changes to interlaced. So, if I don't do that, and I don't process by VOBID, the auto-detection tool will never know.

Without decomb in, then you can see the lines when you encode and author it and it looks like crap. Anyhow, I may not have noticed a difference in quality between avisynth 2.0 to 2.5, but I did notice a speed increase for sure.

So are you saying you use avisynth 2.08 and cce 2.50 and life is all good? Just curious. I didn't realize that you could preview in wmp with the effects of all your filters and processors taking effect in the .avs file. Cool. Might give that a shot. Couldn't you just take out the addaudio() line to preview it, then add it back in when you encode?

[Eyes`Only]

I use avisynth 2.07 with cce2.50, yes. The previewing of .avs to me is a necessity so you can see if the filters you are going to use will do the job! And yes, you could just remove that addaudio line but how lame is that? Having to constantly edit .avs scripts? It's bad enough that you had to manually edit that one because I can't detect the change, but then to have to edit it again to preview it? and then AGAIN to use it?

[rkorkie]

hmmmm, I guess I'm not as lazy as I once thought. Seriously, when I make dvd's, I still do a lot of manual work, and I never really had many problems with it. Yes, your tool helps tons, but editing a file here and there is much better if you can get more speed and quality from newer versions of software, like avisynth 2.51 and cce 2.67. Just my thoughts.

Regardless, I guess if there is a good FAQ about the differences of decomb with avisynth 2.0 and 2.5, and the effects each parameter has, that would be great. Avisynth.org wasn't much help, as well, the info is sorta scattered about in the forums...

[Eyes`Only]

Well in direct reference to your question, I've just run CCE on 2 scripts using decomb with decimate(cycle=5) and Avisynth 2.51. And I didn't have any issues.

Edit: I have now encounted the same error with decimate(cycle=5). I have no idea why. I've checked my source (29.97fps) and my script is perfect. The error is "framerate not supported". Has anyone else ran into this?

[Eyes`Only]

bump

[rkorkie]

I'm not sure what the "bump" means, but like I said, getting rid of the cycle=5 parameter and putting "mode=1,threshold=50" fixed it, but I have no idea what the impact of that is on quality or performance...

[Eyes`Only]

Yeah, this sucks. I'm not going to switch to Avisynth 2.51 until this is fixed, definitely! I value consistency and reliability over speed anyday.

[rkorkie]

So Eyes, did you ever find a solution to the cycle=5 error? Let me tell you what I just discovered. When running your program through LOTR Extended, both discs are hybrid apparently. So it uses telecide and decimate. For some reason cycle=5 loads with disc 1 perfectly. But it bombs on disc 2 with the illegal framerate error. I have a suspicion it could be a dvd2avi issue. I'm gonna try and create the .d2v file with different versions and settings of dvd2avi and see what I get. I'll let you know. Let me know if you have found anything since.

[Eyes`Only]

Yes I did find my problem, I'm guess it pertains to you too. In your AVS Script Editor, hit the Reset button. The problem is that for some reason the AVS script was getting incorrect in the 'normal' box, showing telecide and decimate. But decimating with a cycle=5 on an already forcefilmed source (23.97) results in a 19fps video, which CCE refuses to allow.

[rkorkie]

Ah, good call on that. I have to make sure I do that each time I install a new beta. Anyhow, so if I already encoded a movie with telecide and decimate that didn't actually require them (I just changed the cycle=5 to mode=1,threshold=50 in order to get it to load into CCE), does that ultimately affect its quality or anything else adversely? Or should it be just as good?

[Eyes`Only]

I don't think you'd see any Q loss. Since DIF4U forcefilmed it, that essentially means it wasn't interlaced to begin with. So the telecide/decimate lines shouldn't have done much more that slow down your CCE (decomb is pretty intelligent, it doesn't mess with stuff that it determines doesn't require messing with).

Bottom line is... play it. Does it look acceptable to you? It should still be progressive and perfectly fine.

[rkorkie]

awesome, that's exactly what I thought/hoped. Your tool is really helping me out a lot. I can't see any good reason to not give a donation to you to be quite honest. As well, I'm starting to finally see the light as to what the hell Reauthorist really is. It's too bad you couldn't actually automate Scenarist to automatically output the .VOB file layout from the script you give it (or am I wrong about that?)

[Eyes`Only]

It's always nice to know that someone considers my efforts worthwhile of a donation. :D

It's too bad you couldn't actually automate Scenarist to automatically output the .VOB file layout from the script you give it (or am I wrong about that?)

Hmm.. you lost me there. Rephrase the question please?

[waldok]

I think you'd like reauthorist to "take control" on Scenarist so that it automatically generates the final DVD without any "human" intervention ? Did I get you right ?

Well, I wouldn't like that. Sometimes I met some extras (mostly slideshows) that reauthorist (or DIF4U or whopver it was) didn't deal with correctly and that scenarist wouldn't accept at compile time.
In this case, it is pretty convenient to be able to act on tracks, correct things, and add a little piece of "clever hand action" to scenarist if needed...

Man, what about asking if reauthorist could not also pay your bills and cook dinner ? :p (I vote OK for the bills part)

Waldok:cool: