View Full Version : QuEnc requests/ideas
dragongodz
7th November 2004, 16:03
can people please post their requests and/or ideas that they would like to see with QuEnc here ? that would save clogging up the normal QuEnc threads and make it easier to know whats been requested. :)
Mug Funky
7th November 2004, 16:14
i just said something similar in the QuEnc thread (in the context of a bug report), but:
could max bitrate be on the same GUI section as average bitrate, so we can see them together?
i can't think of anything else i'd like to see in it atm. maybe a premiere plugin? :D
burnman99
7th November 2004, 21:44
The ability to enocde audio & video separately & save as .mp2 & .m2v
A template for VCD/SVCD/DVD.
That's about it. This program is Great!
Rog
Paced
7th November 2004, 23:23
Originally posted by burnman99
The ability to enocde audio & video separately & save as .mp2 & .m2v
Rog
I'm pretty sure you can do that already (with a little editing of your AVS file of course :)) Or, perhaps Nic/dragongodz could add an option similar to CCE's - disable audio - in the 'Audio Codec' drop down box?
//Edit
Also, just wondering, what are the chances of an internal resizer? This is mainly for those whom have no knowledge of AviSynth and just want to load the AVI file - which doesn't have a compliant SVCD/DVD resolution - directly into QuEnc. Perhaps you could allow the user to choose the output resolution? And, of course an option to disable the option for those that already know how to resize in AviSynth :)
Peter Cheat
8th November 2004, 02:22
I wouldn't bother with internal resizing. AviSynth has far better resizing than ffmpeg. Plus Nic would need toallow AVI input, which wouldn't be hard to implement but would cause more problems (see what problems have popped up when muxxing was added). AVS->M2V is the basic idea of the app I believe.
I have a request too :D
More stats like peak bitrate, maximum bitrate, average quantiser, minimum and maximum quantiser etc etc. I've written the code for all of this in NuEnc, just haven't finished arranging the GUI (I hate GUI programming).
burnman99
8th November 2004, 07:24
Originally posted by Paced
I'm pretty sure you can do that already (with a little editing of your AVS file of course :)) Or, perhaps Nic/dragongodz could add an option similar to CCE's - disable audio - in the 'Audio Codec' drop down box?
Well i Can do video only buy using the KillAudio command but is there a way to do AUDIO only?! This would help!
Thanks!
Rog
Teegedeck
8th November 2004, 09:35
An idea for better scaling for high-bitrate matrices in 2-pass: If the summ of values in a custom-matrix is below, say, 1300 a high-bitrate matrix is recognized and the first pass performed at quant=3 instead of quant=2. I would very much like such a thing in XviD, too, BTW...
Paced
8th November 2004, 12:13
Originally posted by Peter Cheat
I wouldn't bother with internal resizing. AviSynth has far better resizing than ffmpeg. Plus Nic would need toallow AVI input, which wouldn't be hard to implement but would cause more problems (see what problems have popped up when muxxing was added). AVS->M2V is the basic idea of the app I believe.
Sorry, I wasn't more clear. What I meant was in its current state, whenever an AVI is loaded directly into QuEnc, I think an AVS file is created for it. I'm not sure if this is possible, since I am but a mere peasant in software development :), but perhaps Nic could somehow tell QuEnc to analyse the AVS input to determine its original resolution, then apply the appropriate calculations for correct resizing (4:3, 4:3 letterbox, 16:9, etc), then add it to the script? Probably more trouble than it's worth, even if it were possible...
Paced
8th November 2004, 12:14
Originally posted by burnman99
Well i Can do video only buy using the KillAudio command but is there a way to do AUDIO only?! This would help!
Thanks!
Rog
You can load a .wav file directly into QuEnc, then it will encode it to MP2/AC3.
Inc
8th November 2004, 15:30
Originally posted by Paced
Sorry, I wasn't more clear. What I meant was in its current state, whenever an AVI is loaded directly into QuEnc, I think an AVS file is created for it. I'm not sure if this is possible, since I am but a mere peasant in software development :), but perhaps Nic could somehow tell QuEnc to analyse the AVS input to determine its original resolution, then apply the appropriate calculations for correct resizing (4:3, 4:3 letterbox, 16:9, etc), then add it to the script? Probably more trouble than it's worth, even if it were possible...
That would mean an integration of a FitCD like applikation "within" Qenc. As FitCD does use the avi-input where a avs script will be generated incl. all PAR based resizings.
Resizings are too complex as they could be integrated in a such newbie friendly way without that advanced users will ran up the walls cause of too less teakable functions ;-)
So FitCD as speparate appl. should be your first choice as you can determine everything whats needed.
But if some c++ resizing routines are needed, Nic could look into Gripfits sources ... but as said above, 90% of the users will do the separate FitCD way.
bergi
9th November 2004, 12:21
Don't forget my request for separated passes in 2pass mode. :)
SILICON
9th November 2004, 17:32
The 3pass or 4pass mode.
For a best quality :-), and more encode time :-(
Mug Funky
11th November 2004, 01:14
i second whoever it was' request for 2-pass fit-to-filesize when the number in the bitrate box is over 15000 (that's the mpeg-2 max isn't it?).
this is probably very much a libavcodec issue, but is nonlinear quantscale possible at all? i'm not sure if it really makes a big difference in the end...
apart from that and what's been said here already, there's not really anything more i'd want out of quenc.
Shubin
11th November 2004, 15:37
A possibility to recover or to continue encoding.
It's for people with old computers.
There are possibly some program states (complete frames I guess)
that could we stored on the HDD and in case of a crush or manual
interrupt the encoder will be able to continue from that stored
state.
I'm not sure that many people would vote for this, but...
just an idea.
Another idea is to be able to store all options in a config file.
Mug Funky
12th November 2004, 06:03
Shubin: i second that one heartily.
i keep getting crashes at about the 35000 frame mark (haven't tracked the problem to anything specific yet, maybe it's a b0rk mpeg2 stream i'm reading from?), and a resume option that maybe continued from the last i-frame (for both 1st and 2nd pass) would be awesome.
a feature like that would really set it apart from other encoders, too. it'd save me a lot of time as well (imagine a batch file that simply resumes constantly until the encode is finished - i'd be able to do overnight encodes and actually have them finished the next day without that disheartening "access violation" error).
[Admiral]
15th November 2004, 08:51
I would also appreciate an internal resizer, though because there isnt one I've been forced to bother learning Avisynth finally lol.
though i disagree that it would make it less user-friendly..
@Peter Cheat: it already DOES support avi-input with this release..
but uh yea.. suggestions are more really just problems that I have....
when I pause the encoding and then resume it then misrepresents the current FPS... like if i was encoding @ 11fps before hand and then I pause for 30minutes and then continue it'll suddenly say its going @ 1.8fps.. and because of that the 'remaining time' will be HUGE..
sometimes it 'catches up' and finishes when i thought it would have, but other times it actually DOES take a long time to finish..
this problem also applies when I start running something else in the background that occasionally takes up some cpu usage (i.e. newsgroup decoding etc). though I have QuEnc's priority set to Low, it never seems to 'catch up' once the cpu has been relieved of all other requests... bleh. yea. but anyways...
my other suggestion is a built-in bitrate calculator, or even better, a system where you just punch in the final size you want, the bitrate of the audio, and it just does it itself (sorta like in gordian knot)
oh and one last suggestion - batch encoding?
I'm trying to re-encode over 100 ~20min divx/xvid/mp4 into dvd-r so yea that would be much appreciated! otherwise i may have to go back to tmpegenc :-( (SLOW!!)
okay yea sorry to sound like a big noob. lol. but yea I am when it comes to mpeg-2
Mug Funky
15th November 2004, 11:01
you can do batch encoding just fine from the command line... just make a .bat file
of course, you'll still have to make the AVS files, but i find it quite easy to just have videos with consecutive names and go through with a text editor. you can use regular expressions if you want to be tricky.
[edit]
oh, just thought of something else: perhaps a way to set b-frame ratio and offset, like in xvid? would this clutter up the GUI too much? (i don't actually know what quenc does as far as offset and ratio).
Peter Cheat
16th November 2004, 06:29
I don't think Nic wants the ratio and offset to be played with. It has a dramatic effect on quality (usually negatively). He has it set to some good defaults. Allowing the user to change is would cause many problems I think.
Bugsy
18th November 2004, 14:13
Originally posted by burnman99
The ability to enocde audio & video separately & save as .mp2 & .m2v
A template for VCD/SVCD/DVD.
That's about it. This program is Great!
Rog
Yes please! Encode to separate audio and video files. A free authoring program like DVDAuthorgui requires separate audio and video. I know I could fiddle the .AVS to give me video only and another tool to give me audio, but why not give the user an option to choose between elementary streams and a muxed file?
Bugsy
burnman99
19th November 2004, 20:21
Originally posted by Bugsy
Yes please! Encode to separate audio and video files. A free authoring program like DVDAuthorgui requires separate audio and video. I know I could fiddle the .AVS to give me video only and another tool to give me audio, but why not give the user an option to choose between elementary streams and a muxed file?
Bugsy
Bugsy, here is a workaround until it is updated...
For the .m2v file:
DirectShowSource("C:\Movie.avi", audio=false)
ConvertToYV12()
For the .mp2 or .ac3 file:
DirectShowSource("C:\Movie.avi", video=false)
ConvertToYV12()
This should give you both the .m2v & .mp2/.ac3 files. You can thank
clickit on the kvcd forum for the scripts.
Hope this helps.
Later!
Rog
Bugsy
23rd November 2004, 14:11
Originally posted by burnman99
Bugsy, here is a workaround until it is updated...
For the .m2v file:
DirectShowSource("C:\Movie.avi", audio=false)
ConvertToYV12()
For the .mp2 or .ac3 file:
DirectShowSource("C:\Movie.avi", video=false)
ConvertToYV12()
This should give you both the .m2v & .mp2/.ac3 files. You can thank
clickit on the kvcd forum for the scripts.
Hope this helps.
Later!
Rog
Thanx Rog!
Wanted to thank clickit on the kvcd forum, but they wanted me to pay to register....? Bad idea! I'm sticking to Doom9.
Bugsy :devil:
PS! Any idea of when to expect v 0.57 or better 0.60 or even better: 1.0?
Nic
24th November 2004, 10:49
PS! Any idea of when to expect v 0.57 or better 0.60 or even better: 1.0?
Maybe soon, I was waiting for the new DVD patch to be submitted to CVS. And it finally has....
-Nic
Koepi
24th November 2004, 11:01
Very nice, can't wait to test it :)
Keep it going Nic!
Regards
Koepi
Nic
24th November 2004, 11:18
Keep it going Nic!
It's hard to....Half-Life 2 is quite addictive :)
-Nic
Koepi
24th November 2004, 14:01
Damn, I have a machine at home which is fast and powerful enough for gaming in the meantime (Barton 2.8k, Radeon9.6k, 1GB DDR-333 dual channel memory on msi k7n2 delta-ilsr, 19" TFT /w DVI,...), but I lack the time for any games besides windows (will it work? will it stay (virus-)clean? ;) ) or "let's see if it helps functionality if I move this code block there..." - and of course "let's see what we can stress this new QuEnc build with" :)
So, come on, take the few minutes so we can play too! *hide*
Cheers
Koepi
Mug Funky
24th November 2004, 17:29
koepi: stop bugging the devs... you gotta give a little back to the community as well, you know :D
*hiding too*
[edit]
hehe... btw, VHQ for b-frames rocks. thanks koepi :)
Koepi
24th November 2004, 17:44
Originally posted by Mug Funky
koepi: stop bugging the devs... you gotta give a little back to the community as well, you know :D
*hiding too*
[edit]
hehe... btw, VHQ for b-frames rocks. thanks koepi :)
But but but.... that sysKin's code! :eek:
Enough of the off-topic. Let's patiently wait for Nic frag'ing away all his enemies :)
Cheers
Koepi (yay, xmas market opens tonight, I'll have some "hot wine" in some minutes!)
Teegedeck
24th November 2004, 22:38
Hey, I prefer 'Feuerzangenbowle' these days! :D
But that hot, spicy wine is also yummie!
...an' cheers to you!
Errr... Excuse me being offtopic once again *trying to strike himself*
Nic
25th November 2004, 13:50
(Got even more side tracked...got the SNOW codec compiling in Visual Studio, so I can use all the normal tools I use to optimise stuff....But a new release will be soon-ish)
dragongodz
26th November 2004, 01:20
:sly:
zilog jones
1st December 2004, 17:15
I'd also like to see an integrated bitrate calculator. I can't seem to find any free DVD video calculators anywhere, outside of going half-way through the project wizard in TMPGEnc, or using a *real* calculator (they're so passe!).
Bogalvator
1st December 2004, 20:23
http://www.videohelp.com/calc.htm
Works well for me......
freelock7
2nd December 2004, 08:08
a <shutdown > after encoding would be nice (like EclCCE feature).
dragongodz
2nd December 2004, 12:05
a <shutdown > after encoding would be nice (like EclCCE feature).
QuEnc 0.56 already has it for CLI use so i assume you mean add it to the GUI ?
freelock7
2nd December 2004, 18:02
Yes.
spase
3rd December 2004, 06:02
Originally posted by zilog jones
I'd also like to see an integrated bitrate calculator. I can't seem to find any free DVD video calculators anywhere, outside of going half-way through the project wizard in TMPGEnc, or using a *real* calculator (they're so passe!).
i found a free one called PowerBIT.
it appears to be in german or something, but you can right click the interface to switch languages. i dont remember the website, but i am sure you can google it.
spase
3rd December 2004, 06:08
hmm it has come to my attention that minimum bitrate would be a useful option as well (maybe only to me so that it doesn't studder on my standlone... but i can't be the ONLY one with a standalone that doesn't deal with low low bitrates).
oh yea and 3 or 4 pass would be nice as well... these are the only 2 real reasons i have been using NuEnc.... man i have 'wasted' a lot of time with that program trying different settings, matices, etc.
dragongodz
3rd December 2004, 12:28
hmm it has come to my attention that minimum bitrate would be a useful option as well (maybe only to me so that it doesn't studder on my standlone... but i can't be the ONLY one with a standalone that doesn't deal with low low bitrates).
the reason QuEnc doesnt have it is because with the current avcodec if you use anything other than a min of 0 the rate control goes nuts. thats one thing Peter has fixed in his rate control. :)
spase
3rd December 2004, 13:35
i see. i thought this might be the case.
Guest
6th December 2004, 14:22
Hi,
I'm trying to to get QuEnc to render out a mp2 file - but my avsvideo is generated in avisynth and not loaded(I have to use the images for rendering a fadeout2 on the sound), so I can't use the:
DirectShowSource("C:\Movie.avi", video=false)
Any other idears of how to kill the image in avisynth?
Btw. anyone knows anything of the how the muxxing is comming along in QuEnc(so I don't need this (m2v+mp2+mplex commandline)workaround?
Tin2tin
My DVDslideshowGUI (http://wxbasic.sourceforge.net/phpBB2/viewtopic.php?t=668) using avisynth and QuEnc.
dragongodz
7th December 2004, 13:02
anyone knows anything of the how the muxxing is comming along in QuEnc
well some dvd muxxing patches have been commited to the FFMpeg cvs so muxxing in the next version should be better. will just have to wait and see. :)
unixfs
7th December 2004, 16:41
It would be very nice if avcodec/Quenc encoded dark (and in general uniform) scenes without blocks
(on my TV I see them everywhere, whatever the bitrate, even with qscale=2).
Another artifact that avcodec always produces is ringing:
have you ever noticed how badly are encoded lights
cast by lightbulbs?
I understand these are a major issues (common to xvid/divx), but
you asked requests :)
Boulder
7th December 2004, 17:22
Have you tried using Blockbuster? It can work wonders on dark areas.
Which matrix did you use?
unixfs
7th December 2004, 17:25
I ran a short test with blockbuster, but the source was clean, and
the result was even worse than the standard one.
I never use custom matrices.
Boulder
7th December 2004, 17:53
Originally posted by unixfs
I ran a short test with blockbuster, but the source was clean, and
the result was even worse than the standard one.
And exactly with what settings? Blockbuster doesn't remove existing blocks, it prevents them from appearing in the low-lit areas in the encoding process.
I never use custom matrices.
Maybe it's time to try then? ;)
unixfs
7th December 2004, 20:13
it was a month ago, now I don't remember what settings I used for
blockbuster. I will retry later; what custom matrices do you suggest
for a 720x576 at 2000 kb/s ?
Boulder
7th December 2004, 20:32
Try QLB or Notch. Notch was developed mainly with the low-lit areas in mind so it might help reducing DCT blocks.
Try Blockbuster(method="noise",variance=0.5,seed=1).
unixfs
8th December 2004, 12:57
I just tried your advices: I can still see those blocks, both when
I use QLB alone and when I combine it with blockbuster.
The other settings are: 2passes, mpeg2, 2000 kb/s, dc 11, gop 15,
no bframes, high quality.
Boulder
8th December 2004, 13:03
Could you post a screenshot of a problem frame, preferably both the original and encoded? I'd be interested in seeing the actual frame.
dragongodz
8th December 2004, 13:36
settings are: 2passes, mpeg2, 2000 kb/s, dc 11, gop 15,
GAK!!! BAD, BAD and plain BAD.
1. dc 11 is for high def(high level) footage only, meaning realy big bitrate encoding(15Mb/s or more type encoding). dvd for example can only use 8,9 or 10. for lower bitrate encoding you may want to try a lower value such as 8 or 9.
2. no B frames with dvd frame size but a bitrate of 2000 ? use B frames(i reccomended 2 for dvd), its really is a must for so little bitrate.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.