Guillaume POIRIER | 1 Apr 10:45 2008
Picon

Re: commit: Merge branch 'master' of git <at> git.videolan.org:x264 ( Guillaume Poirier )

Hello,

On 3/31/08, Guillaume POIRIER <poirierg <at> gmail.com> wrote:
>  On 3/31/08, Zuxy Meng <zuxy.meng <at> gmail.com> wrote:
>  > You didn't rebase before you pushed?
>
>
> That's quite possible indeed. The version of GIT that I use may be
>  "outdated" (1.5.3.7, released on 01-Dec-2007 21:21) as it doesn't
>  support the command "git up --rebase", so I left it out when I update.

For what it's worth, I pulled a fresher version of GIT (1.5.4.4)
through "Macports", and that version does support "git pull --rebase",
while 1.5.3.7 didn't.

I shouldn't mess up the repository in that way again then.

Guillaume
Zuxy Meng | 1 Apr 16:40 2008
Picon

Re: Can we post thru gmane?

Hi,

2008/3/22, Zuxy Meng <zuxy.meng <at> gmail.com>:
> Hi,
>
> The newsgroup was marked as unidirectional. Can it be open? Thanks!

Ping...who's the admin of this mailing list?

Son Minh Tran | 1 Apr 18:07 2008
Picon

Capacity of x264

Hi All,
Have someone  already tested the x264 coder for the stream High 
Definition (1280x720 / 1920x1080) in realtime (25, 30 fps)? Can you 
share the experience on the hardware configuration and software setting.
Thanks

_______________________________________________
x264-devel mailing list
x264-devel <at> videolan.org
http://mailman.videolan.org/listinfo/x264-devel

Jason Garrett-Glaser | 1 Apr 18:11 2008
Picon

Re: Capacity of x264

> Hi All,
>  Have someone  already tested the x264 coder for the stream High
>  Definition (1280x720 / 1920x1080) in realtime (25, 30 fps)? Can you
>  share the experience on the hardware configuration and software setting.
>  Thanks

Yes.  Avail Media encodes realtime 1080p/i with 3.2Ghz 8-core Xeon
systems; it is quite possible.  720p is much easier; you really only
need a quad core for that.

Dark Shikari
_______________________________________________
x264-devel mailing list
x264-devel <at> videolan.org
http://mailman.videolan.org/listinfo/x264-devel

Robert Swain | 1 Apr 18:20 2008
Picon

Re: Capacity of x264

On 01/04/2008, Jason Garrett-Glaser <darkshikari <at> gmail.com> wrote:
>  >  Have someone  already tested the x264 coder for the stream High
>  >  Definition (1280x720 / 1920x1080) in realtime (25, 30 fps)? Can you
>  >  share the experience on the hardware configuration and software setting.
>  >  Thanks
>
> Yes.  Avail Media encodes realtime 1080p/i with 3.2Ghz 8-core Xeon
>  systems; it is quite possible.  720p is much easier; you really only
>  need a quad core for that.

Using what settings?

Rob
_______________________________________________
x264-devel mailing list
x264-devel <at> videolan.org
http://mailman.videolan.org/listinfo/x264-devel

Jason Garrett-Glaser | 1 Apr 18:35 2008
Picon

Re: Capacity of x264

On Tue, Apr 1, 2008 at 9:20 AM, Robert Swain <robert.swain <at> gmail.com> wrote:
>
> On 01/04/2008, Jason Garrett-Glaser <darkshikari <at> gmail.com> wrote:
>  >  >  Have someone  already tested the x264 coder for the stream High
>  >  >  Definition (1280x720 / 1920x1080) in realtime (25, 30 fps)? Can you
>  >  >  share the experience on the hardware configuration and software setting.
>  >  >  Thanks
>  >
>  > Yes.  Avail Media encodes realtime 1080p/i with 3.2Ghz 8-core Xeon
>  >  systems; it is quite possible.  720p is much easier; you really only
>  >  need a quad core for that.
>
>  Using what settings?
>
>  Rob
>

CBR 6 megabits, -r2 -m3 -B1 --no-b-adapt --scenecut=-1 -t1 --8x8dct
--partitions i4x4,i8x8 with default AQ.

With the recent x264 speed improvements I've managed to get -m6 in
there while staying realtime.

Dark Shikari
_______________________________________________
x264-devel mailing list
x264-devel <at> videolan.org
http://mailman.videolan.org/listinfo/x264-devel

(Continue reading)

Mojtaba Hosseini | 1 Apr 19:11 2008

Re: Capacity of x264

>  >
>  > Yes.  Avail Media encodes realtime 1080p/i with 3.2Ghz 8-core Xeon
>  >  systems; it is quite possible.  720p is much easier; you really only
>  >  need a quad core for that.

>CBR 6 megabits, -r2 -m3 -B1 --no-b-adapt --scenecut=-1 -t1 --8x8dct
>--partitions i4x4,i8x8 with default AQ.

We have similar experience with 1080p on 2.6GHz quad core (ie can do 25fps)
with approximately these settings:
rc->i_rc_method = X264_RC_ABR
Y only motion estimation (no chroma M.E.)
analyse->i_subpel_refine = 2
rc->i_qp_constant = 25
No b frames
3mbps bitrate
Attachment (winmail.dat): application/ms-tnef, 4207 bytes
_______________________________________________
x264-devel mailing list
x264-devel <at> videolan.org
http://mailman.videolan.org/listinfo/x264-devel
git version control | 2 Apr 12:08 2008

commit: fix shared libs on MacOSX (Guillaume Poirier )

x264 | branch: master | Guillaume Poirier <gpoirier <at> mplayerhq.hu> | Mon Mar 31 10:50:45 2008 +0200| [08b5132ff6e6a8e986b6699987b49624e4efbef3]

fix shared libs on MacOSX
based on a patch by İsmail Dönmez

> http://git.videolan.org/gitweb.cgi/x264.git/?a=commit;h=08b5132ff6e6a8e986b6699987b49624e4efbef3
---

 configure |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/configure b/configure
index 6eb68c8..19d76d4 100755
--- a/configure
+++ b/configure
 <at>  <at>  -463,6 +463,9  <at>  <at>  if [ "$shared" = "yes" ]; then
         echo "SONAME=libx264-$API.dll" >> config.mak
         echo 'IMPLIBNAME=libx264.dll.a' >> config.mak
         echo 'SOFLAGS=-Wl,--out-implib,$(IMPLIBNAME) -Wl,--enable-auto-image-base' >> config.mak
+    elif [ "$SYS" = "MACOSX" ]; then
+        echo "SONAME=libx264.$API.dylib" >> config.mak
+        echo 'SOFLAGS=-dynamiclib -Wl,-single_module -Wl,-read_only_relocs,suppress' >> config.mak        
     else
         echo "SONAME=libx264.so.$API" >> config.mak
         echo 'SOFLAGS=-Wl,-soname,$(SONAME)' >> config.mak

_______________________________________________
x264-devel mailing list
x264-devel <at> videolan.org
http://mailman.videolan.org/listinfo/x264-devel
(Continue reading)

Loren Merritt | 2 Apr 12:58 2008

Re: fix for MSVC

On Mon, 31 Mar 2008, David Lariviere wrote:

> --- a/build/win32/libx264.vcproj
> +++ b/build/win32/libx264.vcproj
>  <at>  <at>  -843,7 +843,7  <at>  <at> 
>                 </FileConfiguration>
>         </File>
>         <File
> -               RelativePath="..\..\common\predict.c">
> +               RelativePath="..\..\common\x86\predict-c.c">
>                 <FileConfiguration
>                         Name="Release|Win32">
>                         <Tool
>  <at>  <at>  -877,7 +877,7  <at>  <at> 
>                 </FileConfiguration>
>         </File>
>         <File
> -               RelativePath="..\..\common\x86\predict-c.c">
> +               RelativePath="..\..\common\predict.c">
>                 <FileConfiguration
>                         Name="Release|Win32">
>                         <Tool

Cosmetics. If msvc insists on adding whitespace and reordering statements, 
then undo that before submitting the patch. Or you could just
write the project file using a text editor; probably easier that way.

> --- a/common/osdep.h
> +++ b/common/osdep.h
>  <at>  <at>  -31,6 +31,17  <at>  <at> 
(Continue reading)

David Lariviere | 2 Apr 14:20 2008

Re: fix for MSVC

*Hits reply after reading Wikipedia article "Posting style" for definition
of top posting*

I just downloaded the latest windows headers yesterday (from "Windows SDK",
what used to be PSDK) and will try to compile to see if it resolves the
problem. 

What is the recommended method of handling the bug for affected versions?

#ifdev msvc_vers < good enough: complain and advise upgrade? 

_______________________________________________
x264-devel mailing list
x264-devel <at> videolan.org
http://mailman.videolan.org/listinfo/x264-devel


Gmane