Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
|
|
Thread Tools | Search this Thread | Display Modes |
9th January 2005, 23:33 | #61 | Link |
H.264 is the Future
Join Date: Dec 2001
Location: UK
Posts: 210
|
The 'Snow' option was a big tease!!
Oh, and pretty sure there is a (small) bug when you select CQ for MPEG4, the default is CQ=800 ! Looks like it's taking the default bitrate from CBR mode - for x264 it changes to CQ26, so that works fine. Cheers Ivan Last edited by ivan_alias; 9th January 2005 at 23:39. |
10th January 2005, 08:53 | #62 | Link | ||||||
clueless n00b
Join Date: Oct 2001
Location: somewhere over the rainbow
Posts: 10,579
|
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
__________________
For the web's most comprehensive collection of DVD backup guides go to www.doom9.org |
||||||
10th January 2005, 09:21 | #63 | Link | |
FFmpeg fan
Join Date: Dec 2003
Location: Germany
Posts: 427
|
Quote:
Hellfred EDIT: Spelling, oh i hate it that much! |
|
10th January 2005, 10:14 | #64 | Link | ||
clueless n00b
Join Date: Oct 2001
Location: somewhere over the rainbow
Posts: 10,579
|
Quote:
Quote:
__________________
For the web's most comprehensive collection of DVD backup guides go to www.doom9.org |
||
10th January 2005, 10:17 | #65 | Link |
x264 developer
Join Date: Sep 2004
Posts: 2,392
|
Yes, I suggested that sysKin merge the two settings in his interface. But then, I'm quite happy leaving both on 0, whereas I hear many people think 0 blurs too much. So if you think you can effectively use them separately, feel free to experiment (I haven't heard of any such study). Suggestions include alpha=0, beta=negative, i.e. full strength but avoids areas with much detail.
|
10th January 2005, 13:22 | #66 | Link | |
x264 developer
Join Date: Sep 2004
Posts: 2,392
|
Quote:
vqscale: range 0.01 .. 255, sane range 1 .. 10. (A given quality in snow needs somewhat lower qscale than the same quality in mpeg4.) default: 0 (lossless). Note that 0 may not be specified; if you want lossless encoding, you must leave out vqscale. (Yes, quantizer can be fractional.) There is no ratecontrol. Constant quantizer is the only mode. pred: 0 => 9/7 wavelet (default). 1 => 5/3 wavelet. 2 => 13/7 wavelet. The different wavelets have slightly different characteristic artifacts. I think 9/7 usually looks best. cmp: full pixel motion comparison function subcmp: hpel/qpel comparison function mbcmp: MB type comparison function Choices that work for snow: 0 (SAD), 1 (SSD), 11 (5/3 wavelet), 12 (9/7 wavelet). Defaults: SAD. While you might think that the wavelet comparators would have an advantage, I find that SSD is usually best (for all 3), with SAD slightly better the remainder of the time. You can add 256 to any of the options to enable chroma_me for that comparison (e.g. mbcmp=257 for SSD with chroma), but I haven't found it to help. qpel: default=off. Always helps. v4mv: default=off. Allows smaller motion partitions. The current MB decision algorithm doesn't make very good use of this: it improves quality, but also increases bitrate. (and you could get more quality per bitrate by reducing quantizer instead.) last_pred: range=0-3, default=0. Tries a few extra predicted motion vectors before doing EPZS search. This option has negligible effect on both speed and quality of snow, so just leave it off. (it does, however, help mpeg4.) In short: the best options in almost all cases are vcodec=snow:vstrict=-1:vqscale=$N:pred=0:cmp=1:subcmp=1:mbcmp=1:qpel |
|
10th January 2005, 15:00 | #67 | Link | ||
Registered User
Join Date: Nov 2001
Posts: 9,770
|
Quote:
Quote:
__________________
Between the weak and the strong one it is the freedom which oppresses and the law that liberates (Jean Jacques Rousseau) I know, that I know nothing (Socrates) MPEG-4 ASP FAQ | AVC/H.264 FAQ | AAC FAQ | MP4 FAQ | MP4Menu stores DVD Menus in MP4 (guide) Ogg Theora | Ogg Vorbis use WM9 today and get Micro$oft controlling the A/V market tomorrow for free |
||
10th January 2005, 15:02 | #68 | Link | |
Registered User
Join Date: Nov 2001
Posts: 9,770
|
Quote:
so beta defines what areas get affected by the deblocking and alpha the strength? if yes, than it might be indeed a good idea to NOT combine them to one option.
__________________
Between the weak and the strong one it is the freedom which oppresses and the law that liberates (Jean Jacques Rousseau) I know, that I know nothing (Socrates) MPEG-4 ASP FAQ | AVC/H.264 FAQ | AAC FAQ | MP4 FAQ | MP4Menu stores DVD Menus in MP4 (guide) Ogg Theora | Ogg Vorbis use WM9 today and get Micro$oft controlling the A/V market tomorrow for free |
|
10th January 2005, 16:47 | #69 | Link | |
stupid
Join Date: Sep 2004
Location: Cologne
Posts: 638
|
Quote:
- when alpha is the strenght, then +1 is a stronger deblocking than 0? I mean is positive deblocking and negative sharpening? - when beta is the area, then 0 means the same effects to the whole picture, negative means only backgrounds get blurred and positive means more blurring to the main parts of the picture.
__________________
cu Joe ------------------------ freedom is just another word for nothing left to loose |
|
10th January 2005, 20:08 | #70 | Link |
x264 developer
Join Date: Sep 2004
Posts: 2,392
|
Deblocking always smooths, never sharpens.
The strength and threshold are always adaptive based on quantizer. alpha=0,beta=0 is tuned for optimal PSNR on most sources. Other values tell it to use the strength and threshold tables from a different quantizer. So qp=25,alpha=-5,beta=-5 uses the same deblocking as qp=20,alpha=0,beta=0. Since higher quantizer => more artifacts => more deblocking needed, higher values of alpha & beta do stronger deblocking. (Note that since h264 uses a logarithmic quantizer, adding/subtracting N from it has the same effect independent of what the original quant was.) If qp+alpha <= 15 or qp+beta <= 15, deblocking is completely disabled for that frame. As for what exactly the parameters do: Consider each potential vertical/horizontal edge in the picture (between macroblocks, or between motion partitions within a macroblock). Derive a threshold (based on qp, beta, and type of block) and strength (based on qp, alpha, and type of block). If the variation within the adjacent blocks is less than threshold, and the difference across the edge is less than strength, then filter this edge. Filter means apply a 6tap blur perpendicular to the edge, but limit the amount of change to any one pixel based on strength. The effect of block type: Edges between non-coded blocks of similar MV are not filtered (because they were deblocked in the previous frame). Non-coded blocks that differ by more than 1 pixel worth of MV are filtered weakly. Normal inter blocks are filtered more. Intra blocks are filtered most. edit: I got alpha and beta swapped. Last edited by akupenguin; 10th January 2005 at 23:29. |
10th January 2005, 22:14 | #71 | Link |
clueless n00b
Join Date: Oct 2001
Location: somewhere over the rainbow
Posts: 10,579
|
v0.1 is out. stay tuned for more
__________________
For the web's most comprehensive collection of DVD backup guides go to www.doom9.org |
10th January 2005, 22:57 | #72 | Link |
FFmpeg fan
Join Date: Dec 2003
Location: Germany
Posts: 427
|
adding options manually and manpage
Hi Doom9
Thanks for this great tool to make handling encoding with mencoder under win32 so much easier. Before I had to use a hand-written batchfile that needed to be updated manually for each and every encode. It is so much more comfortable this way. Two suggestions. What about adding MPlayer/Mencoder manpage (html) to your Package, so that ppl. can actually try to understand what the commandline assembled by your GUI means, and to be able to add some more fancy options to it that may be too exotic or not yet implemented in your GUI? If you do not want to add the file to your package, can you at least mention the url of the html manpage to your readme file for those interested in it. Other question. One is already able to edit the commandline in your GUI, but i did not find my changes in the resulting job.bat. Do you plan to add it? Last thing, I am sometimes not interested in encoding the hole movie/avs script right away, but just the first <framecount> frames of it to test the impact of certain options. Is it possible to add avs2yuv option -frames <framecount> to your GUI so that i do not have to open and edit the AVS script everytime during the process of option optimization. Hellfred. |
11th January 2005, 08:27 | #73 | Link | |
clueless n00b
Join Date: Oct 2001
Location: somewhere over the rainbow
Posts: 10,579
|
Quote:
People who are knowledgeable enough to edit commandlines should imho resort to the commandline.. sure they can use the GUI to get a starting point, but after that, all advanced functionality makes things harder to handle and this is really a tool for people who do not care about the mencoder commandline. I just put the commandline there as a debug measure (it's easy to see if the commandline generation is wrong). I'm also planning on adding tooltips for all the options, thus making the manpage superfluous (I plan to add some "easy" understandable description for all the options plus suggested settings).
__________________
For the web's most comprehensive collection of DVD backup guides go to www.doom9.org |
|
11th January 2005, 08:45 | #74 | Link | ||
Registered User
Join Date: Dec 2002
Location: Russia
Posts: 57
|
Doom9
Quote:
Quote:
|
||
11th January 2005, 09:24 | #75 | Link |
Registered User
Join Date: Dec 2003
Posts: 194
|
Firstly, thanks for the neat GUI Doom9. I seem to have a slight problem getting it working though; here's what happens when I click 'Encode':
------------------------------------------------------------------- C:\Stuff\Programs\MeGUI> C:\Stuff\Programs\MeGUI>avs2yuv "C:\WUTemp\TEST\D2VAVS\test.avs" - | mencoder - -ovc x264 -o NUL: -passlogfile "mencoder-2pass.log" -x264encopts pass=1:qp_constant=26:bframes=1:deblockbeta=-2:rc_buffer_size=700 MEncoder dev-CVS-040228-17:13-3.3.3 (C) 2000-2004 MPlayer Team CPU: Advanced Micro Devices Athlon MP/XP Thoroughbred 1740 MHz (Family: 6, Stepping: 1) Detected cache-line size is 64 bytes CPUflags: Type: 6 MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 0 SSE2: 0 Compiled for x86 CPU with extensions: MMX MMX2 3DNow 3DNowEx SSE Reading C:/Stuff/Programs/MeGUI/mplayer/codecs.conf: 64 audio & 169 video codecs File not found: 'frameno.avi' Failed to open frameno.avi Reading config file C:/Stuff/Programs/MeGUI/mplayer/mencoder: No such file or directory Option ovc: Unknown suboption x264 C:\WUTemp\TEST\D2VAVS\test.avs: 640x352, 25000/1000 fps, 1829 frames Exiting... (error parsing cmdline) Output error: wrote only 316910 of 337920 bytes C:\Stuff\Programs\MeGUI> ------------------------------------------------------------------- I've got the latest versions of mencoder (celtic_druid's) and avs2yuv - as stated in the readme - and they are placed alongside MeGUI.exe in the same directory. Is there something else I'm missing (it's my first attempt at using mencoder, so please be gentle )? Thanks in advance. |
11th January 2005, 09:38 | #76 | Link |
Registered User
Join Date: Oct 2001
Location: Melbourne, Australia
Posts: 2,171
|
MEncoder dev-CVS-040228 = 28th Feb 2004, that would be your problem.
Looks like my 2004.02.26 build is actually 2004.02.28, so you grabbed the oldest, not newest. Last edited by celtic_druid; 11th January 2005 at 09:42. |
11th January 2005, 09:49 | #77 | Link | |
Registered User
Join Date: Dec 2003
Posts: 194
|
Quote:
|
|
11th January 2005, 10:04 | #78 | Link | ||
clueless n00b
Join Date: Oct 2001
Location: somewhere over the rainbow
Posts: 10,579
|
Quote:
Quote:
And if you read my comment about commandlines again, and really think!!! about it a bit, you'll see that there's a very basic problem when commandline and GUI parameters don't match. Feel free to add a reverse commandline -> GUI fields lookup when I release the sources next week-end. Perhaps then you'll realize what it is you're asking for. This really isn't a usability feature, it does just the reverse, make things more complicated.
__________________
For the web's most comprehensive collection of DVD backup guides go to www.doom9.org |
||
11th January 2005, 10:44 | #79 | Link | |
stupid
Join Date: Sep 2004
Location: Cologne
Posts: 638
|
Quote:
But I have one problem which is confusing me while testing myself and reading all the facts about x264: Why do I get blocks when using b-frames in 2 pass mode? ffdshow supports them => it´s not a problem of the player (player also has no problem with Ateme). I´m testing the AVI-file => it´s not a problem of mp4creator or avi2raw. Would be so nice to have b-frame support with MeGUI and x264.
__________________
cu Joe ------------------------ freedom is just another word for nothing left to loose |
|
11th January 2005, 10:56 | #80 | Link |
clueless n00b
Join Date: Oct 2001
Location: somewhere over the rainbow
Posts: 10,579
|
well, the blocks have nothing to do with the GUI, but with the codec. The problem is already known (see here: http://forum.doom9.org/showthread.ph...882#post592882). Once this issue is fixed in the core, you just have to download a new mencoder build that incorporates the new x264 core and you'll be all set. The GUI might also need to be changed over time if there are new core parameters (I understand weighed predition was just added to ffdshow so perhaps we'll see that as an option in x264 soon).
__________________
For the web's most comprehensive collection of DVD backup guides go to www.doom9.org |
|
|