I was looking for the 1:33:1, but thanks anyway, I found it with your link

I really, really don't understand what's going wrong. I'm gonna give it another shot this afternoon, totally starting over.

If this spline36resize forces me to use a different AR than I originally intended (because I ticked NTSC and not Other in Input Resolution), should I go with it?

In other words: is spline36resize defining the resolution beforehand? And if it does, is it useless to adjust it in the Resolution tab in GK?

When you use GK to setup your rip, you cannot change the script.
You can only mod the script before a comp test or before a final rip with the Edit buttons. After you close the comp test & go back to the GK windows all your modified script is deleted & it returns to default.
Whats confusing me is that you say that youve modded the script & its messed up your standard GK windows which is not possible.
All you are doing with spline36resize is replacing the lanczos sharp with the same values that you have already set as default in your script by setting GK to your rip preferences.
I really think something got really screwed up with your GK last night & would recommend you click the reset button (bottom right) & start over with a fresh start.

Hehe, yeah, sorry... 4/3=1.3333333

Just in case:
Never modify the .d2v file, only ever mod the .avs

Mmm, I already found a line in my avs script that could have f00ked things up for sure:



While opening another d2v, it seemed to go right, but after editing the avs it went all wrong again. Probably because of this. stupid me!!

Glad you figure out the problem

I'm busy reencoding it from the beginning now. Comp test gives me 49.2% now This while I have added the spline36resize (480,352). The preview looks like a slideshow.

Have you reduced your audio to mp3? try using that CQM that elchup suggested as that may increase the compress slightly too.

Reducing to mp3 is done by using your new guide on page 1, right? Curious, this is the first time I did that. So actually all my previous rips have AC3 audio?

OK: I have two audio tracks now, one AC3 and one MP3. When I started over, I selected the MP3 one, so now it should be OK, right? Comptest gives me 69.1% now. The preview still looks like a slideshow however...

Hahaha, I keep laughing at the fact that sometimes simple things turn up for me to be done. For me they are new and unknown and for you lot they must be so simple and logical to do that they keep being overlooked in guides

Are you saying that you are unable to edit your script before comp test?
Thats the only way to do it with your chosen filtering and get a more reliable test result

If you think theres something I should add to the guide then tell me what I've missed & I'll add it

I made this guide after only my 2nd or 3rd rip when everything was fresh & so it would be from a beginners perspective as I really struggled to figure it all out with help from loads of people.

I've never converted the audio to MP3 either, I simply ran Taxi 2 through this morning just to see how it worked & took screenshots as I did it. Thanks to Sammi Curr for the suggestion on adding that to the guide

No, I'm not. Where did you get that idea?



I know. I'm much happier with the last result (69.1%) than with the previous results (49-55%). The only thing is that I don't know what the matrix does to the comptestresult. As you can only select the matrix in one of the last screens you get before starting to encode, it's impoossible to see if it does good on the comptestresult or bad. Is there a way by which you can "go back" after having selected a matrix so you can do a comptest with the matrix included?



I don't really think you missed it, but a part on how to edit avs script could be useful. Only after several people posted their scripts into this topic, I got a general idea on where and how to edit. At first I didn't even know what an avs was, so when spud posted "limitedsharpenfaster goes into your avs" I was like "WTF??"

I missed everything that went on in this thread between xmas & new year as I was working away & saw you having a lot of problems & this was one of them & wasnt sure if youd managed to sort that.



Yes, go to the options tab & bottom right you have default XviD settings for 1st & 2nd pass. Add your CQM into them & try again



I've not added AVS scripting to the guide for the simple reason this is a beginners guide. I'm going to add a small part about it along with setting up XviD next, but today I focussed on the basics again.

Ah, another very useful tip of something I didn't know anything about




Good. I know it's a beginners guide, but people started talking about editing the avs very soon: on my first GK rip, to be exact


Tonight I'm gonna let GK rip the movie with jawors, and if the result doesn't please me, I'll try again tomorrow with the matrix elchupa posted. What is the simplest way of changing the matrix but leave everything else intact settingswise?

One thing I really hate about GK is that you have to edit your avs every fucking time you re-open the d2v/avs. Why can a simple program like notepad save my changes and GK can't?

When you change the matrix in XviD that is all you are changing. All other custom settings you have chosen remain intact

Including the edited avs?

The CQM is simply a custom quantization matrix. This handles how it manipulates pixels & that is all it does. Any modifications you have made to your XviD settings are not affected by changing them.

There is absolutely no way that changing your CQM is going to change your AVS script as that is a totally seperate thing completely.

GK is simply a GUI interface that uses several different programs at the same time.

The first try worked out. Today I'm gonna rip it with the other matrix, to check the differences. At least I'm relieved the ripping worked again, without giving me nonsensical errors and superwidths.

The verdict is as follows:

Jawors: good, colours are bright.
EQMv3ulr: good, but colours look a bit washed out.

So I'm posting the rip which was made with Jawors here.

Interesting. For me it was the other way around.

Might depend on the source, too.

Thats all it is. Unfortunately what scripts or CQMs work best on 1 rip are unlikely to produce the same results on a different rip. Each source needs individual attention thus making ripping an art form