2014-01-01, 11:03 AM
I've been testing out a few things with the Swagger "Try it out" feature for playing things using VLC and nDroid.
Using /public/VLCService/StreamByScheduleOID is straight-forward enough as I only have to pass http://<server-ip>:7648 to whatever Android media player app the user chooses. Limited testing but good results so far.
When streaming live tv with /public/VLCService?Channel=X however the value of "StreamLocation" in the JSON response shows an absolute path local to my npvr server ("D:\\nPVR\\LiveTV\\x-newa-live.192.168.0.10.ts" for example).
I've got it working for brief tests by using the Videos view in nDroid and navigating to the Live TV folder and selecting the "x-newa-live.192.168.0.10.ts" buffer file.
The tests are "brief" because of the need to regularly send the "heartbeat" to keep the whole thing alive (and I can't do that yet). So basically, what were the thoughts behind designing it this way, i.e., what sort of client was it intended for? Just curious really in case I'm missing something about the way it works.
Cheers,
Brian
Using /public/VLCService/StreamByScheduleOID is straight-forward enough as I only have to pass http://<server-ip>:7648 to whatever Android media player app the user chooses. Limited testing but good results so far.
When streaming live tv with /public/VLCService?Channel=X however the value of "StreamLocation" in the JSON response shows an absolute path local to my npvr server ("D:\\nPVR\\LiveTV\\x-newa-live.192.168.0.10.ts" for example).
I've got it working for brief tests by using the Videos view in nDroid and navigating to the Live TV folder and selecting the "x-newa-live.192.168.0.10.ts" buffer file.
The tests are "brief" because of the need to regularly send the "heartbeat" to keep the whole thing alive (and I can't do that yet). So basically, what were the thoughts behind designing it this way, i.e., what sort of client was it intended for? Just curious really in case I'm missing something about the way it works.
Cheers,
Brian