Log in

View Full Version : Custom Matrices


Pages : [1] 2 3 4

*.mp4 guy
13th October 2006, 11:16
[edit] I was going to leave this post as it was, but it has been recently bumped to the front page. Currently the cases that these cqms were meant to fix are handled very well by psychovisual optimizations within X264, such as Dark Shikari's aq, psy rd, and psy trellis, which usually work better then cqms, in my (and everyone elses) opinion. Cqms can still be usefull, but not most of the time, and certainly not for the majority of people.

This thread is to provide a place for me to keep up to date versions of my Mpeg4-avc cqms, and somewhere to refer people who want copies of them. If you have any questions about these matrices in particular feel free to ask them here; however I would apriciate it if more general questions (stuff about matrices in general, etc.) were kept out of this thread, to keep it succinct. Some matrices used in commercial HD-DVD/Blu-Ray encodes can be found in another thread (http://forum.doom9.org/showthread.php?t=124755).

With the addition of the deadzone parameter there is yet another value that needs to be tweaked to get the best results, I will specify any deadzone settings that i think are neccesary to get the most out of a matrix by posting the command line, IE "--deadzone-inter 6 --deadzone-intra 6". Megui now has gui options for changing the deadzone settings, reffered to as luma intra deadzone, and luma inter deadzone.

M4G LRM V4: LRM is for low to very low bitrates, 1cd or less, and MRM may even be better for some 1cd encodes at this point. It is designed to avoid artefacts more then to preserve detail. 0:0 for smooth encodes, -3;0 for moderate encodes.
INTRA4X4_LUMA =
8,22,32,47,
22,48,55,57,
32,55,63,69,
47,57,69,84

INTRA4X4_CHROMAU =
16,20,34,64,
20,40,62,78,
34,62,98,138,
64,78,138,168

INTRA4X4_CHROMAV =
16,20,34,64,
20,40,62,78,
34,62,98,138,
64,78,138,168

INTER4X4_LUMA =
12,28,28,32,
28,32,35,38,
28,35,42,46,
32,38,46,55

INTER4X4_CHROMAU =
18,24,34,41,
24,40,48,56,
34,48,64,92,
41,56,92,110

INTER4X4_CHROMAV =
18,24,34,41,
24,40,48,56,
34,48,64,92,
41,56,92,110

INTRA8X8_LUMA =
8,11,10,16,24,28,29,32,
12,13,14,19,26,27,29,33,
14,13,16,24,28,29,32,35,
14,17,22,30,32,34,38,39,
18,22,28,32,37,42,45,47,
24,27,29,34,42,49,55,57,
29,29,32,38,45,55,63,69,
32,33,35,39,47,57,69,84

INTER8X8_LUMA =
13,14,16,18,20,21,22,24,
14,15,18,19,20,21,22,25,
16,18,20,21,22,23,25,27,
18,19,21,23,25,26,29,31,
20,20,22,25,28,31,35,38,
21,21,23,26,31,37,42,48,
22,22,25,29,35,42,51,61,
24,25,27,31,38,48,61,76
M4G MRM V2: MRM is supposed to work well at moderate bitrates (and sometimes does well even at low and high bitrates, though it isn't suited for transparency). It should give a good balance of details and artefacts, it looks similar to HVS best. 0:-1 for smooth results (not recommended) -1:-2 for moderate sharpness, -2:-4 for high sharpness. should be used with "--deadzone-inter 6 --deadzone-intra 6" to get a more detailed picture, at the cost of a small amount of ringing.
INTRA4X4_LUMA =
10,10,20,30,
10,10,34,33,
20,34,52,76,
30,33,76,112

INTRA4X4_CHROMAU =
8,8,24,72,
8,8,41,144,
24,41,96,200,
72,144,200,255

INTRA4X4_CHROMAV =
8,8,24,72,
8,8,41,144,
24,41,96,200,
72,144,200,255

INTER4X4_LUMA =
10,18,20,20,
18,18,34,44,
20,34,52,76,
20,44,76,112

INTER4X4_CHROMAU =
16,22,22,22,
22,22,22,56,
22,22,72,96,
22,56,96,128

INTER4X4_CHROMAV =
16,22,22,22,
22,22,22,56,
22,22,72,96,
22,56,96,128

INTRA8X8_LUMA =
12,12,14,20,24,26,30,32,
12,12,15,22,24,27,30,36,
14,15,20,26,27,31,34,40,
20,22,26,30,35,38,40,46,
24,24,27,35,42,48,50,52,
26,27,31,38,48,56,60,64,
30,30,34,40,50,60,72,80,
32,36,40,46,52,64,80,96

INTER8X8_LUMA =
12,16,16,18,20,22,25,28,
16,16,17,20,20,23,26,28,
16,17,20,22,24,26,29,31,
18,20,22,25,28,31,33,38,
20,20,24,28,33,37,43,49,
22,23,26,31,37,46,56,65,
25,26,29,33,42,56,70,88,
28,28,31,38,49,65,88,115
M4G HRM V2: HRM is for high to very high bitrates depending upon your source, however the new version scales quite well so if you really wanted to you could use it at any bitrate without problems. For transparency it should be used with the "--deadzone-inter 4 --deadzone-intra 6" switches added to the commandline, without the quotes. since it is designed for transparency, there shouldn't be any noticible properties it introduces to the picture. B predict mode should be set to none if your source is very grainy(and you wan't it to stay that way), or has many low contrast areas, otherwise b-rdo should be disabled and b prediction should be set to auto. I would apriciate feedback on any sources that cannot reach transparency with this matrix, as I have run into a few, but cannot currently find a solution.
INTRA4X4_LUMA =
15,6,15,22,
6,7,25,30,
15,25,38,48,
22,30,48,96

INTRA4X4_CHROMAU =
16,6,24,72,
6,8,41,144,
24,41,96,200,
72,144,200,255

INTRA4X4_CHROMAV =
16,6,24,72,
6,8,41,144,
24,41,96,200,
72,144,200,255

INTER4X4_LUMA =
4,11,15,22,
11,11,25,30,
15,25,38,48,
22,30,48,96

INTER4X4_CHROMAU =
5,16,16,16,
16,16,16,56,
16,16,72,96,
16,56,96,128

INTER4X4_CHROMAV =
5,16,16,16,
16,16,16,56,
16,16,72,96,
16,56,96,128

INTRA8X8_LUMA =
24,7,7,12,15,20,21,23,
8,9,14,15,18,21,23,21,
10,12,15,17,17,21,26,20,
14,15,17,17,18,33,30,23,
15,17,17,21,26,39,39,29,
18,18,20,24,33,39,41,35,
21,24,29,34,39,45,45,38,
27,35,36,39,38,38,38,38

INTER8X8_LUMA =
6,10,13,13,15,16,18,22,
10,10,12,15,15,16,21,24,
13,12,15,16,19,21,25,27,
13,15,16,21,24,28,30,34,
15,15,19,24,30,36,37,40,
16,16,21,28,36,42,45,52,
18,21,25,30,37,45,55,72,
22,24,27,34,40,52,72,96
M4G Smooth V1: An all purpose smooth matrix that blocks very little, gives a similar look to smooth mpeg2 video. -3:0 works well for inloop. Some sources may need to have b-frame mode set to none to work properly with this matrix
INTRA4X4_LUMA =
4,9,18,45,
9,16,35,180,
18,35,225,255,
45,180,255,255

INTRA4X4_CHROMAU =
14,22,32,72,
22,24,41,144,
32,41,96,200,
72,144,200,255

INTRA4X4_CHROMAV =
14,22,32,72,
22,24,41,144,
32,41,96,200,
72,144,200,255

INTER4X4_LUMA =
4,9,18,45,
9,16,35,180,
18,35,225,255,
45,180,255,255

INTER4X4_CHROMAU =
16,22,22,22,
22,22,22,56,
22,22,72,96,
22,56,96,128

INTER4X4_CHROMAV =
16,22,22,22,
22,22,22,56,
22,22,72,96,
22,56,96,128

INTRA8X8_LUMA =
5,11,10,16,28,68,80,80,
12,12,14,18,32,73,90,110,
14,13,16,30,51,87,138,112,
14,17,28,36,80,174,160,124,
18,28,47,88,136,255,206,154,
30,42,86,128,162,208,226,184,
60,128,156,174,206,241,240,202,
144,184,190,196,224,200,206,198

INTER8X8_LUMA =
5,11,10,16,22,28,38,46,
12,12,14,18,26,38,45,70,
14,13,16,24,34,41,51,125,
14,17,22,24,37,50,100,155,
18,22,28,42,70,135,160,180,
24,26,39,50,135,175,200,205,
30,45,51,100,160,200,225,230,
48,70,125,155,180,205,230,255
M4G High Detail V3.1: A very sharp matrix, works best at mid bitrates. -3:0 is the recommended deblocking setting. This matrix is NOT designed to keep grain well, its supposed to look sharp and crisp, not keep everything in the source, it should look detailed, but not transparent, so little pieces of grain and noise are usually some of the first things to get removed.
INTRA4X4_LUMA =
6,16,22,28,
16,24,32,40,
22,32,48,72,
28,40,72,112

INTRA4X4_CHROMAU =
12,22,32,72,
22,24,41,144,
32,41,96,200,
72,144,200,255

INTRA4X4_CHROMAV =
12,22,32,72,
22,24,41,144,
32,41,96,200,
72,144,200,255

INTER4X4_LUMA =
9,20,21,24,
20,21,24,44,
21,24,56,80,
24,44,80,112

INTER4X4_CHROMAU =
16,22,22,22,
22,22,22,56,
22,22,72,96,
22,56,96,128

INTER4X4_CHROMAV =
16,22,22,22,
22,22,22,56,
22,22,72,96,
22,56,96,128

INTRA8X8_LUMA =
8,9,11,13,16,21,24,27,
9,9,12,15,18,22,24,29,
11,12,15,19,22,25,28,32,
13,15,19,24,27,30,34,37,
16,18,22,27,34,39,41,46,
21,22,25,30,39,48,59,74,
24,24,28,34,41,59,81,109,
27,29,32,37,46,74,109,160

INTER8X8_LUMA =
12,12,12,12,13,16,19,25,
12,12,12,12,13,16,21,27,
12,12,13,15,18,21,26,33,
12,12,15,21,25,30,37,45,
13,13,18,25,34,43,54,64,
16,16,21,30,43,60,76,94,
19,21,26,37,54,76,102,132,
25,27,33,45,64,94,132,177

matrices in a 7zip (http://forum.doom9.org/attachment.php?attachmentid=6910&d=1173213612)

Thunderbolt8
13th October 2006, 11:25
it would be nice if you could add a description to each mask, what it is supposed to do and under which circumstances to use (low/mid/high bitrates etc.)

*.mp4 guy
13th October 2006, 11:43
Not sure what you mean by the "source". I'll get around to adding descriptions later.

shon3i
13th October 2006, 13:44
Can you put all matrices in one zip together. And can you reccomend me some for 1 CD rip, where bitrate usualy 500-1000kbps. Thanks

bond
13th October 2006, 17:38
a description for what each matrix purpose is is definitely needed, or did you just set them up by using dices? ;)

fields_g
15th October 2006, 05:11
Can you put all matrices in one zip together.

Another thought.... I know MeGUI supports profile distrobution through the update server. I don't recall it being used for CQMs. Anyone know if the current MeGUI support this if fed the right files? Once the explanations are developed, and M4G (and the server admins) belive your matrix tweaking is mature enough, I wouldn't mind seeing them delivered in such a way. It should work pretty slick once the server is working again.

foxyshadis
15th October 2006, 05:37
Nice. But while copying them, I noticed that you're missing INTRA4X4_LUMA and INTRA4X4_CHROMAU from MRM. Which so happens to be the one I most want to test. =p

*.mp4 guy
15th October 2006, 14:08
and M4G (and the server admins) belive your matrix tweaking is mature enough, I wouldn't mind seeing them delivered in such a way. It should work pretty slick once the server is working again. M4G is a less unwieldy contraction of my D9 nickname, sorry for the confusion.

Nice. But while copying them, I noticed that you're missing INTRA4X4_LUMA and INTRA4X4_CHROMAU from MRM. Which so happens to be the one I most want to test. =p thanks for noticing that, fixed.

shon3i
15th October 2006, 18:19
Aswome, thank you so much, now testing.

DDogg
15th October 2006, 19:40
*.mp4 guy, thanks for the work and the descriptions. Can you share your thoughts on matching one of these matrices, or others for that matter, with the CQ-ASP_Q2_eq() profile? Size is not an overriding issue. Transparency is my main goal, but speed as well - moving a 200+ DVD collection to x264 takes a while. The CQ-ASP_Q2_eq() settings seem to provide quality, reasonable speed, and reasonable compression. Realize there is no one size fits all answer- just would appreciate your subjective opinion on a good place to start, matrix wise.

bond
15th October 2006, 19:45
M4G MRM V2: MRM is supposed to work well at moderate bitrates (and sometimes does well even at low and high bitrates, though it isn't suited for transparency). It should give a good balance of details and artefacts, it looks similar to HVS best. yummie :)

*.mp4 guy
15th October 2006, 20:37
@bond it is very important to use the modified deadzone settings if you want it to look like hvs best.

@ddog I don't have the CQ-ASP_Q2_eq() profile, from the name it looks like its an asp profile for megui(?), if its not could you post a link to the xml file here so I can see what its like.

*.mp4 guy
15th October 2006, 21:06
@DDogg MRM will work well, though the results won't always be transparent, HRM might work well too, but you would have to deal with larger files, and disable b-prediction, and sometimes there wouldn't be any benefit.

shon3i
17th October 2006, 21:11
@*.mp4 guy i get very good result with M4G Smooth V1 with all parameters you gave, with 720x464 (War Of The Worlds very grainy movie) @ 773kbps, i have few questions, is this matrix desinged for mid-low bitrates, and it is better tha LRM or MRM for same bitrate, and you mean about b prediction, did you mean about --weightb switch or ?

Thanks

*.mp4 guy
18th October 2006, 02:25
it is made to work at any bitrate (where you aren't trying for transparency). It isn't "better" then any of the other matrices, its just different, it usually does well on blurry/grainy footage, or on material with lots of gradients. Sometimes X264 doesn't handle matrices well, when that happens setting b-frame mode to none will fix the problem, thats what I meant by "disabling b-prediction".

desta
18th October 2006, 03:33
Thanks for these mp4guy. :)

Could i just ask, what sort of values do you have in mind (roughly) when you say "low to very low bitrates" .. "moderate/mid bitrates" .. "high/very high bitrates" ?

Is it something like:

low = < 800
mid = 800 to 1500
high = 1500 +

... sorry to generalise. Just asking for my own benefit.

*.mp4 guy
18th October 2006, 04:04
Low = 1cd or less (IE 900 - whatever).
Medium = Anything more then low and less then high.
high = Transparent or almost transparent (dvd quality), bitrate tends to vary.

desta
18th October 2006, 04:06
ok, thanks for clarifying. :)

shon3i
18th October 2006, 17:30
it is made to work at any bitrate (where you aren't trying for transparency). It isn't "better" then any of the other matrices, its just different, it usually does well on blurry/grainy footage, or on material with lots of gradients. Sometimes X264 doesn't handle matrices well, when that happens setting b-frame mode to none will fix the problem, thats what I meant by "disabling b-prediction".
Ok, thanks for info, indeed i get very good and smooth picture, with this matrix.

foxyshadis
18th October 2006, 20:27
Smooth is the best I've used for CG video of any matrix. It's really awesome!

akupenguin
18th October 2006, 20:43
How did Smooth's INTRA8X8_LUMA end up being neither monotonic nor symmetric?

*.mp4 guy
18th October 2006, 23:34
How did Smooth's INTRA8X8_LUMA end up being neither monotonic nor symmetric?
Well it is predominantly monotonic (though I suppose thats an oxymoron) long story short I stole some of the frequency weighting from the JPEG matrix, which after a lot of testing turned out to work the best for what I wanted to do, anyway, the mpeg matrix isn't monotonic or symetrical either and HVS Best isn't monotonic, though it is symetrical.
Smooth is the best I've used for CG video of any matrix. It's really awesome!
Thanks, just out of curiosity what type of cg is your source, is it like pixars stuff or is it pseudo-realistic cg?

akupenguin
19th October 2006, 00:32
Yes, I see that the quant matrix recommended in the jpeg standard is also nonmonotonic and asymmetric, and has a dc value much higher than the other low freqs (like your HRM intra).

Nonmonotonic: ok, I can believe that there's a difference between even and odd frequencies regarding their tendency for blocking artifacts.
Asymmetric: the only ways this can happen, are if there's a difference in the amount of vertical vs horizontal texture in an average movie (this is true for motion, and some motion estimation algorithms exploit that), or if it's tuned for anamorphic. Of course, the best solution in either case would be to generate a matrix based on the content of the current movie, rather than depending on averages. If you can quantify the psy decisions that went into the creation of the average matrix.

*.mp4 guy
19th October 2006, 00:53
Yes, I see that the quant matrix recommended in the jpeg standard is also nonmonotonic and asymmetric, and has a dc value much higher than the other low freqs (like your HRM intra).

Nonmonotonic: ok, I can believe that there's a difference between even and odd frequencies regarding their tendency for blocking artifacts.
Asymmetric: the only ways this can happen, are if there's a difference in the amount of vertical vs horizontal texture in an average movie (this is true for motion, and some motion estimation algorithms exploit that), or if it's tuned for anamorphic. Of course, the best solution in either case would be to generate a matrix based on the content of the current movie, rather than depending on averages. If you can quantify the psy decisions that went into the creation of the average matrix.

Its true that relying upon pre-generated matrixes isn't optimal in some regards, but there hasn't been much success whith automated generation of matrices either, so it makes sense to use pre-generated averages to create matrices, in most cases.

Thunderbolt8
19th October 2006, 14:19
Thanks, just out of curiosity what type of cg is your source, is it like pixars stuff or is it pseudo-realistic cg?
just out of curiosity, what does cg mean at all ? :p

foxyshadis
19th October 2006, 16:04
Thanks, just out of curiosity what type of cg is your source, is it like pixars stuff or is it pseudo-realistic cg?

Pixar type stuff. Minimal texturing and lots of smooth edges and gradients. Haven't tried other stuff with it yet.
just out of curiosity, what does cg mean at all ? :p

Computer generated.

elguaxo
19th October 2006, 23:38
Great thread. Thanks *.mp4 guy

elguaxo
21st October 2006, 13:47
Is M4G Smooth V1 similar to your M4G-V3 matrix?

*.mp4 guy
21st October 2006, 15:02
Is M4G Smooth V1 similar to your M4G-V3 matrix?
Yes, actualy its a new version with a new name, to (hopefully) keep things from getting confusing. The old version was a preliminary design I had been working on for a while, which is why it had a generic name. At this point the only thing thats likely to change are the chroma matrices, I think they may be a bit too agressive, but I have to do more testing.

check
29th October 2006, 14:40
hi, Have you any suggestions for matrices to try for ~q18-20 for 720p anime? The particular source I'm playing with alternates between zero detail pure toon scenes and painted backgrounds with oodles of details. Overall complexity is low, and the final bitrate will probably end up around 1.2-1.4mbits (a 1.4gb target size), but 2mbits is also a possibility.

*.mp4 guy
29th October 2006, 15:22
At that bitrate you might be able to get away with a cqm on anime, but it is probably still not a good idea. Try adding "--deadzone-inter 6 --deadzone-intra 6" (without quotes) to the custom command line parameters section in megui instead of using a cqm, it will cause less detail to be dropped, and will probablt work better then a cqm on anime.

elguaxo
29th October 2006, 16:11
Try adding "--deadzone-inter 6 --deadzone-intra 6" (without quotes) to the custom command line parameters section in megui

Would be the same replacing </CustomEncoderOptions> with <CustomEncoderOptions>--deadzone-inter 6 --deadzone-intra 6</CustomEncoderOptions> in one of the profiles?

*.mp4 guy
29th October 2006, 16:52
Yeah that should work fine.

elguaxo
30th October 2006, 00:22
:thanks:

check
30th October 2006, 00:51
hmm, interesting. So are x264 cqms bad ideas in general for anime, or are your matrices simply not tuned for cartoon sources?

DryFire
30th October 2006, 01:23
I took it to mean that at those quants you won't get much from it.

*.mp4 guy
30th October 2006, 03:11
Cqms aren't usefull for anime until there won't be any visible ringing artefacts, at which point a cqm that can preserve more detail and block less will probably help. However I don't have a good idea of where the trade off occurs since I don't encode anime much. Which is why I recommended a more conservative solution by just lowering the deadzone setting, which might work better for anime at high bitrates then one of my cqms anyway, as I said I have not done much testing on the subject.

In theory it should be possible to make a matrix that looks better on anime then the flat matrix at higher bitrates, I beleive Soulhuter made one for Xvid a while ago, but its not something I've given much thought to.

Mc Onyx
30th October 2006, 11:32
First of all thanks for the matrices and your time spent on them, well done. Second, can you suggest any of your matrices for HD Encoding at 720p 4-5Mbit. I read somewhere here that at that high resolution and bitrate, it doesn't really matter which one to use. And i can simply use flat matrix, but please clarify if i'm wrong. Thanks

check
30th October 2006, 14:10
Thanks for the feedback mp4, I'm running some encodes now with modified deadzone settings thanks to your idea.

*.mp4 guy
30th October 2006, 18:59
The same general rules apply to HD as SD, the biggest difference comes from the viewing conditions, many displays can easily show the flaws in SD content, but may have trouble showing the same problems in HD content becuase of the increased resolution, which can lead people to falsely assume that HD can be overcompressed without problems. If you wan't the best results you have to find settings that look good to you on sd content, then use the same Q values and settings on hd content, this will ensure that you don't end up throwing away quality that you might miss later when higher resolution display are more readily available.

At your bitrate MRM should give you transparent results, though without knowing more about your source its really hard to say.

Thunderbolt8
4th November 2006, 06:22
I need some advice on encoding a movie and the (possible) use of custom matrixes. I am planning to make a 1,46 GB rip from texas chainsaw massacre (1974) ultimate edition. dvd is ntsc, movie length 1:23:20, the audio stream is ~260 mb, so ~1,2 GB should remain for the video stream. I can use either 2 pass encode or -crf mode with a ~corresponding size.
my problem is that my pc is quite slow for encoding and also tends to crash once a day, so I cannot really try too much out without spending a whole week on one movie. thats why I'd like to have some advice for parameters like the use of custom matrixes (which) or deadzone settings (if needed) and so on so I can already aim at the best regions without too much having to try out. I took some screenshots via vlc snapshot (im screenshot newbie), if they arent really useful then tell me plz so I can try to make new ones (and tell me how to do it better -.-).
considering the video quality, I post some comments from dvdcompare.net:

"-disc "Ultimate Edition" - Steelbook Packaging. High definition source, restored by Don May of "Synapse Films". Some quotes from him about the new transfer (source: HTF - hometheaterforum):
*The new HD transfer was not created from 35mm materials. It was created from the original 16mm vault materials.
*The older version was so noise-reduced (with DVNR) that most of the grain was removed and smoothed out, along with detail and sharpness.
*The grain was there because of the film stock used. Tobe himself told that there was no conscious decision to make the film look "documentary-style", with the graininess, etc. He was trying to film the best movie he could. The heavy grain structure you've seen on prints, etc. were caused by a combination of the film stock used and the cheap 35mm blow-ups done by the distributor at the time."

http://img153.imageshack.us/img153/7016/vlcsnap77783qf2.th.png (http://img153.imageshack.us/my.php?image=vlcsnap77783qf2.png)
http://img149.imageshack.us/img149/1267/vlcsnap78747zd0.th.png (http://img149.imageshack.us/my.php?image=vlcsnap78747zd0.png)
http://img153.imageshack.us/img153/3345/vlcsnap84156kw6.th.png (http://img153.imageshack.us/my.php?image=vlcsnap84156kw6.png)
http://img175.imageshack.us/img175/5923/vlcsnap80949ml3.th.png (http://img175.imageshack.us/my.php?image=vlcsnap80949ml3.png)
http://img149.imageshack.us/img149/7954/vlcsnap81217pg0.th.png (http://img149.imageshack.us/my.php?image=vlcsnap81217pg0.png)
http://img153.imageshack.us/img153/7459/vlcsnap83369vz2.th.png (http://img153.imageshack.us/my.php?image=vlcsnap83369vz2.png)

*.mp4 guy
4th November 2006, 16:38
There isn't much high frequency detail in any of the screenshots you posted, and they are all fairly noisy, so its a fair bet that the smooth matrix would work the best for you (assuming that you aren't close to transparency at 2mbps, I would guess that you wouldn't) since you don't wan't to do more then one encode you should set "bframe mode" to "none" to avoid possible problems, also make sure you have enabled "no fast p-skip" otherwise just use whatever you like for quality vs speed. -2:-1 should work pretty well for deblocking. The defualt deadzone settings should be fine aswell.

Thunderbolt8
4th November 2006, 17:54
what is meant with high frequency detail, has it something to do with the bitrate of the dvd ?
I could do lets say 3 encoded to try out, but I really dont want to make more, cause it simply will take too long on my comp. so there is a little room for experimenting, just not much.
should I use the 2 pass mode or -crf mode ? and what are the usual deadzone settings, since they are not implented in the gui yet ? are they usually diasbled (and trellis enabled) or is it this one here "--deadzone-inter 6 --deadzone-intra 6" ?

Thanks so far, Im gonna try that out now.

*.mp4 guy
4th November 2006, 18:11
The usual deadzone settings are what is used when you don't specify anything. You want to hit a specific bitrate, so you should obviously use 2pass mode. High frequency detail more or less corelates to how sharp the image is, though its a bit more complicated then that.

Thunderbolt8
4th November 2006, 18:46
just to clarify again, since I am using / have to use a certain profile mostly trellis is activated and the deadzone settings havent been implented into sharktooths profiles yet, so it means in that case for smooth v1 matrix deadzone is off (=not in command line) and trellis activated ?

*.mp4 guy
5th November 2006, 08:35
That should work fine, though I haven't done much testing with trellis.

desta
5th November 2006, 16:00
I was wondering.. is using AQ together with your matrices something you would say is best not to do, or is it still ok?

*.mp4 guy
5th November 2006, 17:06
Well they shouldn't need aq, but if you like the way it looks with them there isn't any reason I can think of that you shoudn't use it.

desta
5th November 2006, 19:13
Ok, thanks again. :)

Zeest
20th November 2006, 05:40
What would you recommend for older movies (80's) and a video bitrate of around 1400-1500. Movies like The Thing, Come and See etc. I'm using SharkTooth's HQ_Slower profile.