Serious problems when using Koepi's xvid 1.0 beta3 (solved @ least)

[Seimour]

Several problems, when using this codec such as:
If I use AS @ L5, I don't know why but it produced enormous files on 2nd pass, even I had indicate the size!
But if I use (Unrestricted) the size is matched but the average fps get down from 25 (original) to 18.
I've done all of them with the default options, so I can't understand why is this happening.
I'll try to add some pictures, if I find a place where put them :(
Well I'll have to find a place somewhere..
Bye fellas

[Koepi]

Seimor:

since you're the only one reporting this and several posters here use AS @ L5 according to their reports, it must be something with your setup.

Hit the "Load defaults" button once more please.

Sometimes users forget that the size is in KB, not in bytes. Some mistake kb for being bytes.

Regularly, users mistake "target size" and "target bitrate" - it's changeable, so make sure that the value you enter makes sense according to what the button shows.

Make sure to read the xvid-1.0 guide from doom9 again.

Regards
Koepi

[Seimour]

Ok, I'll try with your new beta if I found any problem (wish me luck) :p
By the way, I didn't realize that now the movie size was in KB, I didn't look it and thought that it was like in koepi's-24062003. I'm sorry for not having payed too much atention.
Thanks for answering Koepi!!

[Koepi]

Hu? It is and was kb before? Nothing changed in taht matter, my point was that if you hit that button it will change between bitrate and size wanted. And also, I saw people mistaking the size desired for beeing MBs or even just bytes.

Regards
Koepi

[Seimour]

Fantastic, now it works fine, the only problem is that if I continue playing movies using ffdshow the movie doesn't play fluently, it loses frames. Then I began to read other people's posts (should I have done this b4?) :cool: and I realized that this would be solved if I played the movie using XviD instead of ffdshow.
But know there's only one stupid question to make you koepi, ;) how can I make it to not flip the image on every movie I play? perhaps for next rc2 should be a great idea to create a button on "decoder properties" called "Save as default" or "save as profile.."
Well I'll keep an eye on it, bye Koepie & thanks for your time :D

[sysKin]

Read some more and you'll discover that it's been fixed very recently - you can even download new directshow decoder that doesn't flip anymore :)

Have fun,
Radek

[Leak]

Originally posted by sysKin
- due to popular demand, you can disable fast-first-pass if you want to
- encoder will automatically adjust your overflow and min quant so that it doesn't make stupid mistakes

Ahem - sorry for hijacking an unrelated thread here, but... w00t! :)

By the way - did your decoder fixes already make it into CVS? The last few XviD builds from Gamr that I tested all shipped with a non-working (read: the installer already reported an error when registering it, and manually registering it didn't help either) DirectShow decoder...

EDIT: well, I just wiped XviD from my machine and installed Gamr's latest Pentium 4 build - it reported no error with the decoder, but it doesn't work either; while I can view XviD AVIs, Graphedit shows that it's actually the AVI Decompressor being used to decode the file - if I'm not completely wrong that'd be the VfW wrapper, right?

(Of course, installing your decoder update fixes this, but I guess if Gamr's builds shipped with a working decoder it wouldn't hurt either... :))

EDIT2: I guess I spoke too soon - using your xvid.ax4.zip decoder in conjunction with Gamr's XviD-pentium4-200401312010.exe gives strange colors when I force the colorspace to YV12 in the decoder, but will work fine if I use YUY2... :confused:

I guess I'll try the PPro and 486 builds, maybe the compiler screwed up some optimization?

EDIT3: Okay, so it doesn't seem to be b0rked compiler optimization, but some bytes being swapped:


DirectShowSource("LastExile_01.avi",fps=25.0)


exhibits the same problem (well, duh...), but


DirectShowSource("LastExile_01.avi",fps=25.0)
SwapUV()


fixes that... I guess that means that the bug isn't in your decoder (as it works perfectly in Niltze), but somewhere in the core...

Hope this helps... :)

np: Static - Waking Up (Flavour Has No Name)

[Koepi]

While sysKin fixed dshow like suggested by sh0dan and then some more, gruel fixed the core to make more sense of the internal colour spaces.

So we have to sync that again - but then, it's your fault when you use stuff right away from CVS ;)

The fix will come tomorrow I think (if there _is_ something wrong).

Regards
Koepi

[Leak]

Originally posted by Koepi
While sysKin fixed dshow like suggested by sh0dan and then some more, gruel fixed the core to make more sense of the internal colour spaces.

So we have to sync that again - but then, it's your fault when you use stuff right away from CVS ;)

Yeah right - that's what one gets for being nosy and wanting to see how turning off fast first pass will work in future releases... *cries* :p

The fix will come tomorrow I think (if there _is_ something wrong).

Well, if there isn't anything wrong with XviD I guess I'll better have my eyes checked ASAP... ;)

np: HIM - Disco Lips (Certified Dope Vol. 4: Babylon's Burning)

[Seimour]

If I use turbo on the first pass, it would be reflected on the quality of the movie?
Is there a great diference between using it or not?
Is a good idea to use it also on the 2nd pass?
Well I think that I don't have more doubts (hope), bye! :p
Edit ..
Well I've been looking around and I haven't been able to find where can I get a new version of ffdshow which give support to XviD 1.0, you know, to avoid fliping the image and jumping/freezing/loosing of frames. Normally I get them here:
ffdshow (http://athos.leffe.dnsalias.com/)

[Koepi]

Seimor:

read a little bit around in the threads you find on the first page here. You'll find the answers you're looking for there discussed to the finest details.

The search button also works like charme, it's sure not broken - and that would be a good starter to comply to the forum rules which you had to agree to when signing up for this board ;)

Koepi

[sysKin]

Just let me explain what's going on - Gamer has automatic build system on the core and VfW libraries, but he can't compile directshow under linux. As a result, he just adds a pre-compiled directshow to his installer.

Now, ever since gruel's change, they are no longer compatible with each other. The same applies to my directshow build.

If I'm not mistaken, directshow has to be compiled again, with new xvid.h, done :D

Radek

[Seimour]

It won't happen anymore, from now on I'll read all the forum rulez b4 writting any post. Enough for today, let's relax for tomorrow.
Goood night!