Some new stuff:

What's new in this version:

fully compatible with Mac OS X 10.5 Leopard and supports the following key new features of Mac OS X 10.5: Quick Look, iChat, Spaces.
Support has been added for TerraTec Cinergy S USB, a DVB-S satellite tuner using USB 2.0.
Support has been added for the TerraTec Cinergy Piranha, a new DVB-T and DAB Radio USB stick available in Europe.
Support has been added for the Pinnacle 72e, a new DVB-T-only USB stick available in Europe and Australia.
Support has been added for the Logitec LDT-1S302U, a new ISDB-T USB stick available in Japan.
A problem where EyeTV would stall during an update of the electronic programming guide if the network connection was unavailable has been fixed.
EyeTV 250 Plus can now open multiple live television windows on the same DVB or ATSC multiplex.
For Freebox, streams with more than 10 radio stations are now supported.
For computers with multiple active network interfaces, EyeTV's Wi-Fi Access feature now respects the preferred network list in the Network system preference pane.
EyeTV Wi-Fi Access now works properly with aliases to the EyeTV Archive folder.
EyeTV Wi-Fi Access now correctly displays EyeTV recording names in non-Latin character sets.

Coverflow browsing, not mentioned in that list, an EyeTV archive is pure joy :)

No mention of the Apple Remote bug. Anyone try it yet?

In case anyone needs a link:
http://www.versiontracker.com/dyn/moreinfo/macosx/15645

Apple remote works.

Apple remote works.
Great news!

Jerry, thanks for posting the link. Hopefully this will fix the frame dropping issue Ted and others reported with 2.5 on their Mac Minis. (Fortunately, I did not experience any frame dropping with EyeTV 2.5 on my 1.66 GHz CoreDuo Mini under Leopard.)

Just an fyi, the EyeTV digital audio kernel panic is still around with 2.5.1 and Leopard.

Anyone tried it with iChat Theater? Wondering if it's possible to share the Live Buffer?

Anyone tried it with iChat Theater? Wondering if it's possible to share the Live Buffer?

I think it only works with wifi enabled recordings, which are iPhone sized streamable conversions that are within the EyeTV recording packages. Hence you are really only streaming smallish MP4's over iChat not MPEG2 TS's which QT can't really handle anyway (which is what the live buffer would be).

No one else with a Leopard and 2.5.1 digital audio kernel panic yet?

Never had one.

Alas, I continue to have missed recordings with EyeTV 2.5.1 and Leopard, as discussed in the EyeTV 2.5 thread (http://www.avsforum.com/avs-vb/showthread.php?t=913132). Today I missed three out of four scheduled shows because our CoreDuo Mini failed to wake up & start recording.

To reiterate, many of us noted the same wake-from-sleep unreliability during early Tiger releases, and also during some Panther point-updates. I believe this is more of an Apple issue than an EyeTV bug. Somehow Apple keeps forgetting that it's solved this problem before & the faulty sleep algorithm keeps creeping back into the code base... at least that's how it seems.

So we have three options for this wake-from-sleep failure:

Put up with frequent missed recordings... not good!
Revert to OS 10.4.9 where this was never an issue.
Leave our Mini in 'Never Sleep' mode until bug (hopefully) gets fixed again.
Can anybody think of a fourth option?

I believe this is more of an Apple issue than an EyeTV bug. Somehow Apple keeps forgetting that it's solved this problem before & the faulty sleep algorithm keeps creeping back into the code base... at least that's how it seems.

If your Mac is sleeping and you try to wake it by moving the mouse or using the keyboard, does it wake up? If not, then I understand your point, but, if so, then I don't.

Personally, I only let the monitor turn off. From what I have read, it is not clear that letting a harddrive sleep has any advantages.

No one else with a Leopard and 2.5.1 digital audio kernel panic yet?
Not yet. I haven't had one in months. I don't think I've had one since I added my HD-Home Run (although they probably stopped a while before). Got me.

It may have something to do with display resolution or HDMI?? I mostly seemed to be getting them when I was test driving a 1080P Samsung -- now that I'm back to my slightly lower rez 20" ACD all is well. Could be pure coincidence of course.

Coverflow browsing, not mentioned in that list, an EyeTV archive is pure joy :)
Do you mean in the Finder or EyeTV? I certainly haven't figured out a way to do it in EyeTV -- if there is one, please let us know how.

Do you mean in the Finder or EyeTV? I certainly haven't figured out a way to do it in EyeTV -- if there is one, please let us know how.

No, just the finder. I like it because the recordings at least don't look like nondescript icons, especially true for recordings prepared for wifi where you can quicklook them. I have a bunch of drives and constantly moving things around for EyeTV so it may be more close to my heart than many others here ;)

If your Mac is sleeping and you try to wake it by moving the mouse or using the keyboard, does it wake up? If not, then I understand your point, but, if so, then I don't. The point is this issue has cropped up several times before. The sleep problem went away and it stayed away when Apple released 10.4.4 (I think) through 10.4.9. Now it's back in Leopard. All other sleep/wake functionality appears to be fine under Leopard.

Having previously communicated with Nick at Elgato about this issue it seems to be a Mac OS X code base problem.

Again, EyeTV 2.4 NEVER had wake-from-sleep problems under OS 10.4.9; whereas EyeTV 2.4, EyeTV 2.5 and EyeTV 2.5.1 have frequent wake-from-sleep failures under Leopard.

Personally, I only let the monitor turn off. From what I have read, it is not clear that letting a harddrive sleep has any advantages. Spin-down sleep has the advantage of reducing heat dissipation inside our Mini. The Mini's fan doesn't have to blow dust into our Mini around the clock, causing wear and tear as moving parts grind against accumulating dust 24/7, 365 days a year.

I've had three more failed recordings since I wrote last night, though none of those were important losses. I'm still trying to get a sense of the wake-from-sleep failure frequency. So far our CoreDuo Mini + EyeTV 500 had over ten failures under Leopard and only two successful wakes-from-sleep.

Can anybody else confirm wake-from-sleep problems for EyeTV 2.5.1 and Leopard?

Hmm, 2.5 crashed constantly when trying to setup my channels, so I'm a bit hesitant to go to 2.5.1, but, after Friday Night Lights finish, I'll start to play.

Can anybody else confirm wake-from-sleep problems for EyeTV 2.5.1 and Leopard?

No, but then I never had any missed recordings or wake-from-sleep issues prior to this, Machound. That's with a CD Macbook, two 500s and firewire external storage. My two longstanding EyeTV issues have been 1) the random digital audio kernel panic and 2) not going to sleep after finishing recording. When I had a mini in the extender role, I didn't care, I left that thing running 24/7, but now that I have a Macbook there, I do care, I want it to spin down since it runs hot.

Anyway, my first Leopard install on the Macbook was an upgrade, I lived with it and 2.5.1 for the first week, and several nights after recording my Macbook still failed to sleep. Tried the typical El Gato troubleshooting tips, to no avail. Never missed a recording, though, it would wake from sleep just fine. The other day I decided to do a Leopard "erase & install" just for the hell of it, since I still had my solid 10.4.10 bootable SuperDuper backup just in case. So I wiped it clean, reinstalled Leopard, did the various Apple software updates, then instead of using Migration Assistant I only added back 2.5.1, re-entered the EyeTV2 activation, my TitanTV account info, repopulated the guide info and let preferences know where my old archive was.

It woke up to record last night's scheduled recordings, and then went to sleep smoothly afterward. One day in, and I'm happy so far. Today I'll put my iTunes library and preferences back (my music is on a 320GB external USB drive) and re-enter my sharing, keychain and network passwords. Then I'll gradually add back what I need, as Leopard versions become available. Bottom line, I bet I had a lot of residual junk on there that even though I thought I had been pretty good about uninstalling stuff over time, I probably missed much--you download and play with codecs, you try a different front end, change your login, try to improve Quicktime performance, you experiment with a Harmony remote, download various third party drivers, upgrade software and keep multiple versions around, you know, the normal home theater tinkering--and since I had an afternoon free, and really didn't use that Mac for anything other than home theater, I figured what the hell, give an erase and install a shot. It's working so far. Might not be your solution, but might be worth a try.

Good advice. Like your first Leopard install, I did an upgrade. Actually, it was an accident that I missed the Options button to do archive-and-install... but everything worked smoothly afterward so I didn't think twice about it. Perhaps it's time to heed your advice and start with a clean Leopard erase-and-install. I'm not sure when I'll have time to do that... life is pretty busy these days.

Thanks for giving hope that my wake-from-sleep problem isn't insoluble. Responding in kind, I have go-to-sleep issue on my PowerBook (which I no longer use for EyeTV recording) but not on our CoreDuo Mini. The PowerBook is extremely sensitive to the slightest mouse jiggle, such as when the kids run down the hallway. Unwanted PowerBook awakenings started at around OS 4.4.4, curiously at the time our CoreDuo Mini's wake-from-sleep issue was fixed. I saw similar PowerBook sleep misbehavior late in Panther development too (10.3.7-10.3.8.) Once awakened, my PowerBook stays on constantly, regardless of Energy Saver settings, until I put it manually to sleep. It's still on OS 10.4.9.

Suffice to say Mac Sleep isn't as reliable as we would like it to be. EyeTV is only part of the Sleep story.

What's EyeConnect, and why is it using 96% CPU while recording??? I was doing an OS X run through for somebody today, and fired up activity monitor, and to my shock, even while just recording one program EyeTV was gobbling up most of the CPU (1.66 Ghz CoreDuo). Ideas?

What's EyeConnect, and why is it using 96% CPU while recording??? I was doing an OS X run through for somebody today, and fired up activity monitor, and to my shock, even while just recording one program EyeTV was gobbling up most of the CPU (1.66 Ghz CoreDuo). Ideas?
And, I should add it is getting nearly 100% CPU at all times -- even when EyeTV is doing absolutely nothing. This has got to be buggy software. Can someone else with EyeTV fire up the Activity Monitor and confirm my observation? Thanks!

What's EyeConnect...

EyeConnect (http://www.elgato.com/index.php?file=products_eyeconnect) is a UPNP server. I tested it for a while ages ago and it never used more than a few percent of CPU running on the same hardware as you. It is installed under Library:StartupItems. Check the ElGato web site for uninstall instructions.

Craig

Ted, El Gato built Eyeconnect into 2.5, that's how they enable streaming EyeTV recordings to iPods and iPhones.

In EyeTV Preferences, look under the Wi-Fi access, is it on or off? Is there a chance you're converting all your recordings to H.264 versions by mistake? That would max out both cores. There's probably a FAQ on this at the El Gato site, I wouldn't be surprised if it automatically converts all your recordings if you have that preference turned on.

Found it:

http://faq.elgato.com/index.php/faq/more/597/

Ted, El Gato built Eyeconnect into 2.5, that's how they enable streaming EyeTV recordings to iPods and iPhones.

In EyeTV Preferences, look under the Wi-Fi access, is it on or off? Is there a chance you're converting all your recordings to H.264 versions by mistake? That would max out both cores. There's probably a FAQ on this at the El Gato site, I wouldn't be surprised if it automatically converts all your recordings if you have that preference turned on.
Right -- I figured out that's what it was and turned it off. However, there is definitely a bug there -- it was not in the process of converting anything -- it's only function should have been to wait for a connection and stream if necessary. And no, it wasn't the neighbors streaming either -- my WiFi is password protected :) Yet it was maxing out one of the CPU cores.

No, but then I never had any missed recordings or wake-from-sleep issues prior to this, Machound. That's with a CD Macbook, two 500s and firewire external storage..... It woke up to record last night's scheduled recordings, and then went to sleep smoothly afterward. One day in, and I'm happy so far.... since I had an afternoon free, and really didn't use that Mac for anything other than home theater, I figured what the hell, give an erase and install a shot. It's working so far. Might not be your solution, but might be worth a try. You nailed it! Archive and Install fixed my wake-from-sleep problem... at least, everything recorded fine yesterday and this morning. Yours was a first rate tip. I'm kicking myself for not trying Archive and Install before ranting about a nonexistent OS bug.

Score another point for the Mac HTPC community's shared wisdom! I can't overstate the power this forum brings in reasoning our way out of trouble spots.

Regards, MacHound

Here's a long-standing problem I've been having with EyeTV: we're watching a show that's currently being recorded (and we're like half an hour behind). Now, when the recording stops, the playback (which is somewhere in the middle of the show) stops and eyetv switches to the live view. Has anybody noticed this?

EDIT: this is happening with 2.5.1 and it's been happening before. It's independent of OS (happened in Tiger, happened yesterday on 10.5).

Here's a long-standing problem I've been having with EyeTV: we're watching a show that's currently being recorded (and we're like half an hour behind). Now, when the recording stops, the playback (which is somewhere in the middle of the show) stops and eyetv switches to the live view. Has anybody noticed this?

EDIT: this is happening with 2.5.1 and it's been happening before. It's independent of OS (happened in Tiger, happened yesterday on 10.5).

This has been a bug since the beginning. It has ruined more than one football game that I started watching after it had started. Nothing like watching the beginning of a game then suddenly you are live at the last seconds and see the final score

:(

Kevin

Had a zero bytes recording last night (wasn't a sleep problem because the Mini was awake doing iPhoto/FrontRow slideshows).

It turned out that EyeTV wasn't seeing the HD HomeRun for some reason (it was seeing the EyeTV 500, but the recording was presumably scheduled with the HDHR). Power cycling the HDHR didn't help. Stopping and restarting the EyeTV software fixed it. Anyone else experience this?

Here's a long-standing problem I've been having with EyeTV: we're watching a show that's currently being recorded (and we're like half an hour behind). Now, when the recording stops, the playback (which is somewhere in the middle of the show) stops and eyetv switches to the live view. Has anybody noticed this?

EDIT: this is happening with 2.5.1 and it's been happening before. It's independent of OS (happened in Tiger, happened yesterday on 10.5).I recently asked Elgato about this. Here is their response:
Thank you for contacting Elgato Systems.

We haven't forgotten about this - it wasn't ready for 2.5.

What we did was a small step forward - when the recording ends and EyeTV jumps to live, EyeTV marks that recording at the exact spot of the jump.

So, you can open the Editor to find that exact spot - it will have a marker at it. You can then watch from there.

Again, this is not a final solution, and we should have this resolved pretty soon. I apologize for the delay.

_

Ah, thanks for the info rackerby. Hopefully they can get this into a 2.5.2 release...

ditto that...it's very annoying when Eyetv takes you out of the recording to go to live...

ditto, rackerby. I actually submitted another support ticket with them on Saturday as I find this so very annoying. Guess it's the old story: they're spending their money to implement new features instead of doing bug-fixes... oh well....

Anyone else find it annoying that the 'exit menu' option does not appear on the full screen menu if you've watched anything. I just don't get it - when you first enter the menu you have the option to exit it (you leave the full screen menu with no Eyetv windows open), but once I watch something (live or recorded) and I leave it, then the option is gone. When I force it to leave full screen, I'm taken back to the show or channel I was watching.

Anyone know a way around it?

Anyone else find it annoying that the 'exit menu' option does not appear on the full screen menu if you've watched anything. I just don't get it - when you first enter the menu you have the option to exit it (you leave the full screen menu with no Eyetv windows open), but once I watch something (live or recorded) and I leave it, then the option is gone. When I force it to leave full screen, I'm taken back to the show or channel I was watching.

Anyone know a way around it?

I've been wondering about this too! I thought I'm too dumb to find the exit button. And it's so totally annoying to get taken back to the original show, which you just decided to leave (sic!). For me, the current (unacceptable situation) means to leave the machine in either the full screen menu, or in the last show (paused, for example). Apart from that the only two other options I'm aware of are either entering frontrow or putting the thing to sleep. What a f**ked up situation is this? The goddamn Apple Remote isn't helpful either - half the time I get taken back to the previous show because I hit menu once too often.... I want a regular remote so that there's not 5 menus to step through every time I wanna exit or watch a show.
Sorry for the rant.

ditto that...it's very annoying when Eyetv takes you out of the recording to go to live...

This bug is terrible, especially for sports, and it is good to hear that it is at least on Elgato's radar now. My work around is to set EyeTV to automatically record for some additional length of time after the program is scheduled to end. This gives you a little extra time to catch up to the live broadcast. If you are watching sports, it covers you if the game goes over the scheduled time, and also makes it less likely the final score will be on the live screen at the time of the jump to live TV.

You can set this up in the Preferences window. The default is 2 minutes or something, I have mine set to 20. If you have EyeTV scheduled to record something immediately following the first program, it will start the next recording and NOT record the extra time on the first program, so it isn't helpful if you are doing back-to-back recordings.

No one else with a Leopard and 2.5.1 digital audio kernel panic yet?

I have never had one until last night. :( I was watching a recorded show in EyeTV, skipping commercials with the Apple Remote and recording another show when it crashed on me. Upon reboot, it showed a kernel panic in the Digital Audio Module called from EyeTV. Bummer. Good thing I still had the HD-TiVo recording the same shows.

Any word from EyeTV on what causes this?

I have never had one until last night. ...Upon reboot, it showed a kernel panic in the Digital Audio Module called from EyeTV. ...Any word from EyeTV on what causes this?

No, no news from Elgato. I've submitted this almost a year ago.

Did you submit the crash report to apple? Please say yes! I'm afraid this is our only hope: we need to flood apple with these crash logs. (If it really is apple's fault).... I'm beginning to have doubts about this though....

No, no news from Elgato. I've submitted this almost a year ago.

Did you submit the crash report to apple? Please say yes! I'm afraid this is our only hope: we need to flood apple with these crash logs. (If it really is apple's fault).... I'm beginning to have doubts about this though....

I did indeed submit a report. I just heard that the SageTV 6.3.1 Beta supports the HDHomeRun. I gotta give it a try.

I have never had one until last night. I was watching a recorded show in EyeTV, skipping commercials with the Apple Remote and recording another show when it crashed on me.

That's how it usually happened to me--watching one high def recording with digital audio out, recording one or two others, and using the Apple remote to FF. However, since I did a clean install of Leopard and reinstalled EyeTV from scratch about 3 weeks ago, I've tempted fate by refusing to toggle off digital to system sound, and haven't had the kernel panic since.

(Macbook, 10.5.1, dual EyeTV500s, 2.5.1, archive on a firewire external--and like you, I also cover my ass by recording concurrently with a high def DVR, in my case the LG.)

That's how it usually happened to me--watching one high def recording with digital audio out, recording one or two others, and using the Apple remote to FF. However, since I did a clean install of Leopard and reinstalled EyeTV from scratch about 3 weeks ago, I've tempted fate by refusing to toggle off digital to system sound, and haven't had the kernel panic since.

(Macbook, 10.5.1, dual EyeTV500s, 2.5.1, archive on a firewire external--and like you, I also cover my ass by recording concurrently with a high def DVR, in my case the LG.)

Interesting. I too did a clean install of Leopard and EyeTV on my new Mac Mini (it came with Tiger installed. I formatted the disk and installed Leopard). I also set the system sound to digital out. I had the crash before I took the update to 10.5.1. My hardware is a 2GHz C2D Mac Mini, 1GB RAM, recording from a HDHomeRun to an firewire external drive. I'm going to try the SageTV Beta...

I too am waiting for the done-recording-go-live bug.

As far as EyeConnect goes: I tried using it for my UPnP device but while it was not using up a large number of CPU cycles, it had a severe memory leak. After having it running for about 24 hours, even when not serving media, it would be taking between 500 and 600 MB of real memory on my 1.5 GB iMac (original Core Duo).

Talking with the el gato support had me trashing my "iTunes Music Library.xml" file, but that only got it down to about 200-300 MB.

So make sure if you are using the web interface to EyeTV you keep an eye on the amount of RAM eyeConnect is using.

Is there any way to assign a specific tuner (namely my EyeTV 500 to a specific scheduled recording)? I keep getting bitten by the no signal/zero byte recording bug, which is strictly associated with my HD Home Run and thus would like to assign my higher priority recordings to the EyeTV 500.

BTW, the bug is new (in my setup). It was not happening before 2.5.1/Leopard.

Ted, I don't think so. (I believe) El Gato's official stance still is that multiple tuners are officially unsupported and experimental. Which means it's up to users to figure out the bugs when trying certain combinations of devices. Their new support/discussion forum is up and running now--perhaps head over there and poke around in the threads, you might turn up something:

http://forums.elgato.com/index.php

Ted, I don't think so. (I believe) El Gato's official stance still is that multiple tuners are officially unsupported and experimental. Which means it's up to users to figure out the bugs when trying certain combinations of devices. Their new support/discussion forum is up and running now--perhaps head over there and poke around in the threads, you might turn up something:

http://forums.elgato.com/index.php
Yes, that's correct -- while you were answering here, I was checking the Elgato forum, and there is no way to do it as yet, and multiple tuners are officially unsupported. I did post asking them for the pick your tuner feature... Of course fixing the underlying (zero byte/no signal) bug would be even better.

yeah, that's too funny, I just went there and saw your post--but that thread did offer a potential workaround, at least in the sense that it appears possible to keep the 500 on one Mac, turn off support for the Homerun on that Mac, and then run the Homerun on a remaining Mac--doesn't help those with just one Mac in the house, though.

As far as your bug, have you tried moving your archive around? Years ago when I had a very brief bout with the zero byte recording, it ended up being a particular external enclosure not waking up quickly enough.

As far as your bug, have you tried moving your archive around? Years ago when I had a very brief bout with the zero byte recording, it ended up being a particular external enclosure not waking up quickly enough.
That's an interesting suggestion, but I don't think it's the problem -- I had two recording scheduled simultaneously -- one worked no problem, the other was zero byte.

But more to the point, I witnessed this happening a couple of times, and even trying to change the channel on a Live TV window to the channel that wouldn't record didn't work -- it said "No Signal". The first time I fixed it by restarting the EyeTV software. The second time I fixed it by changing Live TV to *another* channel (which was currently recording on another tuner), and then back to the "No Signal" channel, which now worked.

So, to sum up, I see no evidence that the disk not waking up is the issue. Also, the archive is on the same disk that was working fine all along. Although, I did change the Firewire chain recently (farther away from the Mini in the chain than any of the EyeTV related devices), by adding a 1TB FW800 drive (using a FW400 to 800 cable, chained the other FW800 drive off of it & replaced the LaCie NEC burner with a OWC Pioneer burner).

That's an interesting suggestion, but I don't think it's the problem -- I had two recording scheduled simultaneously -- one worked no problem, the other was zero byte.

But more to the point, I witnessed this happening a couple of times, and even trying to change the channel on a Live TV window to the channel that wouldn't record didn't work -- it said "No Signal". The first time I fixed it by restarting the EyeTV software. The second time I fixed it by changing Live TV to *another* channel (which was currently recording on another tuner), and then back to the "No Signal" channel, which now worked.

So, to sum up, I see no evidence that the disk not waking up is the issue. Also, the archive is on the same disk that was working fine all along. Although, I did change the Firewire chain recently (farther away from the Mini in the chain than any of the EyeTV related devices), by adding a 1TB FW800 drive (using a FW400 to 800 cable, chained the other FW800 drive off of it & replaced the LaCie NEC burner with a OWC Pioneer burner).

Just got this recently too, but, had already downgraded to 2.4.1 since I've been having trouble with 2.5+ (edit bug, and instability scanning/assigning channel names). I have a pair of 500s and ended up disconnecting one after hooking up one at a time and found one of the tuners got no signal. So now I'm having fewer 0s recordings, but, my QAM signal seems to be having trouble too (stupid NBC affiliate). Need to also check by changing channels to see if that fixes some (Comcast just remapped the upper HD channels so was worried that thing got mucked up.)
I'm recording to a NAS, but, once my Seagates return I'll probably try an internal drive too.
Just wish eyeTV was more forgiving of signal problems, not just cutting off an stopping when it looses the signal.

erik, just to give you a data point, I've had no trouble with my two 500s in 2.5.1, but it took an erase and install of Leopard to do it AND I've always had really good QAM signal strength.

Ted, you could try a couple of things: first, rule out a hardware issue by trying a different HD Homerun, even if you have to buy one locally just to return it; second, is this problem happening only with two scheduled recordings starting at the same time--or does it happen sometimes just with an isolated single recording? If the former, try never starting two recordings simultaneously--even if it means recording a wasted hour. (If it were possible to pad each recording individually, have one start 2 minutes early and the other 3 minutes early, that would be nice, but it's not that sophisticated.)

and third, revisit the daisychain issue by stripping down, removing things and changing locations. Getting all these different firewire chipsets to play nice together can be tricky--I learned the hard way with two 500s--so get rid of your burner, get rid of anything with an 800 bus that you're dropping down to 400--some of those FW800 1TB externals like the MyBooks can be very problematic--and yank out the 500. I'd strip all the way down to one Mac, one firewire 400 external and the HD Homerun. Then try to repeat your zero byte recording bug.

Finally, run it for a while where you don't allow any drive to spin down, neither the Mac nor the firewire external, and try to repeat your bug. Doing these last two troubleshooting steps will help you better isolate whether it is indeed a bug and something within EyeTV's control.

I see no evidence that the disk not waking up is the issue. Also, the archive is on the same disk that was working fine all along. Although, I did change the Firewire chain recently (farther away from the Mini in the chain than any of the EyeTV related devices), by adding a 1TB FW800 drive (using a FW400 to 800 cable, chained the other FW800 drive off of it & replaced the LaCie NEC burner with a OWC Pioneer burner).

Absent a hardware issue in your Homerun, my money is on this being your problem, rather than any "bug" in EyeTV software. What are the exact model external drives--the FW800 one you were using and the new 1TB one? Are they ones you made up yourself or commercial products? Then we can find out exactly what's in them, i.e. Oxford, Initio, PL, etc.

And I thought I was bad with two 500s, a Pioneer superdrive external and a LaCie d2 320GB external in a single firewire daisychain off my Macbook. In my case, most of my main issues revolved around the 500s being bus-powered and needing to be right next to the mini (initially) or Macbook (now) in the chain, with powered enclosures after them. And it took me a while to get the sequence right and the bridges/chipsets that were compatible.

So you go:

Mini > EyeTV500 > 1 TB FW800 enclosure > older FW800 enclosure > Pioneer burner?

And you're telling the HD Homerun to record to the "old FW800" enclosure?

But more to the point, I witnessed this happening a couple of times, and even trying to change the channel on a Live TV window to the channel that wouldn't record didn't work -- it said "No Signal". The first time I fixed it by restarting the EyeTV software. The second time I fixed it by changing Live TV to *another* channel (which was currently recording on another tuner), and then back to the "No Signal" channel, which now worked.


Did you check that you have both antenna inputs of the HDhomerun connected and both receive a signal? (sorry if this is a dumb question)
I'm asking 'cause I'm having the same problem - I got about 10 0-byte recordings in the last 2 weeks, basically since I've been fumbling around with the antennas. I did rerun the setup to tell eyetv that now only one antenna is connected, but I get the impression it still sometimes wants to use the 2nd input (no simulaneous recordings). I have to reconnect the 2nd input and see if this helps.

Did you check that you have both antenna inputs of the HDhomerun connected and both receive a signal? (sorry if this is a dumb question)
I'm asking 'cause I'm having the same problem - I got about 10 0-byte recordings in the last 2 weeks, basically since I've been fumbling around with the antennas. I did rerun the setup to tell eyetv that now only one antenna is connected, but I get the impression it still sometimes wants to use the 2nd input (no simulaneous recordings). I have to reconnect the 2nd input and see if this helps.
Yes, I did check -- I have repeatedly opened three live windows simultaneously (using both HD-HR & the one EyeTV Tuner simultaneously). I have successfully recorded three show simultaneously any number of times. The problem is:
1) Recent
2) Intermittent
3) Involves the HD-HR only
4) Is correctable while in progress by either restarting the EyeTV software or manually changing live TV channels

If you have experienced kernel panics when using EyeTV (2.x or 3.x) with digital audio, Elgato would like to get your input. We are trying to find a way to reproduce this problem so we can get to the bottom of it.

See this thread on our forum: http://forums.elgato.com/viewtopic.php?f=86&t=1579

Mike Evangelist
Elgato