digitalFAQ.com Forums [Archives]

digitalFAQ.com Forums [Archives] (http://www.digitalfaq.com/archives/)
-   Video Encoding and Conversion (http://www.digitalfaq.com/archives/encode/)
-   -   FFMPEG: QuEnc (http://www.digitalfaq.com/archives/encode/8643-ffmpeg-quenc.html)

kwag 03-23-2004 11:26 PM

Quote:

Originally Posted by audioslave
Thanks. I found this - a GUI version called DoPulldown here:
http://www.doom9.org/Soft21/SupportU...wn.1.0.0.0.zip Is it the same program exept for the GUI?

Yes, I believe so :)

-kwag

audioslave 03-23-2004 11:30 PM

Burning right now...
I'll let you know in a second or two...

audioslave 03-23-2004 11:35 PM

YES :!: That was it. Works like a charm :wink: Damn, this looks good. The quality of QuEnc 0.45 is really something else :!: :)
Thank you for the tip Kwag.

kwag 03-23-2004 11:58 PM

Now try encoding the complete movie using CalcuMatic (or other bitrate calcs) to get your average bitrate. Then see if the final size matches closely the wanted size ;)

-kwag

incredible 03-24-2004 02:06 AM

Kwag, the GOP 3 Frames issue to me seems like an Scene Change issue.

kwag 03-24-2004 02:17 AM

Quote:

Originally Posted by incredible
Kwag, the GOP 3 Frames issue to me seems like an Scene Change issue.

Yes it does. But only when very close scenes are detected. If you look when the GOP was 6, there is no problem. There should be a constraint in the encoder to limit the GOP size to a minimum of IBBP (4 frames), and that should correct the issue. Or really: minGOPSize = number_of_B_Frames + 2 ;)

-kwag

marcellus 03-24-2004 05:15 AM

Quote:

Originally Posted by kwag
Quote:

Originally Posted by incredible
Kwag, the GOP 3 Frames issue to me seems like an Scene Change issue.

Yes it does. But only when very close scenes are detected. If you look when the GOP was 6, there is no problem. There should be a constraint in the encoder to limit the GOP size to a minimum of IBBP (4 frames), and that should correct the issue. Or really: minGOPSize = number_of_B_Frames + 2 ;)

-kwag

I think this issue can be resolved. ffvfw has an option for minimum interval between I frames and since is also libavcodec based I think that nic can expose that setting as an advanced option.

Anyway, QuEnc made a lot of progress but it's output is still under the quality of ffvfw (ffdshow actually) and the gain in speed does not pay the quality loss. But it's still 0.45 release...

Edit: Well, I forgot, another big advantage of QuEnc is VBV compliancy. I wonder why ffvfw is the only libavcodec incarnation thas has this issue, why milan does not fix it...

marcellus

incredible 03-24-2004 06:15 AM

As I got the actual QuEnc vers. .... where can you see a command line option??? My vers. does not show one, neither shurely to alter it as its not avaiable.

He should offer more options of ffmpeg in his GUI .... for example processing interlaced sources.

vmesquita 03-24-2004 06:23 AM

Man, it's very fast!!!!! :D 8)
I am currently encoding a AVI movie using the latest Dialhot v4 script:
With Trellis, GOP 18 and KVCD Notch I get 19.5 fps,
Without trellis, it goes up to 24 fps (realtime!)
Amazing speed.
Can't comment on quality yet, let's wait for the outcome. I am doing 2 pass VBR. I had previously encoded this movie using CCE so I'll be able to do a good comparison.

@incredible:
Do this:
QuEnc /?
A window will pop up with command-line options.

marcellus 03-24-2004 07:33 AM

Quote:

Originally Posted by marcellus
I think this issue can be resolved. ffvfw has an option for minimum interval between I frames and since is also libavcodec based I think that nic can expose that setting as an advanced option.

I have to retract what I said. In ffvfw the minimum I interval setting doesn't work as expected. With any value other than 1 for min I interval all GOPs are screwed, it puts a lot of consecutive P frames
Normal GOP: IBBPBBPBB....
Screwed (example): IPPPBBPPPPPPBBPPP..

kwag 03-24-2004 10:24 AM

Quote:

Originally Posted by marcellus

Edit: Well, I forgot, another big advantage of QuEnc is VBV compliancy. I wonder why ffvfw is the only libavcodec incarnation thas has this issue, why milan does not fix it...

Well, you can use VBVPatcher on your ffvfw encodes, and then the MPEG file will be "branded" compliant.
But the way I see it, I find QuEnc much more simpler and flexible than ffvww, and I'm getting extremely good results.
I think we will all be using QuEnc more often ;)

-kwag

marcellus 03-24-2004 11:37 AM

@kwag
I agree with you, QuEnc is very good. I would like though to have all the libavcodec options out to play with them. :twisted: I hope it will be in 1.0 release.
I know that QuEnc has a very good quality right now but I'm targeted on small resolution (352x288) and any artifact is more annoying than with full resolution (I have double size blocks on TV screen). So thats why I am very picky and since the speed of ffvfw is acceptable at 352x288 (25-30 fps) and VBV issue is ignored by my player, you know what I choose for the moment. I am sure that QuEnc could do a better job with the right settings but we still have not access to them.
marcellus

audioslave 03-24-2004 04:45 PM

As I posted earlier; my encode of Shrek looks amazing! Even though I encoded it in MPEG-2 and SVCD resolution (480x480). Have anyone tried QuEnc with MPEG-1 output? Results :?:

kwag 03-24-2004 04:46 PM

Quote:

Originally Posted by audioslave
Have anyone tried QuEnc with MPEG-1 output? Results :?:

I did, and I also liked the MPEG-2 results better. Seems the encoder creates better results at MPEG-2.

-kwag

audioslave 03-24-2004 05:00 PM

Yes. And another thing that's great about being able to encode good looking KSVCD's (MPEG-2) is that they're playable almost everywhere - on almost everybody's stand alone DVD players :D Even at my parents' house... :wink:

audioslave 03-24-2004 05:13 PM

From what I understand it's best to use a closed GOP?
The setting I used for Shrek (NTSC) were the following:

Main window
* MPEG-2
* Use VBR - Checked
* High Quality - Checked
* Use Trellis Quant - Checked (But have no clue what this is :roll: )
Advanced options
* Force Closed GOP - Checked
* Use KVCD "Notch" Matrix - Checked
* GOP Size=18
* Max B-Frames=2
* 4:3 Aspect Ratio

Then, in the main window, I simply pasted the average bitrate I got from CalcuMatic and clicked Encode. Ta-da!
Please, inform me if I should use some other settings for my encodes.

Question: Can we use the GOP from the TMPEnc templates with QuEnc (PAL=25, NTSC=30, Film=24)?

@Kwag
Very nice quality on your Red Planet clip :!:

EDIT: If you use HybridFuPP to encode your movies - Take the average bitrate from CalcuMatic and multiply it by 1.05 :wink:

vmesquita 03-24-2004 05:17 PM

Well, my test got a very wierd result. I asked to encode 480x480 at 976 kbps, and used trellis, 2 pass VBR, Notch, GOP 18.
The file came out at 725 kbps. I opened it with BitrateViewer, and The Q line was constant at 2.67. I have the same file encoded with CCE at "real" 976 kbps, but still could not do a side by side comparisson. I opened the encoded file and it looked good, but in 17" monitor most stuff do. :D

kwag 03-24-2004 05:20 PM

Quote:

Originally Posted by audioslave
From what I understand it's best to use a closed GOP?
The setting I used for Shrek (NTSC) were the following:

Main window
* MPEG-2
* Use VBR - Checked
* High Quality - Checked
* Use Trellis Quant - Checked (But have no clue what this is :roll: )
Advanced options
* Force Closed GOP - Checked
* Use KVCD "Notch" Matrix - Checked
* GOP Size=18
* Max B-Frames=2
* 4:3 Aspect Ratio

Then, in the main window, I simply pasted the average bitrate I got from CalcuMatic and clicked Encode. Ta-da!
Please, inform me if I should use some other settings for my encodes.

You got them all right :D
Quote:


Question: Can we use the GOP from the TMPEnc templates with QuEnc (PAL=25, NTSC=30, Film=24)?
Yes, but I think this encoder doesn't like longer GOPs very much. Stick to 15(PAL) or 18(NTSC)
Quote:


@Kwag
Very nice quality on your Red Planet clip :!:
Thanks :D
Quote:


EDIT: If you use HybridFuPP to encode your movies - Take the average bitrate from CalcuMatic and multiply it by 1.05 :wink:
No. It shouldn't make any difference, because the encoder is trying to maintain average bitrate.
BTW, what was your final file size on "Shrek", compared to the size wanted by CalcuMatic :?:

-kwag

audioslave 03-24-2004 05:26 PM

kwag wrote
Quote:

No. It shouldn't make any difference, because the encoder is trying to maintain average bitrate.
BTW, what was your final file size on "Shrek", compared to the size wanted by CalcuMatic
Actually, when I first encoded Shrek (my first try with QuEnc) with the average bitrate from CalcuMatic the final vide file got about 40 MB too small. But then I multiplied the avg.bitr. by 1.05 and the final movie - muxed - is 806 MB, perfect!

Note: When I use Incredible's Slicer routine to predict I also have to multiply the wanted sample size by 1.05 to get the final encode right.

EDIT: This is when I use HybridFuPP to encode the DVD's

vmesquita 03-24-2004 05:28 PM

Wait a minute....
So the average bitrate is not the average bitrate that the movie will be encoded? :? :? :?


All times are GMT -5. The time now is 01:25 AM  —  vBulletin © Jelsoft Enterprises Ltd

Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.