Gainnothing
22nd November 2011, 07:45
My full post did not fit all in one posting. So here comes the next part.
I have another Question and it kind of relates to Neuron’s guide in an indirect way about teleciding and Frame order.
PS—If I lost you in my calculations google the quick guide where I learned how to make these calculations. And also for my shorthand ( )() means multiplication and ()() / ()() means the product divided by a product. Or even (x/x) / (x/x) which in this case is taking the answer of x/x and then multiplying by the reciprocal because it is division. Not all countries use the same shorthand. And I am terrible at reducing big numbers.
Back somewhere on this forum I noticed a posting and some procedures for TFF and BFF. And I know that is not Best Friends Forever or boyfriends forever. LOL. Last year, fields were not even considered in my encoding until literally NOW. And the only reason I WANT to consider them now is because I want to know the Neuron way or the appropriate way of telecine in Avisynth.
Ok. So I do the guide’s suggestion. Make a nothing script (source only + AssumeTFF() or AssumeBFF() followed by Separatefields() and open in vdub. Yay. Vdub has been neglected—downloaded but used on rare occasions. I did that in for BOTH TFF and BFF. And it is the same thing in both scripts: left to right as normal but the second field always kind of shifts up slightly or down slightly(not noticeable unless you separated fields).
So my question is: Since BOTH AssumeTFF and AssumeBFF does the same thing except shifting up or down would that mean the video is NOT INTERLACED, thus progressive. I know it is progressive since dgavcdec told me but for the sake of knowledge if assumetff and AsumeBFF results in the same left to right direction, can you assume that it is progressive? AND 2.) If it is progessive, should I do “interlace encoding” if burning for DVD?
And 3.) can nueron2 add parse DGA to dgavcdec just like dgindex has? I actually encoded a bit of a video, stopped it, put the m2v in dgindex, made a d2v, and loaded the d2v and parsed it to see the order and it said: BFF. But I am not sure if that was done by my encoder QUENC or if that is the way it was when it was just raw h264.
That was like a 3 part question.
Now, the question about telecine (noun) and teleciding (verb). LOL
I do not want to even mention my demuxed audio. I will mention that later. Let us just deal with the video h264.
1.) my question a minute ago was that if something is in progessive, should it be interlaced. So this question is: how do you write the script Telecide for that part?
2.) Now that you answered the question about Telecide what do you recommend as a next part of the script. I ask this because Teleciding usually deals with film to video, not 25 FPS video to 29.97002997002997 ? Again, before 264 video was demuxed it was FILM 23.976, or the long number above, in a mp4 container. So is there a way to speed the 25 h264 video by 4.970029970029967 when using telecide? Once I get the film video at NTSC then I probably can easily speed up the sound to match it.
SUMMARY OF ALL QUESTIONS FOR THOSE WHO ARE LOST IN MY WORDINESS:
This was from PART ! Questions Resizing (refer back to that posting if need be).
1.) What is the ACTIVE PICTURE AREA in a 640 x 360 matrix since this sampling matrix is not included in the NTSC chart in the article? My guess for active sampling area for 640 x 360 is 646 5/22 x 368. Is this a fair guess? Is it gong to chop off the video? Is it going to add more black stuff? What is your opinion? Why or Why not? Please refer to the procedure as outlined in “A Quick Guide to Digital Video Resolution and Aspect Ratio Conversions. Look at my guesses for PAR as NOT outlined for 640 x 360? Does 640 x 360 actually have an active image area when on an NTSC system? Again, you may ask “Is this a test of our smartness or a guide?” The answer is NO. It is a LONG ESSAY QUESTION that I need help with and requires some calculations so you know where I am coming from.
These Questions are from PART 2 Questions: Understanding Frame and Speed
2.) Since BOTH AssumeTFF and AssumeBFF does the same thing except shifting up or down would that mean the video is NOT INTERLACED, thus progressive. I know it is progressive since dgavcdec told me but for the sake of knowledge if assumetff and AsumeBFF results in the same left to right direction, can you assume that it is progressive? AND 2.) If it is progessive, should I do “interlace encoding” ?
3.)can nueron2 add parse DGA to dgavcdec just like dgindex has? I actually encoded a bit of a video, stopped it, put the m2v in dgindex, made a d2v, and loaded the d2v and parsed it to see the order and it said: BFF. But I am not sure if that was done by my encoder QUENC or if that is the way it was when it was just raw h264.
3.) my question a minute ago was that if something is in progressive, should it be interlaced. So this question is: how do you write the script Telecide for that part?
3B.)Now that you answered the question about Telecide what do you recommend as a next part of the script. I ask this because Teleciding usually deals with film to video, not 25 FPS video to 29.97002997002997 ? Again, before 264 video was demuxed it was FILM 23.976, or the long number above, in a mp4 container. So is there a way to speed the 25 h264 video by 4.970029970029967 when using telecide? Once I get the film video at NTSC then I probably can easily speed up the sound to match it. Keep in mind the h264 video when in the MP4 container was film but when demuxed became 25 fps. What method was used for demuxing—Graphedit (gdcl demultiplexor, diavc decoder, wav dest to write as a wav and dump.ax to dump the 264 file and coreaac(I found a freeware version somewhere somehow).
For all of those who participate in the reply to this posting I really appreciate it as some people may just read this article, get tired and would rather watch episodes of American Dad or Family Guy or old episodes of The Simpsons than to reply to my posting. For those who do both—you are a megastar supercoder.
And again, I will say this one more time: I do not have tons of experience with avisynth. I have picked up bits and pieces through reading things, but really have not bothered to use them such as good old bobby (dgbob). And I used Fdecimate ONCE or twice and that was only because I got a weird video to deal with that was double that rate of film. . Most of the time it has just been source with the HACK and encode and end up with only seeing 90 % of the video on screen. But now maybe those days will change soon.
So even though these were several questions to help me with, did you lean anything new?
I have another Question and it kind of relates to Neuron’s guide in an indirect way about teleciding and Frame order.
PS—If I lost you in my calculations google the quick guide where I learned how to make these calculations. And also for my shorthand ( )() means multiplication and ()() / ()() means the product divided by a product. Or even (x/x) / (x/x) which in this case is taking the answer of x/x and then multiplying by the reciprocal because it is division. Not all countries use the same shorthand. And I am terrible at reducing big numbers.
Back somewhere on this forum I noticed a posting and some procedures for TFF and BFF. And I know that is not Best Friends Forever or boyfriends forever. LOL. Last year, fields were not even considered in my encoding until literally NOW. And the only reason I WANT to consider them now is because I want to know the Neuron way or the appropriate way of telecine in Avisynth.
Ok. So I do the guide’s suggestion. Make a nothing script (source only + AssumeTFF() or AssumeBFF() followed by Separatefields() and open in vdub. Yay. Vdub has been neglected—downloaded but used on rare occasions. I did that in for BOTH TFF and BFF. And it is the same thing in both scripts: left to right as normal but the second field always kind of shifts up slightly or down slightly(not noticeable unless you separated fields).
So my question is: Since BOTH AssumeTFF and AssumeBFF does the same thing except shifting up or down would that mean the video is NOT INTERLACED, thus progressive. I know it is progressive since dgavcdec told me but for the sake of knowledge if assumetff and AsumeBFF results in the same left to right direction, can you assume that it is progressive? AND 2.) If it is progessive, should I do “interlace encoding” if burning for DVD?
And 3.) can nueron2 add parse DGA to dgavcdec just like dgindex has? I actually encoded a bit of a video, stopped it, put the m2v in dgindex, made a d2v, and loaded the d2v and parsed it to see the order and it said: BFF. But I am not sure if that was done by my encoder QUENC or if that is the way it was when it was just raw h264.
That was like a 3 part question.
Now, the question about telecine (noun) and teleciding (verb). LOL
I do not want to even mention my demuxed audio. I will mention that later. Let us just deal with the video h264.
1.) my question a minute ago was that if something is in progessive, should it be interlaced. So this question is: how do you write the script Telecide for that part?
2.) Now that you answered the question about Telecide what do you recommend as a next part of the script. I ask this because Teleciding usually deals with film to video, not 25 FPS video to 29.97002997002997 ? Again, before 264 video was demuxed it was FILM 23.976, or the long number above, in a mp4 container. So is there a way to speed the 25 h264 video by 4.970029970029967 when using telecide? Once I get the film video at NTSC then I probably can easily speed up the sound to match it.
SUMMARY OF ALL QUESTIONS FOR THOSE WHO ARE LOST IN MY WORDINESS:
This was from PART ! Questions Resizing (refer back to that posting if need be).
1.) What is the ACTIVE PICTURE AREA in a 640 x 360 matrix since this sampling matrix is not included in the NTSC chart in the article? My guess for active sampling area for 640 x 360 is 646 5/22 x 368. Is this a fair guess? Is it gong to chop off the video? Is it going to add more black stuff? What is your opinion? Why or Why not? Please refer to the procedure as outlined in “A Quick Guide to Digital Video Resolution and Aspect Ratio Conversions. Look at my guesses for PAR as NOT outlined for 640 x 360? Does 640 x 360 actually have an active image area when on an NTSC system? Again, you may ask “Is this a test of our smartness or a guide?” The answer is NO. It is a LONG ESSAY QUESTION that I need help with and requires some calculations so you know where I am coming from.
These Questions are from PART 2 Questions: Understanding Frame and Speed
2.) Since BOTH AssumeTFF and AssumeBFF does the same thing except shifting up or down would that mean the video is NOT INTERLACED, thus progressive. I know it is progressive since dgavcdec told me but for the sake of knowledge if assumetff and AsumeBFF results in the same left to right direction, can you assume that it is progressive? AND 2.) If it is progessive, should I do “interlace encoding” ?
3.)can nueron2 add parse DGA to dgavcdec just like dgindex has? I actually encoded a bit of a video, stopped it, put the m2v in dgindex, made a d2v, and loaded the d2v and parsed it to see the order and it said: BFF. But I am not sure if that was done by my encoder QUENC or if that is the way it was when it was just raw h264.
3.) my question a minute ago was that if something is in progressive, should it be interlaced. So this question is: how do you write the script Telecide for that part?
3B.)Now that you answered the question about Telecide what do you recommend as a next part of the script. I ask this because Teleciding usually deals with film to video, not 25 FPS video to 29.97002997002997 ? Again, before 264 video was demuxed it was FILM 23.976, or the long number above, in a mp4 container. So is there a way to speed the 25 h264 video by 4.970029970029967 when using telecide? Once I get the film video at NTSC then I probably can easily speed up the sound to match it. Keep in mind the h264 video when in the MP4 container was film but when demuxed became 25 fps. What method was used for demuxing—Graphedit (gdcl demultiplexor, diavc decoder, wav dest to write as a wav and dump.ax to dump the 264 file and coreaac(I found a freeware version somewhere somehow).
For all of those who participate in the reply to this posting I really appreciate it as some people may just read this article, get tired and would rather watch episodes of American Dad or Family Guy or old episodes of The Simpsons than to reply to my posting. For those who do both—you are a megastar supercoder.
And again, I will say this one more time: I do not have tons of experience with avisynth. I have picked up bits and pieces through reading things, but really have not bothered to use them such as good old bobby (dgbob). And I used Fdecimate ONCE or twice and that was only because I got a weird video to deal with that was double that rate of film. . Most of the time it has just been source with the HACK and encode and end up with only seeing 90 % of the video on screen. But now maybe those days will change soon.
So even though these were several questions to help me with, did you lean anything new?