The device does what it claims… it transcodes most any type of video file and produces an H.264 file formatted for your device (iPhone, iPod, AppleTV, BeyondTV, etc.). The processing time is (more or less) equal to the length of the video. e.g. A 60 minute video takes around 60 minutes to transcode.

My only complaint is that it uses 100% of my machine’s CPU while processing. I recall seeing a blurb about this somewhere in the documentation, but I thought it said it used “some” of the CPU. On my Macbook Pro 2.16Ghz, it spiked out the entire time. Obviously, that causes the internal fan to kick into overdrive, generating a good bit of noise.

The older non-HD version did NOT use the host CPU, so the transcode time was longer. But on a laptop I would gladly sacrifice the longer time in lieu of the fan noise. On a desktop, it would be a non-issue for me. A perfect solution would be to have a setting in the software that allowed you to choose how much of the CPU was used.

Some folks in various forums have complained about (and demonstrated) very dark videos from the device, but none of my tests were dark.

Overall, it’s a neat gadget. My only complaint is the CPU issue.

Create a multi-part file using the split command, then join it on the remote server after it transfers. Example: Start with a zipped file (somefile.zip), then run…

split -b 10m somefile.zip someprefix-

That will take somefile.zip, chop it into 10MB pieces and name them “someprefix-aa, someprefix-ab, etc.” Run “man split” for all the options:

split -b number[ k|m ] [-a suffixlength] [filename [prefix] ]

If your file will be split into more than 52 pieces, you’ll need to change the number of suffix length. The default is 2 (a-z, twice).

After transferring the pieces to the remote server, re-assemble them with cat…

cat someprefix-aa someprefix-ab ... > somefile.zip

Having problems getting iSCSI LUNs to appear in ESXi after enabling a second VMkernel switch on a separate subnet? Make sure you disable/re-enable the ESXi iSCSI Initiator AFTER adding the new vSwitch on the isolated network. I think iSCSI discovery only occurs on the Vswitches enabled at the time the initiator is enabled. Here is my scenario:

I recently setup an MD3000i SAN to connect to our VMware ESXi hosts via iSCSI on our internal LAN. My test server only has two NICs, but I only enabled eth0 with an IP of and left eth1 unused. I enabled iSCSI on the host, set send targets, config’d host access, created host-to-virt disk map, etc. and rescanned HBA. The test worked fine. After scan completed, I was able to see the LUNs in ESXi.

Next, I wanted to enable eth1 and move the iSCSI traffic off to dedicated, isolated, switches.

So I physically moved the MD iSCSI cables to 2 standalone switches, edited the MD Host Ports, setting them back to the defaults (192.168.130.x & 131.x). I left the two MD management ports in the LAN.

I enabled ESXi eth1 as VMkernel and set to IP in same range as one of the segments (192.168.130.103).

On ESXi, I removed the old send targets and entered the new IPs (192.168.130.101 & 102).

Rebooted everything for good measure. Rescanned HBA, but the LUNS did NOT show up in ESXi.

The solution? After enabling the VMKernel switch on the different subnet, disable ESXi iSCSI Initiator and reboot (maybe not needed, but I find ESXi likes a reboot for many things). When it returns (5+ minutes for mine), ENABLE the ESXi iSCSI Initiator and rescan HBA. I think iSCSI discovery only occurs on the Vswitches enabled at the time the initiator is enabled.

I’m NOT a brand snob. I’ve owned both Sigma and Tamron lenses, and typically pick the product with the best performance/price ratio. As an advanced amateur, I use my equipment a good bit. But if a photo component fails, my family is not going starve.

So when I decided to buy a grip for my new D300, I started by looking at the Nikon MB-D10 plus any major contenders; mainly, the Phottix BP-D300. That didn’t last long… most folks agree it is a significant step down from the Nikon, so I quickly ruled it out.

I thought my search was over, so I started price shopping for the MB-D10. As usual, Amazon seemed to have the best deal. In fact, at one point, their price was $233 with free shipping (at time of writing, it has increased to $249). My finger was on the buy button… then I decided to look around the web just one more time.

During my final trip to the forums I found a rather lengthy thread on the Nikon form at dpreview.com.

That got me interested in the Chinese knockoffs sold by LINK delight. The price was a lot lower. Depending on the package, as low as $67 + $20 for international shipping. The reviews are good and I thought I found a winner.

THEN, on page 245 (ok, it just seemed that way… more like page 5), someone mentioned that Adorama sold the same thing for $79 with FREE shipping. The transit time would be a lot less and I liked the idea of buying from a US company in case of returns, so I bought it. Turns out, it’s the same exact product. On the box, the brand is “Meike.” Part numbers MK-D300 & ZE-NBG300. Adorama calls it “Flashpoint Professional Battery Grip for the Nikon D300/D700.”

I’ve only had it a couple of days, but so far it’s great! All the buttons work as expected and the fit is nice. It is all plastic, so it’s not as durable or “solid” as the Nikon, but at 1/3rd the price, what do you expect?

I’ll update this post if I have any problems. But so far, I highly recommend it.

Update 1: I’ve been UNABLE to get my camera to shoot at 8FPS using rechargeable NiMH batteries.

Update 2: I guess the batteries were not 100% fully charged. I had charged them a day or two prior to testing. After doing a full charge and testing right away, the Info screen shows 8fps.

You can buy this from:

• Adorama - $79 w/Free Shipping
• LINK delight’s eBay Store- $67 and up + Shipping

Comes with two trays. Obviously, the battery is not included.

This is everything in the box (plus a “manual”).

Perhaps they are finally clearing their inventory leading up to a Nikon announcement on April 14th?

As it turns out, Fort Boise WMA is a great place for birds, but not so great for bird photography.

The main entrance road splits two wetland areas. You can see them clearly on this Google Map:

View Larger Map

During the spring months, there are thousands of birds joining in a cacophony of squawking and honking. And they are fairly antsy… not staying in one pool for very long.

The problem is, these areas are closed to visitors and they are both (mostly) hidden from view. There is no way to get elevated high enough to be at eye level with the birds. So you have to wait for them to flock to a different pond and catch a few belly shots as they fly overhead.

There are other areas further back towards the river that allow exploring year-round. We saw several raptors and a wide range of field birds.

It’s a fun place to explore and there are several geocaching opportunities in the area.

Of particular interest to me… Andy says:

“Music and video are both formats that the iPhone OS can simply view outside of the iPod app. If I just copy it into my Air Share, I can play it with just a tap. I often put whole albums on the iPhone, if I don’t yet know if I want to throw them into my big iTunes soup. That’s a particularly big plus when it’s a 700 meg movie file and I don’t know if I want to burn up that much space on my notebook’s little hard drive by actually importing it into iTunes.”

Only $4.99. Go read the review… good stuff.

Flying with Fish has the details.

However, the unit has a design flaw; the charger fits too tight around the back of the unit. In fact, as I recently found out, it is SO tight that it can easily destroy the headset when removing it.

When I contacted Aliph customer service, they were cordial, but unwilling to help since I couldn’t find my receipt.

After some additional research, I found a video tutorial showing the best way to remove the charger. Apparently, this is known issue.

It’s really lame of Aliph to not stand behind their product. I definitely WILL NOT be buying my replacement headset from them.

Check out Zach Arias’ video post from Scott Kelby’s blog.