Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

Comment: Re:Adapt (Score 1) 626

by pezezin (#27293605) Attached to: Windows and Linux Not Well Prepared For Multicore Chips

I don't have a final solution quite yet (though I am working on it as a thought project), but the problem we need to solve is getting a new instruction set which is inherently capable of parallel operation, not on adding more cores and pushing the responsibility onto the programmers for multi-threading their programs.

Like the old Cray machines, or the new NEC SX series? After having studied them, I wonder why manufacturers don't add long vector instructions to current CPUs, they are much more flexible than short vectors (SIMD).

Comment: Re:Linux, Macs, and Windows PCs (Score 1) 1147

by pezezin (#27286909) Attached to: Ballmer Scorns Apple As a $500 Logo

I recently bought a Precision M4400 with a Core 2 Duo T9400, 4 GB of RAM, Quadro 770M with 512 MB of dedicated RAM, 15" matte 1440x900 display, with white LED backlighting, a 200 GB, 7200 RPM hard-drive, and Vista Bussiness (I use Windows for games, I don't care what version it is). It cost me 1800 euros. At the time, a MacBook Pro with a similar configuration had a cost of 2500 euros. Now, this was in Spain, I have heard that in USA macs are cheaper.

PS: about having a big screen and HDD... I have it plugged to an external 22" display and a 500 GB eSATA drive. Plenty of space.

Comment: Re:Performance? Benefits? (Score 1) 127

by pezezin (#25091951) Attached to: Dirac 1.0.0 Released

While they give a very natural style of compression on still images (JPEG-2000, etc), they do not translate well to moving sequences because, unlike all other current codecs, the image is not broken up into blocks that can then be tracked and diff'd in time.

You seem to be confusing motion estimation/compensation with residual coding. Dirac does break the image into blocks, using overlapped block motion compensation. However, the residual image is coded as a whole, thanks to wavelets. This should greatly reduce blocking artifacts.

You will have a head crash on your private pack.

Working...