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/08/29 00:44]
neds
dvr:advanced [2021/03/02 04:05] (current)
neds
Line 88: Line 88:
 <​code>​RecordPath=<​full path to desired directory for recordings></​code>​ <​code>​RecordPath=<​full path to desired directory for recordings></​code>​
 <​code>​StorageID=</​code>​ <​code>​StorageID=</​code>​
 +<​code>​Port=</​code>​
 <​code>​RecordStreamsMax=</​code>​ <​code>​RecordStreamsMax=</​code>​
 <​code>​PlaybackStreamsMax=</​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="​). 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="​).
Line 101: Line 103:
 \\ \\
 **StorageID**\\ **StorageID**\\
-This is an entirely optional setting, as all of the DVR software installation methods will automatically generate a unique StorageID. This is mainly used for very specific situations such as testing, and most users can safely ignore this setting.+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
  
 \\ \\
Line 116: Line 122:
  
 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. 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"​.
  
 \\ \\
  • Last modified: 2019/08/29 00:44