Earl Noe

PS. The tuner I'm using is a HDHomeRun CONNECT 104F1993 Version 20170930 Model: HDHR4-2US , Firmware: 20170930. The device shown in EyeTV prefs is Geniatech HDHomeRun HDHR-US with the same firmware version.The Silicon Dust website is prompting to install a new firmware version. If that were to break EyeTV compatibility, I have no idea how to revert. Since it's working fine w/ EyeTV, I'm going to pass on upgrading the firmware.

My email address has changed, and I can't figure out how to change this setting in this forum, so I am not receiving notices about new posts or replies.

This probably won't be news to some of you, but I thought I'd post my experience anyway. Overnight recently, my venerable HDHR went dark. I checked the brick with a voltmeter, about the extent of my electronics expertise, and it seemed to be putting out 5 volts, so I assumed the tuner itself had gone blooey. Since it had served me so well, I ordered what appeared to be a new, identical HDHR-US. When it came today, out of curiosity, I plugged the new brick that came with the new unit into my old tuner, and it lit up. Idiot. There was something wrong with the brick, and before ordering a new unit I should have gone out to the box o' bricks in my shed and seen if I had something with the right voltage/plug and tried that. Also, out of curiosity, I visited myhdhomerun.com as suggested by the literature that came with the new unit. It said "no hd homerun connected" with the old unit hooked up. Nowhere on the Silicon Dust website was any mention whatsoever of EyeTV as compatible software. There were big pitches for the free app and the subscription guide and DVR services. Really curious now, just to be cautious, I booted up into a clone of my boot drive with the new unit connected. It works just fine, exactly like the old HDHR-US. The only discernible difference is that now myhdhomerun.com can see my homerun. Probably it is just new firmware. Presumably, I could now subscribe to the guide and DVR services, but I'm perfectly happy for now with EyeTV and xmltv guides. FYI

I've never had a system panic for any reason, so I can't comment. The HD Homerun and EyeTV software I got some years ago for around $200 are still working fine with the xmltv guide solution described in this forum. If for some reason I find I can't live without a 64-bit OS, and the present setup is still working as good as it is now, I'll probably just dedicate my present mid-2010 mini to EyeTV.

Thanks for the suggestions. All three subchannels of my local PBS broadcast on two different frequencies. XMLTV had a listing for all of the subchannels, and though they were not named identically, a close inspection of the names allowed me to match them up. I did mis-assign the listing for one subchannel, but fixed that by deleting it from the Channels list, rescanning >Update scan, then assigning the right matchup. The duplicate recording bug SEEMS to have been fixed by deleting one of the two frequencies in Channels for the offending Channel. Odd thing is, the duplicate recording bug has never happened with either of the other two subchannels, though they each have two frequencies. It was almost certainly caused by something I did, though I don't know what.

I have never had a recording failure with EyeTV that wasn't user error. I wish my other applications, like browsers, were as reliable.

Thanks. That is the case for this channel. I had hoped that unchecking one of the frequencies would fix the problem, but it doesn't seem to have. Unchecking one causes the corresponding Guide listing to go away, unchecking the other has no effect. I'm going to try deleting one channel from the channels list.

Thanks. I never directly edit what is in the Schedules list and use the Guide. EyeTV is running all the time. A hard reboot of the HDHR had no effect. Most annoying.

Sure. I place the archive on the boot drive because it is always mounted and accessible whenever the computer is booted up. All the copies of EyeTV on bootable partitions can share the same archive, which is always available whether any of the other volumes are mounted or not. You can put it anywhere, but the boot drive is the one that's always conveniently mounted.

The method provided by the helpful fellow members of this forum, especially Wisconsin Eric, for automating listings from xmltv.com has been working like a charm, with one bug I can't figure out: On one channel, a local PBS station, scheduled programs are being recorded by both tuners of the HDHR, creating two identical recordings. I thought it might have to do with creating Smart Guides, but deleting them has had no effect. Has anyone ever encountered this problem? Any suggestions? Just as I was typing this, I thought a hard reset of the tuner might work.

I find double-clicking on an .eyetv file wherever it is stored, regardless of folder or drive name, will cause it to open in the EyeTV that is running. The preview image will stay in the Recordings pane until deleted. The preview image can not return to the associated recording when attempting to play if the volume has been unmounted, and sometimes it will not always find the recording if the volume has been unmounted and remounted, but double-clicking the file itself will cause it to resume playing where it was when stopped.

That's great. Sometimes the names of the channels in your xmltv lineup don't quite match your Channels list, but it's possible to suss out what the matching listing in your lineup is the correct match. The search box in the lineup window can help narrow it down, sometimes by call letters. If you make a mistake in assigning a listing, you can highlight that channel in the Channels list, delete it, and then do Auto Tune > Advanced > Update Scan and the channel(s) you deleted should reappear in the Channels list. You will have another chance to assign a listing when you change the dropdown for them.

I should have mentioned mine is 7520.

Here is the start of the file channels.plist: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>TV source type</key> <integer>1</integer> <key>TV system</key> <integer>3</integer> <key>TV system variant</key> <integer>3</integer> <key>channel list</key> <array> It goes on at some length, like this: <key>EPG Lineup</key> <string>20434</string> <key>EPG Provider</key> <integer>7</integer> <key>EPG Provider Channel ID</key> <integer>590265122</integer> <key>active</key> <true/> <key>artificial name</key> <false/> <key>channel name</key> <string>CW (KWGN) Denver, CO</string> <key>channel number</key> <integer>34</integer> <key>logical channel number</key> <integer>2</integer> <key>minor logical channel number</key> <integer>1</integer> <key>service</key> <data> AAAAAKAEAzGYCQxoGAAAAwAAAAA= </data> and so on.