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
http_api [2020/05/13 23:04]
neds
http_api [2020/09/20 16:16] (current)
neds
Line 62: Line 62:
 <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-channelsyou 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 23:04