From xvid-devel-bounces@xvid.org Wed Dec 1 08:38:54 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 36082126D85 for ; Wed, 1 Dec 2004 08:38:54 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 2A4BF154F2; Wed, 1 Dec 2004 08:44:47 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from tom.com (unknown [202.108.255.197]) by edu.bnhof.de (Postfix) with SMTP id 3E09F153FD for ; Wed, 1 Dec 2004 08:44:36 +0100 (CET) MIME-Version: 1.0 Message-ID: <41AD6DD1.00012A.03540@bjapp25> Date: Wed, 1 Dec 2004 15:08:01 +0800 (CST) From: zgdragon@tom.com To: xvid-devel@xvid.org X-Priority: 3 X-Originating-IP: [218.19.56.121] X-Mailer: 163net X-Content-Filtered-By: Mailman/MimeDel 2.1.4 Subject: [XviD-devel] about the key frame X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1516025499==" Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org --===============1516025499== Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 aGksDQogICAgRXZlcnlvbmUsIGkgd3JpdGUgYSB4dmlkIGVuY29kZXIodmVyc2lvbiAxLjAy KSB3aXRoIGRpcmVjdHNob3cgZmlsdGVyLCBhbmQgbGluayB0aGUgeHZpZCBjb3JlIGFzIHN0 YXRpYyBsaWJyYXJ5KG5vdCB1c2UgdGhlIHh2aWQuZGxsKS4NCg0KICAgIHRoZSBwcm9ibGVt IGlzLCBpIHRlc3QgbXkgZW5jb2RlciB1c2luZyB0aGlzIHByb2Nlc3M6IHZpZGVvIGNhcHR1 cmUgLT4gbXkgZW5jb2RlciAtPiB4dmlkIGRlY29kZXIgLT4gdmlkZW8gcmVuZGVyLCBzbywg YnkgdGhlIFVTQiBjYW1lciwgaXQgd29yayBvaywgYnV0IHdoZW4gaSBjaGFuZyB0byB1c2Ug dGhlIHZpZGVvIGNhcmQsdGhlIHZpZGVvIHJlbmRlciB3aW5kb3cgY2FuIHNlZSBub3RoaW5n LCh1c2UgdGhlIHh2aWQgdmZ3IGNvZGVjIGFsbCBpcyBvaykNCg0KICAgIGFuZCAsdGhyb3Vn aHQgaSBkZWJ1ZywgaSBmaW5kIHhpdmQgZGVjb2RlciBjYW4gZ2VybmFsIHRoZSBrZXkgZnJh bWUgd2hlbiB1c2luZyB4dmlkIHZmdyBjb2RlYywgYnV0IHVzZSB0aGUgZW5jb2RlciBpIHdy aXRlIGl0IGNhbid0IGdlcm5hbCB0aGUga2V5IGZyYW1lLC4NCg0KICAgIHBscyBoZWxwIG1l LCB0aGFua3MgYSBsb3QuDQoNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgIGh1Z28uDQo= --===============1516025499== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel --===============1516025499==-- From xvid-devel-bounces@xvid.org Wed Dec 1 10:05:33 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id F3093126D85 for ; Wed, 1 Dec 2004 10:05:32 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 07A3B15961; Wed, 1 Dec 2004 10:11:33 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from web54604.mail.yahoo.com (web54604.mail.yahoo.com [68.142.225.188]) by edu.bnhof.de (Postfix) with SMTP id 7117115359 for ; Wed, 1 Dec 2004 10:11:27 +0100 (CET) Received: (qmail 46611 invoked by uid 60001); 1 Dec 2004 09:05:23 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=Y77ULrgttXcdrCSMr3V0kXiw1u20mjU6TlO5ZX/6Ij7vewtdWedYpDyNIrroc3PpBJasbR5qirW8kT/IS0uOhi2O0MP9tqTASuytmjxHZO2P8YByeMmqBeipDMaRIHN8TzwCusVIW3B4lT1jzHFPbRN9N3B9F8/1kMWM9Sh+384= ; Message-ID: <20041201090523.46609.qmail@web54604.mail.yahoo.com> Received: from [61.95.224.103] by web54604.mail.yahoo.com via HTTP; Wed, 01 Dec 2004 01:05:23 PST Date: Wed, 1 Dec 2004 01:05:23 -0800 (PST) From: lakshmikanth r Subject: Re: [XviD-devel] about the key frame To: xvid-devel@xvid.org In-Reply-To: <41AD6DD1.00012A.03540@bjapp25> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hi, I am new to this MPEG4 encoding , I hope you can reply my question about DCT. In the XVID software, I have doubts regarding the implememtation of the DCT algorithm it is as follows, Can you pls let me how arrive at the following constants, #define FIX_0_298631336 ((int) 2446) /* FIX(0.298631336) */ #define FIX_0_390180644 ((int) 3196) /* FIX(0.390180644) */ #define FIX_0_541196100 ((int) 4433) /* FIX(0.541196100) */ #define FIX_0_765366865 ((int) 6270) /* FIX(0.765366865) */ #define FIX_0_899976223 ((int) 7373) /* FIX(0.899976223) */ #define FIX_1_175875602 ((int) 9633) /* FIX(1.175875602) */ #define FIX_1_501321110 ((int) 12299) /* FIX(1.501321110) */ #define FIX_1_847759065 ((int) 15137) /* FIX(1.847759065) */ #define FIX_1_961570560 ((int) 16069) /* FIX(1.961570560) */ #define FIX_2_053119869 ((int) 16819) /* FIX(2.053119869) */ #define FIX_2_562915447 ((int) 20995) /* FIX(2.562915447) */ #define FIX_3_072711026 ((int) 25172) /* FIX(3.072711026) */ I think there are coefficient constants. I want to specifically know whoe to arrive at the following constants, (0.298631336) (0.390180644) (0.541196100) (0.765366865) (0.899976223) (1.175875602) (1.501321110) (1.847759065) (1.961570560) (2.053119869) (2.562915447) (3.072711026) Awaiting your response, With regards, R.lakshmikanth --- zgdragon@tom.com wrote: > hi, > Everyone, i write a xvid encoder(version 1.02) > with directshow filter, and link the xvid core as > static library(not use the xvid.dll). > > the problem is, i test my encoder using this > process: video capture -> my encoder -> xvid decoder > -> video render, so, by the USB camer, it work ok, > but when i chang to use the video card,the video > render window can see nothing,(use the xvid vfw > codec all is ok) > > and ,throught i debug, i find xivd decoder can > gernal the key frame when using xvid vfw codec, but > use the encoder i write it can't gernal the key > frame,. > > pls help me, thanks a lot. > > > hugo. > > _______________________________________________ > XviD-devel mailing list > XviD-devel@xvid.org > http://list.xvid.org/mailman/listinfo/xvid-devel > __________________________________ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Wed Dec 1 10:06:38 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 09F88126D85 for ; Wed, 1 Dec 2004 10:06:38 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id E4626159F7; Wed, 1 Dec 2004 10:12:37 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from web54610.mail.yahoo.com (web54610.mail.yahoo.com [68.142.225.194]) by edu.bnhof.de (Postfix) with SMTP id 4AC1C154FC for ; Wed, 1 Dec 2004 10:12:29 +0100 (CET) Received: (qmail 31955 invoked by uid 60001); 1 Dec 2004 09:06:25 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=p6vxjO84pKag51+yHAFBjhaMIrgtpkeOkSb0dq3cX7b7zD/+RROah+/xzLUj5U+XHTF6wFtEDnRMGcDgQA2gIHNl79cbFR9DOgiPflH6WVCDh0hoPTnQnOKGhUXGEsPSh5ac0EKiWlwpgYZxp6rnCOpqB+eMWqqqec4SkA1FRgw= ; Message-ID: <20041201090625.31953.qmail@web54610.mail.yahoo.com> Received: from [61.95.224.103] by web54610.mail.yahoo.com via HTTP; Wed, 01 Dec 2004 01:06:25 PST Date: Wed, 1 Dec 2004 01:06:25 -0800 (PST) From: lakshmikanth r Subject: Re: [XviD-devel] about the key frame To: xvid-devel@xvid.org In-Reply-To: <41AD6DD1.00012A.03540@bjapp25> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hi, I am new to this MPEG4 encoding , I hope you can reply my question about DCT. In the XVID software, I have doubts regarding the implememtation of the DCT algorithm it is as follows, Can you pls let me how arrive at the following constants, #define FIX_0_298631336 ((int) 2446) /* FIX(0.298631336) */ #define FIX_0_390180644 ((int) 3196) /* FIX(0.390180644) */ #define FIX_0_541196100 ((int) 4433) /* FIX(0.541196100) */ #define FIX_0_765366865 ((int) 6270) /* FIX(0.765366865) */ #define FIX_0_899976223 ((int) 7373) /* FIX(0.899976223) */ #define FIX_1_175875602 ((int) 9633) /* FIX(1.175875602) */ #define FIX_1_501321110 ((int) 12299) /* FIX(1.501321110) */ #define FIX_1_847759065 ((int) 15137) /* FIX(1.847759065) */ #define FIX_1_961570560 ((int) 16069) /* FIX(1.961570560) */ #define FIX_2_053119869 ((int) 16819) /* FIX(2.053119869) */ #define FIX_2_562915447 ((int) 20995) /* FIX(2.562915447) */ #define FIX_3_072711026 ((int) 25172) /* FIX(3.072711026) */ My guess is that these are some coefficient constants. I want to specifically know who to arrive at the following constants, (0.298631336) (0.390180644) (0.541196100) (0.765366865) (0.899976223) (1.175875602) (1.501321110) (1.847759065) (1.961570560) (2.053119869) (2.562915447) (3.072711026) Awaiting your response, With regards, R.lakshmikanth --- zgdragon@tom.com wrote: > hi, > Everyone, i write a xvid encoder(version 1.02) > with directshow filter, and link the xvid core as > static library(not use the xvid.dll). > > the problem is, i test my encoder using this > process: video capture -> my encoder -> xvid decoder > -> video render, so, by the USB camer, it work ok, > but when i chang to use the video card,the video > render window can see nothing,(use the xvid vfw > codec all is ok) > > and ,throught i debug, i find xivd decoder can > gernal the key frame when using xvid vfw codec, but > use the encoder i write it can't gernal the key > frame,. > > pls help me, thanks a lot. > > > hugo. > > _______________________________________________ > XviD-devel mailing list > XviD-devel@xvid.org > http://list.xvid.org/mailman/listinfo/xvid-devel > __________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Wed Dec 1 10:44:50 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 3FDE5126D85 for ; Wed, 1 Dec 2004 10:44:50 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 93C5916438; Wed, 1 Dec 2004 10:50:50 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from tom.com (unknown [202.108.255.197]) by edu.bnhof.de (Postfix) with SMTP id 1BC2F15989 for ; Wed, 1 Dec 2004 10:50:40 +0100 (CET) MIME-Version: 1.0 Message-ID: <41AD9280.00003F.21903@bjapp7> Date: Wed, 1 Dec 2004 17:44:32 +0800 (CST) From: zgdragon@tom.com To: xvid-devel@xvid.org Subject: =?gb2312?B?UmU6IFJlOiBbWHZpRC1kZXZlbF0gYWJvdXQgdGhlIGtleSBmcmFtZQ==?= X-Priority: 3 X-Originating-IP: [218.19.56.121] X-Mailer: 163net X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0211170436==" Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org --===============0211170436== Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="gb2312" b2gsIA0KICAgc29ycnksIGkgY2FuJ3QgcmVwbHkgeW91ciBEQ1QgcXVlc3Rpb24sIGlmIHlv dSB3YW50IHRvIGdldCB0aGUgYW5zd2VyIGZvciB0aGlzIHF1ZXN0aW9uLCB5b3Ugc2hvdWxk IGVtYWlsIHRvIHh2aWQgWHZpRCBBbm5vdW5jZSAoeHZpZC1hbm5vdW5jZUB4dmlkLm9yZyku DQogDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBodWdvLiANCg0K PiBIaSwNCj4gDQo+IEkgYW0gbmV3IHRvIHRoaXMgTVBFRzQgZW5jb2RpbmcgLCBJIGhvcGUg eW91IGNhbiByZXBseQ0KPiBteSBxdWVzdGlvbiBhYm91dCBEQ1QuDQo+IA0KPiBJbiB0aGUg WFZJRCBzb2Z0d2FyZSwgSSBoYXZlIGRvdWJ0cyByZWdhcmRpbmcgdGhlDQo+IGltcGxlbWVt dGF0aW9uIG9mIHRoZSBEQ1QgYWxnb3JpdGhtIGl0IGlzIGFzIGZvbGxvd3MsDQo+IA0KPiBD YW4geW91IHBscyBsZXQgbWUgaG93IGFycml2ZSBhdCB0aGUgZm9sbG93aW5nDQo+IGNvbnN0 YW50cywNCj4gI2RlZmluZSBGSVhfMF8yOTg2MzEzMzYgICgoaW50KSAgMjQ0NikJLyoNCj4g RklYKDAuMjk4NjMxMzM2KSAqLw0KPiAjZGVmaW5lIEZJWF8wXzM5MDE4MDY0NCAgKChpbnQp ICAzMTk2KQkvKg0KPiBGSVgoMC4zOTAxODA2NDQpICovDQo+ICNkZWZpbmUgRklYXzBfNTQx MTk2MTAwICAoKGludCkgIDQ0MzMpCS8qDQo+IEZJWCgwLjU0MTE5NjEwMCkgKi8NCj4gI2Rl ZmluZSBGSVhfMF83NjUzNjY4NjUgICgoaW50KSAgNjI3MCkJLyoNCj4gRklYKDAuNzY1MzY2 ODY1KSAqLw0KPiAjZGVmaW5lIEZJWF8wXzg5OTk3NjIyMyAgKChpbnQpICA3MzczKQkvKg0K PiBGSVgoMC44OTk5NzYyMjMpICovDQo+ICNkZWZpbmUgRklYXzFfMTc1ODc1NjAyICAoKGlu dCkgIDk2MzMpCS8qDQo+IEZJWCgxLjE3NTg3NTYwMikgKi8NCj4gI2RlZmluZSBGSVhfMV81 MDEzMjExMTAgICgoaW50KSAxMjI5OSkJLyoNCj4gRklYKDEuNTAxMzIxMTEwKSAqLw0KPiAj ZGVmaW5lIEZJWF8xXzg0Nzc1OTA2NSAgKChpbnQpIDE1MTM3KQkvKg0KPiBGSVgoMS44NDc3 NTkwNjUpICovDQo+ICNkZWZpbmUgRklYXzFfOTYxNTcwNTYwICAoKGludCkgMTYwNjkpCS8q DQo+IEZJWCgxLjk2MTU3MDU2MCkgKi8NCj4gI2RlZmluZSBGSVhfMl8wNTMxMTk4NjkgICgo aW50KSAxNjgxOSkJLyoNCj4gRklYKDIuMDUzMTE5ODY5KSAqLw0KPiAjZGVmaW5lIEZJWF8y XzU2MjkxNTQ0NyAgKChpbnQpIDIwOTk1KQkvKg0KPiBGSVgoMi41NjI5MTU0NDcpICovDQo+ ICNkZWZpbmUgRklYXzNfMDcyNzExMDI2ICAoKGludCkgMjUxNzIpCS8qDQo+IEZJWCgzLjA3 MjcxMTAyNikgKi8NCj4gDQo+IE15IGd1ZXNzIGlzIHRoYXQgdGhlc2UgYXJlIHNvbWUgY29l ZmZpY2llbnQgY29uc3RhbnRzLg0KPiBJIHdhbnQgdG8gc3BlY2lmaWNhbGx5IGtub3cgd2hv IHRvIGFycml2ZSBhdCB0aGUNCj4gZm9sbG93aW5nIGNvbnN0YW50cywNCj4gKDAuMjk4NjMx MzM2KSANCj4gKDAuMzkwMTgwNjQ0KSANCj4gKDAuNTQxMTk2MTAwKSANCj4gKDAuNzY1MzY2 ODY1KSANCj4gKDAuODk5OTc2MjIzKSANCj4gKDEuMTc1ODc1NjAyKSANCj4gKDEuNTAxMzIx MTEwKSANCj4gKDEuODQ3NzU5MDY1KSANCj4gKDEuOTYxNTcwNTYwKSANCj4gKDIuMDUzMTE5 ODY5KSANCj4gKDIuNTYyOTE1NDQ3KSANCj4gKDMuMDcyNzExMDI2KSANCj4gDQo+IEF3YWl0 aW5nIHlvdXIgcmVzcG9uc2UsDQo+IA0KPiBXaXRoIHJlZ2FyZHMsDQo+IFIubGFrc2htaWth bnRoDQo+IC0tLSB6Z2RyYWdvbkB0b20uY29tIHdyb3RlOg0KPiANCg0KPT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KxbW7+dHHweXJ+SBodHRwOi8v c21zLnRvbS5jb20vaW5kZXgyLnBocD9pbmM9MyZ0eXBlPTI0CsSmzdDC3sCtweXJ+SBodHRw Oi8vc21zLnRvbS5jb20vaW5kZXgyLnBocD9pbmM9MyZ0eXBlPTI2Cs73w8XX08HlyfkgaHR0 cDovL3Ntcy50b20uY29tL2luZGV4Mi5waHA/aW5jPTMmdHlwZT0yNQoKxbW7+dHH0KHNvCBo dHRwOi8vc21zLnRvbS5jb20vaW5kZXgyLnBocD9pbmM9MgrFtbv50ce08828IGh0dHA6Ly9z bXMudG9tLmNvbS9pbmRleDIucGhwP2luYz0yJnR5cGU9Mzc0MArO98PF19PNvMasIGh0dHA6 Ly9zbXMudG9tLmNvbS9pbmRleDIucGhwP2luYz0yJnR5cGU9MzAKCsrWu/q147joIGh0dHA6 Ly9zbXMudG9tLmNvbS9pbmRleDIucGhwP2luYz1zb25nCj09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09 --===============0211170436== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel --===============0211170436==-- From xvid-devel-bounces@xvid.org Wed Dec 1 10:50:43 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 62DA8126D85 for ; Wed, 1 Dec 2004 10:50:43 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id D4BC516448; Wed, 1 Dec 2004 10:56:43 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from ftp.ilog.fr (ftp.ilog.fr [81.80.162.195]) by edu.bnhof.de (Postfix) with ESMTP id 5ADB515402 for ; Wed, 1 Dec 2004 10:56:39 +0100 (CET) Received: from laposte.ilog.fr (cerbere-qe0 [81.80.162.193]) by ftp.ilog.fr (8.13.1/8.13.0) with ESMTP id iB19oZGL013168 for ; Wed, 1 Dec 2004 10:50:35 +0100 (MET) Received: from latitude344 ([172.17.4.249]) by laposte.ilog.fr (8.13.1/8.13.1) with ESMTP id iB19oT48024555 for ; Wed, 1 Dec 2004 10:50:29 +0100 (MET) Subject: Re: [XviD-devel] FDCT constants From: skal To: xvid-devel@xvid.org In-Reply-To: <20041129064652.90961.qmail@web54608.mail.yahoo.com> References: <20041129064652.90961.qmail@web54608.mail.yahoo.com> Content-Type: text/plain Organization: Message-Id: <1101894622.1472.11.camel@latitude344> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 01 Dec 2004 10:50:22 +0100 Content-Transfer-Encoding: 7bit X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hi, On Mon, 2004-11-29 at 07:46, lakshmikanth r wrote: > HI, > > I am a new to the field of MPEG4 encodeing and I was > going through your xvid reference code and in specfic > DCT calculation. The following line of code is found > in dct.c > " > #define FIX_0_298631336 ((int) 2446) /* > FIX(0.298631336) */ [...] > #define FIX_3_072711026 ((int) 25172) /* > FIX(3.072711026) */ these constants are mostly tan[k.pi/16]. Have a look there: http://skal.planet-d.net/coding/dct.html in particular the part where 2d-rotations with 3 mults are described. Skal _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Wed Dec 1 13:46:34 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id AEFDF126D85 for ; Wed, 1 Dec 2004 13:46:33 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 0099215971; Wed, 1 Dec 2004 13:52:21 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from web54602.mail.yahoo.com (web54602.mail.yahoo.com [68.142.225.186]) by edu.bnhof.de (Postfix) with SMTP id AB42E154E5 for ; Wed, 1 Dec 2004 13:52:01 +0100 (CET) Received: (qmail 25203 invoked by uid 60001); 1 Dec 2004 12:45:55 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=pW9mCiu+2q+aIX6gTVjjh1NiV/1ybDhW9Dqw8FeVrE0PSkM+SYTVpE9kd9AYTY/jnkL9I+fZcfuyD+nIX9cdMjonVLwqowe3DbjHtGDb1peIFHLBqtqxA/3DUphWY9pdfTB0wBCLvX7tLblx9uEo8m5WOvEQSHlBKBHXWA7p294= ; Message-ID: <20041201124555.25201.qmail@web54602.mail.yahoo.com> Received: from [61.95.224.103] by web54602.mail.yahoo.com via HTTP; Wed, 01 Dec 2004 04:45:55 PST Date: Wed, 1 Dec 2004 04:45:55 -0800 (PST) From: lakshmikanth r Subject: Re: [XviD-devel] FDCT constants To: xvid-devel@xvid.org In-Reply-To: <1101894622.1472.11.camel@latitude344> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hi, I have gone through the website that you had reffered.But I am afraid I am not able to understand. Can you pls take a specfic example of a constant and explain me to to derive it, I would very thankfull to you. Awaiting your response, With regards, R.lakshmikanth --- skal wrote: > > Hi, > > On Mon, 2004-11-29 at 07:46, lakshmikanth r wrote: > > HI, > > > > I am a new to the field of MPEG4 encodeing and I > was > > going through your xvid reference code and in > specfic > > DCT calculation. The following line of code is > found > > in dct.c > > " > > #define FIX_0_298631336 ((int) 2446) /* > > FIX(0.298631336) */ > > [...] > > > #define FIX_3_072711026 ((int) 25172) /* > > FIX(3.072711026) */ > > > these constants are mostly tan[k.pi/16]. > Have a look there: > > http://skal.planet-d.net/coding/dct.html > > in particular the part where 2d-rotations > with 3 mults are described. > > Skal > > _______________________________________________ > XviD-devel mailing list > XviD-devel@xvid.org > http://list.xvid.org/mailman/listinfo/xvid-devel > __________________________________ Do you Yahoo!? All your favorites on one personal page – Try My Yahoo! http://my.yahoo.com _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Wed Dec 1 13:48:53 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id E5814126D85 for ; Wed, 1 Dec 2004 13:48:52 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id EAE5516417; Wed, 1 Dec 2004 13:54:45 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from cam-admin0.cambridge.arm.com (iPass.cambridge.arm.com [193.131.176.58]) by edu.bnhof.de (Postfix) with ESMTP id 17E1F1597B for ; Wed, 1 Dec 2004 13:54:36 +0100 (CET) Received: from cam-mail2.cambridge.arm.com (cam-mail2.cambridge.arm.com [10.1.127.39]) by cam-admin0.cambridge.arm.com (8.12.10/8.12.10) with ESMTP id iB1Clhmb020835 for ; Wed, 1 Dec 2004 12:47:43 GMT Received: from ZIPPY.Emea.Arm.com (bungle.Emea.arm.com [10.1.255.82]) by cam-mail2.cambridge.arm.com (8.9.3/8.9.3) with ESMTP id MAA19911 for ; Wed, 1 Dec 2004 12:48:30 GMT X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 1 Dec 2004 12:48:29 -0000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: native output format of xvid Thread-Index: AcTXpA6AAl7DvDGhTs6VHSRV9V6YCQ== From: "Anand Patel" To: Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.4 Subject: [XviD-devel] native output format of xvid X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hi, What is the native output format of the xvid decoder, before any colourspace conversion takes place? =20 The reason im asking, is that my platform contains some hardware that will perform colourspace conversion, providing it is in a certain YUV format. =20 Thanks Anand =20 _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Wed Dec 1 14:24:23 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 2C270126D85 for ; Wed, 1 Dec 2004 14:24:23 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id ED7F215989; Wed, 1 Dec 2004 14:30:23 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from postfix3-2.free.fr (postfix3-2.free.fr [213.228.0.169]) by edu.bnhof.de (Postfix) with ESMTP id 7F32315971 for ; Wed, 1 Dec 2004 14:30:17 +0100 (CET) Received: from imp4-q.free.fr (imp4-q.free.fr [212.27.42.4]) by postfix3-2.free.fr (Postfix) with ESMTP id 0EB05C11A for ; Wed, 1 Dec 2004 14:24:12 +0100 (CET) Received: by imp4-q.free.fr (Postfix, from userid 33) id BE462B29B; Wed, 1 Dec 2004 14:24:12 +0100 (MET) Received: from 195.101.164.39 ([195.101.164.39]) by imp4-q.free.fr (IMP) with HTTP for ; Wed, 1 Dec 2004 14:24:12 +0100 Message-ID: <1101907452.41adc5fcb4a6b@imp4-q.free.fr> Date: Wed, 1 Dec 2004 14:24:12 +0100 From: Edouard Gomez To: xvid-devel@xvid.org Subject: Re: [XviD-devel] native output format of xvid References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.5 X-Originating-IP: 195.101.164.39 X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Selon Anand Patel : > Hi, What is the native output format of the xvid decoder, before any > colourspace conversion takes place? > > The reason im asking, is that my platform contains some hardware that > will perform colourspace conversion, providing it is in a certain YUV > format. > > Thanks Anand It's YV12. -- Edouard Gomez _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Wed Dec 1 19:40:01 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 38246126D85 for ; Wed, 1 Dec 2004 19:40:01 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 1BE051591E; Wed, 1 Dec 2004 19:45:56 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from mx.wmich.edu (mx-tmp.wmich.edu [141.218.1.43]) by edu.bnhof.de (Postfix) with ESMTP id D0528154DA for ; Wed, 1 Dec 2004 19:45:45 +0100 (CET) Received: from fleming.admin.private (avs01.service.private [172.30.31.161]) by mercury.admin.private (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0I8200IMQ3NTF560@mta02.service.private> for xvid-devel@xvid.org; Wed, 01 Dec 2004 13:39:35 -0500 (EST) Received: from mta-avs02.service.private ([172.30.30.162]) by fleming.admin.private (SMSSMTP 4.0.0.59) with SMTP id M2004120113393427413 for ; Wed, 01 Dec 2004 13:39:34 -0500 Received: from [192.168.0.4] (24.247.144.72.kzo.mi.chartermi.net [24.247.144.72]) by mercury.admin.private (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPSA id <0I8200HO23TXEW60@mta02.service.private> for xvid-devel@xvid.org; Wed, 01 Dec 2004 13:39:35 -0500 (EST) Date: Wed, 01 Dec 2004 08:46:22 -0500 From: DT To: xvid-devel@xvid.org Message-id: <41ADCB2E.3040805@chartermi.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040818) Subject: [XviD-devel] Memory leak using decoder? X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org I am trying to use XviD in my application to decode video, and everything appeared to be working fine until I checked memory usage. The amount of free memory available on the system steadily declines as my program runs. However, if I comment out the line that calls the decoder, this huge memory waste does not occur. I am calling the decoder almost exactly like the API example program does: memset(&xvid_dec_frame, 0, sizeof(xvid_dec_frame_t)); xvid_dec_frame.version = XVID_VERSION; decoder_stats->version = XVID_VERSION; xvid_dec_frame.general = 0; /* Input properties */ xvid_dec_frame.bitstream = buf_ptr; xvid_dec_frame.length = new_bytes; /* Output properties */ xvid_dec_frame.output.plane[0] = out_buffer; xvid_dec_frame.output.stride[0] = stream_x_dim*2; xvid_dec_frame.output.csp = XVID_CSP_YUY2; out = xvid_decore(decoder_handle, XVID_DEC_DECODE, &xvid_dec_frame, decoder_stats); return out; Is there something wrong with how I am calling the decoder? Should I be freeing some buffer the decoder creates each frame? Or is there a known memory leak in XviD when using YUY2 or something? As I said before, commenting out the xvid_decore call causes the problem to go away. Sorry, I'm pretty new to using video decoders myself like this. I would really appreciate any advice that could help me figure this out! Thanks, Kyle _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Wed Dec 1 20:32:31 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id D9996126D85 for ; Wed, 1 Dec 2004 20:32:31 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 213E0159BC; Wed, 1 Dec 2004 20:38:33 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from edgomez.kicks-ass.org (edgomez.kicks-ass.org [82.225.208.184]) by edu.bnhof.de (Postfix) with ESMTP id DBD771597B for ; Wed, 1 Dec 2004 20:38:30 +0100 (CET) Received: from edy by edgomez.kicks-ass.org with local (Exim 4.34) id 1CZaD6-0001iS-1U for xvid-devel@xvid.org; Wed, 01 Dec 2004 20:32:20 +0100 Date: Wed, 1 Dec 2004 20:32:20 +0100 From: Edouard Gomez To: xvid-devel@xvid.org Subject: Re: [XviD-devel] Memory leak using decoder? Message-ID: <20041201193220.GA6316@edgomez.kicks-ass.org> Mail-Followup-To: Edouard Gomez , xvid-devel@xvid.org References: <41ADCB2E.3040805@chartermi.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41ADCB2E.3040805@chartermi.net> User-Agent: Mutt/1.5.6+20040907i X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org DT (darktyco@chartermi.net) wrote: > I am trying to use XviD in my application to decode video, and > everything appeared to be working fine until I checked memory usage. The > amount of free memory available on the system steadily declines as my > program runs. However, if I comment out the line that calls the decoder, > this huge memory waste does not occur. I am calling the decoder almost > exactly like the API example program does: > > memset(&xvid_dec_frame, 0, sizeof(xvid_dec_frame_t)); > > xvid_dec_frame.version = XVID_VERSION; > decoder_stats->version = XVID_VERSION; > > xvid_dec_frame.general = 0; > > /* Input properties */ > xvid_dec_frame.bitstream = buf_ptr; > xvid_dec_frame.length = new_bytes; > > /* Output properties */ > xvid_dec_frame.output.plane[0] = out_buffer; > xvid_dec_frame.output.stride[0] = stream_x_dim*2; > xvid_dec_frame.output.csp = XVID_CSP_YUY2; > > out = xvid_decore(decoder_handle, XVID_DEC_DECODE, &xvid_dec_frame, > decoder_stats); > > return out; > > Is there something wrong with how I am calling the decoder? Should I be > freeing some buffer the decoder creates each frame? No xvid buffers are allocated only once at decoder startup, or when decoder first encounters a VOL header (a mpeg4 header which carries the width/height information) > Or is there a known > memory leak in XviD when using YUY2 or something? xvidcore hans't any memory leak (at least none that eyeballs can see nor memory checking programs can detect) But as i can see, you're using thunderbird on X11, so with some luck you're even probably using a Linux based OS. If that's the case then i advise you using "valgrind" on your program. For better reports, compile everything with debug infos, and statically link against xvidcore. Then run it through valgrind, and it should tell you how much is leaked. > As I said before, > commenting out the xvid_decore call causes the problem to go away. > Sorry, I'm pretty new to using video decoders myself like this. I would > really appreciate any advice that could help me figure this out! Maybe you don't free the decoder instance once you're done with your stream ? -- Edouard Gomez _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Thu Dec 2 09:12:54 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 726D7126D82 for ; Thu, 2 Dec 2004 09:12:54 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 13C441655C; Thu, 2 Dec 2004 09:18:53 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from web15310.mail.bjs.yahoo.com (web15310.mail.cnb.yahoo.com [202.43.216.185]) by edu.bnhof.de (Postfix) with SMTP id 1926716558 for ; Thu, 2 Dec 2004 09:18:48 +0100 (CET) Message-ID: <20041202081226.73557.qmail@web15310.mail.bjs.yahoo.com> Received: from [211.95.163.86] by web15310.mail.cnb.yahoo.com via HTTP; Thu, 02 Dec 2004 16:12:26 CST Date: Thu, 2 Dec 2004 16:12:26 +0800 (CST) From: mayfig To: Xvid MIME-Version: 1.0 Content-Type: text/plain; charset=gb2312 Content-Transfer-Encoding: 8bit Subject: [XviD-devel] MotionVector implementation in the case of decoding field predicted MB of interlaced mode X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org in the case of interlaced mode , it seems Xvid do not implement well when the decoded MacroBlock is a field predicted MB. I am trying to correct it, but it seems something wrong with my understanding . For when I add the part of MotionVector for the bottom field and then perform the relevant interpolation of half-pel in the source code, the resulted picture has more problem than before. 1. I am not sure when the current MB is a field predicted MB. if the function below pmv = get_pmv2(dec->mbs, dec->mb_width, bound, x, y, k) still valid(Consider the three cases in Section 7.7.2..1 of MPEG4 Standard)? 2. To implement the interpolation of MotionVectors of Top field and bottom field interpolate8x8_field_switch(dec->cur.y, dec->refn[ref].y, 16*x_pos, 16*y_pos, mv[0].x, mv[0].y, stride, rounding); interpolate8x8_field_switch(dec->cur.y, dec->refn[ref].y, 16*x_pos + 8, 16*y_pos, mv[0].x, mv[0].y, stride, rounding); interpolate8x8_field_switch(dec->cur.y, dec->refn[ref].y, 16*x_pos, 16*y_pos+8, mv[1].x, mv[1].y, stride, rounding); interpolate8x8_field_switch(dec->cur.y, dec->refn[ref].y, 16*x_pos+ 8, 16*y_pos+8,mv[1].x, mv[1].y, stride, rounding); It seems something wrong. Is there anyone would like to give me some suggestion? _________________________________________________________ Do You Yahoo!? ×¢²áÊÀ½çÒ»Á÷Æ·ÖʵÄÑÅ»¢Ãâ·ÑµçÓÊ http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/ _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Fri Dec 3 09:55:46 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 90FE4126D82 for ; Fri, 3 Dec 2004 09:55:46 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id C95B716572; Fri, 3 Dec 2004 10:01:46 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from web54609.mail.yahoo.com (web54609.mail.yahoo.com [68.142.225.193]) by edu.bnhof.de (Postfix) with SMTP id 8A5071654D for ; Fri, 3 Dec 2004 10:01:37 +0100 (CET) Received: (qmail 57000 invoked by uid 60001); 3 Dec 2004 08:55:29 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=IpnU8mWdys4b/4IQ/4OAH+4v6z85c2tKTZe7wBKVCv4/HxwGGEdywSfroceWQP+x5psyqgD72H99uTnCyRnYoqyZJZ5qScFsZT4qO3EhXhNkDiSqOpoq6xlOj+IK0UCem4k9G6C4CAsGapHB2J7XahpDPMD57SsJcCpYqe02/Hg= ; Message-ID: <20041203085529.56998.qmail@web54609.mail.yahoo.com> Received: from [61.95.224.103] by web54609.mail.yahoo.com via HTTP; Fri, 03 Dec 2004 00:55:29 PST Date: Fri, 3 Dec 2004 00:55:29 -0800 (PST) From: lakshmikanth r To: Xvid MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [XviD-devel] Query regarding IDCT implementation X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hi All, I was studing the xvid code and I would like to have more information on the algorithm paper mentioned in the implementation of IDCT inverse two dimensional DCT, Chen-Wang algorithm (cf. IEEE ASSP-32, pp. 803-816, Aug. 1984) 32-bit integer arithmetic (8 bit coefficients) 11 mults, 29 adds per DCT If any one has the description of algorthim/paper, can you pls mail it across to me. Awaiting your response. With regards, R.lakshmikanth __________________________________ Do you Yahoo!? Yahoo! Mail - Find what you need with new enhanced search. http://info.mail.yahoo.com/mail_250 _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Fri Dec 3 15:39:18 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id DA3D6126D82 for ; Fri, 3 Dec 2004 15:39:18 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id BE08B16543; Fri, 3 Dec 2004 15:45:21 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from hotmail.com (bay20-f12.bay20.hotmail.com [64.4.54.101]) by edu.bnhof.de (Postfix) with ESMTP id 3F475163F8 for ; Fri, 3 Dec 2004 15:45:18 +0100 (CET) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 3 Dec 2004 06:39:05 -0800 Message-ID: Received: from 210.50.248.33 by by20fd.bay20.hotmail.msn.com with HTTP; Fri, 03 Dec 2004 14:38:02 GMT X-Originating-IP: [210.50.248.33] X-Originating-Email: [a_dunstan@hotmail.com] X-Sender: a_dunstan@hotmail.com From: "Andrew neveryoumind" To: xvid-devel@xvid.org Date: Sat, 04 Dec 2004 01:38:02 +1100 Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-OriginalArrivalTime: 03 Dec 2004 14:39:05.0096 (UTC) FILETIME=[D6AEB080:01C4D945] Subject: [XviD-devel] init_vlc_tables on AMD64 X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org I've been experimenting with xvid and the windows x86-64 beta and the init_vlc_tables function in bitstream/mbcoding.c is giving me problems. Specifically, the following line: if (level_esc <= max_level[intra][last][run] && run <= max_run[intra][last][level_esc]) { eventually causes a page fault because level_esc seems to be negative (or more accurately, very large because it's an unsigned int). At the register level, when it is added to the address of max_run[intra][last] the overflow stays in the result rather than being discarded like in 32-bit mode. So my question is should level_esc be a signed int (which fixes the page fault) or is there a bug somewhere else making level_esc negative when it shouldn't be? _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Tue Dec 7 10:20:51 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 1F75C126D83 for ; Tue, 7 Dec 2004 10:20:51 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 636731656D; Tue, 7 Dec 2004 10:26:57 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from web42201.mail.yahoo.com (web42201.mail.yahoo.com [66.218.93.202]) by edu.bnhof.de (Postfix) with SMTP id 4ADC91646C for ; Tue, 7 Dec 2004 10:26:52 +0100 (CET) Received: (qmail 46421 invoked by uid 60001); 7 Dec 2004 09:20:36 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=QlYpS4EpZaByO1BJg0tpNcBPmELunzSVtM9a6VVyaHUvZAmNKGTK/DvyHt8bBENHClddQvjdSI4DQF55DI+/Rth1ZQSXLIGI7LUt2T7KH0Q2Ar+OWo9M+Sm5I6YSOC2Dixw2WyxNxZHdWHjVGe9Xu6bFzBTG77T9bBLsxEEO6a4= ; Message-ID: <20041207092036.46418.qmail@web42201.mail.yahoo.com> Received: from [203.244.221.1] by web42201.mail.yahoo.com via HTTP; Tue, 07 Dec 2004 01:20:36 PST Date: Tue, 7 Dec 2004 01:20:36 -0800 (PST) From: Ram Sinha To: xvid-devel@xvid.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.4 Subject: [XviD-devel] help needed X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hi, I am trying to understand the xvid source code... So I tried to build the xvid source in visual studio and debug it.. but after building no executable is created.. plz help .. how do we debug the code in visual studio? here's how i proceeded: 1. build the xvidcore.dsw choosing libxvidcor project as the active project. 2. Open the vfw.dsw and build it.. gives an error INK : warning LNK4075: ignoring /EDITANDCONTINUE due to /INCREMENTAL:NO specification Creating library Debug/xvidvfw.lib and object Debug/xvidvfw.exp ¸í·É ±¸¹®ÀÌ Æ²¸³´Ï´Ù. Error executing c:\windows\system32\cmd.exe. xvidvfw.dll - 1 error(s), 1 warning(s) 3. No executable is made. Please explain as to how i can debug the code in visual studio. Thanking you, Ram --------------------------------- Do you Yahoo!? The all-new My Yahoo! – What will yours do? _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Tue Dec 7 10:54:41 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id EEFAE126D83 for ; Tue, 7 Dec 2004 10:54:40 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id AF70A1593B; Tue, 7 Dec 2004 11:00:52 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from web13424.mail.yahoo.com (web13424.mail.yahoo.com [216.136.175.155]) by edu.bnhof.de (Postfix) with SMTP id 45747BFE0 for ; Tue, 7 Dec 2004 11:00:48 +0100 (CET) Received: (qmail 96414 invoked by uid 60001); 7 Dec 2004 09:54:32 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=KmhZTEvusqZmomCGiN68BhypdXMVPs4Q4rWydyHhzxjoMAPAQTo0InU6BMhwuY996BpwHIwfFmRg7P1BsNRz3eoMVAHj6WnLk3Yvibs1Xe7zcuoozLxueSZuDg6gTu6YkKCFUy6l6Nh4FUFDx1ypgDabur/zJ7SAy85J/kL+6YQ= ; Message-ID: <20041207095432.96412.qmail@web13424.mail.yahoo.com> Received: from [203.244.221.1] by web13424.mail.yahoo.com via HTTP; Tue, 07 Dec 2004 01:54:32 PST Date: Tue, 7 Dec 2004 01:54:32 -0800 (PST) From: Tushit Bharthuar To: xvid-devel@xvid.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [XviD-devel] GMC X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hi, When we are calculating offset, should not the offset be restricted by the image size? e.g. In the case of Predict_16x16_C if v>=H Offset becomes image height multiplied by the source stride. which is outside the image. I may be going wrong somewhere. Can you please explain? Thanks Tushit __________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Tue Dec 7 11:18:42 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 9F11E126D83 for ; Tue, 7 Dec 2004 11:18:42 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 7D51116416; Tue, 7 Dec 2004 11:24:54 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from ftp.ilog.fr (ftp.ilog.fr [81.80.162.195]) by edu.bnhof.de (Postfix) with ESMTP id DEF5316409 for ; Tue, 7 Dec 2004 11:24:51 +0100 (CET) Received: from laposte.ilog.fr (cerbere-qe0 [81.80.162.193]) by ftp.ilog.fr (8.13.1/8.13.0) with ESMTP id iB7AIaM0024866 for ; Tue, 7 Dec 2004 11:18:36 +0100 (MET) Received: from latitude344 ([172.17.4.249]) by laposte.ilog.fr (8.13.1/8.13.1) with ESMTP id iB7AIUaW015436 for ; Tue, 7 Dec 2004 11:18:30 +0100 (MET) Subject: Re: [XviD-devel] GMC From: skal To: xvid-devel@xvid.org In-Reply-To: <20041207095432.96412.qmail@web13424.mail.yahoo.com> References: <20041207095432.96412.qmail@web13424.mail.yahoo.com> Content-Type: text/plain Organization: Message-Id: <1102414644.1480.12.camel@latitude344> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 07 Dec 2004 11:17:24 +0100 Content-Transfer-Encoding: 7bit X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Tushit, On Tue, 2004-12-07 at 10:54, Tushit Bharthuar wrote: > Hi, > > When we are calculating offset, should not the offset > be restricted by the image size? > e.g. In the case of Predict_16x16_C if v>=H Offset > becomes image height multiplied by the source stride. > which is outside the image. Actually, it's not really "outside" the image, but rather exactly on the bottom/right boundary. Offset remains strictly in [0,H]. Since edges are replicated, we can nevertheless read source and weight it even if offset=H. Note that in such case, the weight for pixel "Offset" is 1, and the weight for pixel "Offset+1" is 0. Hence, even if we read outside the image, the result is zeroed by the null weight. hope it helps, Skal _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Wed Dec 8 22:55:55 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 6FFC5126D83 for ; Wed, 8 Dec 2004 22:55:55 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 81D9B165C1; Wed, 8 Dec 2004 23:02:07 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by edu.bnhof.de (Postfix) with ESMTP id B144B165BB for ; Wed, 8 Dec 2004 23:02:00 +0100 (CET) Received: from [10.23.36.59] (unknown[63.164.145.161]) by comcast.net (sccrmhc13) with ESMTP id <200412082155280160097vive>; Wed, 8 Dec 2004 21:55:28 +0000 Message-ID: <41B777D8.4070509@comcast.net> Date: Wed, 08 Dec 2004 13:53:28 -0800 From: Zack Smith User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: xvid-devel@xvid.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [XviD-devel] television server / streaming xvid? X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hello, I'm looking for information about this idea of streaming xvid. The user apakian had said in the xvid web forum that he had developed a "television server". Can someone please direct me to a download ? Thanks, -- Zack Smith plinius@comcast.net _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Thu Dec 9 03:04:56 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id BCB96126D82 for ; Thu, 9 Dec 2004 03:04:56 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 5BB4814C0C; Thu, 9 Dec 2004 03:11:11 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from web13423.mail.yahoo.com (web13423.mail.yahoo.com [216.136.175.154]) by edu.bnhof.de (Postfix) with SMTP id 808EE14612 for ; Thu, 9 Dec 2004 03:11:07 +0100 (CET) Received: (qmail 62517 invoked by uid 60001); 9 Dec 2004 02:04:43 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=sWEs/5GVTFuoBF0Qcy6dpWO4Pay0KNDsWF0V8VxNGF5VRaH8pQGNLwFGAAcioPnnzJirWhlI1jZr1lo00UzAmnTyqPL+lidJGejxKPIYiEar4BBGU088vOBHK3TJ/0H592rE4CbieO2xbgBgjaxa5y4R5TCvHNZDObeIFGn0n0Q= ; Message-ID: <20041209020443.62515.qmail@web13423.mail.yahoo.com> Received: from [203.244.221.1] by web13423.mail.yahoo.com via HTTP; Wed, 08 Dec 2004 18:04:42 PST Date: Wed, 8 Dec 2004 18:04:42 -0800 (PST) From: Tushit Bharthuar To: xvid-devel@xvid.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [XviD-devel] GMC help X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hi, Is the calculation for effective number of warping points correct? if (nb_pts<2 || (pts->duv[2].x==0 && pts->duv[2].y==0 && pts->duv[1].x==0 && pts->duv[1].y==0 )) { if (nb_pts<2 || (pts->duv[1].x==0 && pts->duv[1].y==0)) { if (nb_pts<1 || (pts->duv[0].x==0 && pts->duv[0].y==0)) { nb_pts = 0; } else nb_pts = 1; } else nb_pts = 2; } Shouldnot the checking for pts->duv[1].x==0 && pts->duv[1].y==0 not be there in the first statement? Thanks and regards, Tushit __________________________________ Do you Yahoo!? The all-new My Yahoo! - What will yours do? http://my.yahoo.com _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Thu Dec 9 08:10:23 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 12E03126D82 for ; Thu, 9 Dec 2004 08:10:23 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 320F216636; Thu, 9 Dec 2004 08:16:37 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from postfix3-1.free.fr (postfix3-1.free.fr [213.228.0.44]) by edu.bnhof.de (Postfix) with ESMTP id 09D1916635 for ; Thu, 9 Dec 2004 08:16:32 +0100 (CET) Received: from nas-cbv-9-62-147-113-6.dial.proxad.net (nas-cbv-9-62-147-113-6.dial.proxad.net [62.147.113.6]) by postfix3-1.free.fr (Postfix) with ESMTP id 2505D1734A5 for ; Thu, 9 Dec 2004 08:10:05 +0100 (CET) Subject: Re: [XviD-devel] GMC help From: skal To: xvid-devel@xvid.org In-Reply-To: <20041209020443.62515.qmail@web13423.mail.yahoo.com> References: <20041209020443.62515.qmail@web13423.mail.yahoo.com> Content-Type: text/plain Organization: Message-Id: <1102576064.4071.16.camel@latitude344> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 09 Dec 2004 08:08:26 +0100 Content-Transfer-Encoding: 7bit X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Tushit, On Thu, 2004-12-09 at 03:04, Tushit Bharthuar wrote: > Hi, > Is the calculation for effective number of warping > points correct? > if (nb_pts<2 || (pts->duv[2].x==0 && pts->duv[2].y==0 > && pts->duv[1].x==0 && pts->duv[1].y==0 )) { > if (nb_pts<2 || (pts->duv[1].x==0 && > pts->duv[1].y==0)) { > if (nb_pts<1 || (pts->duv[0].x==0 && > pts->duv[0].y==0)) { > nb_pts = 0; > } > else nb_pts = 1; > } > else nb_pts = 2; > } > Shouldnot the checking for pts->duv[1].x==0 && > pts->duv[1].y==0 not be there in the first statement? Why should it? So far the norm is (ugly-ly) designed, nb_pts==3 with duv[2]={0,0} is *not* equivalent to nb_pts==2. Actually, nb_pts==3 can be mapped to nb_pts==2 only when duv[2].x = -duv[1].y and duv[2].y = duv[1].x (notwithstanding the rounding, width and height issues). But, code-wise, this simplification does not alleviate the computations. Only the nb_pts==1 is "interesting"(*) to simplify. bye! Skal (*) "interesting" = using a DivX-based metric, of course. Other people are not "aware" ((C) Jean-Clod) bwehehe _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Thu Dec 9 23:28:59 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id BACA9126D82 for ; Thu, 9 Dec 2004 23:28:59 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id B08E81662B; Thu, 9 Dec 2004 23:35:14 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from smartmx-02.inode.at (smartmx-02.inode.at [213.229.60.34]) by edu.bnhof.de (Postfix) with ESMTP id 02064165F8 for ; Thu, 9 Dec 2004 23:35:08 +0100 (CET) Received: from [62.99.252.218] (port=61949 helo=[192.168.0.2]) by smartmx-02.inode.at with esmtp (Exim 4.34) id 1CcWmH-0007sP-3I for xvid-devel@xvid.org; Thu, 09 Dec 2004 23:28:49 +0100 Message-ID: <41B8D19A.3010402@x-ray.at> Date: Thu, 09 Dec 2004 23:28:42 +0100 From: Reini Urban User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.8a4) Gecko/20040927 X-Accept-Language: de, en MIME-Version: 1.0 To: xvid-devel@xvid.org Subject: Re: [XviD-devel] television server / streaming xvid? References: <41B777D8.4070509@comcast.net> In-Reply-To: <41B777D8.4070509@comcast.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Zack Smith schrieb: > I'm looking for information about this idea of > streaming xvid. The user apakian had said in the > xvid web forum that he had developed a > "television server". Can someone please direct > me to a download ? http://videolan.org -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Fri Dec 10 01:05:34 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 2C265126D82 for ; Fri, 10 Dec 2004 01:05:34 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 896E61655D; Fri, 10 Dec 2004 01:11:50 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from edgomez.kicks-ass.org (edgomez.kicks-ass.org [82.225.208.184]) by edu.bnhof.de (Postfix) with ESMTP id 433701653F for ; Fri, 10 Dec 2004 01:11:47 +0100 (CET) Received: from edy by edgomez.kicks-ass.org with local (Exim 4.34) id 1CcYHo-0006bb-NN for xvid-devel@xvid.org; Fri, 10 Dec 2004 01:05:28 +0100 Date: Fri, 10 Dec 2004 01:05:28 +0100 From: Edouard Gomez To: xvid-devel ML Message-ID: <20041210000528.GE7414@edgomez.kicks-ass.org> Mail-Followup-To: Edouard Gomez , xvid-devel ML Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6+20040907i Subject: [XviD-devel] [BUG] Last patch in encoder.c breaks encoder X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hey, seems like the last patch from sysKin breaks the encoder badly. This patch relies on the fact every block goes through RD optimisation which is obviously bad idea, so encoder ends up trying to encode inter block filled with 0, but these function assume there is at least one non zero value in the 8x8 block and doesn't check for index<64 in order to speed up things a bit. This results in nice segfaults whatever sequence you encode w/o vhq enabled. Meaning all first passes would fail. -- Edouard Gomez _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Fri Dec 10 02:40:19 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 3C803126D82 for ; Fri, 10 Dec 2004 02:40:19 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id BF85216561; Fri, 10 Dec 2004 02:46:35 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from grunt22.ihug.com.au (grunt22.ihug.com.au [203.109.249.142]) by edu.bnhof.de (Postfix) with ESMTP id AC02915929 for ; Fri, 10 Dec 2004 02:46:31 +0100 (CET) Received: from dsl-17.161.240.220.lns02-waym-adl.dsl.comindico.com.au [220.240.161.17] by grunt22.ihug.com.au with esmtp (Exim 3.35 #1 (Debian)) id 1CcZlF-0001zV-00; Fri, 10 Dec 2004 12:39:57 +1100 Message-ID: <41B8FE82.30207@ihug.com.au> Date: Fri, 10 Dec 2004 12:10:18 +1030 From: Radek Czyz User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: xvid-devel@xvid.org Subject: Re: [XviD-devel] [BUG] Last patch in encoder.c breaks encoder References: <20041210000528.GE7414@edgomez.kicks-ass.org> In-Reply-To: <20041210000528.GE7414@edgomez.kicks-ass.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Edouard Gomez wrote: > Hey, > > seems like the last patch from sysKin breaks the encoder badly. > > This patch relies on the fact every block goes through RD optimisation > which is obviously bad idea, so encoder ends up trying to encode inter > block filled with 0, but these function assume there is at least one non > zero value in the 8x8 block and doesn't check for index<64 in order to speed > up things a bit. > > This results in nice segfaults whatever sequence you encode w/o vhq enabled. > Meaning all first passes would fail. What did you ever expect from me? ^^ Now seriously, it's my way of making bugs: I haven't forgotten anything, the non-vhq blocks have (initial) cbp of 63 at all cases I can test (which is good), and I just changed this line: pMB->cbp = MBTransQuantInter(...); into MBTransQuantInter(); so cbp is not updated by transquant. Heh.... Fixed now... Radek _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Fri Dec 10 06:14:57 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 14F7F126D82 for ; Fri, 10 Dec 2004 06:14:57 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 691B31667D; Fri, 10 Dec 2004 06:21:14 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from xvid.org (222-152-215-254.jetstream.xtra.co.nz [222.152.215.254]) by edu.bnhof.de (Postfix) with SMTP id A99141667A for ; Fri, 10 Dec 2004 06:21:10 +0100 (CET) From: michael@xvid.org To: xvid-devel@xvid.org Date: Fri, 10 Dec 2004 18:14:51 +1300 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="67761242" Message-Id: <20041210052110.A99141667A@edu.bnhof.de> X-Content-Filtered-By: Mailman/MimeDel 2.1.4 Subject: [XviD-devel] robos! X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org --67761242 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit veja detalhes!!!. --67761242 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel --67761242-- From xvid-devel-bounces@xvid.org Fri Dec 10 08:57:14 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 7BD69126D82 for ; Fri, 10 Dec 2004 08:57:14 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 81DBD16669; Fri, 10 Dec 2004 09:03:31 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from postfix4-2.free.fr (postfix4-2.free.fr [213.228.0.176]) by edu.bnhof.de (Postfix) with ESMTP id 87C7B16664 for ; Fri, 10 Dec 2004 09:03:29 +0100 (CET) Received: from lille-2-62-147-1-118.dial.proxad.net (lille-2-62-147-1-118.dial.proxad.net [62.147.1.118]) by postfix4-2.free.fr (Postfix) with ESMTP id 939CA25593A for ; Fri, 10 Dec 2004 08:57:07 +0100 (CET) Subject: Re: [XviD-devel] [BUG] Last patch in encoder.c breaks encoder From: skal To: xvid-devel@xvid.org In-Reply-To: <41B8FE82.30207@ihug.com.au> References: <20041210000528.GE7414@edgomez.kicks-ass.org> <41B8FE82.30207@ihug.com.au> Content-Type: text/plain Organization: Message-Id: <1102665296.2936.7.camel@latitude344> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 10 Dec 2004 08:54:56 +0100 Content-Transfer-Encoding: 7bit X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Howdy, On Fri, 2004-12-10 at 02:40, Radek Czyz wrote: > Edouard Gomez wrote: > > Hey, > > > > seems like the last patch from sysKin breaks the encoder badly. > > > > This patch relies on the fact every block goes through RD optimisation > > which is obviously bad idea, so encoder ends up trying to encode inter > > block filled with 0, but these function assume there is at least one non > > zero value in the 8x8 block and doesn't check for index<64 in order to speed > > up things a bit. > > > > This results in nice segfaults whatever sequence you encode w/o vhq enabled. > > Meaning all first passes would fail. > > What did you ever expect from me? ^^ oh! talking about bugs, here's mine: it's been reported in doom9's forum that trellis quant is overflowing for very low Q=1~2. Thanks to Koepi, it seems that either reducing the precision used for trellis (TL_SHIFT) or forbidding usage of trellis for Q<=2 fixes the problem. I'd favor the last solution, which seems to have been tested ok, without noticeable loss of quality. So, if it's ok with you, we could change line 219 of mbtransquant.c to something like: if(sum && pMB->quant>2 && (frame->vop_flags & XVID_VOP_TRELLISQUANT)) { ... } to prevent call of trellis quant for low quant. bye! Skal _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Sun Dec 12 11:30:28 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id D5461126D82 for ; Sun, 12 Dec 2004 11:30:28 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 3100F166BA; Sun, 12 Dec 2004 11:36:43 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from edgomez.kicks-ass.org (edgomez.kicks-ass.org [82.225.208.184]) by edu.bnhof.de (Postfix) with ESMTP id 8584215969 for ; Sun, 12 Dec 2004 11:36:38 +0100 (CET) Received: from edy by edgomez.kicks-ass.org with local (Exim 4.34) id 1CdQzS-0002SN-2z for xvid-devel@xvid.org; Sun, 12 Dec 2004 11:30:10 +0100 Date: Sun, 12 Dec 2004 11:30:10 +0100 From: Edouard Gomez To: xvid-devel ML Message-ID: <20041212103010.GA7374@edgomez.kicks-ass.org> Mail-Followup-To: Edouard Gomez , xvid-devel ML Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6+20040907i Subject: [XviD-devel] [RFC] AMD64 support X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hello, I started merging the work from Andre Werthmann, and i'm wondering if i must include all simd code or just the oneswhich performs best. I mean we know amd64 supports mmx, mmxext, sse, sse2. At the moment i ported the cpuid function just in case we include 3dnow functions. In that case when Intel will ship their emt64 CPUs, we'll have to have an alternative to 3dnow functions... So the question is: - Do i dumbly include all asm code port or, - Do i include only meaningfull functions (mostly xmm functions which perform far better than sse2, and are more accurate than their mmx cousins for MPEG quant) -- Edouard Gomez _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Sun Dec 12 12:13:20 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 17443126D82 for ; Sun, 12 Dec 2004 12:13:20 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 39E621669F; Sun, 12 Dec 2004 12:19:41 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from smtp4.wanadoo.fr (smtp4.wanadoo.fr [193.252.22.27]) by edu.bnhof.de (Postfix) with ESMTP id D176B16695 for ; Sun, 12 Dec 2004 12:19:37 +0100 (CET) Received: from me-wanadoo.net (unknown [127.0.0.1]) by mwinf0406.wanadoo.fr (SMTP Server) with SMTP id 75C2E1C0029E for ; Sun, 12 Dec 2004 12:13:02 +0100 (CET) Received: from blackbird.bzh (Mix-Rennes312-4-50.w80-9.abo.wanadoo.fr [80.9.226.50]) by mwinf0406.wanadoo.fr (SMTP Server) with ESMTP id CB32E1C0029A for ; Sun, 12 Dec 2004 12:13:01 +0100 (CET) Received: from Sketches.bzh (Sketches.bzh [192.168.1.66]) by blackbird.bzh (Postfix) with ESMTP id 680E01325F for ; Sun, 12 Dec 2004 12:13:00 +0100 (CET) Received: by Sketches.bzh (Postfix, from userid 500) id 955D768574; Sun, 12 Dec 2004 12:12:57 +0100 (CET) Subject: Re: [XviD-devel] [RFC] AMD64 support From: Guillaume POIRIER To: xvid-devel ML In-Reply-To: <20041212103010.GA7374@edgomez.kicks-ass.org> References: <20041212103010.GA7374@edgomez.kicks-ass.org> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Date: Sun, 12 Dec 2004 12:12:56 +0100 Message-Id: <1102849977.3174.16.camel@Sketches> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hi, Although I'm not a developer, merely a doc maintainer, I'd like to express myself about this issue... Le dimanche 12 d=E9cembre 2004 =E0 11:30 +0100, Edouard Gomez a =E9crit : > I started merging the work from Andre Werthmann, and i'm wondering > if i must include all simd code or just the oneswhich performs best. > I mean we know amd64 supports mmx, mmxext, sse, sse2. At the moment > i ported the cpuid function just in case we include 3dnow functions. > In that case when Intel will ship their emt64 CPUs, we'll have to > have an alternative to 3dnow functions... AFAIK, XviD already features different SIMD asm for both Athlon and P-IV, so it looks to me that being able to squeeze every CPU cycle using "proprietary" SIMD like 3D-Now! is nothing new, isn't it? > So the question is: > - Do i dumbly include all asm code port or, > - Do i include only meaningfull functions (mostly xmm functions which > perform far better than sse2, and are more accurate than their mmx > cousins for MPEG quant) For that, I couldn't say much but offer my help to test this port as I just set-up an AMD-64 box this week-end. Regards, Guillaume _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Sun Dec 12 12:25:27 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 6E141126D82 for ; Sun, 12 Dec 2004 12:25:27 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 24B39166EB; Sun, 12 Dec 2004 12:31:49 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by edu.bnhof.de (Postfix) with SMTP id A3A72166E5 for ; Sun, 12 Dec 2004 12:31:47 +0100 (CET) Received: (qmail 14642 invoked by uid 65534); 12 Dec 2004 11:25:23 -0000 Received: from pD955FEB5.dip.t-dialin.net (EHLO lofi.dyndns.org) (217.85.254.181) by mail.gmx.net (mp001) with SMTP; 12 Dec 2004 12:25:23 +0100 X-Authenticated: #443188 Received: from kiste.my.domain (kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id iBCBPKuk010847 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Sun, 12 Dec 2004 12:25:21 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) From: Michael Nottebrock To: xvid-devel@xvid.org Date: Sun, 12 Dec 2004 12:25:20 +0100 User-Agent: KMail/1.7.1 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200412121225.20429.michaelnottebrock@gmx.net> X-Virus-Scanned: by amavisd-new Subject: [XviD-devel] Small ia64 buglet in 1.0.2 X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Found this while browsing buildlogs, doesn't seem like there are many xvid users on ia64 FreeBSD since nobody reported it yet. :-) Anyway, patch below. --- src/quant/quant.h     Thu Dec  9 12:19:54 2004 +++ src/quant/quant.h     Thu Dec  9 12:20:07 2004 @@ -82,7 +82,7 @@  #endif  #ifdef ARCH_IS_IA64 -quanth263_intraFunc dequant_intra_ia64; +quant_intraFunc dequant_h263_intra_ia64;  #endif  /***************************************************************************** -- ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Sun Dec 12 12:48:16 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 7299E126D82 for ; Sun, 12 Dec 2004 12:48:14 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id C1C6B1670D; Sun, 12 Dec 2004 12:54:30 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from edgomez.kicks-ass.org (edgomez.kicks-ass.org [82.225.208.184]) by edu.bnhof.de (Postfix) with ESMTP id 9BD761670D for ; Sun, 12 Dec 2004 12:54:26 +0100 (CET) Received: from edy by edgomez.kicks-ass.org with local (Exim 4.34) id 1CdSCn-0002pU-Rb for xvid-devel@xvid.org; Sun, 12 Dec 2004 12:48:01 +0100 Date: Sun, 12 Dec 2004 12:48:01 +0100 From: Edouard Gomez To: xvid-devel@xvid.org Subject: Re: [XviD-devel] [RFC] AMD64 support Message-ID: <20041212114801.GB7374@edgomez.kicks-ass.org> Mail-Followup-To: Edouard Gomez , xvid-devel@xvid.org References: <20041212103010.GA7374@edgomez.kicks-ass.org> <1102849977.3174.16.camel@Sketches> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1102849977.3174.16.camel@Sketches> User-Agent: Mutt/1.5.6+20040907i X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Guillaume POIRIER (guillaume.poirier@etudiant.univ-rennes1.fr) wrote: > AFAIK, XviD already features different SIMD asm for both Athlon and > P-IV, so it looks to me that being able to squeeze every CPU cycle using > "proprietary" SIMD like 3D-Now! is nothing new, isn't it? Well, looking at the active developers, none has an AMD64 computer. I don't pan on buying such a box until the architecture becomes more stable hardware wise, i mean there are already 2 sockets in a 1 year timelife of the CPU, PCI-express is also something being in transition... all this is too risky to make a choice now I'm pretty sure if i buy an AMD64 now, i'll regret my choice. So, considering no developer has an AMD64, maintaining so many lines of code w/o corresponding hardware is a lot harder than you think. SSH access is good for checking you don't do things wrong when merging someone else's work, but it's not ideal. Moreover, amd64 ships with sse2, which is emulated with mmx opcodes... so it's slow. amd64 supports mmxext, so why bothering with mmx (if there is a xmm version) ? Do you get the dilemna now ? It's not like on ia32 CPUs where, to get maxpeed you had to support tons of sub-intruction sets, amd64 is sort of "standardized" arch at the moment, we can rely on stable instruction set at least for this hardware generation. ... until intel decides to enter the market with a mostly compatible CPU but supporting SSE2 and SSE3 natively, because they are intel's technology. -- Edouard Gomez _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Sun Dec 12 14:40:18 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 73FDD126D82 for ; Sun, 12 Dec 2004 14:40:18 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 70C2416694; Sun, 12 Dec 2004 14:46:39 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from mail.broadpark.no (mail.broadpark.no [217.13.4.2]) by edu.bnhof.de (Postfix) with ESMTP id 2567E1592F for ; Sun, 12 Dec 2004 14:46:36 +0100 (CET) Received: from dead2 (195.80-202-50.nextgentel.com [80.202.50.195]) by mail.broadpark.no (Postfix) with ESMTP id 4593750E1 for ; Sun, 12 Dec 2004 14:40:11 +0100 (MET) Message-ID: <004101c4e050$9efdb890$0a00000a@dead2> From: "Hans K. Rosbach" To: References: <20041212103010.GA7374@edgomez.kicks-ass.org><1102849977.3174.16.camel@Sketches> <20041212114801.GB7374@edgomez.kicks-ass.org> Subject: Re: [XviD-devel] [RFC] AMD64 support Date: Sun, 12 Dec 2004 14:43:25 +0100 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org > Well, looking at the active developers, none has an AMD64 computer. > I don't pan on buying such a box until the architecture becomes > more stable hardware wise, i mean there are already 2 sockets in > a 1 year timelife of the CPU, Actually there are 3 sockets: 754, 939, 940 754 is for mainstream desktop use. Single memory channel 939 is for heavy duty single-cpu workstations. Dual memory channels 940 is for servers. 1-8 cpus. Dual memory channels per cpu A new socket roumoured to be 941/942 will be introduced for the DDR2 capable chips around 2006 when DDR2 is fast and cheap. > PCI-express is also something being > in transition... all this is too risky to make a choice now > I'm pretty sure if i buy an AMD64 now, i'll regret my choice. PCI express is right around the corner, and makes the choice equally difficult on the Intel platform aswell. There are big advantages with PCI express, but it should pose no difference in software other than performance. As a side note, Tyan is sampling a dual system that incorporates 3 north-bridge chipsets..! Two nvidia ones, each one has a 16x pci-e and a gbit lan connection. The third is an AMD chipset that provides two pci-x buses. In other words, the ultimate enthusiast or server board.. I want one.. > Moreover, amd64 ships with sse2, which is emulated with mmx opcodes... > so it's slow. amd64 supports mmxext, so why bothering with mmx (if there > is a xmm version) ? Do you get the dilemna now ? It's not like on ia32 CPUs > where, to get maxpeed you had to support tons of sub-intruction sets, amd64 > is sort of "standardized" arch at the moment, we can rely on stable instruction > set at least for this hardware generation. The next generation AMD64 cpus are roumoured to be SSE3 capable, so there are interesting things coming in the future aswell. Also the dual-core cpus will make the speed balance shift somewhat. -=Dead2=- _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Sun Dec 12 15:16:24 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 68BD7126D82 for ; Sun, 12 Dec 2004 15:16:24 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 958121670A; Sun, 12 Dec 2004 15:22:45 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from edgomez.kicks-ass.org (edgomez.kicks-ass.org [82.225.208.184]) by edu.bnhof.de (Postfix) with ESMTP id 0B72416705 for ; Sun, 12 Dec 2004 15:22:40 +0100 (CET) Received: from edy by edgomez.kicks-ass.org with local (Exim 4.34) id 1CdUWF-0003Ut-PI for xvid-devel@xvid.org; Sun, 12 Dec 2004 15:16:15 +0100 Date: Sun, 12 Dec 2004 15:16:15 +0100 From: Edouard Gomez To: xvid-devel@xvid.org Subject: Re: [XviD-devel] [RFC] AMD64 support Message-ID: <20041212141615.GC7374@edgomez.kicks-ass.org> Mail-Followup-To: Edouard Gomez , xvid-devel@xvid.org References: <20041212114801.GB7374@edgomez.kicks-ass.org> <004101c4e050$9efdb890$0a00000a@dead2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <004101c4e050$9efdb890$0a00000a@dead2> User-Agent: Mutt/1.5.6+20040907i X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hans K. Rosbach (hk@circlestorm.org) wrote: > > Well, looking at the active developers, none has an AMD64 computer. > > I don't pan on buying such a box until the architecture becomes > > more stable hardware wise, i mean there are already 2 sockets in > > a 1 year timelife of the CPU, > > Actually there are 3 sockets: 754, 939, 940 > > 754 is for mainstream desktop use. Single memory channel > 939 is for heavy duty single-cpu workstations. Dual memory channels > 940 is for servers. 1-8 cpus. Dual memory channels per cpu Ah see i missed one :-) > A new socket roumoured to be 941/942 will be introduced for > the DDR2 capable chips around 2006 when DDR2 is fast and cheap. Ok ok so even more choice in so little timelife. > > PCI-express is also something being > > in transition... all this is too risky to make a choice now > > I'm pretty sure if i buy an AMD64 now, i'll regret my choice. > > PCI express is right around the corner, and makes the choice equally difficult > on the Intel platform aswell. There are big advantages with PCI express, but > it should pose no difference in software other than performance. But, my development machine is my desktop machine, so the bucks i put on it directly impact other components i use for my pleasure(tm). A NVidia 6600 SLI config would be yummy :-) The main problem i have for choice is that i need to upgrade my Graphic card. And if i want to still have the option to pay my GCs at low price, it seems i'll have to buy a PCIe MB, and if i want to keep the SLI option as well, i'll have to buy a nforce4 chipset driven MB. But linux support for nforce is bad, i don't like having "binary drivers only" for so important pieces of hardware. So now, mix that with my will to have a SLI system and an AMD64 CPU and you'll understand why i don't want to make my choice now... i'll patiently wait before i can play with fragment shaders on my new geForce and kick some monsters' asses in Doom3 :-) > As a side note, Tyan is sampling a dual system that incorporates 3 north-bridge > chipsets..! Two nvidia ones, each one has a 16x pci-e and a gbit lan connection. > The third is an AMD chipset that provides two pci-x buses. In other words, the > ultimate enthusiast or server board.. I want one.. > > > Moreover, amd64 ships with sse2, which is emulated with mmx opcodes... > > so it's slow. amd64 supports mmxext, so why bothering with mmx (if there > > is a xmm version) ? Do you get the dilemna now ? It's not like on ia32 CPUs > > where, to get maxpeed you had to support tons of sub-intruction sets, amd64 > > is sort of "standardized" arch at the moment, we can rely on stable > instruction > > set at least for this hardware generation. > > The next generation AMD64 cpus are roumoured to be SSE3 capable, so > there are interesting things coming in the future aswell. Well unless it's emulated :-) > Also the dual-core cpus will make the speed balance shift somewhat. That's only an OS thing, it will not impact xvidcore arch. -- Edouard Gomez _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Sun Dec 12 16:56:42 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 6C2E5126D82 for ; Sun, 12 Dec 2004 16:56:42 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 51121BFE9; Sun, 12 Dec 2004 17:03:04 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from mail.broadpark.no (mail.broadpark.no [217.13.4.2]) by edu.bnhof.de (Postfix) with ESMTP id D3F6C9CC6 for ; Sun, 12 Dec 2004 17:03:00 +0100 (CET) Received: from dead2 (195.80-202-50.nextgentel.com [80.202.50.195]) by mail.broadpark.no (Postfix) with ESMTP id 4B2D8557C for ; Sun, 12 Dec 2004 16:56:35 +0100 (MET) Message-ID: <000901c4e063$ad14eb70$0a00000a@dead2> From: "Hans K. Rosbach" To: References: <20041212114801.GB7374@edgomez.kicks-ass.org><004101c4e050$9efdb890$0a00000a@dead2> <20041212141615.GC7374@edgomez.kicks-ass.org> Subject: Re: [XviD-devel] [RFC] AMD64 support Date: Sun, 12 Dec 2004 17:00:17 +0100 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org > So now, mix that with my will to have a SLI system and an AMD64 CPU and you'll > understand why i don't want to make my choice now... i'll patiently wait > before i can play with fragment shaders on my new geForce and kick some > monsters' asses in Doom3 :-) You need to get the Tyan card I mentioned then.. =) http://www.theinquirer.net/?article=20030 > > The next generation AMD64 cpus are roumoured to be SSE3 capable, so > > there are interesting things coming in the future aswell. > Well unless it's emulated :-) Lets hope it's not. > > Also the dual-core cpus will make the speed balance shift somewhat. > That's only an OS thing, it will not impact xvidcore arch. Nah, I'm talking about cache optimizations. Should not change on the AMD unless they add a shared L3 cache, but for Intel with the shared L2 cache it's bound to become another factor to take into account when optimizing for several cpu types. -=Dead2=- _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Sun Dec 12 19:03:18 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id EE019126D82 for ; Sun, 12 Dec 2004 19:03:17 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id BDE41153EA; Sun, 12 Dec 2004 19:09:39 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by edu.bnhof.de (Postfix) with ESMTP id 3FDBD14CDD for ; Sun, 12 Dec 2004 19:09:36 +0100 (CET) Received: from [194.97.50.144] (helo=mx1.freenet.de) by mout1.freenet.de with esmtpa (Exim 4.43) id 1CdY3s-0001z8-8b for xvid-devel@xvid.org; Sun, 12 Dec 2004 19:03:12 +0100 Received: from p5487d380.dip.t-dialin.net ([84.135.211.128] helo=smk.imweber.dyndns.org) by mx1.freenet.de with esmtpsa (ID stkrause@justmail.de) (TLSv1:RC4-SHA:128) (Exim 4.43 #13) id 1CdY3s-0002cv-1V for xvid-devel@xvid.org; Sun, 12 Dec 2004 19:03:12 +0100 Received: from stkrause by smk.imweber.dyndns.org with local (Exim 4.34) id 1CdY3r-0001YA-FK for xvid-devel@xvid.org; Sun, 12 Dec 2004 19:03:11 +0100 From: Stephan Krause To: xvid-devel@xvid.org Subject: Re: [XviD-devel] Small ia64 buglet in 1.0.2 Date: Sun, 12 Dec 2004 19:03:11 +0100 User-Agent: KMail/1.7.1 References: <200412121225.20429.michaelnottebrock@gmx.net> In-Reply-To: <200412121225.20429.michaelnottebrock@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412121903.11304.s_kraste@ira.uka.de> X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Michael Nottebrock wrote: > Found this while browsing buildlogs, doesn't seem like there are many xvid > users on ia64 FreeBSD since nobody reported it yet. :-) To be honest, I'm surprised there are only so few errors... I lost my ia64 acc some one-and-a-half year ago, so there has been no testing form my part... I would be glad to hear about some test results, if you had any... And there should be much place for optimizations, as the code was written on (and optimized for) an itanium 1, so I think the assembly could perform much, much better. If I happen to have some spare time, I maybe try gathering some of the people who first wrote the ia64 port and do some coding (and get a fresh account on an itanium 2). But I can't make any promises, as I have to write my diploma thesis... Regards, Step'would-like-to-be-ia64-"maintainer"-but-doesn't-have-enough-time'han _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Sun Dec 12 22:32:58 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id B1C00126D82 for ; Sun, 12 Dec 2004 22:32:58 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 39D35167DC; Sun, 12 Dec 2004 22:39:20 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from smtp06.web.de (smtp06.web.de [217.72.192.224]) by edu.bnhof.de (Postfix) with ESMTP id 20B2A167D1 for ; Sun, 12 Dec 2004 22:39:16 +0100 (CET) Received: from [84.135.94.220] (helo=p54875EDC.dip.t-dialin.net) by smtp06.web.de with esmtp (WEB.DE 4.103 #184) id 1CdbKl-0007nP-00 for xvid-devel@xvid.org; Sun, 12 Dec 2004 22:32:51 +0100 From: Martin Kuball To: xvid-devel@xvid.org Date: Sun, 12 Dec 2004 21:01:04 +0100 User-Agent: KMail/1.7.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412122101.04142.MartinKuball@web.de> X-Sender: MartinKuball@web.de Subject: [XviD-devel] documentation of mpeg4 bitstream format? X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hi! I'm looking for some documentation about the mpeg 4 bitstream format. Is there any doc available on the internet for free? Or is the only way to try to understand the xvid bitstream source code? Which does lool like a lot of work and time. Martin _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Sun Dec 12 22:34:10 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 3254C126D82 for ; Sun, 12 Dec 2004 22:34:10 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 3F5C1167E4; Sun, 12 Dec 2004 22:40:33 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from hotmail.com (bay20-f13.bay20.hotmail.com [64.4.54.102]) by edu.bnhof.de (Postfix) with ESMTP id AD14F167E1 for ; Sun, 12 Dec 2004 22:40:30 +0100 (CET) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 12 Dec 2004 13:34:00 -0800 Message-ID: Received: from 210.50.40.185 by by20fd.bay20.hotmail.msn.com with HTTP; Sun, 12 Dec 2004 21:33:14 GMT X-Originating-IP: [210.50.40.185] X-Originating-Email: [a_dunstan@hotmail.com] X-Sender: a_dunstan@hotmail.com In-Reply-To: <20041212103010.GA7374@edgomez.kicks-ass.org> From: "Andrew Dunstan" To: xvid-devel@xvid.org Subject: RE: [XviD-devel] [RFC] AMD64 support Date: Mon, 13 Dec 2004 08:33:14 +1100 Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-OriginalArrivalTime: 12 Dec 2004 21:34:00.0845 (UTC) FILETIME=[4B6C43D0:01C4E092] X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org >So the question is: > - Do i dumbly include all asm code port or, > - Do i include only meaningfull functions (mostly xmm functions which > perform far better than sse2, and are more accurate than their mmx > cousins for MPEG quant) Not sure if you consider this relevant, but the x86-64 version of windows only supports SSE and SSE2 instructions using the XMM registers so all functions need to be 128-bit. Also from what I can gather windows uses different registers to pass function parameters from those used in linux. _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Sun Dec 12 23:08:19 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id C8F55126D82 for ; Sun, 12 Dec 2004 23:08:19 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 25EC5167FA; Sun, 12 Dec 2004 23:14:42 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from edgomez.kicks-ass.org (edgomez.kicks-ass.org [82.225.208.184]) by edu.bnhof.de (Postfix) with ESMTP id 71B3F167F7 for ; Sun, 12 Dec 2004 23:14:39 +0100 (CET) Received: from edy by edgomez.kicks-ass.org with local (Exim 4.34) id 1Cdbsz-0005Px-HG for xvid-devel@xvid.org; Sun, 12 Dec 2004 23:08:13 +0100 Date: Sun, 12 Dec 2004 23:08:13 +0100 From: Edouard Gomez To: xvid-devel@xvid.org Subject: Re: [XviD-devel] [RFC] AMD64 support Message-ID: <20041212220813.GF7374@edgomez.kicks-ass.org> Mail-Followup-To: Edouard Gomez , xvid-devel@xvid.org References: <20041212103010.GA7374@edgomez.kicks-ass.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6+20040907i X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Andrew Dunstan (a_dunstan@hotmail.com) wrote: > >So the question is: > > - Do i dumbly include all asm code port or, > > - Do i include only meaningfull functions (mostly xmm functions which > > perform far better than sse2, and are more accurate than their mmx > > cousins for MPEG quant) > > Not sure if you consider this relevant, but the x86-64 version of windows > only supports SSE and SSE2 instructions using the XMM registers so all > functions need to be 128-bit. Also from what I can gather windows uses > different registers to pass function parameters from those used in linux. Well, well, well... Firstly i'd say: why on earth would windows forbid the usage of 64 bit instructions on a 64bit processor ? ;-) Secondly i'd add: That would be very bad for windows users, because the port i merge is then only unix friendly. Thirdly i'd conclude by: Contributions will be welcomed if that's true. Fourthly i'll post script by: I didn't check if that's true at all, but i doubt MS would do such a stupid thing. As for the register convention, well this could be true. -- Edouard Gomez _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Mon Dec 13 03:30:55 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 6C501126D82 for ; Mon, 13 Dec 2004 03:30:55 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 1E14A166F5; Mon, 13 Dec 2004 03:37:17 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from hotmail.com (bay20-f32.bay20.hotmail.com [64.4.54.121]) by edu.bnhof.de (Postfix) with ESMTP id 87FF8166F2 for ; Mon, 13 Dec 2004 03:37:12 +0100 (CET) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 12 Dec 2004 18:29:04 -0800 Message-ID: Received: from 210.50.40.185 by by20fd.bay20.hotmail.msn.com with HTTP; Mon, 13 Dec 2004 02:28:07 GMT X-Originating-IP: [210.50.40.185] X-Originating-Email: [a_dunstan@hotmail.com] X-Sender: a_dunstan@hotmail.com In-Reply-To: <20041212220813.GF7374@edgomez.kicks-ass.org> From: "Andrew Dunstan" To: xvid-devel@xvid.org Subject: Re: [XviD-devel] [RFC] AMD64 support Date: Mon, 13 Dec 2004 13:28:07 +1100 Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-OriginalArrivalTime: 13 Dec 2004 02:29:04.0304 (UTC) FILETIME=[8381BB00:01C4E0BB] X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org >Firstly i'd say: why on earth would windows forbid the usage of 64 bit >instructions > on a 64bit processor ? ;-) I'm not absolutely positive about this (meaning I haven't tested it myself), but I do know windows doesn't save the x87 stack between task switches. The compiler also doesn't support intrinsics which use the _m64 data type (not that any intrinsics are used here, but if their compiler doesn't support 64 bits...). To be sure I'll assemble some MMXEXT code and see what happens. > >Secondly i'd add: That would be very bad for windows users, because the >port i merge > is then only unix friendly. Windows passing method: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/kmarch/hh/kmarch/64bitAMD_b93fc900-b7fb-4dad-b8bd-1510ee99f62f.xml.asp Maybe some "%if DEFINED" (where DEFINED is the target os) in the .asm files to move the parameters into known registers, or else maintain a new set of asm for windows? Also on windows the following registers are non-volatile (must be preserved by called function): r12:r15 rdi, rsi, rbx, rbp, rsp the low 64-bits of xmm6:xmm15 <- would require changes to current assembly > >Thirdly i'd conclude by: Contributions will be welcomed if that's true. I've already taken most of the 128-bit assembly and made it work under x86-64 windows. Apart from the parameter passing, it's nearly the same as the linux stuff. Having both in one source might get messy, but it's possible. _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Tue Dec 14 01:08:56 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 3A877126D82 for ; Tue, 14 Dec 2004 01:08:56 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 33E0A1677B; Tue, 14 Dec 2004 01:15:18 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from edgomez.kicks-ass.org (edgomez.kicks-ass.org [82.225.208.184]) by edu.bnhof.de (Postfix) with ESMTP id 7475816778 for ; Tue, 14 Dec 2004 01:15:09 +0100 (CET) Received: from edy by edgomez.kicks-ass.org with local (Exim 4.34) id 1Ce0F8-0003FT-8C for xvid-devel@xvid.org; Tue, 14 Dec 2004 01:08:42 +0100 Date: Tue, 14 Dec 2004 01:08:42 +0100 From: Edouard Gomez To: xvid-devel ML Message-ID: <20041214000842.GC6728@edgomez.kicks-ass.org> Mail-Followup-To: Edouard Gomez , xvid-devel ML Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6+20040907i Subject: [XviD-devel] Small report from my amd64 merging effort X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hello, Just a small and fast report about how things are going with my amd64 merge from Andre Werthmann. The commit logs from an arch/tla repo on a amd64 box: base-0 tag of ed.gomez@free.fr--2004-1/xvidcore--head--0.0--patch-96 patch-1 Merged mainline up to patch-101 patch-2 Merged mainline again for hotfixes patch-3 Added x86_64 detection in configure system patch-4 Added src/utils/x86_64_asm files patch-5 Added /src/quant/x86_64_asm files patch-6 Added src/motion/x86_64_asm files All patches include work from the original port + my special and usual cleaning touch that makes me such a pedantic maintainer :-) Well in fact, my pedantic level seems to lower a bitlately as some of you may have noticed, because there is still place left for improvements, the more obvious one being not swaping registers to match the 32 bit code register mapping :-) i'd be better adapting the code surrounding these parts . But the majority of the port is clean enough. I had just to make sure elf function marking was right and another few small details, like testing everytime new functions were merged in order to make sure the function were behaving 1:1 as the ia32 port. I'll merge into my public tree at [1] pretty soon, and if everything seems right... it'll actually make its way to the CVS a bit after. Just a quick poll on this mailing list: Who's able to test the port once i manage publishing it properly for 1.1 tree ? [1] http://ed.gomez.free.fr/arch-repositories/ed.gomez@free.fr--2004-1 PS: thks to Andre Werthmann for the port thks to David Liontooth for giving me an ssh access to a bi-opteron box. -- Edouard Gomez _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Tue Dec 14 15:52:45 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id E6D9B126D82 for ; Tue, 14 Dec 2004 15:52:44 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id CF84415A1E; Tue, 14 Dec 2004 15:59:03 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from mailserv.aei.mpg.de (mailserv.aei.mpg.de [194.94.224.6]) by edu.bnhof.de (Postfix) with ESMTP id 9773B15953 for ; Tue, 14 Dec 2004 15:59:02 +0100 (CET) Received: by mailserv.aei.mpg.de (Postfix, from userid 65534) id CE5DD2D3E11; Tue, 14 Dec 2004 15:51:34 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mailserv.aei.mpg.de (Postfix) with ESMTP id 96F9E2D4316 for ; Tue, 14 Dec 2004 15:51:34 +0100 (CET) Received: from silentbox17.aei.mpg.de (silentbox17.aei.mpg.de [172.16.27.17]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client did not present a certificate) by mailserv.aei.mpg.de (Postfix) with ESMTP id 547262B8C4A for ; Tue, 14 Dec 2004 15:51:32 +0100 (CET) Date: Tue, 14 Dec 2004 15:51:31 +0100 (CET) From: Andre Werthmann To: xvid-devel@xvid.org Subject: RE: [XviD-devel] [RFC] AMD64 support In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS snapshot-20020531 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on mailserv.aei.mpg.de X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=no version=2.64 X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org On Mon, 13 Dec 2004, Andrew Dunstan wrote: >> So the question is: >> - Do i dumbly include all asm code port or, >> - Do i include only meaningfull functions (mostly xmm functions which >> perform far better than sse2, and are more accurate than their mmx >> cousins for MPEG quant) > > Not sure if you consider this relevant, but the x86-64 version of windows > only supports SSE and SSE2 instructions using the XMM registers so all > functions need to be 128-bit. Also from what I can gather windows uses > different registers to pass function parameters from those used in linux. The ABI for passing integer arguments is different in windows and linux. In linux (that's what I used for the port), %rdi, %rsi, %rdx, %rcx, %r8 and %r9 are used to pass INT type parameters, in windows rcx, rdx, r8 and r9 are used. Further arguments are pushed on the stack. (Also on windows parameters smaller than 64 bits are not zero extended while in linux they are.) > > > _______________________________________________ > XviD-devel mailing list > XviD-devel@xvid.org > http://list.xvid.org/mailman/listinfo/xvid-devel > > _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Tue Dec 14 21:21:37 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 35904126D82 for ; Tue, 14 Dec 2004 21:21:37 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id DEEB715945; Tue, 14 Dec 2004 21:27:56 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from smtp2.wanadoo.fr (smtp2.wanadoo.fr [193.252.22.29]) by edu.bnhof.de (Postfix) with ESMTP id 22BA815945 for ; Tue, 14 Dec 2004 21:27:53 +0100 (CET) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0204.wanadoo.fr (SMTP Server) with SMTP id 5BEDD1C00256 for ; Tue, 14 Dec 2004 21:21:20 +0100 (CET) Received: from blackbird.bzh (Mix-Rennes301-1-137.w193-250.abo.wanadoo.fr [193.250.27.137]) by mwinf0204.wanadoo.fr (SMTP Server) with ESMTP id DC7BC1C00255 for ; Tue, 14 Dec 2004 21:21:19 +0100 (CET) Received: from Sketches.bzh (Sketches.bzh [192.168.1.66]) by blackbird.bzh (Postfix) with ESMTP id 9771913284 for ; Tue, 14 Dec 2004 21:20:24 +0100 (CET) Received: by Sketches.bzh (Postfix, from userid 500) id 0920E53846; Tue, 14 Dec 2004 21:20:22 +0100 (CET) Subject: Re: [XviD-devel] Small report from my amd64 merging effort From: Guillaume POIRIER To: xvid-devel ML In-Reply-To: <20041214000842.GC6728@edgomez.kicks-ass.org> References: <20041214000842.GC6728@edgomez.kicks-ass.org> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Date: Tue, 14 Dec 2004 21:20:21 +0100 Message-Id: <1103055621.4205.7.camel@Sketches> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hi, Le mardi 14 d=E9cembre 2004 =E0 01:08 +0100, Edouard Gomez a =E9crit : > Just a quick poll on this mailing list: > Who's able to test the port once i manage publishing it properly for 1.1 > tree ? >=20 > [1] > http://ed.gomez.free.fr/arch-repositories/ed.gomez@free.fr--2004-1 Yes, I'll be able to test the port this weekend.=20 ... but as I'm absolue newbie on using arch, I'll have to dig thought the doc to figure out how to get the latest revision of your tree... unless someone tells me what to type? ,-) Regards, Guillaume _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Wed Dec 15 10:02:39 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 2883C126D82 for ; Wed, 15 Dec 2004 10:02:39 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 629AD163FE; Wed, 15 Dec 2004 10:08:58 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from web15305.mail.bjs.yahoo.com (web15305.mail.cnb.yahoo.com [202.43.216.180]) by edu.bnhof.de (Postfix) with SMTP id 98CC715A2D for ; Wed, 15 Dec 2004 10:08:51 +0100 (CET) Message-ID: <20041215090206.71619.qmail@web15305.mail.bjs.yahoo.com> Received: from [211.95.163.86] by web15305.mail.cnb.yahoo.com via HTTP; Wed, 15 Dec 2004 17:02:06 CST Date: Wed, 15 Dec 2004 17:02:06 +0800 (CST) From: mayfig To: Xvid MIME-Version: 1.0 Content-Type: text/plain; charset=gb2312 Content-Transfer-Encoding: 8bit Subject: [XviD-devel] Inquiry Skal About Decoding field predicted MacroBlock X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hi, When Xvid decodes an interlaced sequence which includes field-predicted MB, it does not function well ,for it has problem on the motion compensation in this case, i am trying to correct it, although has got some improved result, but still not satisfactory. I noticed that Skal has good implementation in his "sklmp4-0.23" for the special case, so could Skal reply some of my inquiry? 1) in the interlaced mode, the decoded reference MB:( dec->refn[ref].y ,dec->refn[ref].u,dec->refn[ref].v,) and the decoded current MB (dec->cur.y,dec->cur.u,dec->cur.v) , are organized in the mode of Frame Picture, i.e. , the two fields of the frame are interleaved, Am I right? So I changed the function which implements interpolation accordingly. 2) with respect to the Subclause of 7.7.2, i corrects the computation of MVx,MVy. and also updates the referenced MV. 3) With respect to Subclause 6.3.6.3, also taking the forward_top_field_reference and forward_bottom_field_reference flag into account. And I think the referenced field comes from the previous VOP, am i right? Since the description about the referenced field in ISO/IEC 13808-2, there is some difference, Am i right? Thanks. _________________________________________________________ Do You Yahoo!? ×¢²áÊÀ½çÒ»Á÷Æ·ÖʵÄÑÅ»¢Ãâ·ÑµçÓÊ http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/ _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Wed Dec 15 18:17:29 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id B08E8126D82 for ; Wed, 15 Dec 2004 18:17:29 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 34C8C166E8; Wed, 15 Dec 2004 18:23:54 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from rax8.informatik.uni-stuttgart.de (ramail.informatik.uni-stuttgart.de [129.69.183.98]) by edu.bnhof.de (Postfix) with ESMTP id 23CFC166E5 for ; Wed, 15 Dec 2004 18:23:50 +0100 (CET) Received: from [129.69.183.35] (rai35.informatik.uni-stuttgart.de [129.69.183.35]) by rax8.informatik.uni-stuttgart.de (Postfix) with ESMTP id A35BE224F7 for ; Wed, 15 Dec 2004 18:17:19 +0100 (CET) Message-ID: <41C0719F.1080104@gmx.at> Date: Wed, 15 Dec 2004 18:17:19 +0100 From: iibot User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: en-us, en MIME-Version: 1.0 To: xvid-devel@xvid.org Subject: Re: [XviD-devel] [RFC] AMD64 support References: <20041212114801.GB7374@edgomez.kicks-ass.org><004101c4e050$9efdb890$0a00000a@dead2> <20041212141615.GC7374@edgomez.kicks-ass.org> <000901c4e063$ad14eb70$0a00000a@dead2> In-Reply-To: <000901c4e063$ad14eb70$0a00000a@dead2> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: iibot@gmx.at, xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hans K. Rosbach wrote: >>>The next generation AMD64 cpus are roumoured to be SSE3 capable, so >>>there are interesting things coming in the future aswell. >>Well unless it's emulated :-) > Lets hope it's not. Where does this rumor stem from? If I understood the A64 specs correctly, SSE2 is not emulated. Please point me to any relevant information about this. The main problem is the lower clock since SSE2 deals with 2 FP OPs per clock and PIV is still king there. A multiscalar SSE2 unit would rock, though. bis besser, Tobias _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Wed Dec 15 19:46:38 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 0A3E5126D82 for ; Wed, 15 Dec 2004 19:46:38 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 08438BFFF; Wed, 15 Dec 2004 19:53:05 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from edgomez.kicks-ass.org (edgomez.kicks-ass.org [82.225.208.184]) by edu.bnhof.de (Postfix) with ESMTP id 0B6319C66 for ; Wed, 15 Dec 2004 19:53:00 +0100 (CET) Received: from edy by edgomez.kicks-ass.org with local (Exim 4.34) id 1CeMfK-0003Si-02 for xvid-devel@xvid.org; Wed, 15 Dec 2004 01:05:14 +0100 Date: Wed, 15 Dec 2004 01:05:13 +0100 From: Edouard Gomez To: xvid-devel ML Subject: Re: [XviD-devel] Small report from my amd64 merging effort Message-ID: <20041215000513.GA6845@edgomez.kicks-ass.org> Mail-Followup-To: Edouard Gomez , xvid-devel ML References: <20041214000842.GC6728@edgomez.kicks-ass.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041214000842.GC6728@edgomez.kicks-ass.org> User-Agent: Mutt/1.5.6+20040907i X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Edouard Gomez (ed.gomez@free.fr) wrote: > I'll merge into my public tree at [1] pretty soon, and if everything > seems right... it'll actually make its way to the CVS a bit after. Ok some teasing for people who will soon test it: * mencoder+libavcodec as of 2004-12-07 * xvidcore head patch 103 from my tree (probably equivalent to cvs head) + mostly all relevant functions when dealing with options i used for the encoding test. * options used: max_bframes=1:bquant_ratio=150:bquant_offset=100:bf_threshold=0:\ chroma_me:vhq=4:bvhq=0:trellis * Bi-AMD Opteron(tm) Processor 240 (but i don't think the mencoder task migrates CPUs, the load stayed around 50% as mencoder is single threaded). For reference, this CPU is clocked at 1.4GHz * Debian GNU/Linux x86_64 (no 32bit compatibility mode used), 2.6.9-ac kernel There are two runs, they're configured this way: ./configure --prefix=${HOME}/opt/xvidcore --disable-assembly ./configure --prefix=${HOME}/opt/xvidcore C code only: $ time ./twopass-tests.sh =============================================================================== Two pass test name: underworld-trailer Using cached first pass stats (hash - ebffd716144b645ec3013b9db5fb1b4d) Results: xvid: Min PSNR y : 31.73 dB, u : 38.62 dB, v : 44.60 dB, in frame 2581 xvid: Average PSNR y : 39.32 dB, u : 43.08 dB, v : 45.47 dB, for 3534 frames xvid: Max PSNR y : 99.99 dB, u : 99.99 dB, v : 99.99 dB, in frame 1336 Filesize: 15339702 bytes =============================================================================== real 9m26.308s user 9m26.033s sys 0m0.245s Optimized run: $ time ./twopass-tests.sh =============================================================================== Two pass test name: underworld-trailer Using cached first pass stats (hash - ebffd716144b645ec3013b9db5fb1b4d) Results: xvid: Min PSNR y : 31.75 dB, u : 38.59 dB, v : 44.42 dB, in frame 2581 xvid: Average PSNR y : 39.32 dB, u : 43.08 dB, v : 45.47 dB, for 3534 frames xvid: Max PSNR y : 99.99 dB, u : 99.99 dB, v : 99.99 dB, in frame 1336 Filesize: 15336108 bytes =============================================================================== real 3m18.491s user 3m18.281s sys 0m0.218s For reference on my AthlonXP 2200+ (clocked 1.8GHz, no oclocking), Debian i386, 2.6.10-rc3-ck1 (the task scheduler is different, and can influence the bench). Mostly the same softwares. The set of functions used in XviD differ (i use 3dnow functions, and i decided not to port these functions in the x86_64 port) =============================================================================== Two pass test name: underworld-trailer Using cached first pass stats (hash - ebffd716144b645ec3013b9db5fb1b4d) Results: xvid: Min PSNR y : 31,73 dB, u : 38,62 dB, v : 44,45 dB, in frame 2581 xvid: Average PSNR y : 39,33 dB, u : 43,09 dB, v : 45,48 dB, for 3534 frames xvid: Max PSNR y : 99,99 dB, u : 99,99 dB, v : 99,99 dB, in frame 1336 Filesize: 15329386 bytes =============================================================================== real 4m35.253s user 4m28.634s sys 0m0.569s To sump up: - x86_64 non optimized: 6.2fps - x86_64 optimized for this encoding option set: 17.8fps - ia32 optimized: 12.8fps So stay tuned ;-) -- Edouard Gomez _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Wed Dec 15 20:00:31 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 11669126D82 for ; Wed, 15 Dec 2004 20:00:31 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id F3653BFFA; Wed, 15 Dec 2004 20:06:49 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from ftp.ilog.fr (ftp.ilog.fr [81.80.162.195]) by edu.bnhof.de (Postfix) with ESMTP id EAE379C54 for ; Wed, 15 Dec 2004 20:06:47 +0100 (CET) Received: from laposte.ilog.fr (cerbere-qfe0 [81.80.162.193]) by ftp.ilog.fr (8.13.1/8.13.0) with ESMTP id iBFJ0Hdf010382 for ; Wed, 15 Dec 2004 20:00:17 +0100 (MET) Received: from latitude344 ([172.17.4.249]) by laposte.ilog.fr (8.13.1/8.13.1) with ESMTP id iBFJ0Bp0008378 for ; Wed, 15 Dec 2004 20:00:11 +0100 (MET) Subject: Re: [XviD-devel] Inquiry Skal About Decoding field predicted MacroBlock From: skal To: xvid-devel@xvid.org In-Reply-To: <20041215090206.71619.qmail@web15305.mail.bjs.yahoo.com> References: <20041215090206.71619.qmail@web15305.mail.bjs.yahoo.com> Content-Type: text/plain Organization: Message-Id: <1103136977.1481.86.camel@latitude344> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 15 Dec 2004 19:56:18 +0100 Content-Transfer-Encoding: 7bit X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hi Mayfig, On Wed, 2004-12-15 at 10:02, mayfig wrote: > Hi, > > When Xvid decodes an interlaced sequence which includes field-predicted > MB, it does not function well ,for it has problem on the motion compensation in > this case, i am trying to correct it, although has got some improved result, > but still > not satisfactory. > > I noticed that Skal has good implementation in his "sklmp4-0.23" for the > special case, so could Skal reply some of my inquiry? > > 1) in the interlaced mode, the decoded reference MB:( dec->refn[ref].y > ,dec->refn[ref].u,dec->refn[ref].v,) and the decoded current MB > (dec->cur.y,dec->cur.u,dec->cur.v) , are organized in the mode of Frame > Picture, i.e. , the two fields of the frame are interleaved, Am I right? yep. (=> to access fields, you just have to double the stride) > > 3) With respect to Subclause 6.3.6.3, also taking the > forward_top_field_reference > and forward_bottom_field_reference flag into account. And I think the > referenced field comes from the previous VOP, am i right? Indeed, at the beginning of a VOP, you must re-use the field references (top bottom *and* forward/backward) of the last macroblock of the previous VOP. This is also important to store field reference in P-VOP, in case a field-predicted BDirect mode shows up in a subsequent B-VOP. hope it helps, Skal _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Thu Dec 16 15:40:33 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id E1032126D82 for ; Thu, 16 Dec 2004 15:40:32 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 18C751666F; Thu, 16 Dec 2004 15:46:55 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from web15305.mail.bjs.yahoo.com (web15305.mail.cnb.yahoo.com [202.43.216.180]) by edu.bnhof.de (Postfix) with SMTP id BDFC41665D for ; Thu, 16 Dec 2004 15:46:49 +0100 (CET) Message-ID: <20041216091329.76403.qmail@web15305.mail.bjs.yahoo.com> Received: from [211.95.163.86] by web15305.mail.cnb.yahoo.com via HTTP; Thu, 16 Dec 2004 17:13:29 CST Date: Thu, 16 Dec 2004 17:13:29 +0800 (CST) From: mayfig To: xvid-devel@xvid.org In-Reply-To: <1103136977.1481.86.camel@latitude344> MIME-Version: 1.0 Content-Type: text/plain; charset=gb2312 Content-Transfer-Encoding: 8bit Subject: [XviD-devel] Re-Inquiry Skal About Decoding field predicted MacroBlock X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hi,Skal Thanks. Still i want more info about the following > > 3) With respect to Subclause 6.3.6.3, also taking the > > forward_top_field_reference > > and forward_bottom_field_reference flag into account. And I think the > > referenced field comes from the previous VOP, am i right? > > Indeed, at the beginning of a VOP, you must re-use the field > references (top bottom *and* forward/backward) of the last > macroblock of the previous VOP. This is also important to store > field reference in P-VOP, in case a field-predicted BDirect > mode shows up in a subsequent B-VOP. > That means, if the VOP sequence is : I-P-P-P-P-P....-I, after decoding the first P-VOP, i have to store the field references of the last field predicted macroblock of the first P-VOP, and then use the stored field reference ,when decoding the second P-VOP, and in turn.... I am not sure if my understanding is right or not,and do not know why.Would you plz give me more explanation? Take your time. Regards, Mayfig _________________________________________________________ Do You Yahoo!? ×¢²áÊÀ½çÒ»Á÷Æ·ÖʵÄÑÅ»¢Ãâ·ÑµçÓÊ http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/ _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Sat Dec 18 06:00:49 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 4B9AE126D82 for ; Sat, 18 Dec 2004 06:00:49 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 798751593B; Sat, 18 Dec 2004 06:07:16 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from grunt22.ihug.com.au (grunt22.ihug.com.au [203.109.249.142]) by edu.bnhof.de (Postfix) with ESMTP id C8FE9153FA for ; Sat, 18 Dec 2004 06:07:10 +0100 (CET) Received: from dsl-17.161.240.220.lns02-waym-adl.dsl.comindico.com.au [220.240.161.17] by grunt22.ihug.com.au with esmtp (Exim 3.35 #1 (Debian)) id 1CfWhi-00019D-00; Sat, 18 Dec 2004 16:00:31 +1100 Message-ID: <41C3B997.1020002@ihug.com.au> Date: Sat, 18 Dec 2004 15:31:11 +1030 From: Radek Czyz User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: xvid-devel@xvid.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: [XviD-devel] inter/intra screener X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hi everyone, I'm trying to "screen" some macroblocks from R-D INTRA calculations - most macroblocks will never be intra, or even close, and it's unnecessary to calculate their intra R-D. This is quite important because INTRA R-D is very slow - it handles large coefficients (cache misses in calc_bits() ), bits are always added twice (with and without AC/DC prediction) and there is the extra step of ac/dc prediction performed. My attempts with SAD vs DEV are a huge failure :/ even if I skip only some macroblocks (speed gain less than 1%) I'm still loosing much of psnr. I'll try different appoaches (R-D vs deviation, and a 8x8-based deviation rather than 16x16-based) but perhaps you can suggest something better? I'm not interested in decision itself (that will be RD-based) but with some reliable method of measuring "best case intra", to drop the calculations if "best case" is bad enough. Currently I'm looping through all blocks one-by-one, doing transfer->dct->quantization->calculate_bits(1)->prediction->calculate_bits(2)->dequant->calculate_distortion. And I'm checking for early skip after each block. Perhaps reorganizing it would be better..... Any ideas? Radek _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Sat Dec 18 06:26:26 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 8E206126D82 for ; Sat, 18 Dec 2004 06:26:25 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id F1BB01665E; Sat, 18 Dec 2004 06:32:57 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from guard.polynet.lviv.ua (guard.polynet.lviv.ua [217.9.2.1]) by edu.bnhof.de (Postfix) with SMTP id 4C7C0165DB for ; Sat, 18 Dec 2004 06:32:52 +0100 (CET) Received: (qmail 9906 invoked from network); 18 Dec 2004 05:26:07 -0000 Received: from dial85.polynet.lviv.ua (HELO ?217.9.2.85?) (217.9.2.85) by 217.9.2.1 with SMTP; 18 Dec 2004 05:26:07 -0000 Message-ID: <41C3BF71.6060707@polynet.lviv.ua> Date: Sat, 18 Dec 2004 07:26:09 +0200 From: Andrew Voznytsa User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: xvid-devel@xvid.org Subject: Re: [XviD-devel] inter/intra screener References: <41C3B997.1020002@ihug.com.au> In-Reply-To: <41C3B997.1020002@ihug.com.au> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hi, you may try to use MB boundary error. See ftp://jvttest:tester@standards.polycom.com/2003_12_Waikoloa/JVT-J033r1.doc, section 3,*/ "Selective intra mode decision". IMO this should work for MPEG-4 ASP too. /* Best regards, Andrew Voznytsa Radek Czyz wrote: > Hi everyone, > > I'm trying to "screen" some macroblocks from R-D INTRA calculations - > most macroblocks will never be intra, or even close, and it's > unnecessary to calculate their intra R-D. > > This is quite important because INTRA R-D is very slow - it handles > large coefficients (cache misses in calc_bits() ), bits are always > added twice (with and without AC/DC prediction) and there is the extra > step of ac/dc prediction performed. > > My attempts with SAD vs DEV are a huge failure :/ even if I skip only > some macroblocks (speed gain less than 1%) I'm still loosing much of > psnr. > > I'll try different appoaches (R-D vs deviation, and a 8x8-based > deviation rather than 16x16-based) but perhaps you can suggest > something better? I'm not interested in decision itself (that will be > RD-based) but with some reliable method of measuring "best case > intra", to drop the calculations if "best case" is bad enough. > > Currently I'm looping through all blocks one-by-one, doing > transfer->dct->quantization->calculate_bits(1)->prediction->calculate_bits(2)->dequant->calculate_distortion. > > And I'm checking for early skip after each block. > Perhaps reorganizing it would be better..... Any ideas? > > Radek > _______________________________________________ > XviD-devel mailing list > XviD-devel@xvid.org > http://list.xvid.org/mailman/listinfo/xvid-devel _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Sat Dec 18 06:49:55 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 23198126D82 for ; Sat, 18 Dec 2004 06:49:55 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id B8EAB166A8; Sat, 18 Dec 2004 06:56:25 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from grunt21.ihug.com.au (grunt21.ihug.com.au [203.109.249.141]) by edu.bnhof.de (Postfix) with ESMTP id 6D31016694 for ; Sat, 18 Dec 2004 06:56:02 +0100 (CET) Received: from dsl-17.161.240.220.lns02-waym-adl.dsl.comindico.com.au [220.240.161.17] by grunt21.ihug.com.au with esmtp (Exim 3.35 #1 (Debian)) id 1CfXSy-00038I-00; Sat, 18 Dec 2004 16:49:20 +1100 Message-ID: <41C3C508.407@ihug.com.au> Date: Sat, 18 Dec 2004 16:20:00 +1030 From: Radek Czyz User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: xvid-devel@xvid.org Subject: Re: [XviD-devel] inter/intra screener References: <41C3B997.1020002@ihug.com.au> <41C3BF71.6060707@polynet.lviv.ua> In-Reply-To: <41C3BF71.6060707@polynet.lviv.ua> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hi Andrew Voznytsa wrote: > you may try to use MB boundary error. See > ftp://jvttest:tester@standards.polycom.com/2003_12_Waikoloa/JVT-J033r1.doc, > section 3,*/ "Selective intra mode decision". > IMO this should work for MPEG-4 ASP too. > /* > > Best regards, > Andrew Voznytsa Hehe yes, they're doing exactly the same thing I'm doing and for exactly the same reason. The only problem is that in mpeg-4 (a)sp, intra is almost not predicted from other macroblocks - so the boundary error has no effect on intra's rate. They do however confirm that I should try to estimate the rate of intra and compare it to the (known) rate of inter. Right, I knew that ;p and I'll try it soon-ish. As for now, I can help with early-stops - the minimum number of bits taken bu INTRA is 8 (minimum cbp 2, minimum mode 5, and one ac/dc prediction bit) and I can add this eight to our known "so far" as soon as possible. Radek _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Sat Dec 18 08:19:32 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 5B085126D82 for ; Sat, 18 Dec 2004 08:19:32 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 760BE166D7; Sat, 18 Dec 2004 08:26:04 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from guard.polynet.lviv.ua (guard.polynet.lviv.ua [217.9.2.1]) by edu.bnhof.de (Postfix) with SMTP id 6D53B166D2 for ; Sat, 18 Dec 2004 08:25:59 +0100 (CET) Received: (qmail 21190 invoked from network); 18 Dec 2004 07:19:19 -0000 Received: from dial73.polynet.lviv.ua (HELO ?217.9.2.73?) (217.9.2.73) by 217.9.2.1 with SMTP; 18 Dec 2004 07:19:19 -0000 Message-ID: <41C3D9F9.4090508@polynet.lviv.ua> Date: Sat, 18 Dec 2004 09:19:21 +0200 From: Andrew Voznytsa User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: xvid-devel@xvid.org Subject: Re: [XviD-devel] inter/intra screener References: <41C3B997.1020002@ihug.com.au> <41C3BF71.6060707@polynet.lviv.ua> <41C3C508.407@ihug.com.au> In-Reply-To: <41C3C508.407@ihug.com.au> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org IMO it does not depend if (A)SP uses spatial prediction in Intra case or not. SAD / SBE shows you degree of temporal correlation. In case of low temporal correlation it's good place to check Intra modes. I propose the following algorithm prototype: 1) If best Inter cbp is 0 - skip Intra checks at all. 2) compare SBE and best Inter SAD. For example (if up and left edges available): SAD / 256 * 0.5 > SBE / 32 then try to check Intra modes. 3) test only one Intra mode (i.e. no AC/DC) and compare (RD-) with best Inter mode. If numbers are more or less close - do Intra refinement (test other Intra modes). Best regards, Andrew Voznytsa Radek Czyz wrote: > Hi > > Andrew Voznytsa wrote: > >> you may try to use MB boundary error. See >> ftp://jvttest:tester@standards.polycom.com/2003_12_Waikoloa/JVT-J033r1.doc, >> section 3,*/ "Selective intra mode decision". >> IMO this should work for MPEG-4 ASP too. >> /* >> >> Best regards, >> Andrew Voznytsa > > > Hehe yes, they're doing exactly the same thing I'm doing and for > exactly the same reason. The only problem is that in mpeg-4 (a)sp, > intra is almost not predicted from other macroblocks - so the boundary > error has no effect on intra's rate. > > They do however confirm that I should try to estimate the rate of > intra and compare it to the (known) rate of inter. Right, I knew that > ;p and I'll try it soon-ish. > > As for now, I can help with early-stops - the minimum number of bits > taken bu INTRA is 8 (minimum cbp 2, minimum mode 5, and one ac/dc > prediction bit) and I can add this eight to our known "so far" as soon > as possible. > > Radek > _______________________________________________ > XviD-devel mailing list > XviD-devel@xvid.org > http://list.xvid.org/mailman/listinfo/xvid-devel _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Sun Dec 19 23:49:21 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id E5E35126D82 for ; Sun, 19 Dec 2004 23:49:20 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id D6C30C122; Sun, 19 Dec 2004 23:55:54 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from viefep15-int.chello.at (viefep15-int.chello.at [213.46.255.19]) by edu.bnhof.de (Postfix) with ESMTP id 22298C11F for ; Sun, 19 Dec 2004 23:55:49 +0100 (CET) Received: from Gwob ([84.114.133.201]) by viefep12-int.chello.at (InterMail vM.6.01.03.05 201-2131-111-107-20040910) with SMTP id <20041219165553.OQN20195.viefep12-int.chello.at@Gwob> for ; Sun, 19 Dec 2004 17:55:53 +0100 From: skal To: xvid-devel@xvid.org MIME-Version: 1.0 Message-Id: <20041219165553.OQN20195.viefep12-int.chello.at@Gwob> Date: Sun, 19 Dec 2004 17:55:57 +0100 Content-Type: text/plain;charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.4 Subject: [XviD-devel] Re:please try again X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org -------- Virus Warning Message -------- The virus (Exploit-MIME.gen.b) was detected in the attachment . The attached File has been removed. Nachfolgender Virus (Exploit-MIME.gen.b) wurde im Attachment gefunden, deshalb wurde das Attachment gel=F6scht. F=FCr Fragen dazu steht Ihnen der chello Helpdesk sehr gerne zur Verf=FCgung. Weitere Informationen zum Virenschutz: http://portal.chello.at/av-info.html Le serveur de mail chello a d=E9tect=E9 le virus Exploit-MIME.gen.b dans le fichier inclus dans ce mail. Ce fichier a donc =E9t=E9 supprim=E9e pour en =E9viter la diffusion. Pour plus d'information, merci de cliquer sur le lien suivant http://www.chello.fr Az =D6nnek k=E9zbes=EDtett lev=E9l mell=E9klet=E9ben a v=EDrussz=FBr=F5 rendszer a(z) Exploit-MIME.gen.b nev=FB v=EDrust tal=E1lta, ez=E9rt a(z) nev=FB = mell=E9kletet biztons=E1gi okokb=F3l elt=E1vol=EDtotta. Tov=E1bbi inform=E1ci=F3=E9rt, k=E9rj=FCk kattintson az al=E1bbi hivatkoz=E1sra: http://home.hun.chello.hu/upcmnfc/start/tamogatas/virusszures/ V p=F8=EDloze byl detekov=E1n virus Exploit-MIME.gen.b. P=F8=EDloha = byla proto odstran=ECna. Pro dotazy kontaktujte pros=EDm technickou podporu. W za=B3=B1czniku wykryto wirus Exploit-MIME.gen.b. Plik zosta=B3 usuni=EAty. Wi=EAcej informacji znajdziesz na stronie internetowej: http://home.pol.chello.pl/upcmnfc/start/pomoc/wirusy/ V prilo=BEenom s=FAbore bol zisten=FD v=EDrus (Exploit-MIME.gen.b). S=FAbor bol odstr=E1nen=FD. V pr=EDpade ot=E1zok pros=EDm kontaktujte linku technickej podpory. http://www.chello.sk ---------------------------------------- _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-users-bounces@xvid.org Mon Dec 20 00:33:39 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 78334126D82 for ; Mon, 20 Dec 2004 00:33:39 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 3A4AEC197; Mon, 20 Dec 2004 00:40:10 +0100 (CET) X-Original-To: xvid-users@xvid.org Delivered-To: xvid-users@edu.bnhof.de Received: from s5.lansco.de (s5.lansco.de [212.63.130.170]) by edu.bnhof.de (Postfix) with ESMTP id B7C08C193; Mon, 20 Dec 2004 00:40:05 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by s5.lansco.de (Postfix) with ESMTP id C2E33A0C0; Mon, 20 Dec 2004 00:33:26 +0100 (CET) Received: from pD9539E11.dip.t-dialin.net (pD9539E11.dip.t-dialin.net [217.83.158.17]) by www.lansco.de (IMP) with HTTP for ; Mon, 20 Dec 2004 00:33:26 +0100 Message-ID: <1103499206.41c60fc6a058e@www.lansco.de> Date: Mon, 20 Dec 2004 00:33:26 +0100 From: Michael Militzer To: xvid-devel@xvid.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.3 X-Originating-IP: 217.83.158.17 Cc: xvid-users@xvid.org Subject: [XviD-users] XviD 1.0.3 is out! X-BeenThere: xvid-users@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-users@xvid.org List-Id: xvid-users.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-users-bounces@xvid.org Errors-To: xvid-users-bounces@xvid.org Hello! This is XviD 1.0.3 bugfix release. This release fixes very minor bugs. It is source and binary compatible with the previous version. As a sidenote, the 1.1 is maturing fast these last weeks and it's quite possible Santa Claus could bring you an official beta release of this new tree before the end of this year. The 1.1 tree brings a fair number of optimizations in the decoder, better quality and more speed for the encoder, a brand new PowerPC port, a Linux AMD64 port... Changes since 1.0.2: * xvidcore - Fixed trellis optimization overflow for quant <= 2. - Don't read too short streams. This prevents from reading useless stream garbage. - Fixed 64 bit crashes because of addressing assuming 32bit integers. (Andre Werthman) - Fixed 2 diamond search bugs (one was causing searches in wrong directions, the other one was causing an early exit) * VFW frontend - Better stride calculation * DShow frontend - Better stride calculation The files are available in the download section of XviD.org: http://www.xvid.org/downloads.html -- The "XviD Team" _______________________________________________ XviD-users mailing list XviD-users@xvid.org http://list.xvid.org/mailman/listinfo/xvid-users From xvid-devel-bounces@xvid.org Tue Dec 21 02:58:27 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 767C9126D82 for ; Tue, 21 Dec 2004 02:58:27 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 2110813DA1; Tue, 21 Dec 2004 03:04:58 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from MAIL.yulong.com (unknown [210.75.16.21]) by edu.bnhof.de (Postfix) with ESMTP id 7224413D8D for ; Tue, 21 Dec 2004 03:04:53 +0100 (CET) Received: from dengxiongshu ([128.1.4.26]) by MAIL.yulong.com with Microsoft SMTPSVC(5.0.2195.6713); Tue, 21 Dec 2004 09:43:35 +0800 Message-ID: <003d01c4e6fe$8d4e0a00$1a040180@dengxiongshu> From: =?gb2312?B?tcvQ28rp?= To: Date: Tue, 21 Dec 2004 09:44:03 +0800 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-OriginalArrivalTime: 21 Dec 2004 01:43:35.0810 (UTC) FILETIME=[7C809620:01C4E6FE] X-Content-Filtered-By: Mailman/MimeDel 2.1.4 Subject: [XviD-devel] make motion function more easy be read X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0480179838==" Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org This is a multi-part message in MIME format. --===============0480179838== Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 ZGVhciBleHBlcnQ6DQogIEkgYW0gY29uZnVzZSB3aHkgbm90IHVzZSBtYWNybyBkZWZpbmUgdG8g bWFrZSBzZWFyY2ggZGlyZWN0aW9uIGluIG1vdGlvbiBzZWFyY2ggZnVuY3Rpb24gdG8gYmUgbW9y ZSBlYXN5IHJlYWRpbmc/IFN1Y2ggYXMgY2FuIG1ha2UgbWFjcm8gZGVmaW5lIGFzIGZvbGxvd2lu Zw0KI2RlZmluZSBsRUZUU0VBUkNIRElSRUNUSU9OIDENCiNkZWZpbmUgUklHSFRTRUFSQ0hESVJF Q1RJT04gMg0KI2RlZmluZSBVUFNFQVJDSERJUkVDVElPTiA0DQojZGVmaW5lIERPV05TRUFSQ0hE SVJFQ1RJT04gOA0KSXQgaXMgc28gZWFzeSB0byBkbyBhbmQgbWFrZSBjb2RpbmcgbW9yZSBlYXN5 IGJlIHJlYWQuDQpBbmQgSSB0aGluayBtcGVnLTQgcGFydCAyIHdpbGwgYmUgcmVwbGFjZSBieSBo LjI2NCBpbiB0aGUgZnV0dXJlIGJlY2F1c2UgaC4yNjQgYXJlIHNvIG1vcmUgY29tcHJlc3MgdGhh biBtcGVnNCBwYXJ0IDIuIEFuZCBoYXZlIHh2aWQgIHNvbWUgcGxhbiB0byBkZXZlbG9wIGguMjY0 L21wZWc0IHBhcnQgMTAgY29tcGF0aWJsZT8= --===============0480179838== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel --===============0480179838==-- From xvid-devel-bounces@xvid.org Tue Dec 21 03:06:29 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 0141A126D82 for ; Tue, 21 Dec 2004 03:06:28 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 7AFD013DDE; Tue, 21 Dec 2004 03:13:06 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from MAIL.yulong.com (unknown [210.75.16.21]) by edu.bnhof.de (Postfix) with ESMTP id D2CA813DCC for ; Tue, 21 Dec 2004 03:12:56 +0100 (CET) Received: from dengxiongshu ([128.1.4.26]) by MAIL.yulong.com with Microsoft SMTPSVC(5.0.2195.6713); Tue, 21 Dec 2004 10:05:30 +0800 Message-ID: <001f01c4e701$9cfbfcc0$1a040180@dengxiongshu> From: "???" To: Date: Tue, 21 Dec 2004 10:05:58 +0800 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-OriginalArrivalTime: 21 Dec 2004 02:05:30.0624 (UTC) FILETIME=[8C314800:01C4E701] X-Content-Filtered-By: Mailman/MimeDel 2.1.4 Subject: [XviD-devel] Re: make motion function more easy be read X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0671274551==" Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org This is a multi-part message in MIME format. --===============0671274551== Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: base64 ZGVhciBleHBlcnQ6DQogIEkgYW0gY29uZnVzZSB3aHkgbm90IHVzZSBtYWNybyBkZWZpbmUgdG8g bWFrZSBzZWFyY2ggZGlyZWN0aW9uIGluIG1vdGlvbiBzZWFyY2ggZnVuY3Rpb24gdG8gYmUgbW9y ZSBlYXN5IHJlYWRpbmc/IFN1Y2ggYXMgY2FuIG1ha2UgbWFjcm8gZGVmaW5lIGFzIGZvbGxvd2lu Zw0KI2RlZmluZSBsRUZUU0VBUkNIRElSRUNUSU9OIDENCiNkZWZpbmUgUklHSFRTRUFSQ0hESVJF Q1RJT04gMg0KI2RlZmluZSBVUFNFQVJDSERJUkVDVElPTiA0DQojZGVmaW5lIERPV05TRUFSQ0hE SVJFQ1RJT04gOA0KSXQgaXMgc28gZWFzeSB0byBkbyBhbmQgbWFrZSBjb2RpbmcgbW9yZSBlYXN5 IGJlIHJlYWQuDQpBbmQgSSB0aGluayBtcGVnLTQgcGFydCAyIHdpbGwgYmUgcmVwbGFjZSBieSBo LjI2NCBpbiB0aGUgZnV0dXJlIGJlY2F1c2UgaC4yNjQgYXJlIHNvIG1vcmUgY29tcHJlc3MgdGhh biBtcGVnNCBwYXJ0IDIuIEFuZCBoYXZlIHh2aWQgIHNvbWUgcGxhbiB0byBkZXZlbG9wIGguMjY0 L21wZWc0IHBhcnQgMTAgY29tcGF0aWJsZT8NCkJlc3QgUmVnYXJk --===============0671274551== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel --===============0671274551==-- From xvid-devel-bounces@xvid.org Tue Dec 21 12:33:02 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 1737D126D82 for ; Tue, 21 Dec 2004 12:33:02 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id E617513AD4; Tue, 21 Dec 2004 12:39:34 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from mwinf0105.wanadoo.fr (smtp1.wanadoo.fr [193.252.22.30]) by edu.bnhof.de (Postfix) with ESMTP id 74311C198 for ; Tue, 21 Dec 2004 12:39:31 +0100 (CET) Received: from smtp1.wanadoo.fr (mwinf0108 [172.22.132.38]) by mwinf0105.wanadoo.fr (SMTP Server) with ESMTP id 885234801D87 for ; Tue, 21 Dec 2004 12:15:31 +0100 (CET) Received: from me-wanadoo.net (mail.domain.com [127.0.0.1]) by mwinf0108.wanadoo.fr (SMTP Server) with SMTP id 7D7941C00CE3 for ; Tue, 21 Dec 2004 12:15:25 +0100 (CET) Received: from blackbird.bzh (Mix-Rennes301-2-160.w193-250.abo.wanadoo.fr [193.250.83.160]) by mwinf0108.wanadoo.fr (SMTP Server) with ESMTP id BF5851C00D09 for ; Tue, 21 Dec 2004 12:15:24 +0100 (CET) Received: from Sketches.bzh (Sketches.bzh [192.168.1.66]) by blackbird.bzh (Postfix) with ESMTP id EBF1981C8 for ; Tue, 21 Dec 2004 12:14:36 +0100 (CET) Received: by Sketches.bzh (Postfix, from userid 500) id BBD1125825; Tue, 21 Dec 2004 12:14:37 +0100 (CET) Subject: Re: [XviD-devel] Small report from my amd64 merging effort From: Guillaume POIRIER To: xvid-devel ML In-Reply-To: <20041215000513.GA6845@edgomez.kicks-ass.org> References: <20041214000842.GC6728@edgomez.kicks-ass.org> <20041215000513.GA6845@edgomez.kicks-ass.org> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Date: Tue, 21 Dec 2004 12:14:36 +0100 Message-Id: <1103627676.4214.15.camel@Sketches> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hi, Le mercredi 15 d=E9cembre 2004 =E0 01:05 +0100, Edouard Gomez a =E9crit :=20 > Edouard Gomez (ed.gomez@free.fr) wrote: > To sump up: > - x86_64 non optimized: 6.2fps > - x86_64 optimized for this encoding option set: 17.8fps > - ia32 optimized: 12.8fps My results are quite different, but there is a good explanation for this: first is that the tla "head" checkout doesn't provide me any x86-64 asm (the only ASM directories I get are ppc_asm, x86_asm, ia64_asm) nor x86-64-aware build scripts (whereas Andre Werthmann's port does feature those dirs and scripts, but I can't build it as I don't have yasm on my debian). I re-ran the checkout process : $ tla register-archive \ http://ed.gomez.free.fr/arch-repositories/ed.gomez@free.fr--2004-1/ $ tla get ed.gomez@free.fr--2004-1/xvidcore--head ...but it still doesn't provide any x86-64 code. So for short: I can't build a x86-64 optimized XviD, I just get the pure C generic build. Could it be possible to either make a tarball available which contains a HEAD snapshot or tell me what I'm doing wrong during the checkout? Regards, Guillaume _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Tue Dec 21 13:56:38 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id EDE58126D82 for ; Tue, 21 Dec 2004 13:56:37 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 85CEF9C28; Tue, 21 Dec 2004 14:03:14 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from postfix1-c.free.fr (postfix1-c.free.fr [213.228.0.79]) by edu.bnhof.de (Postfix) with ESMTP id 439B521CF for ; Tue, 21 Dec 2004 14:03:11 +0100 (CET) Received: from postfix4-1.free.fr (postfix4-1.free.fr [213.228.0.62]) by postfix1-c.free.fr (Postfix) with ESMTP id 56C87BD5EDB for ; Tue, 21 Dec 2004 13:37:15 +0100 (CET) Received: from imp4-q.free.fr (imp4-q.free.fr [212.27.42.4]) by postfix4-1.free.fr (Postfix) with ESMTP id 47CFC21A88B for ; Tue, 21 Dec 2004 13:37:10 +0100 (CET) Received: by imp4-q.free.fr (Postfix, from userid 33) id 235ECDDC8; Tue, 21 Dec 2004 13:37:10 +0100 (MET) Received: from 195.101.164.38 ([195.101.164.38]) by imp4-q.free.fr (IMP) with HTTP for ; Tue, 21 Dec 2004 13:37:10 +0100 Message-ID: <1103632630.41c818f619171@imp4-q.free.fr> Date: Tue, 21 Dec 2004 13:37:10 +0100 From: Edouard Gomez To: xvid-devel@xvid.org Subject: Re: [XviD-devel] Small report from my amd64 merging effort References: <20041214000842.GC6728@edgomez.kicks-ass.org> <20041215000513.GA6845@edgomez.kicks-ass.org> <1103627676.4214.15.camel@Sketches> In-Reply-To: <1103627676.4214.15.camel@Sketches> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.5 X-Originating-IP: 195.101.164.38 X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Selon Guillaume POIRIER : > I re-ran the checkout process : > $ tla register-archive \ > http://ed.gomez.free.fr/arch-repositories/ed.gomez@free.fr--2004-1/ > $ tla get ed.gomez@free.fr--2004-1/xvidcore--head > > ...but it still doesn't provide any x86-64 code. It's not merged on that archive yet, i'm maintaining a specific archive on the amd64box which is not publicly available. When i think my merging is complete i'll merge the complete amd64 support at once. So no, you can't get the amd64 1.1 tree yet, i'll try to merge the last bits before friday, because then i'll try to have a break till the new year. -- Edouard Gomez _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Tue Dec 21 20:09:49 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 6DB4A126D82 for ; Tue, 21 Dec 2004 20:09:49 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 8F466C159; Tue, 21 Dec 2004 20:16:27 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from mail.arklinux.org (build.arklinux.osuosl.org [140.211.166.26]) by edu.bnhof.de (Postfix) with ESMTP id 47642C12D for ; Tue, 21 Dec 2004 20:16:21 +0100 (CET) Received: from [192.168.0.90] (pD9524011.dip.t-dialin.net [217.82.64.17]) by mail.arklinux.org (Postfix) with ESMTP id 991C6DD7F2 for ; Tue, 21 Dec 2004 10:59:34 -0800 (PST) From: Bernhard Rosenkraenzer Organization: LINUX4MEDIA GmbH To: xvid-devel@xvid.org Date: Tue, 21 Dec 2004 19:39:31 +0100 User-Agent: KMail/1.7.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412211939.32699.bero@arklinux.org> Subject: [XviD-devel] bitrate control broken in CVS? X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hi, I just tried CVS xvid -- works nicely for normal encodes, but bitrate control appears to be broken. When using it with mencoder, e.g.: mencoder -ovc xvid -oac mp3lame -xvidencopts trellis:gmc:hq_ac:vhq=4:bvhq=1:autoaspect:rc_buffer=65535:max_bframes=2:bitrate=512 -lameopts vbr=0:cbr:br=64 -o test.avi dvd:// I get bitrates around 1.3 MBit/s rather than the expected 512 kBit/s -- is something wrong with xvid CVS atm, or has there been an API modification we'll need adjust for in mencoder? LLaP bero _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Mon Dec 27 02:28:35 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 39AB8126D84 for ; Mon, 27 Dec 2004 02:28:35 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 68C411483F; Mon, 27 Dec 2004 02:35:20 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from MAIL.yulong.com (unknown [210.75.16.21]) by edu.bnhof.de (Postfix) with ESMTP id 941C21481A for ; Mon, 27 Dec 2004 02:35:11 +0100 (CET) Received: from dengxiongshu ([128.1.4.26]) by MAIL.yulong.com with Microsoft SMTPSVC(5.0.2195.6713); Mon, 27 Dec 2004 09:26:58 +0800 Message-ID: <001c01c4ebb3$42d1b710$1a040180@dengxiongshu> From: "???" To: Date: Mon, 27 Dec 2004 09:27:42 +0800 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-OriginalArrivalTime: 27 Dec 2004 01:26:58.0633 (UTC) FILETIME=[289DF390:01C4EBB3] X-Content-Filtered-By: Mailman/MimeDel 2.1.4 Subject: [XviD-devel] somebody can tell me how to use dquant? X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0016771019==" Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org This is a multi-part message in MIME format. --===============0016771019== Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: base64 RGVhciBleHBlcnQ6DQogICAgICAgQ291bGQgIGFueW9uZSB0ZWxsIG1lIGhvdyB0byBpbXBsZW1l bnQgZHF1YW50PyAgIGhvdyBjYW4gSSB1c2UgZHF1YW50PyAgSWYgZHF1YW50IGlzIG5vdCBlcXVh bCB6ZXJvLCBpcyBjdXJyZW50IG1hY3JvJ3MgcXVhbnQgZXF1YWwgdG8gcHJldmlvdXMgIG1hY3Jv J3MgIHF1YW50IGFkZCBjdXJyZW50IG1hY3JvJ3MgZHF1YW50PyBkcXVhbnQgaXMgdG8gdXNlIHRv IG1hY3JvIGxldmVsIHJhdGUgY29udHJvbD8geHZpZCBoYXZlIG5vdCBpbXBsZW1lbnQgbWFjcm8g bGV2ZWwgcmF0ZSBjb250cm9sLHNvIEkgZG9uJ3QgdW5kZXJzdGFuZCBkcXVhbnQgaXMgdXNlIGlu IHh2aWQgLGl0IGlzIGZvciBmdXR1cmU/DQpCZXN0IHJlZ2FyZA0KeGlvbmdzaHUsZGVuZw== --===============0016771019== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel --===============0016771019==-- From xvid-devel-bounces@xvid.org Mon Dec 27 19:46:55 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 13D08126D82 for ; Mon, 27 Dec 2004 19:46:55 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id 7BE3E14A2C; Mon, 27 Dec 2004 19:53:39 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from moloch.freelancehosting.net (moloch.freelancehosting.net [67.18.130.98]) by edu.bnhof.de (Postfix) with ESMTP id E0B0A14A22 for ; Mon, 27 Dec 2004 19:53:35 +0100 (CET) Received: (qmail 7560 invoked from network); 27 Dec 2004 18:40:01 -0000 Received: from aaubervilliers-151-1-24-112.w83-114.abo.wanadoo.fr (HELO ?83.114.143.112?) (83.114.143.112) by freelancehosting.net with SMTP; 27 Dec 2004 18:40:00 -0000 Message-ID: <41D05705.5050002@cedelia.com> Date: Mon, 27 Dec 2004 19:40:05 +0100 From: Mathieu Germain Organization: Cedelia User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: en-us, en MIME-Version: 1.0 To: xvid-devel@xvid.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [XviD-devel] StreamPlug and the xvid GPL license - X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hi everyone, I'm sorry this is going to be a very long post, please take some time to read as we really want to fix the situation quickly since we have infringed on the GPL license of xvid and did not intend to. Here's the situation I am part of cedelia, a team that has developed a software called StreamPlug and recently released it. It's a browser plugin for windows that can stream any MPEG4 ASP codec over HTTP and supports vorbis for the sound (and uses ogg/ogm as container). The plug-in itself is about 200k to download, making it really fast to download (which was one of our main goal : speed, lightness, simplicity). In order to make it as simple for the user as possible we integrated our own MPEG4 decoder inside the plugin so that one does not have to go look for the codecs or install anything else. All that's needed for the playback is included in the 200k. And that's where there's a problem : we used parts of the xvid decoder for our decoder (on the ground that we find xvid to be the best dev around). I cannot stress enough that there was never intention to infringe/steal anything and make it a proprietary code. Our interpretation was just wrong : since we do not provide any encoder and simply use some parts of xvid's, which we do not modify, we assimilated that as an aggregation of our code and the xvid code. Simply, instead of making the user download two elements separately we included the xvid part in our dll. Which was a mistake from our part and we sincerely apologize about it. We never hid that we were using xvid and it clearly appears in our dll. We simply did things in order to be compatible and never even dreamt of claiming paternity over the xvid codec. Radek/sysKin brought our attention to this two days ago through the doom9.org forums. We now want to do whatever we have to do to make this situation clean and not infringe on your license and your work. I had the opportunity to then discuss with radek the possibilities that are offered to us and of course, there's GPL'ing streamplug. But various reasons prevent us as of now to do so. We don't feel very secure about the security it provides and moreover, streamplug is part of a larger set of softwares under development which would then have to be GPL too while we would like to use these tools/softs for commercial purposes. GPL might become an option in the future and we often thought about it but it is not at the moment. So that we came up with two different solutions : 1) "Mere Aggregation" Radek explained to me the exact meaning of the notion of "mere aggreagtion" in the GLP license. As i understand it, if a non-GPL software uses GPL components, this can only be done by separating the two executables, allowing one to be GPL and the other to be under whatever license it is. Would it be OK if we did this : - Separate the Streamplug code from the xvid code and make them two distinct dll (and we would of course provide the lib for that dll etc) - Make it possible to download both our dll and the xvid dll at once I'm not sure about the second point. As i understand it it seems that an association of two components is considered aggregation only if the two packages have different installers on a CD-Rom or different download links on a website. I'm sure you will all see why this is a bit of a pain for us if we have to make two separate downloads, since the whole point with streamplug is that it is so small to download and simple to install, while delivering superior quality (unlike other more famous streaming applications). Basically this solution consists in compiling our xvid decoder and complying with all the requirements GPL has and make the xvid dll a component, but we'd like to know if it'd be possible to still make it a one-download installation. If this solution is ok, we think we're able to implement it within days and replace the current streamplug version. 2) Getting rid of the xvid parts we use We could also get rid of all that's xvid and reduce what we have to MPEG4 specs without anything from xvid. We would of course provide you with a copy of the lib so that you can verify that we did indeed get rid of anything xvid in our decoder. It would take us about 2 weeks ( we think ) to release a new version under these terms. The biggest disadvantage we see in this is that it is a bit of a shame : we find that an application like StreamPlug can be of benefit for the xvid community and again i can't stress enough that in no way can streamplug become a danger for future developments of xvid ; we always provided links to the sources we used for our decoder inside streamplug and anyone can access the information we had. We did not change a thing, never claimed paternity or hid we used xvid and only sought compatibility. We always advise people to use xvid for their encodes and the whole story here is basically a big confusion from our part on the terms of the GPL license. I hope one of these solutions will suit you. I guess the second one can only be all right, i just wish you guys give a thought about this and how we could maybe work it out another way, making streamplug a close support of xvid. If the first solution isn't suitable we'll do the other one. In the meantime we are unsure about what to do with the current version of streamplug, should we stop distributing it altogether? We will announce the changes we'll make on streamplug as soon as you give us directives as to what you want us to do and explain what we did wrong on cedelia.com. Again i'm really sorry about the length and incredible nuisance such a post can be. Moreover we as people feel pretty bad about the whole thing. We have the greatest respect for GPL communities and will comply with what we're told. We wish the xvid community a long-lasting predominance in the realms of compression (and incidentally a happy new year). Cedelia Team Link to download streamplug : www.streamplug.com (compatible with mozilla/firefox/netscape and IE on windows) _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel From xvid-devel-bounces@xvid.org Thu Dec 30 14:31:23 2004 Return-Path: X-Original-To: itdp@fh-biergarten.de Delivered-To: itdp@localhost Received: from edu.bnhof.de (edu.bnhof.de [213.167.167.52]) by mail.kliche.org (Postfix) with ESMTP id 0B569126D85 for ; Thu, 30 Dec 2004 14:31:23 +0100 (CET) Received: from edu.bnhof.de (localhost [127.0.0.1]) by edu.bnhof.de (Postfix) with ESMTP id E4F2C14878; Thu, 30 Dec 2004 14:38:09 +0100 (CET) X-Original-To: xvid-devel@xvid.org Delivered-To: xvid-devel@edu.bnhof.de Received: from nil.math.uni-bonn.de (mail.math.uni-bonn.de [131.220.120.11]) by edu.bnhof.de (Postfix) with ESMTP id 71FE21484C for ; Thu, 30 Dec 2004 14:38:06 +0100 (CET) Received: from login.math.uni-bonn.de (login.math.uni-bonn.de [131.220.120.13]) by nil.math.uni-bonn.de (Postfix) with ESMTP id 8825B58E60; Thu, 30 Dec 2004 14:11:50 +0100 (CET) Date: Thu, 30 Dec 2004 14:08:27 +0100 (CET) From: Christoph Lampert To: xvid-devel@xvid.org Subject: Re: [XviD-devel] StreamPlug and the xvid GPL license - In-Reply-To: <41D05705.5050002@cedelia.com> Message-ID: References: <41D05705.5050002@cedelia.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: X-BeenThere: xvid-devel@xvid.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: xvid-devel@xvid.org List-Id: xvid-devel.xvid.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xvid-devel-bounces@xvid.org Errors-To: xvid-devel-bounces@xvid.org Hi, I'm not the lawyer round here, but I had to answer similar mails quite often already, so I'll do this as well: On Mon, 27 Dec 2004, Mathieu Germain wrote: > 1) "Mere Aggregation" > ... > Would it be OK if we did this : > - Separate the Streamplug code from the xvid code and make them two > distinct dll (and we would of course provide the lib for that dll etc) > - Make it possible to download both our dll and the xvid dll at once > I'm not sure about the second point. > ... I'm sure you will all see why this is a bit of a pain for us... Yes, and sorry for putting it that way, but that is exactly the point. The GPL is targeted _against_ combination with proprietary products, not in favor of it. So, the rules are very very strict. This is not to punish you or any other company, but intended to help Free Software. If your product is released under GPL, you can use XviD "almost as you like". If you products is not, then you are not allowed to combine it with XviD. Now, to the "legal" stuff: If you create one installer for your product and XviD, the result is a combined product of both, which isn't permitted by GPL. Not only the technical side (one DLL, two DLLs) matters, but also what the user sees. Also, "mere aggregation" means that your products can work _without_ XviD, and can XviD work without your products. They just come e.g. on the same CD, or from the same website. If that isn't the case (e.g. because your product relies on XviD to show MPEG-4), then it's not mere aggregation, no matter how any installers you use. We somehow accept it, if a program can _optionally_ use an already installed version of XviD, because then it's the users choice to download and install XviD, or to not do it. That when having two download links for your product and for XviD might be acceptable. > 2) Getting rid of the xvid parts we use > We could also get rid of all that's xvid and reduce what we have to > MPEG4 specs without anything from xvid. Again, sorry to put it that way, but that is the best solution, because you shouldn't have used XviD from the very beginning. If you have questions on the GPL, read it, or go to www.fsf.org/licenses for explanations, a FAQ etc. I must say that find it very unprofessional to use somebody else's copyrighted code without understanding the license attached to it. > If the first solution isn't suitable we'll do the other one. In the > meantime we are unsure about what to do with the current version of > streamplug, should we stop distributing it altogether? Regarding GPL, you have to immediately stop distribution (in fact, you already had to stop when Radek first informed you, or, in real fact, you never had to right to distribute in first place). However, we won't hack your webserver if you don't act immediately, so maybe as an act of good will, I'll suggest the following (this is my personal oppinion, maybe the others can comment on it): You said you would need two weeks for a "XviD"-free version of StreamPlug. Therefore, I'd say we'll don't check your website for the next two weeks, and only if two weeks from now XviD is still in the product, you have to stop the distribution. However, this is just for the free version. For business licenses, I'm pretty sure we all agree that you must not give out licenses of software which includes XviD code! Also, if you did so before, you should inform the customers that the product they purchased contains an illegal (yes, it's a break of copyright law) copy of XviD, so the license that they obtained from you is not enough for them to use the product, but they should get a "legalized" version from you. I know that this email may sound horrible, but this is how XviD is licensed, and we chose GPL for a reason, namely to prevent people to just take it and create proprietary solution on it. It's nice of you to help promote XviD, but the license situation for XviD is clear, and not changed by that. yours Christoph _______________________________________________ XviD-devel mailing list XviD-devel@xvid.org http://list.xvid.org/mailman/listinfo/xvid-devel