Endless Paradigm

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

Dunno whot happend here,. except offcourse i installed a SSD with Win7 x64.
Twice the previous score,. O_o?

[Image: 2njv7zo.png]

Code:

			x264 HD BENCHMARK 3.0 RESULTS 
 
Please do not compare it with older versions of the benchmark! 
Please copy/paste everything below the line to to report your data 
 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
 
Results for x264.exe r1342 
-------------------------- 
encoded 1442 frames, 45.62 fps, 3900.68 kb/s
encoded 1442 frames, 45.57 fps, 3900.68 kb/s
encoded 1442 frames, 45.60 fps, 3900.68 kb/s
encoded 1442 frames, 45.42 fps, 3900.93 kb/s
encoded 1442 frames, 12.75 fps, 3971.85 kb/s
encoded 1442 frames, 12.81 fps, 3971.84 kb/s
encoded 1442 frames, 12.78 fps, 3969.39 kb/s
encoded 1442 frames, 12.82 fps, 3970.64 kb/s
 
 
System Details 
-------------- 
	Name			Intel Core i5
	Codename		
	Specification		Intel(R) Core(TM) i5 CPU       M 540  @ 2.53GHz
	Core Stepping		
	Technology		32 nm
	Stock frequency		2533 MHz
	Core Speed		2793.1 MHz
 
Northbridge			Intel ID0044 rev. 02
Southbridge			Intel QM57 rev. 05
 
Memory Type			
Memory Size			4096 MBytes
 
Windows Version			Microsoft Windows XP Professional  Service Pack 3 (Build 2600) 
 
Number of processors		1
Number of threads		4
	Number of threads	4 (max 16)
	L2 cache		2 x 256 KBytes, 8-way set associative, 64-byte line size
	Instructions sets	MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, EM64T
	Package (platform ID)	Socket 1156 LGA (0x4)
 
	Temperature 0	82°C (179°F) [0x17] (Core #0)
	Temperature 2	85°C (184°F) [0x14] (Core #2)

Dad's new laptop.

Pretty good for a laptop. A dual core laptop, achieving 80% the performance of my desktop quad (though my quad is like first generation).

Code:

			encoded 1442 frames, 31.69 fps, 3908.27 kb/s
encoded 1442 frames, 31.80 fps, 3908.27 kb/s
encoded 1442 frames, 31.50 fps, 3908.27 kb/s
encoded 1442 frames, 31.35 fps, 3908.27 kb/s
encoded 1442 frames, 5.95 fps, 3966.52 kb/s
encoded 1442 frames, 5.98 fps, 3966.55 kb/s
encoded 1442 frames, 5.96 fps, 3966.22 kb/s
encoded 1442 frames, 6.03 fps, 3966.56 kb/s

Wonder if 64 bit x264 would help speed things up?

Mickey Wrote: [ -> ]Wonder if 64 bit x264 would help speed things up?

Maybe - but there's no point because if wee're all using different builds wee're gonna get incomparable results.

Not sure if you should be 8th or 9th - your second pass is lower than squees one but your first pass is higher.

I'll keep you in 8th for now.

What the hell the software is 581mb !! just for a benchmark! app, I'd rather list my computer parts than download this!
CPU: core i7 860
MB: Gigabyte P55A-UD3P
GPU: ATI RADEON HD 5850

Mickey Wrote: [ -> ]Wonder if 64 bit x264 would help speed things up?

Around 10% speed up, which is actually quite significant.

BUT, you'll have to either....
    1. Directly input into x264 (get a version built with ffms2 input).
    2. Decode and pipe to x264 with some other decoder (eg. Mplayer, ffmpeg).
Or if you need/want to use avisynth (for filtering or whatever other reasons)...
    3. Use a 64bit avisynth, of which there currently is only some unofficial builds which are buggy as hell.
    4. Use normal avisynth, and pipe it to x264 with something like avs2yuv.

Senseito7 Wrote: [ -> ]Maybe - but there's no point because if wee're all using different builds wee're gonna get incomparable results.

Yeah. Worth looking into if you do a lot of encoding at home though.

Senseito7 Wrote: [ -> ]Not sure if you should be 8th or 9th - your second pass is lower than squees one but your first pass is higher.

I'll keep you in 8th for now.

9th. Second pass is more important, since more time is spent on that than the first pass, and it's the pass that actually encodes stuff. For quad cores, 1st pass doesn't even use up 100% CPU (thus not a good benchmark).

Actually, it would be best to calculate some harmonic mean and rank based on that, but I don't think anyone could be stuffed doing that.

x264 keeps crashing in like every other app :/ can't use x264 with handbrake, anything I can do? Just got a new laptop and installed Windows 7 64 bit.

Assassinator Wrote: [ -> ]
Mickey Wrote: [ -> ]Wonder if 64 bit x264 would help speed things up?

Around 10% speed up, which is actually quite significant.

BUT, you'll have to either....
1. Also use a 64bit avisynth, of which there currently is only some unofficial experimental builds which are buggy as hell.
2. Decode and pipe to x264 with some other 64bit decoder (eg. Mplayer, ffmpeg).
3. Use normal avisynth, and pipe it to x264 with something like avs2yuv.
4. Directly input into x264 (get a version built with ffms2 input).

Mickey Wrote: [ -> ]x264 keeps crashing in like every other app :/ can't use x264 with handbrake, anything I can do? Just got a new laptop and installed Windows 7 64 bit.

Never used Handbrake before, so I have no idea how that works internally. You can try asking Zinga, who if I remember correctly, uses Handbrake.

That being said, unless your frontend is specifically designed to use 64bit x264, then most likely it won't work if you just simply replace the x264 binary with a 64bit version.

Here's my new laptop's 3DMark06 score! I am proud of the little trooper :P

[Image: 3DMark06score.png]

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

Vegetano1

Assassinator

squee666

Mickey

S7*

bloodangel619

Assassinator

Mickey

Assassinator

Hellgiver