Thursday
May072009
Elgato Turbo 264HD - Update
Thursday, May 7, 2009 at 10:23PM
Today I received my replacement Elgato Turbo 264HD from Germany. In my earlier post I mentioned that my Turbo264HD was overheating and couldn't encode for more than 40 mins at a time without failing-out. I decided to get it replaced and sent it off to Elgato in Germany. Three anxious weeks of waiting later and my replacement device has been delivered back to me.
I am very happy to confirm that the replacement device does not overheat. I've had it encoding 1080p MP4s continuously for over two hours this evening and it's performed impeccably.
Excellent - thanks Elgato. Now if only they could sort out the iMovie09 export problem, I'd finally be able to finish off editing my holiday footage.
I am very happy to confirm that the replacement device does not overheat. I've had it encoding 1080p MP4s continuously for over two hours this evening and it's performed impeccably.
Excellent - thanks Elgato. Now if only they could sort out the iMovie09 export problem, I'd finally be able to finish off editing my holiday footage.

Reader Comments (3)
What is the iMovie09 export problem?
Its a pretty significant one.
After completing editing in iMovie09 the next stage is to export the movie. To do this you choose the Share function and then pick the type of codec you want to use.
Installing the Elgato software adds an additional codec option to this list (Elgato 264HD) - and the idea is that choosing this utilises the dongle to significantly accelerate the process.
Unfortunately it doesn't work. The dongle lights up but no acceleration takes place. From memory my 1.5 hr movie took about 12 hours to export using Apple's own 720p codec or an estimated 16 hrs using the Elgato one. If it was working properly then it probably should take no more than a couple of hours.
Now I could swear it worked properly when I first got the stick, for about a day - but then Apple sent out a bug fix update to iMovie09 and since then it hasn't worked.
The good news is that Elgato are aware of the problem and therefore hopefully will fix it in the next version of software. The fix is taking longer than I'd expect though as it's a pretty essential feature.
Hi Techmoan,
I saw your tweet that the problem is not fixed! Do we have a sample here and EXACT steps how to reproduce using the latest 1.0.2 Turbo.264 HD software? (BTW: Did you try a reboot of your Mac after you installed both Turbo.264 HD and iMovie updates?) Please feel free to contact me via email.