QuEnc 0.55 [Alpha]

[Nic]

Hi,

http://nic.dnsalias.com/QuEnc.zip
(Sourcecode: http://nic.dnsalias.com/QuEnc_src.zip )

So busy, so thought i'd release a quick update. This version is pretty much a test version as I haven't had time for any testing. When finalized and a few more things added it will become v0.60.

Changes:

Now can select TFF or BFF
Now can select a custom matrix (using XviD style matrix files)
Added alternate scan to interlace encoding option
AviSynth Exception handling (if there was a problem in the AVS File, a MessageBox will popup with the error)
Better stability (with luck ;) Should never crash on exit or with AviSource, etc etc)
No longer uses DLLs, links directly, as DLLs are rarely compatible between versions and only cause problems (IMHO)
Updated to latest CVS
Minor speed up code


Let me know how you get on,
-Nic

ps
I plan to add a few more bits and pieces before 0.60 (some of the things straight from NuEnc :) ). But want to check stability with you guys first.

[Paced]

Thanks for the update Nic, I'll try it out as soon as I get the chance.

[Peter Cheat]

Custom matrix was definately a necessary feature. Field ordering selection was also a common request. Good job.

btw,
How did you fix the crash on exit? I just couldn't figure it out.

[Nic]

Hi Peter,

Thanks. :) To fix the crash (and have AVS Exceptions), just use AVSReader.h and AVSReader.cpp from the latest QuEnc source. Was to do with closing down the AVI stuff properly. (Strangely)

@Peter & everyone:
What other features are needed/asked for/wanted?

-Nic

[Peter Cheat]

Some requests that have come up are:

-audio encoding (mp2 would be easy to implement)
-encoding preview (why? I don't know)
-muxing
-shutdown when done option (not necessary, can use external app)


There were probably others, I can't remember them now.

[Nic]

Audio encoding -
Well libavcodec's is probably the poorest quality MP2 Encoding because there's no psychoacoustic model. Perhaps we can add another library for doing that.

Encoding Preview -
Yup that is a waste of time ;) lol, but maybe it could be useful. We'd have to encode the frame then decode it then output it to a window. Might be fun....Hmmm might add that, what do others reckon (generally it would just slow down the encode)

Muxing-
We could add another dialog in there that just uses the mplex code. Could be useful I suppose

Shutdown-
I think my version has already got that.

One thing that would be good I suppose is to write a proper Program Stream with Audio and Video taken from the AVS and encoding as MP2 and MPEG-2. Another thing to look at I suppose.

What would you guys all vote for?

Cheers,
-Nic

[Peter Cheat]

I vote for mp2 encoding via toolame and mp3 encoding via lame :D
Throw in AC3 while were at it. I could implement it if I knew where I can find information on AviSynth and how to take the audio data out.

Muxing would also be useful (using latest version of mplex). Commandline is too hard for some people.

BTW, I tested QuEnc 0.55 Alpha. It seems to be slower than previous versions, but results was still very good as expected (tested on Bourne Supremacy trailer).

[Teegedeck]

Originally posted by Nic
One thing that would be good I suppose is to write a proper Program Stream with Audio and Video taken from the AVS and encoding as MP2 and MPEG-2. Another thing to look at I suppose.
That would be fantastic and just what I'd need to easily reencode some stuff and leave it at my parents' home in order to watch it on a DVD player during some of the longer and more boring visits...

Thanks for the new version, Nic!

[dragongodz]

select a custom matrix (using XviD style matrix files) - works

Shutdown-
I think my version has already got that.
it has and it works (windows xp SP1).

where do you come up with these great ideas ? :cool:

mp2 encoding via toolame
already mentioned to Nic a loooong time ago. he does need reminding some times now he's getting older though. :D

mp3 encoding via lame
completely undesirable and dangerous. newbies are meant to be able to safly use this too.

also -
AviSource - 2 pass works
2 pass - 1 or 2 frames works.

now a bug -
VBR time length wrong, even effected by bitrate.
example - 40 second clip. encode VBR(mpeg 1 or 2) at 3000 on playback said 15seconds but did keep playing past that. at 2000 playback length reported as 9 seconds. tested with MediaPlayerClassic internal mpeg decoding and windvd.
CBR however did not suffer the same problem.

[freelock7]

Thanks Nic to add the matrix option. It's very useful when working at low bitrate.
Works fine.

[Peter Cheat]

The time is reported correctly with the tests I've done.

Tested using Windows Media Player 6.4 and Windows Media Player 9.0 using Elecard MPEG2 decoder (also reported correctly by FFDShow, but the decoding in that is fubar atm).

Maybe it is a decoder fault dragongodz?

Why is MP3 encoding undersirable? It's available in TMPEnc, and TMPEnc can't even mux it properly! You could easily create a message saying that "using MP3 audio is a bad idea so don't do it unless you know what you are doing". A lot of new DVD players can play it, so why not throw it in?

[lithoc]

@Peter
I've tried your mplex2, my DVD player can't playback. It only output garbage audio signal but the video is fine.
I think mp3 is optional, it is not a DVD-Video standard.

But if you must, I think noob user need to be warn.

Cheers,

[Mug Funky]

woo-hoo! thanks for the alternate scan, and field order, nic.

i'm off to see how this performs on PAL fieldblends :devil: i'm thinking it'll be a CCE killer by now.

[Peter Cheat]

Not all new players can play it. But the chances are pretty good if your DVD player plays MP3 CDs. It is out-of-standard after all. Brand-name DVD players may not support it because they like to disallow cool undocumented features (friends Sony DVD player spits my discs out). In Australia, If you've got a newish cheapo ATD or Audiosonic DVD player, the ones I've tested work :D

You sometimes get garbage audio if you are trying to play 48kHz mp3 audio when a player only supports 44.1kHz. I've noticed this on one particular player (cheap import, brand was GP or something).

Back on topic. I think that it is a good idea. AC3 encoding would also be good. I've sort of tried to do it, but I suck when it comes to VFW. I can't find the documentation I need.

[RobertR]

First of all thanks for your efforts Nic (even if i'm screwed and can't use QuEnc under Linux :)))

What i would like to see in QuEnc is ability of creating GOPs on given frame. I know that Peter has it on ToDo list but i'd rather have him working on ratecontrol ;)

[lithoc]

Originally posted by Peter Cheat
You sometimes get garbage audio if you are trying to play 48kHz mp3 audio when a player only supports 44.1kHz. I've noticed this on one particular player (cheap import, brand was GP or something).



HHmmm... may b i should give a second try on 44.1khz cos last time when I try it, was 48khz sampling.

Now that what I called non-standard :) cos according to mp3 standard, 48khz is always there.
May be is because it is (s)vcd that doesn't support 48khz.
but i try svcd (mpeg2 + 48khz mp2) is ok.
I never play a normal 48khz mp3 only disc in my dvd player tho.

Anyway thanks for your oppinion.

[dragongodz]

Maybe it is a decoder fault dragongodz?
maybe but its strange that both MPC's internal decoder and windvd both suffer from it. i will have to try some others when i get time.

Why is MP3 encoding undersirable? It's available in TMPEnc, and TMPEnc can't even mux it properly! You could easily create a message saying that "using MP3 audio is a bad idea so don't do it unless you know what you are doing". A lot of new DVD players can play it, so why not throw it in?
yes Tmpgenc can do it, by use of an external encoder. are there any other encoders that you know of that can ?
as for why not throw it in -
.its not any sort of standard(or remotly close).
.some players may play it but is that even close to a majority ? i doubt it.
.its just a really bad idea. :D

[damian_dimitri]

hello,

thank you for all the time you put in this great tool.
I was looking at the new option; Xvid style matrix files. So i ran to the Xvid thread. I found these ones;
http://forum.doom9.org/showthread.php?s=&threadid=83125
Can i use these?
It does have an other extension then *.txt.

thank you in advance.

Damian

[Paced]

Originally posted by damian_dimitri
hello,

thank you for all the time you put in this great tool.
I was looking at the new option; Xvid style matrix files. So i ran to the Xvid thread. I found these ones;
http://forum.doom9.org/showthread.php?s=&threadid=83125
Can i use these?
It does have an other extension then *.txt.

thank you in advance.

Damian

Yes you can (as long as it was created, and saved, within XviD's configuration screen), just make the 'Files of Type' = 'All Files' when selecting a matrix. Or, you could always just rename the extension to .txt.

[Nic]

is .xcm a common extension for that style of Matrix file? If so i'll add it.

If anybody want's another type to be supported post links to examples and i'll add them.

(Also I've never checked that the matrices are being used properly, they should be, but they might not be, so if someone can confirm it then please let me know :) )

Cheers,
-Nic

[damian_dimitri]

Hello,

ty both for the fast reply.
I am new to all this matrix stuff, but i want it to give a go with dvd-rebuilder. So i honestly can't answer if *.xcm is the normal extension.

btw.. trying Quenc at the moment with dvd2svcd..not sure if it accept the matrix, but it does encode :)

till soon

Damian

[Teegedeck]

Well, I guess the best proof we can hope for is different filesizes and different quality when using the same constant... which reminds me: Why isn't there a constant quantizer mode? :)

[Nic]

@Tee: Good question, I'm still not sure if it will behave when restricted to one quant. I'll try it....should be just a case of setting min quant and max quant to the same value.

-Nic

[damian_dimitri]

hi

i tried to rename the *xcm file to *.txt. But when i opened it, as *.txt, i don't see anything readable. So i am not sure if it just can be renamed.


Damian

[Nic]

It can be renamed, the examples I had were in *.txt format. (available here: http://nic.dnsalias.com/XviD_Quant_Matrices.zip )
Renaming them will only make it easier for you to find them by browsing in QuEnc, that's the only difference.

You won't find anything readable. it's a 128 byte file with each byte representing one of the numbers of the two matrices.

-Nic

[dragongodz]

Also I've never checked that the matrices are being used properly, they should be, but they might not be, so if someone can confirm it then please let me know
i already did. bitrate distribution changes with different matrices so yes i would say it is working.

is .xcm a common extension for that style of Matrix file?
the ones that come with Koepis build/installer(in zip) are all .txt. however the .xcm probably came from using this matrix ed by Ligh since thats the extention it uses.
http://forum.doom9.org/showthread.php?s=&threadid=73666

Why isn't there a constant quantizer mode?
Good question
Mug Funky already asked about this before. you do still have the list dont you Nic ? :)

update on the playback time problem.
moonlight mpeg splitter with MPC decoder played by MPC(of course)= bad
moonlight mpeg splitter with intervideo decoder played by MPC = bad
windvd 6 = bad

mainconcept mpeg splitter with MPC decoder played by MPC(of course)= good
mainconcept mpeg splitter with intervideo decoder played by MPC= good

also windvd 6 had the same problem playing back a MainConcept elementry stream so i will have to get the latest version and see if thats been fixed.

[Nic]

@dgz: Yup, you give me all the good ideas, I pretty much instantly forget them. My memory is cr*p, but least we're working as a team ;) Testing constant quant now (at least for first pass (Q=2), seeing if it helps)). Getting my faster computer soon....spent a little too much money, I should start taking donations lol! ;)

I think the problem is in mpeg.c, there have been a number of wacky little changes. Look at emails by Chris and Paul Curtis on the ffmpeg mailing list...I think they've mentioned something similar.

Cheers,
-Nic

[Peter Cheat]

I can confirm that the matrices are exactly as they should be (checked with ReStream). Values correspond to the values I put in so its all ok there. Is the time problem really an issue. It will go away when you mux the file, presumably it will be muxed at some stage (you need audio :D).

[Nic]

The problem won't necessarily go away. GOP Timings could be completely wrong or something else that could make very picky players fail. I admit it shouldn't be too much of an issue, but it's one i'd like to correct (or to be corrected ;) )

-Nic

ps
Thanks for the confirmations :)

[dragongodz]

Is the time problem really an issue. It will go away when you mux the file, presumably it will be muxed at some stage (you need audio
well i already said under what conditions it happens. so seems to be a software(splitter) problem not limited to QuEnc. i havent tested it on hardware.
uhh actually you dont HAVE to have audio at all. its just that in 99.99% of cases you will. :D

Getting my faster computer soon.
so what are you getting exactly ?

Yup, you give me all the good ideas, I pretty much instantly forget them. My memory is cr*p, but least we're working as a team
yes i can forget them aswell which is why i made that list. :)

[Nic]

so what are you getting exactly ?
Yeah, that didn't make sense did it? ;) I meant i'm doing testing now and it's taking forever...grr. Testing on my new rig will be more of a joy...

-Nic

[Peter Cheat]

dragongodz - try to mux the file and see if the time is ok.

[dragongodz]

downloaded latest windvd 6. uninstalled old and installed new. problem still there.

muxxed with audio to vob with Rejig, playback in windvd fixed
muxxed with audio to mpg program stream with bbmpeg, playback in windvd fixed
Tmpgenc crashed when attempting to run. guess its not happy i havent rebooted after installing windvd.

muxxed with audio to vob with Rejig, playback in MPC with moonlight splitter/demuxer set to FPS = bad
muxxed with audio to vob with Rejig, playback in MPC with moonlight splitter/demuxer set to PTS = ok (actually it said it was 1 second short but hey thats a huge improvement)
same results for bbmpeg muxxed files.

[Nic]

Minor Update (for next release):
1) Tried using Overlapped writing for a performance improvement, it wasn't noticeable so I won't bother adding it.
2) Const Quant has been added and will be in the next version. At present if the bitrate is set to 31 or less then it becomes Const Quant mode. (you'll see what I mean)
3) First pass of a 2 pass encode will be done in constant Quant (Q=2)
4) Added .xcm to the matrix browse dialog

5) I'm completely rewriting the way I output files so it outputs them using libavformat (even if it's just a raw M2V stream). This will allow reading video and audio from an AVS file and then outputting them directly to a DVD style Program Stream. Cool huh? (pretty much already working) (to begin with, will use libavcodec for mp2 encoding, will use tooLame later)

Will be out next week,

-Nic

[damian_dimitri]

wow,

hardly can wait.....

damian

[Peter Cheat]

The first pass in Quant 2 is a very good idea. Definately produces better results.

Muxing solves the time problem by the look of things. Can you make it mux to a System Stream too? Actually, that'll probably be a bit much.

[guada]

Thank you Nic, it's some beautiful work.
It's for when, the next optimization,
no it was just a joke :p ;)

Bye ;) ;)

[Teegedeck]

I am looking so forward to the next version! :) :)

[guada]

I can make you Teegedeck confidence.
I remember again of my first post in the Xvid category :)

Bye ;)

[Koepi]

I like the new version, I think the output looks better. And it hits target size more accurately.

Unfortunately it made my computer lock 2 times on the same file, dunno if it was in the same position both times (20% 2nd pass).

So I look forward to the next version with Q2-1st pass, audio encoding and muxing ;-)

Btw., xvid's 2pass2/2pass1 are so modular, maybe you can use some of that code to improve ffmpeg's 2pass code?

Regards
Koepi

[Peter Cheat]

I already tried using XviDs 2-pass code with ffmpeg. Couldn't get the damn thing to work. Its a waste of time trying, believe me.

[Koepi]

Nah, don't forget what kind of genius Nic is. He's probably already added that while we are typing :cool:

I think Nic was involved at least reading-wise) when we were designing the 2pass stuff, so there's a good chance he understands the admittedly not-so-simple code well enough to properly interface it with libavcodec. Just a guess though.

Regards
Koepi

[Peter Cheat]

I know Nic is a genius :D

But it isn't a simple exchange. Masking is also handled by rate control in ffmpeg, as well as a few extra things. XviD source is much easier to understand than ffmpeg source, let me tell you. Not much is explained so you have to work it out line by line. The rate control in ffmpeg is not too bad, the way bitrate overflow and underflow could do with improvement along with fixing some mpeg 1&2 specific issues, but apart from that its not too bad.

[dragongodz]

xvid's 2pass2/2pass1 are so modular, maybe you can use some of that code to improve ffmpeg's 2pass code?
yes i mentioned looking at that a long time ago. especially the work done with the 1.1 branch for rate control.
actually 1 program that does try and use xvid rate control with avcodec is avidemux, http://fixounet.free.fr/avidemux/ . when you select video "dvd(lavcodec)" and go to its settings it has a checkbox for using xvid.

[Peter Cheat]

Have you tried it? :)

The results are, well, a little disappointing. Its output seems worse than when using ffmpeg's rate control.

[fabrice]

Hi,

I'm trying to use an external matrix in quenc, and every encode I do uses the standard matrix (that's at least what Restream says me). Only if I check QLB matrix, Restream indicate me a non-standard matrix.
What am I doing wrong?
My settings are:
- MPEG2
- bitrate 2078
- Use VBR
- High Quality
- Gop size 12
- 16:9 aspect ratio
- 8 DC precision
- 5000 max bitrate
- custom matrix: bach1.txt (a xcm renamed file).

What is wrong?

Thanks,
Fabrice

[mean]

A quick note about using the use of xvid ratecontrol in avidemux.

It uses the old xvid ratecontrol code, because it is a separated libary
and hence can be used for xvid 0.9, mpeg2enc and lavcodec.

Since it is the old 0.9 xvid ratecontrol, the engine does not handle B frames and sees them as p frame.

So B frames are encoded with lower quantizer. The size/quality is worsened by that.

The result with mpeg2enc and "average" bitrate is rather good.
(a bit slow thought), but mpeg2enc takes care of enforcing the max bitrate/vbv buffer model issue.

The idea for lavcodec was to be ready to use any ratecontrol easily.
And i intend to switch to newer xvid rate control and mix it with
peter vbv buffer model, but using the same framework
e.g. outside of lavcodec.

Following lavcodec changes and having to merge stuff is not really my idea of fun, so i tend to try to limit deep change in lavcodec.

Except some tiny stuff like the 3:2 pulldown patch.

[mean]

And vanilla lavcodec ratecontrol for mpeg1/2 is simply unusable on picky
standalone that enforce every line of the iso spec
Such as non-MT based pioneer and some philips.

[dragongodz]

And i intend to switch to newer xvid rate control and mix it with
peter vbv buffer model
the reason i explicitly mentioned the 1.1 branch of Xvid is worth looking at is because it has a VBV compliancy option. not to mention VHQ for B frames and stricter scaling options. :)

[mean]

thanks for the tip

[Peter Cheat]

The VBV buffer underflow treatment is sort of like what I have done (same concept, different implementation). It's good, but slow too (for loop within for loop within for loop isn't nice!). VHQ for b-frames would be very good. Anyone game enough to try implementing that into ffmpeg? The only thing I could have a go at porting to ffmpeg are the optimised sad compare functions to speed up encoding. I'll have another (really good) look at the current xvidcore and see if I can put this rate control into ffmpeg.

@dragongodz or koepi
What are the major advatages of xvid's current rate control over its previous rate control, and the method used in ffmpeg? In my modifications I fixed the small I big B problem. Maybe my scaling is a bit slow, but it targets filesizes well (probably better than original ffmpeg as I am not using "bitrate tolerance" parameter).

@fabrice
Put your mouse over the save symbol. It will show the matrix being used. (Clicking on it will let you save it). "Standard" means you want to change to the standard matrix (a bad idea if you didn't encode with the standard matrix).

[fabrice]

Hi,

@Peter cheat: I know that. It's only that qenc don't use a custom matrix, because I was doing something wrong:

According to qenc source (file avsenc.cpp), the "use QLB matrix" checkbox have to be checked to use a custom matrix file.
So the correct sequence to use a custom matrix is first check the checkbox, and then choose the matrix file... (I was only choosing the matrix file).

Don't seem logical, don't it? I think (but I could be wrong) that it would be more logical using a custom matrix if the filename is present (wihtout looking for checkbox) , and use the qlb matrix if the chechbox is checked...

Thanks,
Fabrice

[Peter Cheat]

You are correct. This is a little bug (or maybe the box should say "choose custom matrix" and default to QLB). Not hard to fix.

[Nic]

Well spotted Fabrice :) I forgot about that. :) Should just be a if ( csMatrixFile.IsEmpty() == FALSE ) for the matrix file thing...I'll revise that in the next release.

My girlfriend is disappearing off to Cuba for 2 weeks, so should be able to get lots done after this weekend.

Keep the suggestions, tips, bugs, etc coming :)

-Nic

[damian_dimitri]

small question;

are quenc's settign stored in the registry?
Just asking because i had 2 quencs on my hdd and they seem to have the same settings afther i changed one.
IS it possible to put the settings in a *ini file instead of the registry?

no big deal...just curious


Damian

[dragongodz]

What are the major advatages of xvid's current rate control over its previous rate control, and the method used in ffmpeg?
xvids old rate control could spike like crazy. as expected giving very good quality to scenes that need it. it is however not exactly hardware player freindly such as with divx profiles which a lot of players use/support.

there are some reports about(and the other options) it mixed in here
http://forum.doom9.org/showthread.php?threadid=84039

also here is a bit from when gruel first commited the VBV code
http://list.xvid.org/pipermail/xvid-devel/2004-June/004310.html

to get the 1.1 branch you need to do a cvs checkout of course.

[Nic]

@damian: Yes they are held in the registry (local_machine\software\QuEnc). I really dislike .ini files, so I doubt i'll support them. But maybe I'll come up with another solution.

-Nic

[damian_dimitri]

hi Nic,

don't worry...i can (or must..lol) live with it.
Love your tool..so it is eassy to accept.
I was just curious

have a good night

Damian

[Peter Cheat]

Originally posted by dragongodz
xvids old rate control could spike like crazy. as expected giving very good quality to scenes that need it. it is however not exactly hardware player freindly such as with divx profiles which a lot of players use/support.

Understood. But the new changes check for VBV underflow while initial scaling, and not again (should really be checked again just before encoding to make sure...)

Originally posted by dragongodz

there are some reports about(and the other options) it mixed in here
http://forum.doom9.org/showthread.php?threadid=84039

Ok thanks.

Originally posted by dragongodz

also here is a bit from when gruel first commited the VBV code
http://list.xvid.org/pipermail/xvid-devel/2004-June/004310.html

Ok. As I said above, another check would probably be necessary to be absolutely sure that VBV will be ok, but I haven't tested this so maybe it is not a problem.

Originally posted by dragongodz

to get the 1.1 branch you need to do a cvs checkout of course.
I've done this and have started to convert it over to ffmpeg. This is going to take some time, and I'm not sure it will work well. Especially the assymetric curve compression, I tried this already a while back and the result was poor (those who gave feedback confirmed this). Give me a few days on this one, and we'll see how it comes out.

[dragongodz]

As I said above, another check would probably be necessary to be absolutely sure that VBV will be ok, but I haven't tested this so maybe it is not a problem.
possibly it will or should need another check. its still relativly new code so really needs much more testing to be tweaked and refined. the stricter scaling option may help aswell. unfortunatly reports of results are limited thus far but thats generally true of most programs. people like to use them but 99% dont want to report findings, just "it doesnt work".

This is going to take some time, and I'm not sure it will work well.
at the very least it may help give you ideas how to improve/speedup/whatever your own code. so worth investigating at least.

[Amnon82]

@fabrice: You can use the external matrices by checking QLB and then open Your Matrix.txt. Then the QLB-Checkbox will get grayed and QuEnc uses Your Matrix.

@Nic: Can't wait for Your next release ;)

[Nic]

The code is coming along quite nicely...Might get it finished tonight, depending on how I feel. :)

At present it will work like this: if given an AVS File that has no audio it will work the same as it does now. If it does have audio then it will encode the video and audio together into a system or program stream (depending on whether it's MPEG-1 or MPEG-2 respectively).
(I suppose I should also make it if it just has audio, only encode a raw audio stream)

The strange thing is, now I've written this code, it makes it very very easy for QuEnc to be an AVS->[Any format ffmpeg supports] type app. Rather than just a MPEG-1/MPEG-2 encoder. But I'm not sure quite what to do with/about that yet.

Let me know your opinions on how you think I should design it....

Cheers,
-Nic

ps
Might release two versions with the next release, one as a standard libavcodec release and one as a Peter Cheat modified libavcodec. So we can contrast and compare. etc :)

[dragongodz]

makes it very very easy for QuEnc to be an AVS->[Any format ffmpeg supports] type app. Rather than just a MPEG-1/MPEG-2 encoder. But I'm not sure quite what to do with/about that yet.
i personally would rather see all the mpeg encoding(including audio) done before worrying about any other output types. we could probably branch other than mpeg to a different program later down the line. so QuEnc = mpeg encoder and ????? = other types encoder.

[damian_dimitri]

hope you feel well to night
I can rub your back... :D jk :p

looking forward to your release

damian

[Mug Funky]

hmm... any ffmpeg codec. that would be pretty cool, but would break the simple and rather elegant interface that QuEnc has. also it would mean having to allow all those extra options that would probably break encodes.

a separate app would be interesting, but there's always ffdshow for that.

there's definitely more of a need for a CCE killer than an ffmpeg GUI. people still work in MPEG-2 for now. i say keep it as it is.

[rambling] it would be kinda cool to see something similar to LAME's --preset standard et al for ffmpeg. that's probably something for the ffmpeg devs to decide. it'd also need some rigourous testing to determine good settings at each quality level. a program with so so many options and not-so-great explanations as to what they all do needs a good set of presets (it's nigh-on impossible to explain the complexities of so many codecs in a simple manual, especially in a way that n00bs will actually understand).

then we could all say to n00bs "use the presets!".

[dragongodz]

a separate app would be interesting, but there's always ffdshow for that.
Ffdshow is only a codec though and if i am reading Nic right he means not only the codecs but output format(as in containers) aswell. yes you could do some things like that using Ffdshow with VirtualdubMod for example(as in different output containers). still it is interesting for a seperate program.

would break the simple and rather elegant interface that QuEnc has. also it would mean having to allow all those extra options that would probably break encodes.
agree 100%. thats why i also said i would prefer to keep QuEnc mpeg 1/2 only. :)

[Peter Cheat]

Definately keep it as MPEG1/2 only for now. Adding other codecs will only add problems, and besides, the other codecs in ffmpeg are not that great (ffmpeg MPEG-4 vs. XviD, you all know which is the better of the two). The new Snw codec might be interesting but it is still under development and probably very dodgy atm. Keep with what we know for now.

btw Nic, if you want my modified sources send me a PM for the latest. I make changes almost daily :D.

My next release NuEnc (coming out tomorrow maybe) was going to have both rate controls available (user chooses old or modified). I'm not sure I'll have time to throw it in, and might be no point if Nic will make two versions.

[Nic]

Ok, I've kept it pure MPEG-1/MPEG-2. It all works well...It's all finished, but want to test it more first.

Also has the option of loading in Wav and AVI files as input (all this does is create a temporary AVS file with WavSource or AVISource and loads that instead). It supports both AC3 and MP2 (although I don't know if it will work with channels >2...I doubt it will)

Cheers,
-Nic

ps
I've PM'd you Peter. :)