Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
http_api [2020/05/13 21:25] – nedshttp_api [2022/09/23 04:25] (current) – neds
Line 5: Line 5:
 The list of available channels can be queried using the following URLs: The list of available channels can be queried using the following URLs:
  
-     http://<device ip>/lineup.json +     http://hdhomerun.local/lineup.json 
-     http://<device ip>/lineup.xml+     http://hdhomerun.local/lineup.xml 
 +     http://hdhomerun.local/lineup.m3u 
 +\\ 
 +//**Note:** "hdhomerun.local" can also be replaced by the deviceID.local or the IP address of the HDHomeRun.// 
 +\\
 \\ \\
- 
 The following information is returned for each program: The following information is returned for each program:
   * "GuideNumber" (virtual channel number). For ATSC the number will be "n.n" format. For all other systems the number will be "n" format.   * "GuideNumber" (virtual channel number). For ATSC the number will be "n.n" format. For all other systems the number will be "n" format.
Line 45: Line 48:
   * heavy: transcode to AVC with the same resolution, frame-rate, and interlacing as the original stream. For example 1080i60 → AVC 1080i60, 720p60 → AVC 720p60.   * heavy: transcode to AVC with the same resolution, frame-rate, and interlacing as the original stream. For example 1080i60 → AVC 1080i60, 720p60 → AVC 720p60.
   *  mobile: trancode to AVC progressive not exceeding 1280x720 30fps.   *  mobile: trancode to AVC progressive not exceeding 1280x720 30fps.
-  *  internet540: transcode to low bitrate AVC progressive not exceeding x540 30fps.+  *  internet540: transcode to low bitrate AVC progressive not exceeding 960x540 30fps.
   *  internet480: transcode to low bitrate AVC progressive not exceeding 848x480 30fps for 16:9 content, not exceeding 640x480 30fps for 4:3 content.   *  internet480: transcode to low bitrate AVC progressive not exceeding 848x480 30fps for 16:9 content, not exceeding 640x480 30fps for 4:3 content.
   *  internet360: transcode to low bitrate AVC progressive not exceeding 640x360 30fps for 16:9 content, not exceeding 480x360 30fps for 4:3 content.   *  internet360: transcode to low bitrate AVC progressive not exceeding 640x360 30fps for 16:9 content, not exceeding 480x360 30fps for 4:3 content.
Line 62: Line 65:
 <WRAP indent> <WRAP indent>
  
-URLs can also use the channel frequency instead of the virtual channel. Use "ch" instead of "v", and the RF channel number or frequency in Hz instead of the virtual channel number. PID filtering is not currently available. +URLs can also use the channel frequency instead of the virtual channel. Use "ch" instead of "v", and the RF channel number or frequency in Hz instead of the virtual channel number. 
-  * RF 14, which is 473MHz, would be http://192.168.0.100:5004/auto/ch473000000+  * Example channel 5 is RF 14, which is 473MHz and would be written as <code>http://192.168.0.100:5004/auto/ch473000000</code> 
 + 
 +  * If the channel has sub-channels, you can use the program number to specify the channel with a dash. For example, channel 5.3 might be -3 (program numbers are not always sequential or starting with 1), it would be written as, <code>http://192.168.0.100:5004/auto/ch473000000-3</code> 
 + 
 +</WRAP> 
 +====Specifying a tuner==== 
 +<WRAP indent> 
 + 
 +The "/auto/" portion of the URL will select the first available tuner. Replacing this with a tuner identifier will force use of a specific tuner. For example: 
 +  * tuner0 - the first tuner 
 +  * tuner1 - the second tuner 
 +  * tuner2 - the third tuner (if you have a 3 or 4 tuner model) 
 +  * tuner3 - the fourth tuner (if you have a 4 tuner model) 
 + 
 +The URL for using the second tuner might look like this: 
 + 
 +<code>http://192.168.0.100:5004/tuner1/v5.1</code>
  
 </WRAP> </WRAP>
  • Last modified: 2020/05/13 21:25