Yoshiofthewire

Members
  • Posts

    72
  • Joined

  • Last visited

Posts posted by Yoshiofthewire

  1. 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.

  2. On 5/10/2019 at 6:33 PM, CoZ said:

    For whatever reason, my DVR service is not showing up any longer.  This WAS working fine.... now it just stopped working.  I just checked and my record engine has an IP of 172.17.0.3 but my Tuner is reporting 192.168.86.31 (which is on my actual LAN - the 172 is not)

    Not sure how to fix this?

     

    I installed the miniDLNA docker to try and "work around" whatever issue is happening.  I set up my docker from the screenshot that @Switchblade provided, pointing it to my HDHomeRun directory and share on my Array.  Hit apply, no errors, but after that... I've got nothing.

     

    Checking the log files of the docker shows these entries over and over (not sure if this info helps?)

     

    
    HDHomeRun RECORD already running
    2019-05-10 18:47:44,365 INFO exited: hdhomerun_dvr (exit status 0; not expected)
    2019-05-10 18:47:45,367 INFO gave up: hdhomerun_dvr entered FATAL state, too many start retries too quickly

     

     

    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.

    • Upvote 1
  3. 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

     

     

  4. 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.