View Full Version : Syskin's IPB decisions
As far as I understand it, Syskin's new IPB doesnt read the stats file (or ignores changes to it). Is this true? Will the ability to add keyframes at specific locations using Syskins IPB ever be added. Id really appreciate if you'd way in on this Syskin. If one of the questions are noobish, please forgive me.
PS Didnt want to hijack the new Xvid thread any further, since this is a very specific question and not a bug report.:o
Koepi
26th June 2003, 06:13
Do you READ?
Then read again what I posted in several threads (i.e. the one to the build):
IN DEV-API-4, WHICH WILL BECOME XVID 1.0 (numbers... tses) THIS IS ALREADY FIXED!
Oh, and by the way: the statsfile gets read. How else should XviD hit the target size....
Koepi
Selur
26th June 2003, 17:36
"How else should XviD hit the target size..."
I thought by using magic.
:D *scnr* :D
My mistake, should have read more. Nuke the thread please, I feel like an idiot.
Koepi
27th June 2003, 23:51
hm. the magic is still there, be assured... i just wanted to give a hint how it works ;)
iago
28th June 2003, 00:13
Just as a reference to the title of the thread, I love syskin's IPB decisions! ;) Though I don't know what that magical source is which he's working on when deciding on his new IPB decisions! (Koepi once had mentioned that syskin worked on only one source! :D) Just kidding...
best regards to all,
iago
edit: He he, see the changelog of the new dev build on uManiac's site! He has improved the PBI decision *again*! :-)
Animaniac
28th June 2003, 00:26
Originally posted by iago
edit: He he, see the changelog of the new dev build on uManiac's site! He has improved the PBI decision *again*! :-)
Too bad uManiac's builds don't have the field fo B-Frame threshold and no option to enable R-D quantization. =(
iago
28th June 2003, 00:32
Too bad uManiac's builds don't have the field fo B-Frame thresholdAfair, syskin also says that the default threshold allows the most intelligent IPB decision. :-)
JohnMK
28th June 2003, 03:22
Most intelligent for easily compressible movies for sure, or for 2 CD encodes & such, but for many 1 CD encodes, Koepi likes to push the threashold from default, to nearly max. In older builds this used to mean 255, but now I think it means something more like 50-60. I think syskin really hates this however, and would prefer people not push it half that far. If you ask him, something like 20 or 30 might be a wise maximum for these movies. It would be nice if the tooltips contained the defaults, and recommendations for another circumstance or two.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.