Yoshiofthewire

Updated to 20200905beta1

Updated to 20200819beta1

Honestly, I haven't run an unraid server in over a year. And updated the server to 20200225

Updated Record to 20200121beta1 Firmware update needed

OK, Trying to update again. I'm push out 20190815beta1, let me know if it breaks things.

OK, I just reverted the change. Let me know if that seems to fix things, then we can look at the update in a week or two

OK, thinking about rolling it back, should I just change the config, or roll the whole thing?

Pushed 20190516beta2. If the new muti-tuner breaks something, please message me and I will revert the change. Info about this update: https://forum.silicondust.com/forum/viewtopic.php?f=119&t=71529 FYI: For the adventuress of you if you aren't also running a Plex Server, here are some tricks. 2 lines have been added to the hdhomerun.conf file. StorageID=UnraidDocker1 RecordStreamsMax=16 The StorageID in the conf file must be specified (and must be unique). I specified this as I was unsure if the server would be able to write to the config file. To limit the number of concurrent recordings set RecordStreamsMax in the conf file. Once this limit is reached another record engine will take over additional concurrent recordings. The default/max is 16. If RecordStreamsMax is set to 0 the server will be used for playback but will not make new recordings.

There are actually 2 different issues here. One is a networking issue with the container. The container is supposed to be in Host Networking Mode. I forget the setting to fix this, but then I haven't used Unraid in some time, so the only changes I have made to the container over the past 2 years has been to update the Record engine by replacing the executable in the Github. Linux Subsystem for Windows for the Win. Side note, the Linux x64 version used by Unraid, also runs on Windows 10 64 bit with Ubuntu installed. .... The Log file error just means that the container isn't seeing that the Record engine is already running, and when it tries to start another one it fails and complains about it. In all honestly, it has always done this, and while I totally admit it is bad form, it shouldn't impact normal operation.

Just pushed 20190417

Updated to [20180817] Warning: Windows users may have issues with the firmware update. See https://forum.silicondust.com/forum/viewtopic.php?f=92&t=69228 for the fix.

I'm not sure why that is happening. I haven't run unraid in a while. Updated docker to 20180802beta1 You need to upgrade the firmware on your device.

20171105beta1 doesn't appear to have an update to the Linux binary or tuner firmware.

Updated to 20171013beta1

Updated to 20170616_beta3

Updated to 20170512beta1 WARNING: As I no longer have an unRaid box I had to extract the binary using Bash on Ubuntu on Windows.

FYI: The Linux Server has not yet been updated.

FYI: Linux didn't get 20161008beta1 (as of 10/8)

Once again you need upgrade the firmware on your tuner to use this release. If the docker won't install (like it wounldn't for me after moving to 6.2) try deleting ALL your docker containers AND IMAGES then reinstalling them.

I haven't seen that. FYI, with this new update I changed the way the program starts. #itisdumb Please keep an eye on it and let me know if the server stops running and I will revert the change.

If you update to the latest build you should now see the Record Webpage linked from the webui link.

Insert complaint that Docker is not pushing the updates down. I can see the new builds on docker, but my NAS is not installing the update. A forced update is not installing it either. If this happens for you please delete and re-create the container. This fixed it for me. ------------------------------------ The docker has been updated to 20160621atest1 so Please update your tuner firmware. To update the firmware install the Windows or Mac install and when asked to install the server, select don't. Then you will get a prompt to configure the tuner after Setup is complete. Then re-setup the tuner, which will update the firmware and you may have to re-scan channels. Then check for Docker updates. You can check your Firmware at http://my.hdhomerun.com/ There is also a link to this on the docker page under . The HDhomerun.conf is stored inside the Container at root and points to /hdhomerun inside the VM. RecordPath=/hdhomerun Port=65002 The docker config then has a mapping to a share in your array. /mnt/user0/hdhomerun

NOTE: The last two updates have also included a firmware upgrade for the tuner. Not installing this update may cause unexpected issues. The $30/year is for guide data. As Schedules Direct charges $25/year for this same data, I don't find this unreasonable. Schedules Direct is the US data source used by the vast majority of Open Source projects.

Did you update the firmware on your HDHomerun Tuner?

FYI:There is an updated Firmware for the HDHomeRun tuners. You should install the Windows or Mac DVR build to get this update.