Log in

View Full Version : Multithreaded XviD - official thread


Pages : 1 2 3 4 5 6 7 [8] 9 10 11

clsid
1st December 2008, 23:39
1.3.0 doesn't have anything that 1.2.0 does not have. It did not even exist a few days ago.

squid_80
2nd December 2008, 03:53
I don't know where this 1.3.0 stuff comes from at all, I can't see any 1.3.0 branch and CVS HEAD is marked as 1.2.1.

1.2.0 x64 should not be used since it has serious bugs as noted on the mailing list. Isibaar checked in a quick fix but it's untested and from looking at it there's still bugs.

avivahl
2nd December 2008, 04:23
I don't know where this 1.3.0 stuff comes from at all, I can't see any 1.3.0 branch and CVS HEAD is marked as 1.2.1.The CVS HEAD is marked as 1.3 (since 3 days ago)... http://cvs.xvid.org/cvs/viewvc.cgi/xvidcore/src/xvid.h?view=log&sortby=date&pathrev=HEAD

The release-1_2-branch is already at 1.2.1: http://cvs.xvid.org/cvs/viewvc.cgi/xvidcore/src/xvid.h?view=log&sortby=date&pathrev=release-1_2-branch

1.2.0 x64 should not be used since it has serious bugs as noted on the mailing list. Isibaar checked in a quick fix but it's untested and from looking at it there's still bugs.
Looking at http://list.xvid.org/pipermail/xvid-devel/2008-December/005985.html
I wouldn't say "serious bugs"... They both said: "although it's possible this won't cause any problems" and "It didn't seem to cause any problems but that may be compiler-dependent and because we're not using double calculations".


@alexins, could you please compile us a [x86+x64] 1.2.1 version using VS8+sp1? (just to be on the safe side)

olnima
2nd December 2008, 13:02
Something is wrong with the newest xvid-build (x86-build from 2.12.2008) on xvid.ru:

During installation-process, after selecting the language I get the following message:

Can not expand "pf64" constant on this version of Windows

(WinXp32 SP3)

x64-build does nor work either (as expected with my Vers. of Windows)

Olnima

Vindarath
2nd December 2008, 13:22
I get the same error aswell with that build.
Running Vista sp1 32bit

squid_80
2nd December 2008, 13:41
Looking at http://list.xvid.org/pipermail/xvid-devel/2008-December/005985.html
I wouldn't say "serious bugs"... They both said: "although it's possible this won't cause any problems" and "It didn't seem to cause any problems but that may be compiler-dependent and because we're not using double calculations".
Andrew = Me. :D

It's possible it won't cause any problems, but also very likely it will when xvid is used with other programs such as virtualdub, avisynth etc. The problem cannot be mitigated by using a different compiler. The latest cvs additions should fix the remaining issues.

sneaker_ger
2nd December 2008, 16:41
Is the chroma optimizer fixed in XviD 1.2 final?

squid_80
2nd December 2008, 17:01
Doesn't look like it.

olnima
2nd December 2008, 17:53
What's wrong with the chroma optimizer?
Is it really buggy or could the effect be better (like f. example the old AQ)?

Olnima

squid_80
2nd December 2008, 18:11
It's not completely broken in the sense that it's going to make a huge ugly mess of your encodes, it just doesn't work exactly as it's meant to (http://forum.doom9.org/showthread.php?p=1120914#post1120914).

Who knows, it might actually be meant to work that way. Gzarkadas said he got better compression with the fixed version though.

alexins
2nd December 2008, 20:34
Something is wrong with the newest xvid-build (x86-build from 2.12.2008) on xvid.ru:

During installation-process, after selecting the language I get the following message:

Can not expand "pf64" constant on this version of Windows

(WinXp32 SP3)

x64-build does nor work either (as expected with my Vers. of Windows)

Olnima

I am sorry!
I made a mistake in the installer. After three hours publish an updated version of.

Sharktooth
2nd December 2008, 21:42
any builds with VAQ yet?

len0x
2nd December 2008, 21:45
or MTK profiles to that matter?..

alexins
2nd December 2008, 23:52
XviD-1.3.0 (CVS)-081203.01.28-VAQ x86/x64 (http://www.xvidvideo.ru/content/view/457/1/) (MSVC9sp1)

WIN64 XMM6/XMM7 bench and asm optimization patch by Andrew Dunstan; fix installer.

or MTK profiles to that matter?..
In the nearest assemblies I will try to add MTK profiles.

alexins
3rd December 2008, 04:27
XviD-1.3.0 (CVS)-081203.06.15-VAQ-MTK x86/x64 (http://www.xvidvideo.ru/content/view/460/1/) (MSVC9sp1)

add MTK profiles ;)

olnima
3rd December 2008, 07:45
...thanks !

Lugia25000
3rd December 2008, 09:06
Can you make always a x86 version without installer on www.xvidvideo.ru? and with new encraw?

I hope you work at the bugs from the new encraw version.

Thank you for all new improvements in Xvid!

Sharc
3rd December 2008, 09:07
Thanks for the new version.
Is VAQ optimized for H.263? Does VAQ have a benefit with custom matrices or is it not recommended?
Secondly, when I select e.g.the Home Theatre Profile, some options are greyed out but remain selected (ticked), like the MPEG matrix or the Quarter Pixel. Do the greyed out parameters still apply, or are they overwritten by the profile selection?

Gromozeka
3rd December 2008, 10:21
Alexins
Земляк, извини чт опишу на русском, с английским плохо, но не мог бы ты добавит ьв XviD также профили от DivX-а, так как это сделано у Jawor-a:
http://jawormat.republika.pl/xvid.html
А то очень удобно, приходится перескакиват ьс твоего билда на его только из-за профилей

alexins
3rd December 2008, 11:56
Gromozeka, сделал! (did!)

XviD-1.3.0 (CVS)-081203.13.35-VAQ-MTK x86/x64 (http://www.xvidvideo.ru/content/view/463/1/) (MSVC9sp1)

add Divx profiles (Jawor's (http://jawormat.republika.pl/xvid.html))

http://s48.radikal.ru/i120/0812/55/79edd8fd69bet.jpg (http://radikal.ru/F/s48.radikal.ru/i120/0812/55/79edd8fd69be.png.html)

Taurus
3rd December 2008, 13:18
XviD-1.3.0 (CVS)-081203.06.15-VAQ-MTK x86/x64 (http://www.xvidvideo.ru/content/view/460/1/) (MSVC9sp1)

add MTK profiles ;)

Great!

Gromozeka
3rd December 2008, 13:59
alexins
Спасибо, родной, обрадовал то как
Спешу поделиться новостью с народом
:thanks:

clsid
3rd December 2008, 15:04
xvid.ax depends on msvcr80.dll. Would it be possible to make a static linked build?

Sharktooth
3rd December 2008, 15:42
yeah it would be great

Lenchik
3rd December 2008, 20:42
when I select e.g.the Home Theatre Profile, some options are greyed out but remain selected (ticked), like the MPEG matrix or the Quarter Pixel.
I dont know if it is a bug in compile or in something else, but videos made through vfw interface and home profile (with packed bitstream greyed out (not changeable)) are using packed bitstream actually (as Gspot says). Does it supposed to be so? Alexins' build 1.2.0 used.

len0x
3rd December 2008, 22:39
Can you make always a version without installer?


I second that as I want to rebuild the installer anyway...

talen9
3rd December 2008, 23:12
I dont know if it is a bug in compile or in something else, but videos made through vfw interface and home profile (with packed bitstream greyed out (not changeable)) are using packed bitstream actually (as Gspot says). Does it supposed to be so? Alexins' build 1.2.0 used.

Packed bitstream is an intrinsic "feature" of home profile. The fact is that is greyed out because you can't modify it, unless if you want that the generated encodes *will not* be compatible with the profile.

That said, there was (at least in the 1.2.-127 versions) a GUI glitch, meaning that the state of the greyed out checkbox was not correctly updated: if you changed your profile to home coming from one where the checkbox was enabled, it would have been greyed out AND enabled, but it would show as disabled if coming from a profile where it was disabled ... sorry if I'm not being very clear :o

I just checked, and in the 1.2.0 alexins build this behaviour is still the same; dunno if it is something that depends on the widget or if something can actually be done in the code .... but, as I said, it's only a (very) minor glitch.

Jawor
3rd December 2008, 23:53
Can you make always a x86 version without installer
Here (http://jawormat.republika.pl/xvid.html) is a 32-bit 1.2.0 build for those of us who don't like installers ;)

It has DivX Profiles and VAQ. There's no encraw though...

Lugia25000
4th December 2008, 00:07
This Build is old and has anything different with the VAQ Version from Dark Shikari.
The Results are different.

alexins builds are newer and the results with Dark Shikaris VAQ Version are the same, but alexins build is faster and has many improvements.

Jawor
4th December 2008, 00:10
This Build is old and has anything different with the VAQ Version from Dark Shikari.
My 1.2.0 build is just a few hours old :)

You can download a ZIP with alexins' 1.3.0 binaries here (http://jawormat.republika.pl/Unpacked.zip).

Lugia25000
4th December 2008, 00:17
sorry, my mistake
Then... thank you :)

You can download a ZIP with alexins' 1.3.0 binaries here (http://jawormat.republika.pl/Unpacked.zip).

Big thx. ^^

olnima
4th December 2008, 09:58
Packed bitstream is an intrinsic "feature" of home profile. The fact is that is greyed out because you can't modify it, unless if you want that the generated encodes *will not* be compatible with the profile.

That said, there was (at least in the 1.2.-127 versions) a GUI glitch, meaning that the state of the greyed out checkbox was not correctly updated: if you changed your profile to home coming from one where the checkbox was enabled, it would have been greyed out AND enabled, but it would show as disabled if coming from a profile where it was disabled ... sorry if I'm not being very clear :o

I just checked, and in the 1.2.0 alexins build this behaviour is still the same; dunno if it is something that depends on the widget or if something can actually be done in the code .... but, as I said, it's only a (very) minor glitch.

...but - Is it right that Home Theater Profile can NOT have more than 1 b-frame? Because this is completely not greyed out...

Olnima

talen9
4th December 2008, 11:56
That's a point that's not entirely clear to me too.

I think that the Divx5 certification (to whom the "home" profile should conform) asserts that "one B-frame" encodes have to be correctly reproduced; "two B-frames" encodes should anyway work on most DivX media players, in my experience, but they could actually be out-of-spec.

kandrey89
4th December 2008, 12:09
Dark Shikari:
So is there a v1.2.1 with VAQ patch?
Could someone compile it?

From what I remember the VAQ improved quality quite a bit!
Thank you Dark Shikari for the code.

Sharc
4th December 2008, 20:12
You may visit:
http://www.koepi.info/

Jawor
4th December 2008, 21:18
A build with VAQ and DivX profiles has just arrived on my site (http://jawormat.republika.pl/xvid.html).

I added *.reg files that delete XviD entries from the registry (there's no "real" installer/uninstaller with my builds).

len0x
4th December 2008, 21:23
A build with VAQ and DivX profiles has just arrived on my site (http://jawormat.republika.pl/xvid.html).


Can I ask for MTK profiles built in as well please?

Jawor
4th December 2008, 21:28
Sure. Where can I find the patch?

olnima
4th December 2008, 21:38
Can I ask for MTK profiles built in as well please?

What's wrong with Alexins Builds? He made a build with MTK and one with divx - profiles.

Olnima

len0x
4th December 2008, 21:53
Sure. Where can I find the patch?

Here: http://celticdruid.no-ip.com/source/xvid.diff

@olnima

Nothing wrong - I just would like to get 1.2.1 binaries without installer.

Jawor
4th December 2008, 21:58
Thanks, I'm looking into it ;)

kandrey89
4th December 2008, 22:10
thank you, earlier when I posted, koepi didn't have any v1.2.1 versions, he still had the v1.1.3 and v1.2-127, so he must have updated it within the last few hours, COOL!

Jawor
4th December 2008, 22:27
I just added a build with MTK profiles.

Ninjers
5th December 2008, 00:31
I installed Koepi's binaries but VDubMod nor VDub will detect it. What do I do now? Install 1.13 and replace the DLLs with the new ones?

Koepi
5th December 2008, 07:01
ninjers:

what os are you using?

I can currently only check within win xp sp3, no vista around here - my 64bits vista machine is still somewhere between the boxes from my move to a new place...

cheers
koepi

turbojet
5th December 2008, 08:50
koepi:
Thanks for the new build. After some testing with this (http://www.koepi.info/Xvid-1.2.1-VAQ-04122008.exe) build it appears that VAQ isn't being enabled with both my custom settings and default with adaptive quantization checked. This was checked with ffdshow OSD frame mean quantizer. Both of jawor's 1.21 builds and alexin's latest 1.30 build have working VAQ. Would you mind looking into it?

olnima
5th December 2008, 11:41
I installed Koepi's binaries but VDubMod nor VDub will detect it. What do I do now? Install 1.13 and replace the DLLs with the new ones?

No Problem here with vfw under XP-SP3.

Olnima

Audionut
5th December 2008, 13:42
No problems here on vista 64bit.

Koepi
5th December 2008, 15:20
@turbojet:

Will look into that this weekend. There is a trapdoor in Dark Shikari's first patch which directly returns without doing anything, and I'm sure that I didn't apply these lines. I'll try his newer version I saw in the according thread again.

Anyhow, it _does_ change something if you activate it. While in my test-encode file size / bitrate stayed the same, the md5 still changed. That might be due to indicating adaptive quantization in the bitsream headers though.

Well, anyhow, I'll look into it.

Cheers
Koepi

Sharktooth
5th December 2008, 16:48
did the api change between the old 1.2 builds and actual 1.2.x /1.3 versions?
if not the new xvid.dll should work with encraw without problems...