EyeTV 2.3.2 Quick Review
Yesterday around 6pm PST, El Gato released a new version of EyeTV’s software. Despite an avalanche of complaints from users over the major changes made in 2.3.1, El Gato ignored all of the major ones and even managed to cripple functionality a little more. Here we go:
PIP – Adding Picture-In-Picture explains a lot about EyeTV’s development focus…even before 2.3.1, they were focusing on adding HUGE functionality to the software. So much that they were completely unable to notice huge mistakes they were making in some of the small details (like making their Mac app look like a verison of Windows OS, for instance).
That said, I like fooling around with PIP…expect a post exclusively about this functionality in the next couple of days.
Change Channels via Apple Remote – It’s no longer necessary to exit Live TV to change a channel, but they pulled Jump Forward and Back in exchange. To that end, I’m not sure this is such a huge step forward. Time will tell if users wanted that functionality, I suppose. But making users jump to the menu to navigate channels was nuts to begin with.
It’s amazingly frustrating when a company straight-up ignores a united voice from their customers for functionality change. 2.3.1 introduced the following:
Eliminated the Front Row menu option
Added a heavily Windows-influenced theme
“De-integrated” Front Row from the app
Switched the way menus change away from Front Row’s style
Made the Apple Remote’s Menu Button trigger Front Row from anywhere in EyeTV
These were all quickly and loudly addressed to El Gato in forums and emails, who offered very little communication (in most cases, none) in return. Most of us held out hope an update would fix some of these oversights.
I knew right away upon seeing the Windows MCE Royal Blue that things weren’t any different from before. And trying it out for a few minutes made me realize I wouldn’t have to elaborate anymore about how disappointed I am…referring people to my 2.3.1 review would accurately reflect my feelings about El Gato’s latest build.
I’ll start hoping 2.3.3 will begin to address the weakened foundation 2.3.1 and 2.3.2 created for customers. But I’m certainly not holding my breath.