Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
30th November 2003, 21:58 | #101 | Link |
Moderator
Join Date: Oct 2001
Location: Germany
Posts: 4,454
|
Interlacing is broken currently (I think it's missing for bframes).
Regards Koepi
__________________
Koepi's new media development site |
30th November 2003, 22:30 | #102 | Link |
Registered User
Join Date: Jul 2003
Posts: 1,152
|
*Cosmetic* Bug:
If you set weight bigger than 2.00 and hit OK it will show as that value in the "XviD Configuration" window. This *might* be confused with a quantinizer of that value (though the weight values lack the brackets...). Or does it indeed work with those values bigger than 2.00? |
30th November 2003, 22:58 | #103 | Link |
Huh?
Join Date: Sep 2003
Location: Uruguay
Posts: 3,103
|
This is just awesome. I'd like to express my thanks to all the XviD dev team for putting so much hard work on this great codec. I can't help but feel sorrow for whoever tries to make an "XviD 1.0 options explained" document, since the number of new or combinable features has gotten so big. I wish I could beta test, but alas, I don't have my computer right now (I'm writing from a cybercoffee, long story) .
P.S: can anyone test how well does 1.0 beta handle quantizer 2 encodes? |
30th November 2003, 23:25 | #104 | Link |
Registered User
Join Date: Nov 2001
Posts: 9,770
|
heya
xvid quality is awesome great work guys! one question about the zone feature: it seems we only can define the start frame! now how can i define where it should end (for example when the credits dont go till the end)? will i have to define 3 zones if i only want 1 zone inbetween the movie? what if i only want to insert 1 keyframe at a position? do i have to define a new zone right after the keyframe? if yes, perhaps it would make things easier if we could define the startframe and the endframe of a zone (like with the old credits feature)...
__________________
Between the weak and the strong one it is the freedom which oppresses and the law that liberates (Jean Jacques Rousseau) I know, that I know nothing (Socrates) MPEG-4 ASP FAQ | AVC/H.264 FAQ | AAC FAQ | MP4 FAQ | MP4Menu stores DVD Menus in MP4 (guide) Ogg Theora | Ogg Vorbis use WM9 today and get Micro$oft controlling the A/V market tomorrow for free |
30th November 2003, 23:42 | #105 | Link |
ffdshow/AviSynth wrangler
Join Date: Feb 2003
Location: Austria
Posts: 2,441
|
Minimum I-frame interval b0rked?
When trying to encode something in 2-pass mode I was getting a severely undersized second pass (with most frames having quantizer 31... o_O); it turns out that setting the minimum I-frame interval to 5 instead of 1 seemed to be the culprit...
Has anybody else experienced this? EDIT: Just tried this again using "Load Defaults" and setting the minimum I-frame interval to 5 - same result: almost all frames get quantizer 31. Using the statsfile from the first pass works fine when turning this option off for the second one, so either the option isn't used for the first pass or it works then, but not for the second one... *wonders* Looks like a bug to me... (not that I can't live without this option, it's just a nasty pitfall as it's totally non-obvious... ) np: B. Fleischmann - Take Your Time (Welcome Tourist) Last edited by Leak; 30th November 2003 at 23:55. |
1st December 2003, 00:29 | #106 | Link | |
plebian
Join Date: Nov 2001
Posts: 775
|
Quote:
|
|
1st December 2003, 00:58 | #108 | Link |
retired
Join Date: Jun 2002
Location: hollywood
Posts: 1,013
|
wannabe,
I think it has got nothing to do with trellis being enabled or not. I have done several two-pass test encodes, all with trellis enabled, and not encountered such a problem. You should search the problem elsewhere. Maybe the problem is the third "..." box from above near the target size setting (that leads to the bitrate calculator) not keeping the entered value, a bug that was reported somewhere before I guess. regards, iago EDIT: aaar9800 also points to the same issue below, and I suppose he is right. Last edited by iago; 1st December 2003 at 01:03. |
1st December 2003, 00:59 | #109 | Link |
Registered User
Join Date: Mar 2003
Location: Tucson, AZ
Posts: 62
|
Wannabe and Leak, I think that you set your desired size of second pass and then go around to check other options. If this is the case then the size will be reset to 700kb and you should change it again.
That thing occured quite a lot for me in early dev-api 4 builds |
1st December 2003, 01:37 | #110 | Link | |
ffdshow/AviSynth wrangler
Join Date: Feb 2003
Location: Austria
Posts: 2,441
|
Quote:
Loaded the defaults and encoded a 30 second clip with the default settings in VirtualDubMod. Then I just switched to 2 pass second pass, set the target size to 2500kB (first pass was 7MB) and lo and behold, it didn't use a quantizer higher than 6. Then I went to the Advanced options page, ticked "Chroma Motion" and okayed my way out of everything. The target filesize still was 2500 and it still worked. Then I went to the Advanced options page again, changed the minimum I-frame interval to 5, okayed out again (target filesize still was 2500) and then the 2nd pass again went bonkers, but yes, it looked as if it targeted 700. Still, the target filesize box still contained 2500 (while it really reverts back to 700 if you hit the bitrate-calc-placeholder-button) and setting the minimum I-frame interval back to 1 and doing another 2nd pass yielded normal results. So I don't believe it's got anything to do with changing settings after entering the target filesize, as I only entered it once and everything was okay while I didn't touch the min. I-frame interval *and* everything went back to normal after setting it back to 1, but not touching anything else. Oh, and deliberately setting the target size to 700kB yielded a 750kB file with a max quantizer of 22, not 31: http://desdemona.ssw.uni-linz.ac.at/...Interval_1.png On the other hand, as soon as I increased the min. I-frame interval to 5 and left everything else (especially the target size of 700) the same: http://desdemona.ssw.uni-linz.ac.at/...Interval_5.png And, as expected, setting it back to 1 fixed the problem again. Hope somebody can make sense of that... EDIT: Actually, min. I-frame intervals 1-3 all yield the same good result, while everything >= 4 freaks out. np: David Holmes - No Mans Land (This Film's Crap, Let's Slash The Seats) Last edited by Leak; 1st December 2003 at 01:42. |
|
1st December 2003, 01:48 | #111 | Link | |
ffdshow/AviSynth wrangler
Join Date: Feb 2003
Location: Austria
Posts: 2,441
|
Quote:
Well, I'm off to bed - maybe someone elsewhere where it's not quarter to two in the morning can reproduce this? np: Autechre - Squeller (EP7) |
|
1st December 2003, 02:37 | #112 | Link | |
Registered User
Join Date: Mar 2003
Location: Norway
Posts: 144
|
Quote:
|
|
1st December 2003, 03:17 | #113 | Link |
Registered User
Join Date: Aug 2003
Posts: 24
|
@Leak
I can reproduce the problem with 40 seconds clip -Load Defaults... -Set Encoding type: Twopass - 1st pass -Uncheck Discard first pass -Encode resulted in a 9.47MB file with all frames at quant 2 -Set Encoding type: Twopass - 2nd pass -Encode resulted in a 9.41MB file with almost all frames at quant 2 -Set Encoding type: Twopass - 2nd pass -Set Minimum I-Frame Interval: 5 -Encode resulted in a 1.68MB file with almost all frames at quant 31 Any Minimum I-Frame Interval other than 0 or 1 will produce file with almost all frames at quant 31. Changing target size have no effect unless the min i-frame int is 0 or 1. Is 0 a legal value for Minimum I-Frame Interval? |
1st December 2003, 05:06 | #114 | Link | |
Registered User
Join Date: Jun 2002
Posts: 250
|
Quote:
(Bitrate has to be limited to 4'000 to be correctly decodec by kiss standalones) |
|
1st December 2003, 06:20 | #116 | Link | |
Registered User
Join Date: Dec 2001
Posts: 987
|
Quote:
|
|
1st December 2003, 08:25 | #117 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,753
|
Wow - so many people praising the XviD development team for finally releasing a beta.
I don't. In fact, I'm quite pissed that you released the codec too early. You released it, although you knew that some important part does not work correctly, as we privately discussed: 2-pass file size prediction in XviD dev4api does not work without B frames! And even with B frames, at least the "average bitrate" display is totally confused: |
1st December 2003, 08:38 | #118 | Link |
Moderator
Join Date: Oct 2001
Location: Germany
Posts: 4,454
|
LigH:
instead of crying or yelling around you should provide us with code to fix the problem :P Regards Koepi
__________________
Koepi's new media development site |
1st December 2003, 09:03 | #119 | Link |
Mushroomeur
Join Date: Jun 2003
Location: Mushrooms of Paris Town
Posts: 267
|
@Ligh : read carefully the first message of this thread. Perhaps you don't know the meaning of a beta release
and great thanks to the xvid team for that geat piece of code Last edited by d'Oursse; 1st December 2003 at 09:06. |
1st December 2003, 09:07 | #120 | Link | |
Fascinated Lurker
Join Date: Feb 2002
Location: Durham, UK
Posts: 243
|
Quote:
1) Burn your encodes to DVD 2) Use the dvd-rom version of the drive firmware instead of the speed-limited one (see rpc1.org) The bitrate issue with the kiss player is just a problem with the drive's inability to spin that fast with cds. The above methods overcome that. |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|