I've never used dvdunatuthor and spuunmux, but dvdauthor and spumux are very good. This thread was created in dvdrhelp when baldrick did the first windows compile, you really should take a look:
http://www.dvdrhelp.com/forum/viewtopic.php?t=180017 There's a multiplataform GUI for dvdauthor called DVDStyler: http://dvdstyler.sourceforge.net/ I haven't tested yet, but it looks nice. :D |
Hi all,
sorry if I change back again to mencoding (BTW vmesquita, I took a look at dvdstyle screenshots and features, and looks nice. When I have this mencoder working the way I want, it will be a nice tool to test :) ). Just to post my last test. It was with last command/settings posted by bilu, this is: Quote:
-didn't use interlaced and NTSC settings (ildct, ilme, vstrict), neither il=i/d, nor hqdn3d -I used vmax_b_frames=2 Encoded twice the same sample, first with this settings (CBR), and second changed to CQ (vqcomp=1). But as I said in my previous post, I think is better for CQ-VBR to have a higher vbitrate (to keep Q low and as constant as possible, and bitrate changing freely. Opposite to CBR where bitrate tends to a low constant value, and Q changes freely between limits). So I set vrc_maxrate=5000 (with notch-matrix don't need else) and vbitrate=4000. Results: vqcomp=0:vbitrate=300:vrc_maxrate=9800 -------------------------------------------------------- file size: 43593 kB bitrate: max 5473 / avg 2114 Q value: max 8.29 / avg 3.10 bitrate viewer graphics: Q varies between 2-4 and in demanding scenes raises at 8. Bitrate tends to be kept low visual quality: in fast scenes appear some blocks; sometimes looks "blured"; washed colours vqcomp=1:vbitrate=4000:vrc_maxrate=5000 --------------------------------------------------------- file size: 44097 kB bitrate: max 5446 / avg 2139 Q value: max 4.20 / avg 2.39 bitrate viewer graphics: Q is kept between 2-3 and raised just once in a complex scene, with high bitrate visual quality: no blocks, no "bluring"; washed colors just in some scenes Don't know if washed colors are in my eyes, or in my mind, since for quality I just can add trellis (that is supposed to be related with quantization, don't think that has nothing to do with colors). Speed was the same (about 7 fps) for both settings. Nice results for both (I still prefer CQ), but this filesizes for 2% of film are a little big (trellis also lowers filesize, but at a encoding time cost). I'm still looking for a way to keep this quality and reduce filesize (scplx_mask maybe also helps, but you said bilu that little). Any suggestion appreciated (I think we're gwtting closer, and we're understanding better how this encoder works). :wink: |
Can you repeat the test on your stream without B-frames?
Bilu |
Some stuff for experiments
Hi,
as a long time linux mencoder user, I'd like to point you to some other interesting features of mencoder (which work well in cygwin too) I hope, at least some of you didn't know this already... 1) You can do an audio conversion pass like: Code:
mencoder -ovc frameno -oac lavc -lavcopts acodec=mp2:abitrate=224 -o frameno.avi FILENAME Code:
mencoder ...lots-of-options... -oac copy .... (instead of -nosound) the audio encoding pass (which is very fast indeed) gives you a prediction of the filesize and hints on the needed bitrate for certain filesizes like: Code:
Writing AVI index... This was meant for divx encoding but can be used for kvcd/kdvd too, I used the predicted value for two 700MB CDs to get a 1.4G KDVD Movie which hit the target very close. This value can be inserted as average bitrate (vbitrate=value), that is, if you don't use CQ (with vqscale=x) 2) it also has a builtin crop-detection, used like this: Code:
mencoder -vf cropdetect,scale=$WID:-3,expand=$WID:$HEI -nosound -ovc lavc "$FILE" -frames 50 You get something like that: Code:
crop area: X: 1..507 Y: 0..383 (-vf crop=506:384:2:0)V:0.000 [1100:223] automatically with (if you wrote the output to /tmp/f): Code:
CROP=`cat /tmp/f | grep vf | tail -n 1 | cut -d "=" -f 2 | tr -d ')'` You get the vf value which you can insert and use with scale and expand like so (CROP is the Variable above): Code:
mencoder ... -vf ... crop=$CROP,scale=$WID:-3,expand=$WID:$HEI ... You can build really nice scripts with this options... Also have a look at this thread: http://www.kvcd.net/forum/viewtopic.php?t=7771 You got me some ideas (haven't had time to test all mencoder filters myself ;) ) Happy mencoding, Neturmel |
bilu,
I already did, was my first test, encoding both tests without b-frames. File size was bigger for both, and I had the problem I described some posts before with PowerDVD: it doesn't play smoothly, it plays aprox 3/4 second and suddenly makes a little jump forward. This way it was very difficult for me to evaluate quality, but without b-frames is supposed to be better... but also for both tests (vqcomp=0 or =1) Now I wanted to encode directly from vob file, and try mencoder internal filters, instead of using avisynth and makeavis. How do I tell mencoder to encode several vobs files and output just 1 stream (sorry, too lazy to read man_page)? And in my first test mencoder hung: it gives a VDec error and says encoder is not compatible with output format. What am I supposed to do to make mencoder encode from a vob file (if any thing is to be done)?. Thanx bilu. |
@digitall.doc
This should work out of the box, vob files should be encoded without any problem. Maybe a bug in the/your win32 version ? Have you installed all mplayer codecs ? To do several vobs: Just pipe the file names to mencoder: Code:
cat *.vob | mencoder ...options.... -of encoded_file_name - Greetings, Neturmel |
neturmel, thanx for the support.
I'm using bilu compiled version, and is working for him. I suppose I have all mplayer codecs needed, since he encodes directly form vobs. Now that I remember, I encoded with previous versions directly from vobs. Maybe you're right, and I've got something missing. Quote:
|
@digitall.doc
"cat *.vob" would feed all VOB files in the current directory to output which is the input for mencoder via "|". If you just did a plain "cat *.vob" without the pipe and the following mencoder command, you would be presented with a nice ascii printout of all vob files in your command shell ( which is quite lengthy and unreadable ;) ) You can use all kinds of wildcard there e.g. "cat VTS_02_*. vob" which would feed all vobs of VTS_02. Hope this helps... Neturmel |
Now got it :wink: .
Still didn't test since I'm waiting bilu feedback, to see how he manages to encode from vob with his compile (the one I use). |
Quote:
Have you tried other players than PowerDVD? Quote:
Bilu |
Quote:
I get this everytime, but it works. This is because the first driver in the built-in codecs.conf is MPEG-2 PES and not libmpeg2. So the first one has to fail. Bilu |
@digitall.doc
Remade the test with a NTSC telecined source, using vmax_b_frames=2. One using vrc_maxrate=5000/vbitrate=1500 and the other using vrc_maxrate=9800/vbitrate=300 using vqcomp=0. Both sucked. Made the same test with vqcomp=1. Both sucked too. I'll continue to avoid B-frames. Will now test using your method but without B-frames. Bilu |
Without B-frames both look good. But using vbitrate=vrc_minrate worked much more VBR and yours much more CBR :?
My method: 6837 KB avg 3143/3.55 peak 4240/4.85 Your method: 6424 KB avg 2952/4.85 peak 3875/9.70 Both using vqcomp=1, the same as vrc_eq=tex. The one made with your method looked blurrier and in BV it looked much more CBR: from some point it started quantizing between 4.5 and 6.5 .The bitrate didn't get much lower than using my method, but it sure seems like it was trying. Maybe that's the Mencoder behaviour: when it thinks it can actually achieve that average bitrate it tries harder, while such a lower vbitrate ends up being ignored. My tests were made with interlaced samples, that was the main difference from yours. I'll make now the same tests over progressive PAL, but for NTSC I already have my conclusions :? Bilu |
Quote:
Don't know if I've got anything missing, but I was able with vmesquita compilation to encode from vob, and now I can't. Maybe I'll try and test again with previous version, to see if there's something wrong in my system... Quote:
I get the same messages you posted from mencoder, but then a windows message appear and crashes... |
|
Quote:
And now, as I was afraid, I don't really understand a single word... Quote:
But your results keep me astonished. They're just opposite to mine. I don't know if it's a question of vbitrate I stated before, or NTSC interlaced source, or is due to different sources (you vob internally filtered in mencoder, and I avisynth script), but I say again, just opposite. It's not just visual quality (it depends upon everybody's eyes and test, subjective 100%, at least for me), but bitrateviewer give opposite results. As I told you, in my tests avg and max Q were far big for vqcomp=0 (I prefer this to "my" vs "your" method, since "my" is already yours, and feels like a contest...), and made lots of spikes, varying a lot, while BR was more stable. And in my tests, vqcomp=1 gave a far steady Q curve, with low avg and max Q value, and oscillating bitrate... :roll: Again, don't know if is due to different source, or if you used vbitrate=1500 instead =4000, but they're too different. I would like to send you, or post here, the encoded tests and bitrateviewer screencaptures so you could see what I'm not able to explain to my poor english :oops: Even, from a theoretical point of view, and from man_page, vqcomp=0 means CBR and vqcomp=1 means CQ, taht is in line with my results, but opposite to yours. Don't know if I did anything wrong in my tests. Anyway, I'll redo my tests, since I want to understand how this encoder behave. |
Quote:
Don't take serious, just joking :lol: . I will give a try. Thanx |
I did your method with vbitrate=1500 and vrc_maxrate=5000.
Will now try with vbitrate=4000 and vrc_maxrate=5000. Bilu |
Again with B-frames, both sucked :roll:
Without B-frames, vbitrate=4000, vrc_maxrate=5000 vqcomp=0 ======= 6801 KB avg 3127/2.19 peak 4271/3.82 vqcomp=1 ======= 6806 KB avg 3129/2.17 peak 4271/3.48 The bitrate and quant curves look just.... equal :? Tests were again made with the same NTSC telecined source. I wouldn't want something that just works on progressive sources. Will now test vbitrate=vrc_minrate vs vbitrate=vrc_maxrate, seems they both provide good results ;) Bilu Bilu |
Without B-frames, same telecine source:
vq1-> vqcomp=1 vbmin -> vbitrate=vrc_minrate vq0-> vqcomp=0 vbmax -> vbitrate=vrc_maxrate minrate=300 maxrate=9800 vq1_vbmin ======= 6837 KB avg 3143/3.55 peak 4240/4.85 vq1_vbmax ======= 6843 KB avg 3146/2.15 peak 4281/3.10 vq0_vbmin ======= 6807 KB avg 3129/3.54 peak 4240/4.85 vq0_vbmax ======= 6843 KB avg 3146/2.15 peak 4281/3.10 The *_vbmin curves seem the same, and the *_vbmax curves also seem the same. The vqcomp parameter seems completely irrelevant. The vbmin curves are different from the vbmax ones. Bitrates don't change that much but quantizer are much higher in vbmin. I'll make other tests but I feel that vbitrate=vrc_maxrate will be my favorite from now on: little difference on the bitrate with much smaller quantizers :) Bilu |
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.