Is Xvid DEAD?

[slicemaster102]

Well,
This is just a simple question but it seems warranted. Is Xvid DEAD? It doesn’t seem that development is active anymore and the codec seems to have stalled out. The newest release is a beta (Xvid 1.1.0 Beta 2) that was released on April 4 of this year. Nothing has been released since. No new member can sign up and the website seems out of date at best, although abandoned is probably more accurate. What is going on? Xvid seems to be more popular then DivX at this point (tons of new internet content available in Xvid) but nothing is happening.

Signed,
Slice

[SeeMoreDigital]

Have you read any of the XviD threads Slice?

XviD is still being worked on and refined.... I have a (beta2) build dated "16 Oct 2005" installed in my PC right now!


Cheers

[mod]

take a look here (http://celticdruid.no-ip.com/xvid/)

[Suchy]

Moreover (IMHO) XviD reach almost maximum of MPEG4 ASP, so whot do You want to improve?

[Kopernikus]

Moreover (IMHO) XviD reach almost maximum of MPEG4 ASP, so whot do You want to improve?

I don`t think so. There is much room to improve XviD. For example read the further Improvements Thread here:

http://forum.doom9.org/showthread.php?t=101346

Other things to improve: Trellis for I-Frames, Psychovisual Enhancements, more RD- Decisions, better ME algos (for example umhex), ....

[IgorC]

XviD is still being worked on and refined.... I have a (beta2) build dated "16 Oct 2005" installed in my PC right now!
Cheers

All tests as SSIM and OPSNR say that there wasn´t quality impovements since beta 1 (january 2005). There is no visual diference between version of17 oct and january. Only bugfix, misc. changes. I think developers trying to get stable realese and don´t introduce new features those may be case of a new bug.

[guada 2]

This codec is not die.
I think, it is necessary to let the time to the developers to prepare the land.
Patience is art to wait.

[slicemaster102]

Have you read any of the XviD threads Slice?

XviD is still being worked on and refined.... I have a (beta2) build dated "16 Oct 2005" installed in my PC right now!


Cheers
Sorry, it was late at night and I wasn’t really paying attention to what I was doing.
Anyways, the reason I ask is simply because the XviD.org (official Xvid homepage) looks to be abandoned. Thanks all for the info.

Also: I am currently looking for a build that will run properly on my new Windows XP Professional x64 Edition box. I usually run “XviD-1.1.0-Beta2-04042005” from Koepi on my XP Pro SP2 boxes but this build seems to have a problem on x64 edition. The codec actually operates fine but the codec configuration doesn’t function under x64 edition. Where are you guys getting your builds (if you can say)? Are any of them in a nice install/uninstall package like Koepi’s? Are they fully functional (can I access the codec configuration panels) under x64 edition? Thanks and any help would be great.

Thanks,
Slice

[Koti]

take a look here (http://celticdruid.no-ip.com/xvid/)

Xvid 64 bit (http://forum.doom9.org/showthread.php?p=651943#post651943) discussion and builds :search:

Ooops looks like links to 64bit builds are broken :(

[slicemaster102]

Xvid 64 bit (http://forum.doom9.org/showthread.php?p=651943#post651943) discussion and builds :search:

Ooops looks like links to builds are broken :(
how about just the latest 32-bit builds? like i say, the codec operates fine, i just can't access the configuration panels.

thanks,

[Koti]

how about just the latest 32-bit builds? like i say, the codec operates fine, i just can't access the configuration panels.

thanks,


see post #3 in this thread

[slicemaster102]

see post #3 in this thread
Do the exe's on that page have nice install/uninstall features like the package distributed by Koepi?

NOTE: I went ahead and D/L the XviD.cvs.head.exe (dated 10/17/2005) and I still have the same problem (plus the install/uninstall package isn’t nearly as nice as with koepi's builds). Either way, here are the error messages it gives me when using either build.

When I try to load the decoder configuration panel it says "error loading xvid.ax"
When I try to load the encoder configuration panel it says "error loading xvidfw.dll"

Any ideas on what is causing the problem? Both builds work on my SP2 box but this problem persists on my x64 box. Is it a problem with compatibility? If so why not fix it? This is the first software compatibility issue I have run into on x64. DivX (32-bit) works fine in x64. NOTE: the codec actually works fine other then the problems mentioned above.

Slice

[squid_80]

When I try to load the decoder configuration panel it says "error loading xvid.ax"
When I try to load the encoder configuration panel it says "error loading xvidfw.dll"

Any ideas on what is causing the problem? Both builds work on my SP2 box but this problem persists on my x64 box. Is it a problem with compatibility? If so why not fix it? This is the first software compatibility issue I have run into on x64. DivX (32-bit) works fine in x64. NOTE: the codec actually works fine other then the problems mentioned above.

Slice
It's a problem with the installer. See here. (http://forum.doom9.org/showthread.php?p=635116#post635116)

[SeeMoreDigital]

After de-installing your older version of XviD (via "Add or Remove Programs") did you re-boot your PC before installing the new version of XviD?

If not.... try again!


Cheers

[slicemaster102]

It's a problem with the installer. See here. (http://forum.doom9.org/showthread.php?p=635116#post635116)

IT WORKED! Thanks! This thread should probably be stickied or something. Anyways, all I had to do was change the path of those shortcuts and it worked. Thanks!

Slice

[nightrhyme]

Have you read any of the XviD threads Slice?

XviD is still being worked on and refined.... I have a (beta2) build dated "16 Oct 2005" installed in my PC right now!


Cheers

Could you please provide a direct link. I don't see any XviD 16.10.05 on the page MOD linked to

[SeeMoreDigital]

Could you please provide a direct link. I don't see any XviD 16.10.05 on the page MOD linked toHere you go: -

http://www.aziendeassociate.it/./cd///XviD.cvs.head.exe


Cheers

[unskinnyboy]

Could you please provide a direct link. I don't see any XviD 16.10.05 on the page MOD linked to
If you look at the title of the page mod linked to, it says 'XviD, mencoder & Other stuff moved'. Then you click on the XviD link in the navigation bar and go here (http://www.aziendeassociate.it/cd.asp?dir=/). Visually scrolling down a bit, you get this (http://www.aziendeassociate.it/cd///xvid.cvs.head.2005.10.16.7z). You can bookmark that page.

EDIT: SMD was faster ;p

[mod]

If you look at the title of the page
:D .....

[Doom9]

Have you read any of the XviD threads Slice?Unfortunately that doesn't seem to be going anywhere.. unless development suddenly moved away from all forums and mailing lists to a place I'm not aware of.

[Kopernikus]

Is there no active developer left? What happened to suxen_drol?

[DeathTheSheep]

Suxen_drol is up and about, or so I presume based on his/her contributions to XviD (and doom9's forum), the latest of which occured rather recently.

[SeeMoreDigital]

I guess it would be useful to have some form of confirmation either way about who is currently working on XviD and/or is capable of continuing the work!

With this in mind, can anybody produce names (or contact details) of people they know who are currently involved in the XviD project?


Cheers

[sysKin]

I guess it would be useful to have some form of confirmation either way about who is currently working on XviD and/or is capable of continuing the work!

With this in mind, can anybody produce names (or contact details) of people they know who are currently involved in the XviD project?


OK I might as well reveal that I have a plan (tm). Starting next week, I'm on summer vacations. Until March in fact. I plan to go back to XviD and continue some development.

Things I want to do:
- finish any remaining issues with 1.1 and release it. ASAP.

- commit Kopernikus' lambda-for-plugins-thingy, and probably remove adaptive quantization. The last depends on whether someone (me?) rewrites lumimasking plugin to use lambdas rather than quantizers.

- see what other things can be fixed. DX50 userdata mess comes to my mind

- investigate some higher quality possibilities. After my recent experience with motion finding, I conclude that two-pass ME *might* be an unexpected win

- see if and how XviD can be multi-threaded. This is mostly fun & self-education, but hopefully multicore/multicpu/ht testers will volunteer to help me. I have several ideas that might produce impressive results, at least in theory and at least on amd's multicore.

Wish me luck if you want to see it happen ;)

[ChronoCross]

you the man sysKin. I look forward to seeing the changes. Plus I'd love to help out testing hyperthreading speed increases.

[Teegedeck]

OK I might as well reveal that I have a plan (tm). Starting next week, I'm on summer vacations. Until March in fact. I plan to go back to XviD and continue some development.
:) Many, many thanks. Devoting vacation-time to XviD means showing real spirit.

- commit Kopernikus' lambda-for-plugins-thingy, and probably remove adaptive quantization. The last depends on whether someone (me?) rewrites lumimasking plugin to use lambdas rather than quantizers. Now, I would resent (;)) that if it means going the x264-way concerning AQ... The recent 'AQ' versions of x264 are really not quite satisfactory Perhaps it would be good to connect AQ with lambda-manipulation, but at least current AQ is an effective tool in two-pass. Edit: Maybe rather implement it as an additional option that can or can not be used in conjunction with AQ?

[Doom9]

well, good luck. Count me as one who might volunteer every now and then to test multithreaded builds.. my X2 needs some work.

[Didée]

syskin, if I'd manage to get vacation as long as well, I'd jump in a plane, and help with doing all the shopping, cooking and washing for you :D

[olnima]

sysKin, are You married? If I wouldn't be, You would be my first choice... :D :D :D

Olnima

[guada 2]

" sysKin, are You married? If I wouldn't be, You would be my first choice... "

olnima
it is not necessary to be press, because work does not have to begin yet. :D

But, I wish him good luck. :)

[bond]

go sys go! ;)

[IgorC]

I can't wait to test it. God bless Syskin's inspiration. :)

[Kopernikus]

Now, I would resent (;)) that if it means going the x264-way concerning AQ... The recent 'AQ' versions of x264 are really not quite satisfactory Perhaps it would be good to connect AQ with lambda-manipulation, but at least current AQ is an effective tool in two-pass. Edit: Maybe rather implement it as an additional option that can or can not be used in conjunction with AQ?

The principle of the x264 AQ is completely different from the XviD AQ. x264 throws bits at flat blue blocks, xvid takes bits from very dark or very light blocks.

You can implement both with lambda as well, and then you have the advantage that it doesnt cost bits.

[yaz]

@sysykin
if u want some torture tests, just call me :)

the bests
y

[Teegedeck]

The principle of the x264 AQ is completely different from the XviD AQ. x264 throws bits at flat blue blocks, xvid takes bits from very dark or very light blocks.

You can implement both with lambda as well, and then you have the advantage that it doesnt cost bits.
Certainly. Well, as it seems I'm the only one who thinks that quantizing MBs slightly differently is worthwhile, that's that then. Out of sheer curiousity; sysKin, will 'conventional' AQ vanish from Ateme's codec, too?

[bond]

Certainly. Well, as it seems I'm the only one who thinks that quantizing MBs slightly differently is worthwhile, that's that then. Out of sheer curiousity; sysKin, will 'conventional' AQ vanish from Ateme's codec, too?i also like aq, when i look at what ateme's avc codec does with aq with walls its pretty good imho

btw x264's aq not only throws bits at blue areas, but also dark areas. it was written for fixing the blue block issue only and also should only be seen as fix for this and not more

[unskinnyboy]

Thanks a lot sysKin - excellent news. Also count me in as yet another tester for testing the multi-threading/HT builds, when they are ready.

[charleski]

i also like aq, when i look at what ateme's avc codec does with aq with walls its pretty good imho
Are you talking about the Nero encoder or are you teasing us again by talking about ateme's unreleased one? :)

[sysKin]

Well, as it seems I'm the only one who thinks that quantizing MBs slightly differently is worthwhile, that's that then.
I wouldn't say you're the only one, the ability to have AQ is there for a good reason I guess. But AQ is messy, takes bits, limits possible macroblock modes and can only be made on macroblocks as a whole. Besides, ASP's quantization - being linear - has huge steps on higher qualities (quants 1-2-3-4). That's unlike AVC.

Lambda, with its ability to save on motion vectors (VHQ) and drop coefficients (trellis) should be able to modulate quality quite a bit.
Out of sheer curiousity; sysKin, will 'conventional' AQ vanish from Ateme's codec, too?How can I know that :0 ;)

[suxen_drol]

Suxen_drol is up and about, or so I presume based on his/her contributions to XviD (and doom9's forum), the latest of which occured rather recently.
yep, i am here. about a week ago, i received a similar email to this thread, who i assume now was the same person. here was my brief response, however he never responded:

> Is Xvid DEAD? Has the project stopped devolopment?
It doesnt look like much is being done anymore.

read response at: http://forum.doom9.org/showthread.php?t=102675

whilst it is true that the development pace has slowed down,
i feel this is only normal given that the project started four
years ago and has reached a level of maturity. your suggestions
and code patches to improve xvid are certainly welcome!

note that we had planned to release xvid v1.1.0 last month,
however this is now likely to happen in december (when i hope
to have some free time).
syskin, there are only two outstanding patches for the release: the name/version patch, and gomgom's recent super-pedantic-sanity patch. when do u plan to make the release? i can probably spare an hour to if u need help.

anyway, i have to agree with the original poster. god bless syskin! and while iam at it, david palmer for president.

-- pete

[sysKin]

syskin, there are only two outstanding patches for the release: the name/version patch, and gomgom's recent super-pedantic-sanity patch. when do u plan to make the release? i can probably spare an hour to if u need help.

Well my my current future plans consist of one exam in 12 hours, another in 36h, and then, in no particular order (listing computer-related stuff only): civ4, catching up work, buying a silent cpu cooler to survive summer and xvid-ing.

I suppose this might mean releasing XviD 1.1 any time, how about this weekend. I remember there was one minor thing in GomGom's patch that I didn't expect, and I wanted to check it out. No need to block 1.1 for this though, can be fixed later (if there really is a need to fix anything).

@all: is there a particular problem with current xvid 1.1 that should be fixed before final release? If so, say now.

[Sharktooth]

Yes... well, it's not a problem but a request: add the "insane" trellis stuff :D

[sysKin]

Yes... well, it's not a problem but a request: add the "insane" trellis stuff :D
Easy stuff ~ :D

[IgorC]

I don´t know if ateme avc psy apliable to xvid. Their psy is different from x264 AQ: quantizers on most part of frame is lower than without psy and to keep bitrate there are optimal inter-p_skip (1-3 bit) on dark area.

[len0x]

How about adding MTK profiles from celtic_druid to official XviD build?

[Sharktooth]

oh, and also the DXN Hi Definition profile :)

[IvS]

sysKin: this (http://forum.doom9.org/showthread.php?t=86180&page=2) is an issue that needs to be fixed. Also note, HD encoding of short clips, for example 10 or 20 seconds, results in very much lower bitrate than stated. The longer the length, the more accurate it is. A clip of several minutes has an accurate bitrate.

[JarrettH]

Well someone had to make the thread :P

I feel like that person in class who didn't want to raise their hand in class to ask a silly question. You've just created the thread everyone is wondering about :) At least there won't be any further threads about it! :cool:

[raeltheimperialaerosolkid]

ehm...Syskin
Maybe another silly question...
There were some doubt
here (http://forum.doom9.org/showthread.php?p=737709#post737709)
and
here (http://forum.doom9.org/showthread.php?t=102907)
about the DXN profiles...

[celtic_druid]

Probably covered on the previous page by "see what other things can be fixed. DX50 userdata mess comes to my mind"

[Didée]

sysKin: this (http://forum.doom9.org/showthread.php?t=86180&page=2) is an issue that needs to be fixed.
No, it is not. (answer (http://forum.doom9.org/showthread.php?p=739530#post739530))

[raeltheimperialaerosolkid]

Probably covered on the previous page by "see what other things can be fixed. DX50 userdata mess comes to my mind"

Well...maybe.
In the meantime I'll stay on the hardrock stable 1.0.3....:D

[sysKin]

Probably covered on the previous page by "see what other things can be fixed. DX50 userdata mess comes to my mind"
No, that's not related to DivX profiles.

Weren't we going to remove them completely?

Anyway, the answer is BOOOO----RIIIINGGG---- :P

[celtic_druid]

Weren't their some claims that when the DivX user data string was changed that it broke compatibiltiy with some standalones? DivX503b1393p instead of DivX999b000p.

In the current CVS the DXN profiles were I think renamed. DXN HT is just Home Theatre, but I never did a compile.

[bond]

In the current CVS the DXN profiles were I think renamed. DXN HT is just Home Theatre, but I never did a compile.why?

i think dxn profiles are good to have,cause it shows how xvid rules dxn :D

[celtic_druid]

Profiles are still there, just renamed:
Home Theatre NTSC, Home Theatre PAL, Cinema Plus NTSC, Cinema Plus PAL

Home Theatre = DXN Home Theater
Cinema Plus = ? Looks a bit like my MTK profiles. For instance qpel can be enabled.

So it still shows how XviD rules DXN and how they can spell theatre.

[stephanV]

uhm, both theater and theatre are correct :p

[suxen_drol]

uhm, both theater and theatre are correct :p

i tend to disagree!
perhaps we need i18n for british and american english.

[Elias]

XviD is not dead. However, progress is very slow; the 1.1 stable version was going to be released at least a month ago.

[Anonymouses]

i tend to disagree!
perhaps we need i18n for british and american english.

From the Cambridge dictionary:

Definition
theatre (BUILDING) Show phonetics
noun [C]
1 UK (US theater) a building, room or outside structure with rows of seats, each row usually higher than the one in front, from which people can watch a performance or other activity:
the Lyceum Theatre
a lecture theatre

Both are correct. :p

[708145]

I wouldn't say you're the only one, the ability to have AQ is there for a good reason I guess. But AQ is messy, takes bits, limits possible macroblock modes and can only be made on macroblocks as a whole. Besides, ASP's quantization - being linear - has huge steps on higher qualities (quants 1-2-3-4). That's unlike AVC.

Lambda, with its ability to save on motion vectors (VHQ) and drop coefficients (trellis) should be able to modulate quality quite a bit.
How can I know that :0 ;)

what about combining lambda with the switch to another quant range?
using a downscaled CQM one could shift the q2-q4 range to q10-q20 which results in much smaller steps.

is this a stupid idea?

bis besser,
T0B1A5

[Kopernikus]

Thats like Didèes 6of9 Matrix works.

But AQ in ASP is very limited. The difference in quantizer of two Macroblocks can differ only by 2, so if you decrease the stepsize, you cannot modulate the quality enough.

And the dquant field (3bits per MB allowing -2:+2 change) is not entropy coded, so there is a overhead of 600 byte per frame (720x576) with AQ. AQ also blocks the 4mv mode.

In AVC AQ is not so limited.

[Manao]

And the dquant field (3bits per MB allowing -2:+2 change) is not entropy codedIf dquant == 0, it takes no bits at all ( it's kinda written alongside the mb type ) so it's entropy coded.

It blocks the 4mv mode only if dquant != 0. Which means it's tricky to decide whether to change a quantizer or not ( because the next block might need to be coded at a different quant with 4 mvs ).

Varying lambda is a better way to do AQ ( at least, easier ), though it might not allow that must variation either. And it might also become quite messy when it comes to changing the lambda of the trellis.

[DeathTheSheep]

As of yesterday, work has been started on the XviD 1.2 CVS.

Whaddya think? AQ gunna be up and running in 1.1 or 1.2?

Cheers

[Elias]

As of yesterday, work has been started on the XviD 1.2 CVS.

Whaddya think? AQ gunna be up and running in 1.1 or 1.2?

CheersI think it's awesome news. Since the work on the 1.2 CVS has been started, will we see the 1.1 Stable release anytime soon?

[len0x]

I take it 1.1 is not going to be released at all and things move on to 1.2 ?

[bond]

I take it 1.1 is not going to be released at all and things move on to 1.2 ?first of all someone has to start coding ;)
syskin? :D

[len0x]

well, I'd say since 1.1 release branch was created almost two weeks ago much coding is not expected :) So shall we just ask C_D to build from that and call it 1.1 final? :D

[SeeMoreDigital]

well, I'd say since 1.1 release branch was created almost two weeks ago much coding is not expected :) So shall we just ask C_D to build from that and call it 1.1 final? :DJoking apart.... I say yes, why not?!

[celtic_druid]

I could rename it, but I wouldn't feel comfortable so you will have to use your imagination with the last 1.1.x build I did.

[raeltheimperialaerosolkid]

The topic that issued the problem has gone forward :)

here (http://forum.doom9.org/showthread.php?p=737709#post737709)

It says that the "packed bitstream" in the DXN profiles wasn't disabled even if the user unchecked it manually. I don't know if it's a problem of some certain build or if it's a source problem...

My 2 cents...

;)

No, that's not related to DivX profiles.

Weren't we going to remove them completely?

Anyway, the answer is BOOOO----RIIIINGGG---- :P

[johnsonlam]

XviD is not dead. However, progress is very slow; the 1.1 stable version was going to be released at least a month ago.

Progress very slow is NOT a "serious" problem, I can wait. I know not much developers now, but IMO they should send some news to Doom9's Admin.

There're too many news around, I don't have time to surf every homepage, for video and audio news Doom9 is my best portal thanks :thanks:

Sometimes I did think being a bit commercial can push the software development faster, like DivX.

[loni_blues]

celtic_druid,

Just a little doubt:
xvid.cvs.release-1_1-branch.2005.11.24.7z and XviD.1.1.cvs.exe would be both the same and "final" 1.1 release?
Thanks a lot,
loni_blues

[celtic_druid]

Same files in both yes. Final? Not sure.

[tommy_vercetti]

Answer to the original question, YES

[boombastic]

why you say that?you can't say it without explain!

[nightrhyme]

Any news from Syskin ?

[sysKin]

Any news from Syskin ?
Like this? http://forum.doom9.org/showthread.php?t=104257

[gatekeeper_007]

This reminds me of some other songs -
XviD is still alive, Xvid is havin' sex... (do u remember?) :p
The truth is that XviD has made for some time now a lot of people talkin' about it all over the world, and they all say one : that codec rocks.
Now the right question should be : will XviD ever die? (this will be a new movie "Hard to die IV"
I can say that I've read all the previous replys... but my opinion is that u didn't shearch enought before postin' - and that u should be more patient.
"we can't always see the stars but they are always there"
:thanks: to Koepi for this great codec.
respect.
I can't wait for a new release :cool:

[Slitheen]

I do think that Xvid is going to be the one that gets left out in the not too distant future. With Divx and Nero Digital AVC codecs being the only ones still standing.

For this reason I've stopped using Xvid.

[Elias]

I do think that Xvid is going to be the one that gets left out in the not too distant future. With Divx and Nero Digital AVC codecs being the only ones still standing.

For this reason I've stopped using Xvid.Why? If anything, XviD is still extremely popular. DivX is only commercially more popular, XviD has a larger fanbase. As for MPEG-4 AVC, x264 will probably beat Nero's lead sooner or later in popularity and quality.

[Slitheen]

For me, it's a question of standalone support, and support that will be still there a few years from now.

[Elias]

For me, it's a question of standalone support, and support that will be still there a few years from now.You don't get it... MPEG-4 in the mp4 container, it's all the same :) Really, there's no real difference (because mp4 doesn't store fourCC in the same way as avi). Just encode XviD right and put it into mp4 and it will work just as good as any Nero Digital ASP in mp4 on any Nero Digital certified DVD player. Same thing with x264.

[Slitheen]

I'm sure you're right. But I'm the voice of the public remember. The only thing I understood from your last post was the MPEG4 bit ;)

[Elias]

What I meant was, it doesn't matter what MPEG-4 codec you use, as long as they're in the MPEG-4 container (mp4), they all work equally good everywhere. Unless of course you use the unrestricted profile features (like e.g. lossless AVC with x264), which far from all standalone DVD players support. x264 is just as much AVC as Nero Digital AVC is H.264 and same with XviD; it's not any less MPEG-4 Part 2 than DivX.

[Elias]

Progress very slow is NOT a "serious" problem, I can wait. I know not much developers now, but IMO they should send some news to Doom9's Admin.

There're too many news around, I don't have time to surf every homepage, for video and audio news Doom9 is my best portal thanks :thanks:

Sometimes I did think being a bit commercial can push the software development faster, like DivX.Did I imply that it was a serious problem? I'm using the XviD 1.2 CVS and it works great. So I don't see any real problem at all.

[ChronoReverse]

Well, the cat's out of the bag now. XviD AVC!

[Teegedeck]

Thanks for liking XviD but XviD is a team effort; please spare some nice thoughts for these core developers also:

Christoph Lampert
Pascal Massimino
Michael Militzer
Peter Ross
Radek Czyz

et.al.

[bond]

Well, the cat's out of the bag now. XviD AVC!xvid avc is not the official name till now, and of course its a totally different codec than xvid

[Kostarum Rex Persia]

But, why creating Xvid avc codec? What is purpose of that? We already use x264 freeware solution.

I think there is no need for xvid avc codec.

[mod]

But, why creating Xvid avc codec? What is purpose of that? We already use x264 freeware solution.

I think there is no need for xvid avc codec.
Where did I hear similar words? ..7zip.. :D

[charleski]

With Divx and Nero Digital AVC codecs being the only ones still standing.
Well for that to happen Ateme will need to finalise their current High Profile encoder and Nero will need to buy it! (And when you do buy it, give it a bit of advertising fanfare FFS, a lot of people are waiting to see what this encoder can do for themselves.)

[Selur]

But, why creating Xvid avc codec? What is purpose of that?
learning how avc really works,...

[skal]

xvid avc is not the official name till now, and of course its a totally different codec than xvid

?!

Bond, this is the second time i "?!" you today. Please, just refrain posting such assertive
*opinions*.

-Skal

[sysKin]

?!

Bond, this is the second time i "?!" you today. Please, just refrain posting such assertive
*opinions*.

Skal, if you guys are so secretive about it, and give no kind of informative announcement, "opinions" is all we've got left.

Bond was referring to information I gave him, which was the best information I had. If it was one year old and no longer true, you can't blame us for not guessing correctly.

[edit]Perhaps I should STFU about it, but I'd like everyone to know that I have some mixed feelings about the revelations - if a codec is referred to as "from XviD team", I have a weird feeling that people like me should not be finding out about it this way (this way == from rants that bond said something wrong because he was repeating after me).

[bond]

thanks for clarifying this syskin :)

[Doom9]

Would it make sense to give me a name for the comparison, the first time the codec was ever mentioned to the general public, then go back and change the name again? Imagine the confusion..

And to everyone: I'm beginning to suspect our Persian king is related to roccosi... remember him?

[bond]

i find "xavc" to be good :)

[sysKin]

Nah XviD2 is a great name, if the code goes opensource. I don't expect any confusion (stuff with "2" in their names are usually different).

[bond]

the "2" will not tell newbies that their xvid hardware player wont play their xvid "2" files ;)

[mod]

Just an idea.. what about X3MD? :D

[Yong]

How about 462x? :rolleyes:
(encode video at 462fps) :D

[Kostarum Rex Persia]

How about 462x? :rolleyes:
(encode video at 462fps) :D

??? That's impossible, at the moment. Even new Avivo Ati Converter can't encode at that high speed.

[Kostarum Rex Persia]

And to everyone: I'm beginning to suspect our Persian king is related to roccosi... remember him?

Are you thinking on me? Why you think that I am related to someone called roccosi, I even never heard for him!!!

[Yong]

??? That's impossible, at the moment. Even new Avivo Ati Converter can't encode at that high speed.
LOL, forget the new AVC codec name i suggetsed :p

imho the new AVC codec name doesnt important, for me.
Im only interest what feature are supported,
quality and encoding speed about this new AVC codec :)

[Kostarum Rex Persia]

Well, Ati H.264 encoder isn't good, it's way behind x264 and Ateme H.264 solutions.

[Doom9]

Am I the only one thinking that if the programmers wanted you to make name suggestions, they'd ask for it?

[Teegedeck]

Hehe; perhaps we should take this name-discussion as an expression of excitement? :) Anyway, IF the XviD people would like suggestions, I'm sure they would put up a poll on xvid.org.

[superdump]

There was a poll regarding what people wanted to see next from XviD and a h.264 codec was one of the options. I voted for further improvements to XviD because development efforts on another h.264 codec would be better spent on making x264 even better, in my opinion. Why have another OK codec when we could have one really brilliant codec?

Still, now it's here, I'll give it a look.

As for a name, I don't think it should have XviD in it as it will be misleading to people who own standalone players which say they can play XviD files.

[DeathTheSheep]

We all saw the results of early AVC codecs squishing the ASP codecs out of the best codec competition early-on.
Well, AVC is often considered the "next step up" from ASP, so maybe AVC does constitute "further improvements."

Name: VixD AVC codec. Maybe make it somethin' different than XviD altogether? "XviD AVC" suits me just fine too, though.

[Doom9]

because development efforts on another h.264 codec would be better spent on making x264 even better, in my opinion.I guess that's the eternal question but how can you decide on what a developer spends his/her time on? Hitting closer to home, why is there a realanime for x264, why is there staxrip when megui did x264 encoding from the getgo? I've had to come to terms with the fact that there are different tools for the same job, just as there are different codecs for the same job. Sometimes it may make sense to pool your resources, sometimes it may not, and whether or not it does is often a point of view question, not something for which there is a general answer that makes sense to everybody.

perhaps we should take this name-discussion as an expression of excitement?While partience certainly isn't my virtue, I tend to think at least I can managed to spend my energy on something else while waiting, and I think it's not such a bad thing. If you keep yourself busy, the wait will be so much shorter ;)

Can we stop the name discussion now please unless isibaar or skal come here asking for name suggestions? Thank you.

[virus]

There was a poll regarding what people wanted to see next from XviD and a h.264 codec was one of the options.
...yeah, and the guys definitely listened to the userbase who voted for AVC support :)

Back in summer/autumn 2004, I was persuaded that XviD could have borrowed some code from x264 (still very incomplete at the time) and merge it in a single ASP+AVC codec.
But now things have changed a lot. x264 has progressed to a point where it really stands out (for performance, encoding options availability, portability, and support by external encoding tools), while still offering a lot of room for further refinement. So in the end it would be important for x264 to continue on its distinctive road without getting merged with anything.
If XviD AVC succeeds, I just hope it won't hurt x264 up to the point to make it lose everyone's interest in it. I also hope each group of devs mantain their own approach without too much code borrowing, or we'll end up with two clones instead of a diversified offering ;)

Anyway, it's kinda useless to debate over this "new" XviD right now imho. Most of the development behind XviD pre-1.0, 1.0.x and 1.1 has come from sysKin and GomGom. And none of them has partecipated into this AVC project (yet). So XviD AVC comes from the guys who lately have been more busy and with little time/interest left for XviD. So, who guarantees that this codec will be developed after its initial release? Nobody of course. We don't even know if it's here to stay.

Does someone rememeber Skal's MPEG-4 codec? Promising, written by an extremely talented coder, open sourced, yet abandoned. hdot264 is another similar example (just look at the devlist, it's still on sf.net - there are even some familiar names in it). It's not the userbase size who dictates the success of an OS codec, not even its world-famous name. Open source software is development-driven, and so I'm more concerned that the OS codecs out there (no matter how many there are) actually get interest from coders, and that each project gets a proper devteam that can always bring it further, even if one or two devs call it quits. Otherwise it will only be wasted time.