<?php $recent = new WP_Query(“page_id=13″); while($recent->have_posts()) : $recent->the_post();?>
<?php the_content(); ?>
<?php endwhile; ?>

Introduction

The RC-1 Infrared Wireless Remote Controller can be used to release the shutter from up to 5 m (16 ft) away from a number of popular Canon EOS camera bodies (including EOS 10, Elan family, EOS IX, EOS Kiss III and EOS Kiss III L).

Check your specific camera manual for compatibility information, since similar models in different markets may have different features. (e.g. EOS 50 Elan 7E )

Operation

Holder
The strap holder is used to secure the RC-1 to the camera strap for storage. Push the red button on the RC-1 to unclip it from the strap holder.

Thread the camera strap around the two lugs on the strap holder before attaching the strap to your camera. Arrange the clip so that you can attach and detach the controller using one hand.

L
Set switch on the RC-1 to the “L” position to disable the button on the RC-1 and prevent accidental tripping of the shutter.

Release
Setup your shot by positioning your camera and lens on a tripod, and checking your composition. If you cannot be sure that a subject will be covered by an autofocus point, use manual focus instead.

When you are ready to shoot, Switch your camera ON, then select the remote release mode. Set the switch on the RC-1 to • then point the RC-1 towards the front of the camera and push the button to release the shutter immediately.

The camera will only respond to a remote control signal for approximately 4 minutes to prevent draining the battery. After that, the remote sensor is shut off, and the remote control icon will disappear from the camera LCD panel. Switch the camera off, then re-enable remote mode for another 4 mintues.

The RC-1 can only be used for shooting photographs one frame at a time. It cannot be used for continuous wind, unlike the RS-60E3 wired remote.

Bulb
When the camera is set to BULB mode, pushing the RC-1 opens the shutter. A second push of the RC-1 closes the shutter. This behaviour is similar to “T” mode mechanical shutter release.

Delay
Setting the switch on the RC-1 to 2. When you push the button, the camera will release the shutter after a two second delay. If you are in the shot, this should be sufficient time to hide the remote controller.

Battery
Replace exhausted batteries with two fresh 3 Volt CR-1220 coin-type cells. Open the battery compartment by sliding the cover in the direction of the arrow.
Specification

Physical
Length 60 mm (2 3/16″) Width 25 mm (1″) Height 13 mm (1/2″) [Not including retaining clip]
Weight 10 g (0.4 oz) [including battery]

Battery
Two button-type CR-1220 (3 Volt) cells

Range
5 m (16.4 ft)
Outdoors use requires a direct line of sight to the sensor, which is usually located on the front of the camera handgrip. Reflections from indoor walls, floor and ceiling are often enough to allow indirect triggering (e.g. from behind the camera).

I have confirmed this wireless remote control to be working flawlessly with the Canon Rebel XSi.

sudo thunar

Browse to:

/lib/plymouth/themes

Rename: “default.plymouth” to “default.plymouth.bak”

Run the following command from the terminal:

sudo update-initramfs -u

Restart your computer and enjoy the text based boot screen.

If you want to change the text “Xubuntu” to something else, edit the file “text.plymouth” under /lib/plymouth/themes

Enjoy!

• Chromium – Stable Channel
• Chromium – Dev Development
• Chromium Daily Builds

This means there is no need to actually build anything, its already done for you. You just need to install the PPA on your system and Chromium will be up to date all the time.

Install from the terminal:

Open a terminal and start by adding the PPA

For the stable channel

sudo add-apt-repository ppa:chromium-daily/stable 

For the dev channel

sudo add-apt-repository ppa:chromium-daily/dev 

For the daily builds channel

sudo add-apt-repository ppa:chromium-daily 

After this you need to update your sources

sudo apt-get update 

When the sources update is complete you just need to install the chromium-browser package and the desired version will be installed

sudo apt-get install chromium-browser

Because of this work, Adobe has been able to partner with Google in providing a “Pepper” implementation of Flash Player for all x86/64 platforms supported by the Google Chrome browser. Google will begin distributing this new Pepper-based Flash Player as part of Chrome on all platforms, including Linux, later this year.

For Flash Player releases after 11.2, the Flash Player browser plugin for Linux will only be available via the “Pepper” API as part of the Google Chrome browser distribution and will no longer be available as a direct download from Adobe. Adobe will continue to provide security updates to non-Pepper distributions of Flash Player 11.2 on Linux for five years from its release.

Flash Player will continue to support browsers using non-”Pepper” plugin APIs on platforms other than Linux.

We will be providing a debug player implementation of the Flash Player browser plugin on Linux, and will update the whitepaper once we have more details on how it will be distributed.

Google Chrome 18 brings two methods of improved graphics support to both newer and older computers. Released today, Google Chrome 18 stable for Windows (download), Mac (download), Linux (download), and Chrome Frameimproves both WebGL and Canvas2D.

To help along WebGL in Chrome on older Windows and Mac computers, it now gets a boost from a software rasterizer called SwiftShader, licensed from TransGaming. SwiftShader only works when Chrome’s baked-in graphics processor acceleration doesn’t run, and in the blog post announcing the update, Google said that it sought out this third-party solution so that “more users will have access to basic 3D content on the web.”

The Canvas2D changes will allow the same older PCs to process game and animation graphics faster. When Google originally debuted the improved Canvas2D in Chrome beta, the company noted that the multitude of older hardware configurations caused significant delays in implementing the improvements. The feature doesn’t yet work for Linux.

In the offing for Chrome 19, due around six weeks from today, and Chrome 20, due just before June’s Google I/O conference, are full implementation of Google’s Native Client (NaCl) tech. Already partially available in the Chrome 19 developer’s version, NaCl and its API set known as Pepper will allow, the company says, gaming support in the browser that will come close to console-quality graphics.

Chrome 18 also updates the Adobe Flash plug-in to its latest version, and makes numerous security and bug fixes. There were no “critical” security fixes, but there were a few “high”-level fixes, out of nine security fixes reported.

• Hardware-accelerated Canvas2D graphics.
• WebGL without the need of 3D graphics hardware through the software rasterizer SwiftShader.
• Brighter “new tab” button.

You can read the Chrome 18 changelog here.

Security fixes and rewards:
Please see the Chromium security page for more detail. Note that the referenced bugs may be kept private until a majority of our users are up to date with the fix.

Some of the items listed below represent the start of hardening measures based on study of the exploits submitted to the Pwnium competition.

• [$500] [109574] Medium CVE-2011-3058: Bad interaction possibly leading to XSS in EUC-JP. Credit to Masato Kinugawa.
• [$500] [112317] Medium CVE-2011-3059: Out-of-bounds read in SVG text handling. Credit to Arthur Gerkis.
• [$500] [114056] Medium CVE-2011-3060: Out-of-bounds read in text fragment handling. Credit to miaubiz.
• [116398] Medium CVE-2011-3061: SPDY proxy certificate checking error. Credit to Leonidas Kontothanassis of Google.
• [116524] High CVE-2011-3062: Off-by-one in OpenType Sanitizer. Credit to Mateusz Jurczyk of the Google Security Team.
• [117417] Low CVE-2011-3063: Validate navigation requests from the renderer more carefully. Credit to kuzzcc, Sergey Glazunov, PinkiePie and scarybeasts (Google Chrome Security Team).
• [$1000] [117471] High CVE-2011-3064: Use-after-free in SVG clipping. Credit to Atte Kettunen of OUSPG.
• [$1000] [117588] High CVE-2011-3065: Memory corruption in Skia. Credit to Omair.
• [$500] [117794] Medium CVE-2011-3057: Invalid read in v8. Credit to Christian Holler.

The bugs [112317], [114056] and [117471] were detected using AddressSanitizer.

We’d also like to thank miaubiz, Chamal de Silva, Atte Kettunen of OUSPG, Aki Helin of OUSPG and Arthur Gerkis for working with us during the development cycle and preventing security regressions from ever reaching the stable channel. $8000 of additional rewards were issued for this awesomeness.

This version also contains the new Adobe Flash release, see release notes. Full details about what changes are in this release are available in the SVN revision log.  Interested in hopping on the stable channel?  Find out how.  If you find a new issue, please let us know by filing a bug.

Karen Grunberg
Google Chrome

A card’s speed depends on many factors, such as the following:

• The likelihood of soft errors that the card’s controller must re-try
• The fact that, on most cards, writing data requires the controller to read and erase a larger region, then rewrite that entire region with the desired part changed
• The possibility of fragmentation: that a body of information the host views as a unit is, for historical reasons, written to non-contiguous regions of memory. (This possibility does not cause rotational or head-movement delays as with magnetic media, but it does vary the amount of computation the card’s controller must do.)

In early SD cards, the speed was measured with the “×” rating, which compared the average speed of reading data to that of the original CD-ROM drive. Currently, the official unit of measurement is the Speed Class Rating, which guarantees a minimum rate at which data can be written to the card.

The newer families of SD card improve card speed by increasing the bus rate (the frequency of the clock signal that strobes information into and out of the card). Whatever the bus rate, the card can signal to the host that it is “busy” until a read or a write operation is complete. Compliance with a higher speed rating is a guarantee that the card limits its use of the “busy” indication.

Speed Class Rating

The Speed Class Rating is the official unit of speed measurement for SD cards. The class number guarantees a minimum write speed as a multiple of 8 Mbit/s (1 MB/s). The SDA defines several speed class ratings, but manufacturers may claim conformance to those ratings without independent verification.

The host device can read a card’s speed class, unlike the earlier “×” speed ratings. A device can warn the user if the card reports a speed class that falls below an application’s minimum need.

These are the ratings of all currently available cards:

Class	Speed
Class 2	2 MB/s
Class 4	4 MB/s
Class 6	6 MB/s
Class 10	10 MB/s

Speed Classes 2, 4, and 6 assert that the card supports the respective number of MB/s as a minimum sustained write speed for a card in a fragmented state. Class 10 asserts that the card supports 10 MB/s as a minimum non-fragmented sequential write speed. By comparison, the older “×” rating measured maximum speed under ideal conditions, and was vague as to whether this was read speed or write speed.

“×” rating

The “×” rating is a multiple of the standard CD-ROM drive speed of 1.2 Mbit/s (approximately 150 kB/s). Basic cards transfer data up to six times (6×) the CD-ROM speed; that is, 7.2 Mbit/s. The 2.0 specification defines speeds up to 200×, but is not as specific as Speed Classes are on how to measure speed. Manufacturers may report best-case speeds and may report the card’s fastest read speed, which is typically faster than the write speed. Vendors including Transcend and Kingston report their cards’ write speed.

This table lists common ratings, the minimum transfer rates, and the corresponding Speed Class (though the comparison is not always exact).

Rating	Read Speed (MB/s)	Write Speed (MB/s)	Speed Class
6×	0.9
10×	1.5
13×	2.0	2.0	2
26×	4.0	4.0	4
32×	4.8	5.0	5
40×	6.0	6.0	6
66×	10.0	10.0	10
100×	15.0	15.0
133×	20.0	20.0
150×	22.5	22.5
200×	30.0	30.0
266×	40.0	40.0
300×	45.0	45.0
400×	60.0	60.0
600×	90.0	90.0

UHS Speed Class

The Ultra-High Speed (UHS) interface is available on some SDHC and SDXC cards. The following ultra-high speeds are specified:

• UHS-I cards, specified in SD Version 3.01, support a clock frequency of 100 MHz (a quadrupling of the original Default Speed), which in four-bit transfer mode could transfer 50 MB/s. UHS-I cards declared as UHS104 also support a clock frequency of 208 MHz, which could transfer 104 MB/s. UHS-I is the only class for which products are currently available.
• Double data rate operation at 50 MHz (DDR50) is also specified in Version 3.01, and is mandatory for microSDHC and microSDXC cards labeled as UHS-I. In this mode, four bits are transferred when the clock signal rises and another four bits when it falls, transferring an entire byte on each full clock cycle.
• UHS-II cards, to be defined in Version 4.0, further raise the data transfer rate to a theoretical maximum of 312 MB/s.

UHS memory cards work best with UHS host devices. The combination lets the user record HD resolution videos to tapeless camcorders while performing other functions. It is also suitable for real-time broadcasts and capturing large HD videos.

Cards that comply with UHS show UHS-I or UHS-II on the label, and report this capability to the host device. Use of UHS requires that the host device command the card to drop from 3.3-volt to 1.8-volt operation and select the 4-bit transfer mode.

Source: link

This has been mentioned in the forums to access the debug menu to force the playback speed (reset after reboot). It may take some tries. Press on the remote:

• Home 5 times
• Rewind 3 times
• Fast forward 2 times

Secret Screen Mode

I found other features, press on the remote:

• Home 5 times
• Fast forward 3 times
• Rewind 2 times

Source: link

It sounds crazy, but it has now been proven by multiple studies that transcranial direct-current stimulation (tDCS) can significantly speed up your brain. In one case, the US Air Force used tDCS on trainee drone pilots tohalve their learning time; likewise, DARPA has used tDCS to speed up the training of snipers. In another study, carried out by the University of New Mexico, test subjects learned how to play a video game twice as quickly while under tDCS, and played the game with heightened performance. Furthermore, tDCS has been shown to have therapeutic effects on people with neurological issues, such as Parkinson’s disease or post-stroke motor dysfunction. And best of all, it’s safe! Or at least, tDCS has no short-term side effects. It is unlikely due to the tiny current involved (9 volts at 2 milliamps), but there could be long-term effects — so we must suggest that you do not try tDCS at home.

With that out of the way, I give you GoFlow β1, a do-it-yourself tDCS kit. Basically, you can buy tDCS machines today, but they’re not cheap (on the order of hundreds or thousands of dollars). GoFlow wants to create a kit with all of the necessary parts for $99, with a simple, solderless schematic that anyone can put together. You can’t buy GoFlow yet, but you ask to be notified when it is.

Even at $99, the GoFlow kit is fairly expensive. Just so you understand just how simple tDCS is, all you have to do is pass 9V at 2mA through your scalp for 30 minutes. To do this, you need a battery, some electrodes, a resistor, and if you’re feeling snazzy (and safe) a current regulator. To be fair, for your $99, GoFlow will give you a plastic housing and provide a potentiometer — presumably so you can find the right voltage for your brain. You also need to know where to place the electrodes on your scalp, to boost the right area of your brain. Judging by the picture on the right, GoFlow will provide a map of the various regions.

If you’re interested in how tDCS actually works, we’ve written about it before in some detail. In effect, tDCS pushes your brain into a state of flow, which you might’ve heard of if you’re a coder or other similarly-inclined lifehacker. Basically, by pumping electrons into your brain, tDCS creates two effects: a) Neurons are made more sensitive, and thus can “fire” faster, and b) After the current is removed, your neurons are left in a “wet clay” state that are more capable of making new connections (i.e. learning).

In non-clinical applications (i.e. performed by at-home enthusiasts), tDCS has been used to improve everything from programming speed and dexterity (perhaps GoFlow is exactly what you need to finally master Perl) to FPS gaming skills. It’s not hard to see how tDCS could pose some ethical considerations, though. Should students be allowed to use tDCS when revising for an exam? (What if some students can afford tDCS kits, but others can’t?) What if pro gamers use tDCS before aStarCraft 2 match? Is that the e-equivalent of using steroids or blood doping?

Read more about the history of tDCS at Nature, or sign up for a GoFlow kit