Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dvr:advanced [2019/06/28 22:21]
neds [Location of recordings]
dvr:advanced [2021/03/02 04:05] (current)
neds
Line 2: Line 2:
 <btn type="​success"​ size="​xs"​ icon="​fa fa-chevron-left">​[[:​DVR|Go back to all DVR topics]]</​btn>​ <btn type="​success"​ size="​xs"​ icon="​fa fa-chevron-left">​[[:​DVR|Go back to all DVR topics]]</​btn>​
  
-==== When using multiple DVR storage devices ====+===== When using multiple DVR storage devices ====
 +<WRAP indent>
  
-=== which "​record engine"​ will record ​===+==== Which "​record engine"​ will have priority ====
  
 Generally whichever record engine has the most free space will do the recording. Generally whichever record engine has the most free space will do the recording.
Line 12: Line 13:
 If a record engine reaches its concurrent stream limit then another record engine will take over additional concurrent streams. The default limit is 16 for Windows/​Mac/​Linux/​BSD. If a record engine reaches its concurrent stream limit then another record engine will take over additional concurrent streams. The default limit is 16 for Windows/​Mac/​Linux/​BSD.
  
-=== Additional notes ===+==== Additional notes ====
  
 The StorageID in the conf file must be specified (and must be unique). The record engine will automatically create and add a StorageID to the conf file if it has write access to the file. Normally, this should happen automatically. ​ The StorageID in the conf file must be specified (and must be unique). The record engine will automatically create and add a StorageID to the conf file if it has write access to the file. Normally, this should happen automatically. ​
Line 18: Line 19:
 To limit the number of concurrent recordings set RecordStreamsMax in the conf file (registry on Windows). Once this limit is reached another record engine will take over additional concurrent recordings. The default/max is 16. To limit the number of concurrent recordings set RecordStreamsMax in the conf file (registry on Windows). Once this limit is reached another record engine will take over additional concurrent recordings. The default/max is 16.
  
-==== When using multiple HDHomeRun tuners ==== +</​WRAP>​ 
-=== which box will be recorded from when the same channel exists on more than one HDHomeRun box === +===== When using multiple HDHomeRun tuners ====
-PLACEHOLDER TEXT+<WRAP indent>​ 
 + 
 +==== which box will be recorded from when the same channel exists on more than one HDHomeRun box ==== 
 +  * If there is a mix of CableCARD and OTA tuners, the OTA tuners will get a higher priority as they tend to have better picture quality than compressed cable signals. 
 +  * HD channels will be prioritized over SD channels. 
 + 
 +</​WRAP>​ 
 +====== Location of recordings ====== 
 +<WRAP indent>
  
-==== Location of recordings ​==== +==== Windows ​====
-=== Windows ​===+
 The default directory for recordings is: The default directory for recordings is:
 <​code>​%PUBLIC%\Recorded TV\HDHomeRun\</​code>​ <​code>​%PUBLIC%\Recorded TV\HDHomeRun\</​code>​
  
  
-To change this directory use regedit to modify the registry:\\+To change this directory ​use the HDHomeRun Setup utility and click on the "​DVR"​ tab. 
 + 
 +A second advanced method to change this setting (only for advanced users) is to use regedit to modify the registry:\\
 Key: HKEY_LOCAL_MACHINE\SOFTWARE\Silicondust\HDHomeRun\DVR\\ Key: HKEY_LOCAL_MACHINE\SOFTWARE\Silicondust\HDHomeRun\DVR\\
 Name: RecordPath\\ Name: RecordPath\\
Line 41: Line 51:
 </​WRAP>​ </​WRAP>​
  
-=== Mac ===+==== Mac ====
 The default directory for recordings is: The default directory for recordings is:
 <​code>/​Users/​HDHomeRun/</​code>​ <​code>/​Users/​HDHomeRun/</​code>​
Line 51: Line 61:
 After editing hdhomerun.conf you will need to reboot the Mac. After editing hdhomerun.conf you will need to reboot the Mac.
  
-=== Linux ===+==== Linux ====
 To specify a path for recordings create a file hdomerun.conf and add a line: To specify a path for recordings create a file hdomerun.conf and add a line:
 <​code>​RecordPath=<​full path to desired directory for recordings></​code>​ <​code>​RecordPath=<​full path to desired directory for recordings></​code>​
Line 57: Line 67:
 The conf file can be specified when running hdhomerun_record by adding --conf <conf filename>​ to the command line. If not specified the record engine will check the current directory and /​etc/​hdhomerun.conf. The conf file can be specified when running hdhomerun_record by adding --conf <conf filename>​ to the command line. If not specified the record engine will check the current directory and /​etc/​hdhomerun.conf.
  
-=== Additional search paths ===+==== Additional search paths ====
  
 Additional search paths can be added by setting RecordPath to: Additional search paths can be added by setting RecordPath to:
Line 65: Line 75:
  
 Additional search paths will be used to locate additional recordings. Additional search paths will be used to locate additional recordings.
 +
 +</​WRAP>​
 +===== hdhomerun.conf options =====
 +<WRAP indent>
 +
 +For MacOS and Android, a file called hdhomerun.conf can be created in the recording directory that contains the following definable parameters.
 +
 +On Linux-based systems (including most commercial NAS systems) the hdhomerun.conf file is required, often created automatically by using a given installation method for the DVR software.
 +
 +On Windows, this data is stored differently. Please see the [[:​dvr:​windows|Windows DVR page]] for information on how change these settings.
 +
 +<​code>​RecordPath=<​full path to desired directory for recordings></​code>​
 +<​code>​StorageID=</​code>​
 +<​code>​Port=</​code>​
 +<​code>​RecordStreamsMax=</​code>​
 +<​code>​PlaybackStreamsMax=</​code>​
 +<​code>​SendfileDisable=</​code>​
 +
 +The hdhomerun.conf file should be a plain text file (no rich text formatting),​ and only end in .conf (not .txt). Each setting is written on a new line in the file. If you have an existing hdhomerun.conf file and a setting isn't present, simply start a new line (press return/​enter) and paste the text in for that setting (such as "​RecordStreamsMax="​).
 +
 +\\
 +**RecordPath**\\
 +The full file path to the desired directory/​folder to be used for recordings. This can be used to specify an external drive as well. We strongly discourage using mounted network drive locations for performance reasons. ​
 +
 +On Windows, this can be set using the HDHomeRun Setup utility.
 +
 +\\
 +**StorageID**\\
 +The record engine will automatically create and add a StorageID to the conf file if it has write access to the conf file. Normally, this should happen automatically. HDHomeRun DVR software installation methods mentioned in the guides will all automatically generate a unique StorageID. This is mainly used for very specific situations such as testing, and most users can safely ignore this setting.
 +
 +\\
 +**Port**\\
 +The port used by the DVR software. ​
 +
 +\\
 +**RecordStreamsMax**\\
 +Sets the number of recording streams, or "​slots"/​channels,​ that the DVR software will allow to happen simultaneously. A setting of 0 will disable that DVR installation for recording, while still allowing previous recordings to be accessed by the HDHomeRun app.
 +
 +The default number of recording streams is 16. Most PCs and NAS devices wired to ethernet should be able to handle that much traffic, but this can be lowered or raised based on the needs of that specific DVR installation. ​
 +
 +\\
 +**PlaybackStreamsMax**\\
 +Sets the number of playback streams, or "​slots",​ that the DVR software will allow to happen simultaneously. Basically, this will set how many users can watch a previously made recording at the same time. This will also impact the live TV buffer, which can allow multiple users to watch a single channel off of a single tuner.
 +
 +The default number of playback streams is 16. Most PCs and NAS devices wired to ethernet should be able to handle that much traffic, but this can be lowered or raised based on the needs of that specific DVR installation. ​
 +
 +For example, if your network and DVR hardware can support more playback streams, you could increase the number to 20 and have 20 TVs/devices all watching the same TV channel, while only consuming a single tuner slot.
 +
 +\\
 +**SendfileDisable**\\
 +SendfileDisable=1 option for use with complex disk/​filesystem configurations that do not work reliably with "​sendfile"​.
 +
 +\\
 +**Live TV buffer note**
 +
 +The DVR software also works to extend the live TV pause/​rewind buffer. Live TV buffers will take at least one slot from PlaybackStreamsMax and RecordingStreamsMax. ​
 +
 +  - Example: if 2 people are watching two different TV channels, even if they are not recording those channels, 2 Playback slots and 2 Recording slots will be consumed. ​
 +  - Example: if 2 people are watching the same TV channel, even if they are not recording that channel, 2 Playback slots and 1 Recording slot will be consumed.
 +  - Example: if a person is watching a previously made recording, only 1 Playback slot will be consumed. No Record slots will be consumed.
 +
 +</​WRAP>​
  
 {{tag>​dvr}} {{tag>​dvr}}
  • Last modified: 2019/06/28 22:21