Jump to content


Photo

ZapStream channel change support?


  • Please log in to reply
3 replies to this topic

#1 CescoAiel

  • Senior Member
  • 213 posts

+2
Neutral

Posted 21 January 2009 - 16:33

I couldn't find anything on this, so I thought I'd post here...

Would it be possible to support zapping from the ZapStream http interface?
On the DBox you could open a stream like "http://<dbox-ip>:<streamport>/<vpid>,<apid>" to zap to the channel specified by the VPID and APID values and then start streaming that. (Not sure whether dreambox supports that in streamts as well, BTW...)

If Zapstream would enable me to open a stream in VLC with something like "http://10.0.0.1:31344/0x206,0x58" (or maybe "http://root:dreambox...344/0x206,0x58") to both zap to the channel I want and start streaming it immediately, it would be possible to bypass the WebGUI altogether if you want to go to a specific channel...

I might even be able to use my Dreamboxes over the internet using Orb (mycast.orb.com) that way... :)

Re: ZapStream channel change support? #2 Sjaaky

  • Senior Member
  • 7,443 posts

+41
Good

Posted 21 January 2009 - 16:41

Streamts allows it only very limited. It will not change the transponder. Whether it allows stream decoding by a cam seems to depend on the boxtype.

This is definitively on my todo list for zapstream. But it might take a while before I find some time to implement it.

Re: ZapStream channel change support? #3 CescoAiel

  • Senior Member
  • 213 posts

+2
Neutral

Posted 21 January 2009 - 17:13

Sounds cool!

I wish I had more available time, so I could look at the DB code myself, and figure out the simplest way to hack something like that together as a wrapper for ZapStream, but I am simply swamped!

Guess I'll have to exercise patience... ;)

(PS: Great app! Great image too!)

Re: ZapStream channel change support? #4 CescoAiel

  • Senior Member
  • 213 posts

+2
Neutral

Posted 22 January 2009 - 00:44

Ok, just thinking out loud here...

What basically needs to be done for a wrapper is:
Open a TCP port to listen to ("listening" port)
On a connect, zap to selected channel (that can even be done with a simple telnet/raw tcp port session to port 80 and the cgi-bin/zapto url)
Start ZapStream if it isn't running (Doesn't /cgi-bin/zapto do that?)
Relay all bits from zapstream to the "listening" port

The last step would be the hardest... ;)


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users