Log in

View Full Version : Avidemux (with emphasis on x264/h264 GUI)


Pages : 1 [2] 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36

LoRd_MuldeR
29th March 2006, 20:45
Is there a chance that the missing x264 options will be added in the next time or are we limited to what we have know? A complete x264 support with all important options would be very nice :)

I'm currently missing mixed_refs and frameref :(

celtic_druid
30th March 2006, 03:38
AVISynth support via proxy seems to be the current objective.

LoRd_MuldeR
30th March 2006, 21:59
AVISynth support via proxy seems to be the current objective.

And x264 dialog will not be completed? :scared:

celtic_druid
31st March 2006, 04:15
Well I didn't say that. You would really need to ask mean @ http://www.avidemux.org/pun/index.php

SadaraX
31st March 2006, 09:40
Damn, I need to check this forum more often. Sorry for all the late replies.

mkv isn't supported, although libavformat does support it, so I guess it might be added later. There is no IFO parsing.

Well, there might be some unseen IFO parsing in the subtitle tool, but nothing related to video. I think Mean has not seen a big port for including mkv input support. I would personally love to see it at least for input, and preferably for output (I prefer mkv over mp4). There are several problems I diagnosed with the AC3 audio, but nothing too major, just some weird/funny problems. They are schedule to be fixed before the next stable release, but that's a while away from now.

That vob index crash you found, did you contact Mean about it? Or report it somehow? I will gladly mention the problem to him, especially since you have a nice fix already. But if you already spoke to him about it, then I won't bother. Do mention if the problem does not get fixed eventually, Mean is a busy man and we all forget things.

Opening MPEG files seems to be fixed in new build :D
But is there a way to open MPEG/VOB files from read-only media?

There is no such feature yet, though you can submit a request for one. It probably would not be all that difficult to do. Theoretically, it can probably done with by tricking the .idx file with its filepath. But I'm not sure how it could be done. But its a valid request, submit it here if you want:

https://bugs.avidemux.org/

About all the x264 crashes and problems with not working (related to the windows builds or not)... the x264/h264 encoding is still being worked on. I am currently updating the GUI now, plus I am sure there will be more code work done underneath the GUI. Basically, the problems are being addressed, just be patient a little longer.... its coming soon. :)

Don't think it can handle decrypted VOB's so

I am checking up on this....


One question about the x264 options: Why is there only "target filsize" and not "traget bitrate" avaible for 2pass mode? Furthermore "target filesize" doesn't hit the correct size. I got a 13MB file instead of 10MB.

Yeah, the size issue has either been addressed or it will be. I have to test, but I remember reporting this problem a while ago. Though a target file size is sometimes off, but not usually more than 2%, 3MB is a bit much.

back to topic:
Two important options still missing are "mixed refs" and "number of ref frames"
And what about subq=7 and nr ???

I will see about getting those added.


why does you allow only "target filesize" with 2pass mode?


You know, I have no answer for that one. I would like to know myself. I will ask Mean when I get around to it. I know why the quantizer is disabled for Two Pass, but you should be able to enter an average bitrate I guess.


Can you explain me this: " same Qz as input"


Is that a valid option for x264/h264? I thought that was only available in XviD? I created a guide a while ago to explain those bitrate terms. Check here for an explanation.

http://openfacts.berlios.de/index-en.phtml?title=AvidemuxEncodeTypes1

I'm currently missing mixed_refs and frameref :(

I cannot guarantee the mixed_refs and frameref, but I am almost 100% they will be added.

Is there a chance that the missing x264 options will be added in the next time or are we limited to what we have know? A complete x264 support with all important options would be very nice :)
...
And x264 dialog will not be completed?


As far as an update to the missing options, I would expect it soon. I am trying to get the x264/h264 GUI options finished before other projects are really tackled. I cannot write much backend-core code, but I can help with GUI's and user input a little. :)

guada 2
31st March 2006, 16:06
:thanks: SadaraX .

Bye :)

SadaraX
1st April 2006, 06:08
Alright, I am doing some updating on the GUI, and I have some questions.

1) Is the valid quantizer range 0-51? I just want to confirm.
2) Should Kf Min (Keyframe Minimum) and Kf Max (Keyframe Maximum) be added as options? There were there orginally, but they are not there anymore.
3) Max IDR frame interval : 300, I am inclined to set the default to 300, instead of 250. Any objections?
4) What's the valid range on Deblocking filter's strength and threshold?
5) Should I try to add "Threads" to the "Sample A/R" section?

Another issue I am working on is the problem of the GUI layout. I am stuck between having the GUI look exactly the same as the windows codec configure window, and making it look more consistant with the Avidemux windows. The change is VERY slight, but still.

Here's what it looks like currently, without any more options planned for. (though tell me if I am missing something). Most of what you see is the what will be default, except for the Encoding Mode Type, Partition decision, Partition Method, and Direct Mode, these I am not sure what (if anything) should be default. I cannot guarantee the "Load Defaults", "Save Defaults", and the "Reset Defaults" will be there as Mean might remove them (not sure).

http://i32.photobucket.com/albums/d47/sadarax/Avidemux/x264-1.png
http://i32.photobucket.com/albums/d47/sadarax/Avidemux/x264-2.png
http://i32.photobucket.com/albums/d47/sadarax/Avidemux/x264-3.png
http://i32.photobucket.com/albums/d47/sadarax/Avidemux/x264-4.png

Things left to do, though not are are my responcibility:

* Get the labels and options to enable/disable on properly according to selection
* Add mouse-over tooltips
* Any extra options left


You can look screen grabs from the VFM version of the x264 encoder window.
http://www.free-codecs.com/screenshots/x264_Video_Codec_screenshots.htm

How does anyone feel about having the following added to the x264 GUI (we don't necessarily have to)? I am not so sure about these, since they are not included in the windows version.


* Fast P-Skip
* Custom quantization matrices
* Buffer control
* Zones

celtic_druid
1st April 2006, 07:22
The VfW GUI isn't the best place to look really since it is lacking in options.

mencoder: http://www1.mplayerhq.hu/cgi-bin/cvsweb.cgi/~checkout~main/libmpcodecs/ve_x264.c?rev=1.49&content-type=text/plain
is probably better or the cli encoder or MeGUI.

SadaraX
1st April 2006, 07:28
The VfW GUI isn't the best place to look really since it is lacking in options.

mencoder: http://www1.mplayerhq.hu/cgi-bin/cvsweb.cgi/~checkout~main/libmpcodecs/ve_x264.c?rev=1.49&content-type=text/plain
is probably better or the cli encoder or MeGUI.

That may be true, but I was given the current x264 gui from within Avidemux, and so I simply continued to work with it. This thread is also here to help add any options that are missing which people want. I don't think Mean really want to write in all the options (at least right away anyhow). :)

LoRd_MuldeR
1st April 2006, 13:04
"Max ref frames" and "Mixed refs" added, nice :)

What I can't see from the screenshots, are the values for "Partition decision"
Is "6b (RDO on B-Frames)" still the maximum, or did you add the new "7" setting?

Furthermore it would be nice, if you could also add the "Noise Reduction" setting to the GUI. Okay, we already have some "Noise Reduction" filters in AViDemux, but giving the user access to x264's Noise Reduction can't be wrong...

:thanks:

LoRd_MuldeR
1st April 2006, 13:25
I just made an encode with "Partition decision" set to "6b (RDO on B-Frames)". But what I got is this:

x264 - core 45 svn-483 - H.264/MPEG-4 AVC codec - Copyleft 2005 - http://www.videolan.org/x264.html - options: cabac=1 ref=1 deblock=1:0:0 analyse=0x3:0x133 me=umh subme=6 brdo=0 mixed_ref=0 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 chroma_qp_offset=0 slices=1 nr=0 bframes=3 b_pyramid=1 b_adapt=1 b_bias=0 direct=2 wpredb=1 bime=1 keyint=250 keyint_min=25 scenecut=40 rc=2pass bitrate=55924 ratetol=1,0 rceq='blurCplx^(1-qComp)' qcomp=0,60 qpmin=10 qpmax=51 qpstep=4 cplxblur=20,0 qblur=0,5 ip_ratio=1,40 pb_ratio=1,30

Seems like brdo is not set to 1, like it should...

SadaraX
1st April 2006, 22:27
"Max ref frames" and "Mixed refs" added, nice :)

What I can't see from the screenshots, are the values for "Partition decision"
Is "6b (RDO on B-Frames)" still the maximum, or did you add the new "7" setting?

Well, I cannot seem to get a screen shot of the menu, so I will tell you what's there:


1 - Very low (Fastest)
2 - Low
3 - Medium
4 - High
5 - Very High (High quality)
6a - Ultra High (RDO)
6b - (RDO on Bframes)



Furthermore it would be nice, if you could also add the "Noise Reduction" setting to the GUI. Okay, we already have some "Noise Reduction" filters in AViDemux, but giving the user access to x264's Noise Reduction can't be wrong...

:thanks:

Ok, I will throw noise reduction in there soon.

SadaraX
1st April 2006, 22:31
I just made an encode with "Partition decision" set to "6b (RDO on B-Frames)". But what I got is this:

x264 - core 45 svn-483 - H.264/MPEG-4 AVC codec - Copyleft 2005 - http://www.videolan.org/x264.html - options: cabac=1 ref=1 deblock=1:0:0 analyse=0x3:0x133 me=umh subme=6 brdo=0 mixed_ref=0 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 chroma_qp_offset=0 slices=1 nr=0 bframes=3 b_pyramid=1 b_adapt=1 b_bias=0 direct=2 wpredb=1 bime=1 keyint=250 keyint_min=25 scenecut=40 rc=2pass bitrate=55924 ratetol=1,0 rceq='blurCplx^(1-qComp)' qcomp=0,60 qpmin=10 qpmax=51 qpstep=4 cplxblur=20,0 qblur=0,5 ip_ratio=1,40 pb_ratio=1,30

Seems like brdo is not set to 1, like it should...

Well, x264 is at svn rev 487, if that's anything. I'm a little confused by your post with relevance to the Avidemux codec GUI. None of the changes I have made are even updated so....

LoRd_MuldeR
2nd April 2006, 12:15
Well, x264 is at svn rev 487, if that's anything. I'm a little confused by your post with relevance to the Avidemux codec GUI. None of the changes I have made are even updated so....

Okay, I'll try to make it more clear:

Partition decision at level 6 means "subme=6" and "brdo=0". That already works in the AviDemux GUI. But level 6b means "subme=6" plus "brdo=1". So the difference is the "brdo" setting. And that is what does not work! When I select 6b in AviDemux I still get "brdo=0". So there's currently no difference between 6 and 6b in AviDemux. I think this should be fixed ASAP.

Furthermore ther's a new level, level 7. AFAIK level 7 means "subme=7" and "brdo=1". Maybe you could add this as well...

:D

SadaraX
2nd April 2006, 12:43
Okay, I'll try to make it more clear:

Partition decision at level 6 means "subme=6" and "brdo=0". That already works in the AviDemux GUI. But level 6b means "subme=6" plus "brdo=1". So the difference is the "brdo" setting. And that is what does not work! When I select 6b in AviDemux I still get "brdo=0". So there's currently no difference between 6 and 6b in AviDemux. I think this should be fixed ASAP.

Furthermore ther's a new level, level 7. AFAIK level 7 means "subme=7" and "brdo=1". Maybe you could add this as well...

:D

Thanks for the information, the new level has been added. Level 5 is still the default label, and I plan to leave it that way unless someone else thinks it should be otherwise (feel free to post). I have adopted these labels, just to help:

1 - Extremely Low (Fastest)
2 - Very Low
3 - Low
4 - Medium
5 - High
6 - Very High
6B - Very High (RDO on Bframes)
7B - Ultra High (RDO on Bframes)

LoRd_MuldeR
2nd April 2006, 12:53
:thanks:

When will the new stuff be ready :confused:


BTW: Think it's called just "7" not "7b", but I might be wrong...

SadaraX
2nd April 2006, 13:11
:thanks:

When will the new stuff be ready :confused:


BTW: Think it's called just "7" not "7b", but I might be wrong...

I left the 'B" on there because it would affect the Bframes. Unless there is a 7 without RDO on BFrames, in which case I might have to add a 7 without a B.

As far as the date, well, I don't know. I still have to read more doc's on the codec and finish the glade files, then start writing the code underneath to make it behave properly. So, I guess I no date yet. I am shooting for two weeks or less, but don't quote me...

LoRd_MuldeR
2nd April 2006, 13:15
I left the 'B" on there because it would affect the Bframes. Unless there is a 7 without RDO on BFrames, in which case I might have to add a 7 without a B.

As far as the date, well, I don't know. I still have to read more doc's on the codec and finish the glade files, then start writing the code underneath to make it behave properly. So, I guess I no date yet. I am shooting for two weeks or less, but don't quote me...

Okay. I'm looking forward. Thanks for your efforts !!!

Sharktooth
2nd April 2006, 13:16
subme and brdo are 2 separate things...
AFAIK subme7 does not imply brdo, you should still manually enable it.

LoRd_MuldeR
2nd April 2006, 13:18
subme and brdo are 2 separate things...
AFAIK subme7 does not imply brdo, you should still manually enable it.

But brdo=1 requires subme=6 or higher, correct?

Sharktooth
2nd April 2006, 13:20
yes, brdo requires RDO modes (6 and 7).

LoRd_MuldeR
2nd April 2006, 13:23
yes, brdo requires RDO modes (6 and 7).

Then I think it's the best to make subme/brdo one setting in the GUI:

1 - Extremely Low (Fastest)
2 - Very Low
3 - Low
4 - Medium
5 - High
6 - Very High
6B - Very High (RDO on Bframes)
7 - Ultra High
7B - Ultra High (RDO on Bframes)

bond
2nd April 2006, 13:31
i think brdo and subme should be seperated options, but brdo should be greyed out when subme <6 is used

LoRd_MuldeR
2nd April 2006, 13:36
i think brdo and subme should be seperated options, but brdo should be greyed out when subme <6 is used

Good idea, but possible with GTK+ ???

bond
2nd April 2006, 13:47
no idea, but i would be surprised if its not possible to grey out options

LoRd_MuldeR
10th April 2006, 15:04
I just checked out the new build (2.2.0 rev1868)

1. MP4 output still broken (just crashes without warning)
2. x264 options not improved any further, seems like SadaraX has not commited anything new yet.
3. "Display filtered output in the main window" options does not have any effect :(


I hope they keep up good work and fix those bugs soon, because I really want to use that tool !!!


//EDIT

Does any body know, what version of TDeint is built-in with AviDemux?
Is it up-to-date and recommended to use ???

mean
10th April 2006, 16:26
Could you detail what you do to make the mp4 output crash ?
AFAIK, it is flaky but works for basic stuff

The rdo/bframe is active for odd level>6 (7/9/11)

Tdeint is ~ 6 month old, but the good news is that you can open avs file
using avsproxy (on both linux & windows, 32 bits & 64 bits)

LoRd_MuldeR
10th April 2006, 17:14
Could you detail what you do to make the mp4 output crash ?
AFAIK, it is flaky but works for basic stuff

1. Open Source (e.g. some MPEG-2 capture)
2. Make a selection
3. Choose encoders (x264 + LameMP3)
4. Choose MP4 output
5. Save File

-> AviDemux just disappears, no error message, nothing

The rdo/bframe is active for odd level>6 (7/9/11)

In my build (rev1868) the maximum level to select is "6b (RDO on b-frames)", but it still does *not* enable brdo! Make an AVI and check it in the Hex-Editor: "brdo=0". Furthermore "mixed_refs" and "nr" is missing. SadaraX was going to add this, but it seems it's not done yet...

Tdeint is ~ 6 month old

Is it possible to include the latest version?
Since it's already built-in, it basically requires to copy over the latest sources, eh?
Or are there a lot modifications neccessary? :confused:

but the good news is that you can open avs file using avsproxy (on both linux & windows, 32 bits & 64 bits)

That is exactly what I don't want to do :(

mean
10th April 2006, 18:26
and x264+aac ?

LoRd_MuldeR
10th April 2006, 18:30
and x264+aac ?

hmm, it encodes. But the resulting MP4 is crap.
In MPC I get only noise instead of sound and in MPlayer/VLC even video is borked...

mean
10th April 2006, 19:03
I just tried on linux
Mplayer does not play it but the official mplayer has a too old lavcodec version
Vlc plays it fine
avidemux plays it fine

Maybe a windows specific bug, i'll look

celtic_druid
10th April 2006, 19:25
Hmmm, could be something I did. Only problem I could detect though was that with mplayer it looked like crap when first playing, presumably until the first IDR frame. No problem with ffdshow. No problem with mplayer for avi output either.

I'll have more of a look tomorrow.

LoRd_MuldeR
10th April 2006, 23:40
found another problem:

rev1868 doesn't index MPEG files. It just freezes.
With old .idx files from rev1844 it works...

SadaraX
11th April 2006, 02:34
found another problem:

rev1868 doesn't index MPEG files. It just freezes.
With old .idx files from rev1844 it works...

You're right, it does crash the program and fail to index the mpeg's.

SadaraX
11th April 2006, 02:51
i think brdo and subme should be seperated options, but brdo should be greyed out when subme <6 is used

Mean has set the encoder to enable RDO if level >= 6, so I am not going to contradict him by adding a seperate option. If people really want this, then post to this thread and maybe Mean will let me change it.

killerhex
11th April 2006, 05:50
does this program have mkv support i cant open any of my mkvs with this any files i need

SadaraX
11th April 2006, 06:38
does this program have mkv support i cant open any of my mkvs with this any files i need

Sorry KillerHex, Avidemux does not (yet) support mkv. There has been no discussion of when it will be added, though it has been asked for already. I do not know what Mean's plans are, but I am pretty sure he wants to finish the mp4 integration and probably tackle a few of the bug reports that have built up, and also finish the x264 update, and possibly the XviD codec update. I do not know how long any of that will take, and though it looks like a lot, I have seen Mean whip out code like a mad-man and add features surprisingly quickly, so it may not be as long as you think. If I have anything to say about it (which is not much), I hope to have mkv support added eventually.

I am reluctantly (personally) to add yet another feature request onto the tracker until I have actually finished the stuff I have said I will help on. Of course, that does not stop anyone else from adding a request for mkv input/output support. I would personally like to use that container over mp4... (especially because it supports vorbis and flac, two things I use a lot).

LoRd_MuldeR
11th April 2006, 11:53
Mean has set the encoder to enable RDO if level >= 6, so I am not going to contradict him by adding a seperate option. If people really want this, then post to this thread and maybe Mean will let me change it.

But it doesn not work, at least for rev1868 :(
Make an AVI, load it into Hex-Editor and check it out yourself:
You'll see "brdo=0", even when you selected "Level 6b"...

celtic_druid
11th April 2006, 12:27
Should be fixed now I think. I'll put a new build up later.

LoRd_MuldeR
11th April 2006, 12:29
Should be fixed now I think. I'll put a new build up later.

:thanks:

LoRd_MuldeR
12th April 2006, 18:02
Jupp, MPEG indexing and the "brdo=0" bug are fixed now :)

Nevertheless I won't use AviDemux for x264 encoding until I can set "ref" to a value higher than only 1 and "mixed_refs" is aviable...

Kostarum Rex Persia
12th April 2006, 23:50
Nevertheless I won't use AviDemux for x264 encoding until I can set "ref" to a value higher than only 1 and "mixed_refs" is aviable...

Yeah, me too?

SadaraX
13th April 2006, 00:33
Nevertheless I won't use AviDemux for x264 encoding until I can set "ref" to a value higher than only 1 and "mixed_refs" is aviable...

Yeah, me too?

Well, this is the important stuff you should definately be posting about. To respond, "Mixed Ref's" is going to be available very soon, but what do you mean by set the "ref" to a higher value? Is this refering to the Max. Ref. Frames (which is also going to be available).

This is more or less what the window looks like, plus a few more default settings and a spinwheel change for the range.

http://i32.photobucket.com/albums/d47/sadarax/Avidemux/x264-2.png

Tell me what you are refering to specifically, and I will try to get it added.

LoRd_MuldeR
13th April 2006, 00:58
Very good news SadaraX :cool:

"Mixed Refs" and "Max. Ref. Frames" is exactly what we need.
But it's not in the current build yet.

Your screenshots look promising. Hope your work is in the build soon !!!
And I hope we will have "Bitrate" and not only "Target Filesize" for 2-Pass mode ^^

SadaraX
13th April 2006, 01:09
And I hope we will have "Bitrate" and not only "Target Filesize" for 2-Pass mode ^^

I want this option too so I will ask Mean if we can get both.

LoRd_MuldeR
13th April 2006, 01:19
I want this option too so I will ask Mean if we can get both.

"Target Filesize" is a nice additional feature, but "Target Bitrate" is essential!

Kostarum Rex Persia
13th April 2006, 02:59
Not to forget --subme 7 and Trellis 2(Trellis always ON), together with RDO for B-Frames.

SadaraX, for all x264 option, please look into MeGUI, and try to implement all options.

Thanks.

SadaraX
13th April 2006, 06:00
Not to forget --subme 7 and Trellis 2(Trellis always ON), together with RDO for B-Frames.

SadaraX, for all x264 option, please look into MeGUI, and try to implement all options.

Thanks.

I will check out the meGUI, ASAP. As for the level 7, this currently what is in the Partition decision list (I will post full screen shots in a day or so):

1 - Extremely Low (Fastest)
2 - Very Low
3 - Low
4 - Medium
5 - High
6 - Very High
6B - Very High (RDO on Bframes)
7 - Ultra High
7B - Ultra High (RDO on Bframes)

I am not sure whether I should add brdo as a seperate option or not not. Would this do for everyone or do we really need to make a seperate option?

Kostarum Rex Persia
13th April 2006, 09:44
I am not sure whether I should add brdo as a seperate option or not not. Would this do for everyone or do we really need to make a seperate option?

No, no need for separate option, just implement 6B - Very High (RDO on Bframes) and 7B - Ultra High (RDO on Bframes)

And, very important x264 option is Direct Auto(automatic decision on 2 pass, between Spatial or Temporal, useful only in two-pass mode)

easyfab
13th April 2006, 18:46
thanks for this tool, it's a very useful all-in-one encoder.

Some nice options like delogo, colors modification...

I just miss 2 filters that i use with avisynth : TomsMoComp and limitedsharpen. But the filters you have are good too.