Customer Rating:  
Summary: Perfect for my needs
Comment: Here's my hardware software setup:
Computer: Mac Mini Core Duo 1.66GHZ, 1 GB of RAM
OS: OS X 10.5.5
QuickTime version: 7.5.5
TV software: Elgato EyeTV 3.x software
TV hardware: Elgato EyeTV 250 Plus hardware
---
Conversion Test:
Method: Using Elgato EyeTV export function with the "Apple TV" profile
Source file: 1:08 1080i HDTV recorded with my Elgato EyeTV Plus
Video output: H.264/AVC, 800 x 540, Millions
Audio output: AAC, Stereo (L R), 48.000 kHz
Output FPS: 29.97
Output Normal Size: 960 x 540 pixels
--
Results:
Time using Turbo.H264: 1:55 -- average CPU load of 25% (both processors)
Time using QuickTime Software: 3:52 -- average CPU load 95% (both processors)
--
Notes:
The video quality looked ever so slightly better to my eyes using a straight QT export without the Turbo.H264 BUT the difference was not nearly enough for me to quibble with the quality or value (to me) of this product. Exports using the Turbo.H264 still look very good to my eyes.
I'm not sure what to make of the fact that the video output width is set to 800 pixels and yet all my files emerge at 960 pixels. I'm assuming there must be some sort of anamorphic PAR conversion built into the encoding process but I'm not losing any sleep/hair over it because the output looks very good on my TV.
--
Conclusion:
The faster your Mac, the less speed benefit you will see. I've run some rudimentary tests using this product on my other Mac's (MBP & an older iMac G5). Once I get firm results and run multiple tests, I'll update this review. I can already tell that the iMac G5 sees an enormous benefit this product and the MBP also benefits but to a lesser extent than either of my slower machines. There also seems but be a difference depending upon what input files one throws at this unit. AVI Xvid files appear to convert very quickly but other file formats do not seem to respond as well.
In my case, the Turbo.H264 is well worth money because I principally use it in conjunction with an Elgato EyeTV. My computer retains plenty of cycles left over to record additional programs while simultaneously exporting previous recordings.
--Stefan
Customer Rating:
Summary: Works Great for Me - 75% Increase in performance.
Comment: I have a Mac 2.16 GHz Intel Core Duo. It has been taking me forever to convert TV shows using VisualHub. Even worse then the amount of time taken, is that it makes my computer pretty much unusable during the conversions. I am using the Apple TV setting (higher quality than I was using with VisualHub) and seeing times reduced 75%. I was getting average fps rates of 5-7 without the device and now am running at 20 fps. I also see no noticeable performance difference while the process is running.
I couldn't be happier. Great product.
Customer Rating:
Summary: Good when it works...if it works
Comment: Really erratic. I try batch converting files from a series (e.g., different episodes from the same TV source), and half of them get converted and the other half gets spit out because Turbo.264 claims it cant handle DivX files. Ive downloaded the "required" software using Turbos link, and the same problem recurs. Whether a single file or a batch of files, Turbo.264 just quits at different places when processing the same file at different times. So far, Ive given up using its software for conversions and have returned to opening an AVI file with QuickTime, then exporting to Apple TV format.
It works fine as an adjunct to EyeTV, but I find it easier to record programs using my cable box DVR. I think the software should be renumbered 0.3, not 1.3.
Also, I think it should have its own power supply because even when hooked up to a POWERED USB 2.0 hub, it sucks so much juice that a warning message pops up on the screen advising me that the hub is overloaded and I should disconnect some of my devices. Of course, I experienced dozens of trials with System Profiler not even recognizing it being connected (because it was way underpowered and therefore invisible) before I got the first overloading message, and then I isolated the Turbo.264 as the sole USB device connected to a powered 7-port USB 2.0 hub. Then it was recognized (but still crashes occasionally).
At least Tech Support came up with the same diagnosis after I contacted them. Problem is, why isnt any of this in the small flyer of an instruction manual?
Customer Rating:
Summary: Does not work well for AppleTV
Comment: I got this for exporting eyeTV recording to appleTV format and first time a try at the end of the process it give an error message and does not create a file. After checking the web site it turns out it is a know bug. When it works it encodes video in a 1to1 speed (one hour recording takes one hour to encode in a mac mini). I am disappointed because my main use was Apple TV encoding. My other use is iPod encoding and that appears to work ok.
When using Turbo.264, some exports to the Apple TV format may fail
Solution
When using Turbo.264, some exports to the Apple TV format may fail before completing.
If you are exporting from within EyeTV, the error reported will be something like 0xE0004051 or 0xE00002E0. You may also see a blank, grey window with the Turbo.264 icon in one corner.
If you are exporting using the Turbo.264 application, version 1.2, the error will be something like -536870176.
In either case, Turbo.264 is prevented from completing the export, due to an issue with the firmware inside the unit. This issue is particular to the Apple TV export preset.
This issue is being researched with the assistance of the hardware manufacturer, and once a solution is found, a software update to Turbo.264 should resolve the problem.
Until then, there are a few workarounds you can use:
1) Export using a setting other than "Apple TV", like "iPod High".
2) Customize your Apple TV export, reducing the resolution by 16 pixels in both directions.
3) Unplug and replug the Turbo.264 before starting the export.
Any of these three steps should allow the export to complete.
We sincerely apologize for the inconvenience that this error has caused.
Customer Rating:
Summary: Multi-task away.
Comment: From what I've gathered about the Turbo.264 from other sites, the faster/newer your processor is, the less remarkable encoding speed you will see. That held true on my system; however, speed wasn't what drew me to this product. What I desperately needed was something that would alleviate the strain on my processor from EyeTV encoding. By strain I mean 9 hours worth of encoding a day. What that translated into was 97% of the processor's capability and a subsequent jump in fan speed from 2000 to 4500 RPM.
Expecting Elgato's toy to just make it possible to passably multi-task, I was floored when I saw that it had in fact brought down the CPU back to the average functioning level (25%) and the fan down to a normal 200 RPM, which is case when EyeTV is neither recording nor encoding.
Bottomline: I would have loved to have seen a noticeable encoding time reduction, but I am completely content with this purchase, knowing that hardware complications will not arise from excessive encoding.
|
