

Just got the Turbo.264 encoder, ran some basic tests. ( First user report from 2007, using early v1.0.1 Turbo.264 software)Įlgato Turbo.264 User Review - real world numbers Also keep in mind the 800圆00 limit for Turbo.264.) Also some notes on lower CPU usage for those multi-tasking (running other apps/tasks while converting video).
#Eyetv 3.0 1 software
( Earlier reports/results follow - using different machines/earlier software and OS X versions - biggest gains are from slower CPU systems. Next time I record a show in EyeTV I'll do some comparisons with and without Turbo.264 connected.

But again not sure if 10.5.6 has made a significant difference in performance. (Some earlier reports below included results from G5 towers that were faster without it also - biggest benefit is from lower-end machines, despite claims.) I still keep it connected though just for the lower CPU usage (as I generally do other things while converting in the background). I've not compared times under 10.5.6, but IIRC my initial results (almost a year ago now) with EyeTV 3.0x converting EyeTV recordings (1080i OTA recordings) to AppleTV (default one-click conversion in EyeTV) were very similar in times (not much difference) on this 2007 AL iMac 2.4GHz. I have just run a test for the AppleTV export on my iMac (specs as described in previous email) for a 46.8MB file (video source 576i, as above) and got 1:06.8 without the Turbo.264 and 1:45.1 with the device, a slowdown of about 36%. In fact, I only learned about the Turbo.264 when I came across this setting! I decided to compare times for the WiFi export first, as this is the setting in EyeTV preferences where they claim using the Turbo.264 would speed up export times.

I then clicked on the "Prepare for WiFi access again" link for each and timed how long the export took with a stopwatch. I recorded two programs in EyeTV - one of exactly 60 seconds length (53.6MB) and another of exactly 5 minutes (263.2MB). I was using EyeTV version 3.0.4 (4279) and the Turbo.264 software is version 1.3 (294) and all of this was running on OS X Leopard 10.5.6. After discovering that my new Turbo.264 was slowing down my exports, I ran some very quick tests using the EyeTV software on my iMac 3.06GHz Intel Core Duo (with 4MB DDR2 RAM).
#Eyetv 3.0 1 tv
#Eyetv 3.0 1 pro
Files exported from Final Cut Pro are no longer cropped.iMovie projects that contained a title at the beginning no longer export at 1 frame per second.QuickTime Player no longer plays back files with an incorrect gamma value.A problem where files encoded from EyeTV 3.1.1 to Apple TV, iPhone or iPod did not contain the sound track has been resolved.Files encoded to iPod/iPhone formats no longer cause the 2nd-gen iPod touch to crash.The "Closed Captions" option creates a QuickTime closed caption track from NTSC sources with closed captions.The "Chapter Markers" option creates QuickTime chapter markers from sources that contain chapter markers, e.g.The "Dolby Digital" option preserves Dolby Digital AC-3 audio when encoding to Apple TV.This reduces encoding speed somewhat, especially on slower Macs.Īdvanced Options: Three advanced custom options have been added. Improved Picture Quality: In many cases, encoded files are sharper due to improved deinterlacing. Their page's change list initially (fixed now) had the exact same features mentioned in the May 2008 v1.3 release (YouTube Upload, DVD Chapter Markers, Dolby Digital AC-3 Audio Passthrough for Apple TV Exports, QuickTime Broadcaster Support and bug fixes) - so I downloaded the ReadMe file for v1.4, which shows these changes:
#Eyetv 3.0 1 update
Turbo.264 v1.4 Software Update: ElGato has posted a v1.4 software update for their original Turbo.264 ( no longer online). Updated for Apple TV conversion tests w/1.1 software Updated for Apple TV setting tests w/CPU usage
#Eyetv 3.0 1 mac
Recent Updates | Mac Upgrades/Repairs | Storage | Video | Audio/HT | Apps/OS/Network | HomeĮncoding Speed Tests with Elgato Turbo.264 Hardware Encoder Encoding Speed Tests with Elgato Turbo.264 Hardware Encoder (Macintosh)
