Search the Community

I have Emby Server running on a Windows 10 computer with an HDHomeRun Prime tuner on my LAN. Invariably, when I use my phone to watch live tv (even briefly) with a WIFI connection to the LAN, the HDHomeRun tuner doesn't release when I'm finished. Android apps have always had a nasty habit of hanging around when they are no longer being used actively. On my phone, I've tried closing the app using "close all" but the tuner is not released. I've also tried doing a "force stop" of the app and that doesn't release the tuner either. I've only found two ways to release the tuner and neither are an acceptable solution: 1) turn the HDHomeRun tuner off and back on, or 2) stop and restart the Emby Server in Windows. This is problematic if I happen to be recording live tv on another tuner. Is there an easy way in Emby Server to identify and "kill" the android client connection to release the tuner?

I've been sick for several days, so this problem started sometime within the past week. Today I attempted to play a live TV channel that had been working flawlessly on my TCL Roku TV, using Blue Neon Night. When I select a live TV channel for playback and clicked "Play" the streen immediately returns to the Emby Blue Neon Night icon on the Roku Home Screen. I checked the HDHomeRun Prime and it works fine when playing on the Emby Server. Next, I tried a Roku 3 with Emby BNN and it also failed to play live TV. I noticed that I was still running server version 3.2.5 so I installed 3.2.7 and restarted. (Same problems.) I then switched to the Emby Preview and discovered that it had been replaced by a new Beta version. When I installed the Beta version, I was pleasantly surprised with the new layout, Guide, etc. However, many of the Live TV channels would timeout when I tried to play them. Some would load and play, but others would not. Other features, such as playback of recorded TV continue to work correctly on the New Emby, the Public beta Emby, and Emby BNN. (BNN appears to be completely broken as far as live TV is concerned.) The new Emby channel appears to have great potential, but on the TCL Roku TV, it seems to have some of the same bugs that were fixed a few months ago on Emby BNN. Are others having similar bad experiences that started in the past week or so? (I can turn on debug and collect log files if necessary, but I wanted to see if this is a known problem first.)

I just bought a TCL Roku TV (uses built-in Roku interface as the primary control for the TV). I've been using the Emby Streaming Channel (app) on several Roku 2 and 3 devices with no problems to watch live TV (using the Emby server with Silicon Dust HDHomeRun Prime cablecard network tuners). For the most part, Roku looks and works exactly the same on the TCL TV. However, some (but not all) of the Live TV channels are not streaming. They start to load and appear to be buffering, but they never start playing. Hitting the Roku back button displays a message in the Emby app saying that the media player closed prematurely. Several channels work normally, but others do not. These same channels ALL work on a Roku 2 or 3 device. Is there a setting that needs to be changed in the Emby server to eliminate this problem?

Currently I have an HDHR Prime on my network consuming 256 Clear QAM from my linear TV provider. In this configuration I don't have an M-Card installed, so I don't have the benefit of it mapping the RF Channels to Virtual Channels. Instead it creates its own RF to Virtual Channel map and assigns channel numbers in the 5000s. I've mapped these HDHR virtual 5000 number channels to the virtual channel number my linear TV provider assigns them in their network. My question is if Emby TV, or through the use of a M3U/XLTV file, will I eventually be able to create these virtual assignments myself to make up for the lack of an M-Card? If so, is there a tentative timeline? Thank you!

I can not play certain channels for the life of me that have drm on using the hdhomerun through the dlna tuner in emby. I have a cable tuning adapter and everything in terms of authorization is positive. This is what i get in my hdhomerun log: HDHomeRun PRIME System Log 19700101-00:00:00 System: reset reason = power on19700101-00:00:01 CableCARD: M-CARD inserted19700101-00:00:01 CableCARD: invalid session 0xDEAD (cchost_session:267)19700101-00:00:03 System: network link 1000f19700101-00:00:04 System: ip address obtained: 198.202.196.177 / 255.255.255.019700101-00:00:06 CableCARD: Cisco card (0103:0001)19700101-00:00:10 CableCARD: authentication status: authentication in progress19700101-00:00:10 CableCARD: authentication status: authentication success, validation success19700101-00:00:17 CableCARD: USB device 05A6:0008 connected19700101-00:00:17 CableCARD: Tuning Resolver connected19700101-00:00:18 CableCARD: Tuning Resolver downstream status: success19700101-00:00:18 CableCARD: Tuning Resolver upstream status: success19700101-00:00:18 CableCARD: Tuning Resolver authentication status: in progress19700101-00:00:18 CableCARD: Tuning Resolver operational status: initializing19700101-00:00:19 CableCARD: Tuning Resolver authentication status: success19700101-00:00:19 CableCARD: Tuning Resolver operational status: ready19700101-00:01:11 Tuner: tuner0 streaming rtp to 198.202.196.195:5526219700101-00:01:11 Tuner: tuner0 tuning 1063 MTVHD (none:375MHz-1)19700101-00:01:12 CableCARD: tuner0 1063 MTVHD (none:375MHz-1) access = subscribed19700101-00:01:17 Tuner: tuner0 streaming rtp to 198.202.196.195:5358819700101-00:01:17 Tuner: tuner0 tuning 1062 BRVHD (none:255MHz-4)19700101-00:01:18 CableCARD: tuner0 1062 BRVHD (none:255MHz-4) access = subscribed19700101-00:01:47 Tuner: tuner0 streaming rtp to 198.202.196.195:5011219700101-00:01:47 Tuner: tuner0 tuning 1064 VH1HD (none:357MHz-4)19700101-00:01:47 CableCARD: tuner0 1064 VH1HD (none:357MHz-4) access = subscribed19700101-00:02:01 Tuner: tuner0 streaming rtp to 198.202.196.195:6534719700101-00:02:01 Tuner: tuner0 tuning 1062 BRVHD (none:255MHz-4)19700101-00:02:02 CableCARD: tuner0 1062 BRVHD (none:255MHz-4) access = subscribed20160227-22:24:47 CableCARD: time changed from Thu Jan 01 00:03:28 1970 to Sat Feb 27 22:24:47 201620160227-22:50:46 Tuner: tuner2 streaming rtp to 198.202.196.195:500120160227-22:50:46 Tuner: tuner2 tuning 1062 BRVHD (none:255MHz-4)20160227-22:50:47 CableCARD: tuner2 1062 BRVHD (none:255MHz-4) access = subscribed20160227-22:53:08 Tuner: tuner2 streaming rtp to 198.202.196.195:500120160227-22:53:08 Tuner: tuner2 tuning 1062 BRVHD (none:255MHz-4)20160227-22:53:09 CableCARD: tuner2 1062 BRVHD (none:255MHz-4) access = subscribed No picture. Every version of emby has wanted to identify and own the prime tuner and if I try to use the serverwmc plugin w/windows media center they compete for the prime. I can't turn of the dlna hdhomerun (its picked up automatically) and it seems I can't play these channels outside of media center even in hdhomeruns viewer software. Any ideas on how to turn off the dlna hdhomerun or get the drm channels with it?

I have been using the built-in Emby DVR feature with mixed results and am currently evaluating the HDHomerun DVR as a backup/alternative method for recording live TV. (To digress briefly, here's my reason for exploring an alternative — Built-in Emby DVR usually works with my HDHomerun Prime, but when I'm recording more than one program at a time, or if I'm just browsing Emby media content, the recordings frequently fail or hang in the active recording state.) The early access HDHomerun DVR software currently uses an add-in for Kodi as its recording user interface, and I really don't like the way it works. However, the recording feature is rock solid and I haven't had a failed recording yet. Here's the problem: I want to store the HDHomerun DVR recorded files in a folder that will allow them to be played back by an Emby client (specifically Roku). If I create a sub-folder in the Recorded TV section, Emby apparently does not support playback of the file because it is not in the expected .ts container format, and it does not attempt to download metadata for the file. (The HDHomerun DVR format is plain old MPEG.) I got around this problem by storing the MPEG-formatted files in the Emby Movies section in a sub-folder called _HDHomerun DVR. This allows me to play the recordings on Roku, However, because Emby thinks the recorded MPEG files are movies, it either attaches the wrong metadata or no metadata at all. It uses movie databases rather that tv databases to search for information. So, to summarize this long post — Is there a way to get Emby to automatically apply TV metadata to an mpeg file?

I have a HDHomerun Prime 3-tuner device that had been running flawlessly with Emby until a couple of days ago. I run Emby Server at startup (not as a Windows service) and I subscribe to Schedules Direct. I have the Emby TV plugin and have successfully recorded live TV in the past. I have three Roku 3 devices and they were all able to play live TV (Charter Cable is my cablecard provider). I could also watch Live TV by opening the Emby Server in a Chrome browser on any PC or Tablet device in my house. There were no streaming /stuttering issues. Suddenly, within the past two days, I can no longer watch live TV at all (not even at the Emby Server host PC, not on Roku, or anywhere else on my network). I can open the SiliconDust HDHomeRun View app and it plays live TV flawlessly from any device on my network. I've rebooted the host computer, restarted the HDHomeRun Prime Tuner, tried running Emby as a service, etc., but nothing seems to work. I'm running Windows 10 64-bit on a very capable Dell XPS 8-core PC and everything related to Live TV from the Emby server just stopped. Any ideas on what could have caused everything to stop working? I have attached a recent log server-63576952823.txt. I'm too new at this game to interpret what the logs mean.