Home || Blog || Main Blog Index

Archive for October, 2007

Chess

27th Open Dutch CC Ch. Final Results

Final Results

Congratulations to the Rybka team for winning the 27th Open Dutch Computer chessimage championship.

Round Results
#Name123456789PBUSBG
1Rybka8w13b12w16b15w14b07w110b19b146 40 9
2Hiarcs12b110w11b04w=6w18b13b=5w17b=6½46½29¾9
3Diep14w11w012b15b=4w=9b12w=6b18w16½41½24¾9
4Deep Junior9w16b=5w=2b=3b=1w18w111b013w145 30 9
5Spike7b=14w14b=3w=1b010w16w=2b011w144½18¾9
6The King13b14w=7b11w02b011w15b=3w014b143 16½9
7Crash Test Dummy5w=11b16w08b=9w=13b11b012w12w=41½18¾9
8XiniX1b013w110b=7w=12b12w04b014w13b041½10 9
9Hermann4b012w014b110w17b=3w011b=13b11w038½10¾9
10IsiChess MMX11w12b08w=9b013w15b014w11w012b=36½9½9
11Zzzzzz10b07w013b=12w=14w16b09w=4w15b03½34½10¾9
12GI-ANT2w09b13w011b=8w014b113w07b010w=36 7¾9
13Joker6w08b011w=14b110b07w012b19w04b02½34½4¾9
14Tzjezz3b05b09w013w011b012w010b08b06w037½9

del.icio.us:27th Open Dutch CC Ch. Final Results digg:27th Open Dutch CC Ch. Final Results

Art

Just Say NO to CMOS Cameras!

An interesting post on CCD vs CMOS from Mr Anderson (syntheyes) himself. =)
—————

This first post is a biggie, the impetus for finally setting up a ~blog. The story starts with my recent purchase of a Canon HV-20 HDV camera, which has a great big sensor, likely derived from Canon’s excellent still cameras, such as the Digital Rebel XT of which I am rather fond.

So the HV-20 generates these incredibly beautiful pictures as you train it on your various typical test scenes. Great color.

BUT! Ooohhh how the story changes when you train it on a moving scene. Little did I realize that the HV-20 has something generally called a “rolling shutter” which means that the top of the image corresponds to an earlier period in time than the bottom of the image.

I have built cameras from scratch (bare chips) in years past, so I know instantly that a rolling shutter is A REALLY BAD IDEA. Sure, it takes great pictures of the kids and dog. But for professional use in moving-camera shots, JUST SAY NO.

Here’s what happens. A vertical line, if you pan left or right, becomes slanted. Standard internet folklore says “don’t do that”—don’t pan fast and it won’t be a problem. Again, that is great for your kids and dog, but for camera tracking and inserting 3-D objects it is completely unacceptable. Even a very slow pan rate will come out to several pixels per frame at HD resolution—- but with SynthEyes and your 3-D rendering software, we are looking to match at a sub-pixel !

If you think that because you don’t pan, this won’t be a problem, think again. The same thing happens on dolly or truck moves. If you tilt up and down, instead of slanting you get very visible vertical stretching or compression. If you shooting forward from a car, your image will be mistimed and probably difficult to see that it has happened.

The most spectacular disaster came from my helicopter charter. With new camera gleefully in hand, I got a quick charter flight together to acquire some new HD example footage, especially for the Bentley Exposition next week.

When you have a rolling shutter, and the vibration of a helicopter, you get one of the most spectacular disasters you have ever seen. In the viewfinder during the flight, it looked fine. But back in the studio, OUCH! It looked like the images had been projected onto a shaking bowl of Jello(tm whoever). This part of the image was going this way, another part a different way, etc. It was all completely and utterly $200 of useless footage straight into the garbage can.

Sony has some CMOS cameras where they apparently try to minimize this by reading out the image several times faster, but it can not eliminate it.

Even if your images do not visibly have distortions due to the rolling shutter, the effect is still there at some level. The tracker positions will be wrong, by up to one frame’s worth of velocity. The errors will be larger, but it’s not like you’ll just have some larger numbers to look at.

The error due to the rolling shutter will be built into the geometry of the scene and camera, resulting in a distorted scene geometry. I know people are going to email me about how SynthEyes is generating the wrong scene geometries and camera paths from their scenes shot with these cameras.

Just to make life interesting, note that a standard film camera can also have a rolling shutter. The design of the shutter will determine the extent of the problem; it is pretty easy to calculate. It may contribute some geometric errors depending on camera motion.

Is there a magic fix for this problem? No. Obviously if you have a CMOS camera you can try to minimize it by avoiding and minimizing camera motion, but that sort of spoils the point of moving pictures, right? There’s a technical thing that SynthEyes could do with a Sizzle script, if the camera motion is very smooth, to compensate for it so that the geometry comes out better. But the images themselves would still be bad, and you wouldn’t be able to render out of max or mayaimage with matching mistimed images.

Your best approach is to stick to CCD cameras. Leave the CMOS ones for the kids and dogs.
_____________
Russ Andersson
Andersson Technologies LLC

del.icio.us:Just Say NO to CMOS Cameras! digg:Just Say NO to CMOS Cameras!

Comet Digital, LLC is pleased to announce that Autodesk, Inc. has acquired the cMuscleSystem plug-in and technology. We feel this transaction is in the best interest of our customers and the long term development of the technology.

Existing cMuscleSystem customers with Autodesk Mayaimage Gold Subscription, formerly Platinum Membership, will now be supported by Autodesk Product Support. For product support requests please use the online form, http://www.cometdigital.com/supportForm.php or login into Autodesk Subscription Center at, http://pointa.autodesk.com/local/enu/portal/signin.jsp.

We appreciate your business and support for the last several years and are excited about the future of the cMuscleSystem technology.

Thank you,

Michael Comet
President, Comet Digital, LLC

del.icio.us:Autodesk, Inc. acquires “cMuscleSystem” from Comet Digital LLC digg:Autodesk, Inc. acquires “cMuscleSystem” from Comet Digital LLC

Name

Hardware

Programmers, team members

Place

Rybka

Intel Core 2 Extreme QX6700 (4 cores), 3200 MHz (remote)

Vasik Rajlich,
Jeroen Noomen (book),
Hans van der Zijden (oper)

Budapest, Hungary
Apeldoorn, NL,
Duivendrecht, NL

Junior
Intel 8-core or 16-core (remote) Amir Ban (prog.)
Shay Bushinsky (prog.)
Boris Alterman (book)
Israel

The King (MP)

Intel Core 2 Duo E6700, 2660 MHz

Johan de Koning

Delft, NL

Hiarcs

Intel Core 2 Extreme QX6700 (4 cores), 3700 or 3420  MHz (remote)

Mark Uniacke (prog.)
Harvey Williamson (oper.)
Enrico Carrisco (tester/oper.)

UK,
UK,

USA
Diep
dual opteron 2.4GHz (remote) Vincent Diepeveen (prog)
John v/d Hoeven (oper.)
Arturo Ochoa M (book)
Veenendaal, NL
Rotterdam, NL
Venezuela
Spike
nothing too fast Volker Böhm (prog.)
Ralf Schäfer (prog.)
Timo Klaustermeyer (book)
Germany
(unconfirmed)
Quad
TV  

Crash Test Dummy

AMD Dual Opteron 270 (4 cores)

Richard Pijl (prog.)
Arturo Ochoa (book)
Minderhout, Belgium,
Venezuela
Homer
Intel Core2 Duo, 3.0 GHz, 2 cores (remote)
Daniel Mehrmann
Germany
IsiChess MMX
AMD64 dual core
Gerd Isenberg, (prog.)
Germany

XiniX

Intel Pentium M. 1700 MHz

Tony van Roon
Elke van Roon (oper.)

Eindhoven, NL

Hermann

Intel Core 2 Duo E6600, 2400 MHz, 4 GB RAM

Volker Annuss
Christian Bartsch (book)

<>Unna, Germany
Niederseefeld, Ger.
Tzjezz Intel Pentium Pentium (Centrino) 1.73 GHz, 1 Gb RAM Ron Appelman (prog.)
Berkhout

Joker

Intel Core 2 Duo, 2.4GHz, 1GB, using one core

Harm Geert Muller (prog.)

Diemen, NL

Zzzzzz
  Gijsbert Wiesenekker
 
Ktulu
  Rahman Paidar (prog)
Edwin Dabbaghyan (oper.)
 

del.icio.us:27th Open Dutch Computer Chess Ch. 26-28 October in Leiden digg:27th Open Dutch Computer Chess Ch. 26-28 October in Leiden

Art

UT3 Demo Commands

Here is a list of UT3 demo commands.
Be sure to test out some of the cool vehicles!

God (god mode)
Allweapons (gives you all weapons)
Allammo (gives you full ammo)
fly (fly around)
walk (stop flying)
ghost (Fly around and go through walls)
stat fps (shows your frame rate {frames per second})
stat net
setsensitivity (set your mouse sensitivity)
suicide (kill yourself)
loaded (same as allweapons)
playersonly (nothing moves except you)
setbind key command (set input is now setbind key command)
shot (takes a screenshot)
behindview 1 (changes view)
open [IP address] [Port number]
summon utgamecontent.utslowvolume_content (slow volume cube)
stat engine (for the rendering info.)
disconnect (disconnect from server)
reconnect (reconnect to server)
exit (quits program)
togglescreenshotmode (disables all hud elements for taking screenshots)
giveweapon utgamecontent.UTWeap_Translocator_Content (translocator)
summon utgamecontent.utvehicle_fury_content (Fury vehicle)
summon utgamecontent.utvehicle_hellbender_content (hellbender vehicle)
summon utgamecontent.utvehicle_darkwalker_content (darkwalker vehicle)
summon utgamecontent.utvehicle_cicada_content (cicada vehicle)
summon utgamecontent.utvehicle_nemesis (nemesis vehicle)
summon utgamecontent.utvehicle_paladin (paladin vehicle)

del.icio.us:UT3 Demo Commands digg:UT3 Demo Commands