wfn1
16th July 2004, 20:06
Good day,
I backed up the first disc of the quadrilogy, the original Alien using dif4u(1.4.7)+numenu4u(rc1)+bccws(.5)+scenaid(.25 revB) and it looks like everything worked out ok but in an effort to understand as much as possible and get a good backup naturally some questions arose. Thankfully I was able to sort most of them out by talking to D3s7, Zeul and the search button.
Here's the gist of what's going on:
My dif4u is set up so that I do not deinterlace anything, i.e. hybrid film/hybrid video/interlaced video decomb options in avs editor are ###'d. Since this Alien project is a multiangle job, it was done by vobid (the disc contains 2 versions of the film, the theatrical rel. and the 2003 director's cut).
There are 91 vobids all in all. Some of the ids, around 15, were designated as hybrid and therefore got encoded as is - 29.976. the rest of the movie was force-filmed and later pulldown'ed by bccws. During the build phase in scenarist i had to adjust the frame count on quite a few ids (the duration -1 frame trick), because Scenarist was complaining about an odd # of frames and erroring out the build.
After the compile while verifying the movie with powerdvd I noticed that when switching from forcefilmed id to the actual 29.976 id there is combing on the screen. I pretty much chalked it off to powerdvd's inability to handle such a transition properly due to the fact that when playing the id in question .mpv by itself there was no combing effect. I tried to test the disc in my Philips DVP642 dvd player and was relieved (for about 10 seconds) to see that there was no combing for the same ids BUT there was a noticeable stutter in the picture+audio when switching to the next scene. The parts of the movie where it happens are the parts of seamlessly branched video where the actual missing footage kicks in. My question is this: is this normal? and can this be fixed if the answer to the first question is no? (is it possible that my player is bad at handling seamless branching). Thank you and sorry for the long post.
I backed up the first disc of the quadrilogy, the original Alien using dif4u(1.4.7)+numenu4u(rc1)+bccws(.5)+scenaid(.25 revB) and it looks like everything worked out ok but in an effort to understand as much as possible and get a good backup naturally some questions arose. Thankfully I was able to sort most of them out by talking to D3s7, Zeul and the search button.
Here's the gist of what's going on:
My dif4u is set up so that I do not deinterlace anything, i.e. hybrid film/hybrid video/interlaced video decomb options in avs editor are ###'d. Since this Alien project is a multiangle job, it was done by vobid (the disc contains 2 versions of the film, the theatrical rel. and the 2003 director's cut).
There are 91 vobids all in all. Some of the ids, around 15, were designated as hybrid and therefore got encoded as is - 29.976. the rest of the movie was force-filmed and later pulldown'ed by bccws. During the build phase in scenarist i had to adjust the frame count on quite a few ids (the duration -1 frame trick), because Scenarist was complaining about an odd # of frames and erroring out the build.
After the compile while verifying the movie with powerdvd I noticed that when switching from forcefilmed id to the actual 29.976 id there is combing on the screen. I pretty much chalked it off to powerdvd's inability to handle such a transition properly due to the fact that when playing the id in question .mpv by itself there was no combing effect. I tried to test the disc in my Philips DVP642 dvd player and was relieved (for about 10 seconds) to see that there was no combing for the same ids BUT there was a noticeable stutter in the picture+audio when switching to the next scene. The parts of the movie where it happens are the parts of seamlessly branched video where the actual missing footage kicks in. My question is this: is this normal? and can this be fixed if the answer to the first question is no? (is it possible that my player is bad at handling seamless branching). Thank you and sorry for the long post.