avisynth and dvdripping ?

[avengerevenge]

hello everyone,

iam new to dvd ripping, i love ripping movies but the problem is
that how to make a quality rip with average size
(like for 1 hour:30 minutes to 700 mb and 2 hour:55 to 900 mb)

i use gordian knot (not auto gordian knot). when ever i rip i see very well that the bits/pixel value is satisfied very well with output resulution,(i never take a output resolution when bits/pixel value is yellow or red)

i do this because,
i feel that making a high resolution rip is not good when compared to making detailed dvd rip(rip with good bits/pixel values).
due to this reason i always end with reolution of of 500's width and 200's height.
but after ripping i feet that the quality should have been more better.
i use ffT3dgpu filter to soften and tweak filter to decrease saturation and brightness, i keep coring=true.

just can any body tell me how to make quality dvd rip
pls guide me with filters and scripts to make one quality rip.

i have doubt that does making video smoooth using fft3Dgpu and temporalsoften helps compressing the movie.
i always use xvid codec for ripping.

[Inspector.Gadget]

Your knowledge is way out of date. Use x264 and feed it with DGIndex and Avisynth - many of the progeams featured in the "MPEG-4 Encoder GUIs" forum will automate this to some degree. This isn't 1999; hard drive space is inexpensive and CDs are no longer the most affordable / most logical backup medium. Rip to whatever dimensions you want, whatever file size you want, etc. Don't overfilter: Avisynth is an incredibly powerful tool, but truly awful mainstream commercial DVDs are IMO few and far between.

[CWR03]

due to this reason i always end with reolution of of 500's width and 200's height.
i feel that making a high resolution rip is not good when compared to making detailed dvd rip(rip with good bits/pixel values).
but after ripping i feet that the quality should have been more better.
Your resolution is why you're not getting quality. You need resolution and bitrate to maintain detail. Increase it to at least 720 width, then adjust bitrate up until the bits/pixel window is no longer yellow and you'll get the encode you want.

You can use x264 with Gordian Knot as long as you use a VfW build, and you can get excellent encodes.

[avengerevenge]

Your knowledge is way out of date. Use x264 and feed it with DGIndex and Avisynth - many of the progeams featured in the "MPEG-4 Encoder GUIs" forum will automate this to some degree. This isn't 1999; hard drive space is inexpensive and CDs are no longer the most affordable / most logical backup medium. Rip to whatever dimensions you want, whatever file size you want, etc. Don't overfilter: Avisynth is an incredibly powerful tool, but truly awful mainstream commercial DVDs are IMO few and far between.
wow inspector gadget i think your answer is really rude, why do you think i said i use xvid codec for ripping, because to watch rips on divx compatible dvd player.
secondly i know this isn't 1999 i know buying cd and hard drives is really cheap these days, and important thing is that anyone can get quality rip of a dvd movie using X264, i know the compression and quality is beyond xvid when compared to x264. no matter what ever you do we will get quality in x264. thats why i dont feel challenge in using x264,
BUT ANYWAY THANKS FOR THE REPLY

[setarip_old]

@avengerevenge

Hi! why do you think i said i use xvid codec for ripping, because to watch rips on divx compatible dvd player.

Instead of so unfairly accusing "Inspector.Gadget" of being rude, when in fact he offered meaningful suggestions in response to your requests/questions, I'd suggest you CAREFULLY re-read your initial post - NOWHERE does it mention that you want to watch your videos on a DivX-compatible player...

[avengerevenge]

@avengerevenge

Hi!

Instead of so unfairly accusing "Inspector.Gadget" of being rude, when in fact he offered meaningful suggestions in response to your requests/questions, I'd suggest you CAREFULLY re-read your initial post - NOWHERE does it mention that you want to watch your videos on a DivX-compatible player...
i think there is no need to mention why xvid is still used for encoding. if people wanted to see there videos or movies in there pc's they would definitely select x264 for encoding. its clear we still use xvid for basic compatibility reason that is with dvd player, i said that i always use xvid, i mentioned the word always, so dont you think that if know xvid codec will i not know x264.
one more thing dude,instead of questioning about the knowledge of user(who posts questions)and telling him that this is not 1990's like some wired history class,can make anyone irritating.
lets go back to my question, i asked very clearly for the gudience in usage of avisynth filters and scripts in my third last line. and then followed by my doubt.
its very clear.

but still if i hurt anyone's feeling, i am sorry, i apologize, i was really irritated when i read that reply, i thought that some one was really gonna guide me by posting some cool avisynth scripts
and telling about some filters,sharing important and ideas. but its not as it looks like.

ok as i said iam sorry. but still setarip_old i request you to think once more about my reply by looking through my vision. anyone can get angry after all we are still humans, and i used no bad words in my reply, i just said it was really rude, thats all man.

[7ekno]

You would retain more detail using more lines, 200 is way too low to even bother using filters to "improve" it when all those "improvements" get hacked to pieces with a resize down to 200 lines ...

With your current method, use Lanczos resize for "detail" retention or "bilinear" for compressability, no other filters are going to matter at 200 lines ;)

If deciding that you want more detail (that is, you end up using more lines), you can pre-process with MCTemporalDenoise(settings="low", flat=true) and neutrally resize with Spline36 ... but really no point when reducing the number of lines by over 50% ...

Also, as long as you are using the VAQ patched XviD, that's about the only improvement you will get out of the encoding software, however it might be worth experimenting as to whether your target device supports more than 1 B-frame, Q-pixel and GMC, each can make an "improvement" in either efficiency or quality ...

7ek

[avengerevenge]

You would retain more detail using more lines, 200 is way too low to even bother using filters to "improve" it when all those "improvements" get hacked to pieces with a resize down to 200 lines ...

With your current method, use Lanczos resize for "detail" retention or "bilinear" for compressability, no other filters are going to matter at 200 lines ;)

If deciding that you want more detail (that is, you end up using more lines), you can pre-process with MCTemporalDenoise(settings="low", flat=true) and neutrally resize with Spline36 ... but really no point when reducing the number of lines by over 50% ...

Also, as long as you are using the VAQ patched XviD, that's about the only improvement you will get out of the encoding software, however it might be worth experimenting as to whether your target device supports more than 1 B-frame, Q-pixel and GMC, each can make an "improvement" in either efficiency or quality ...

7ek

ok thanks for the reply, but one big problem is that when using
McTemperaldenoise filter, is that its tooooooo slow,
when its encoding,its processing only 2.1 or 3.1 frames per second, its required time to encode is show nearly 21 hours for the 1st pass in xvid,(using virtualdubmod with gknot)
its really impossible if you can imagine another 21 hours for the second pass.
what should i do to use Mctemporal very fast.
its really impossible to wait for such long time

[7ekno]

No point using MCTD for ~ 200 lines, just use a Lanczos resize (will be effectively the same when resized down) ...

If you really wanted to maintain quality, you would be doing anamorphic encoding and keeping 480/576 lines of detail ;)

7ek