OKidoki folks, I need some help to get this ball rolling...
I need your help to identify a few things. It came to my
attention that many STBs can handle transcoding easily(?).
Unfortunately, transcoding parameters are not the same for all boxes (different hardware capabilities) and, to make matters worse, are implementation dependent. Meaning it's up to the image developers to implement it the way they want...
Needless to say, that led to a lot of different implementations. And a nightmare from a developer point of view.
But fear not, there is an apparent solution in the horizon. According to slo617 in github,
Quote:You could get the proper URL for streaming by the following request:
http://VUBOX/web/ts.m3u?file=#####.ts&device=phone (transcoded)
http://VUBOX/web/ts.m3u?file=#####.ts&device=etc (original)
http://VUBOX/web/stream.m3u?ref=#####&device=phone (transcoded)
http://VUBOX/web/stream.m3u?ref=##### (original)
Using this method transcoded and original stream differ only in a single parameter.
This would also eliminate the need to configure the streaming port at all.
PS: I am also interested in transcoding. I want to stream over WLAN but have a lot of disturbing WLANs in my neighborhood. Most of the time my WLAN is too slow for streaming without transcoding.
Unfortunately I couldn't make it work with the image I use. Maybe I'm dumb... Since my time is limited and I'm not willing to test every image out there, I need your help.
What do I need from you? Easy!
Post your STB brand and model, image you use (OpenPLi, openATV, Vti, etc.) and (
redacted) URL you use for streaming and/or transcoding.
Please post the complete URL and just redact IP/username/password if applicable. The more information the better.
Thanks.
(2015-11-12, 16:10)h.udo Wrote: [ -> ]OKidoki folks, I need some help to get this ball rolling...
I need your help to identify a few things. It came to my attention that many STBs can handle transcoding easily(?).
Unfortunately, transcoding parameters are not the same for all boxes (different hardware capabilities) and, to make matters worse, are implementation dependent. Meaning it's up to the image developers to implement it the way they want...
Needless to say, that led to a lot of different implementations. And a nightmare from a developer point of view.
But fear not, there is an apparent solution in the horizon. According to slo617 in github,
Quote:You could get the proper URL for streaming by the following request:
http://VUBOX/web/ts.m3u?file=#####.ts&device=phone (transcoded)
http://VUBOX/web/ts.m3u?file=#####.ts&device=etc (original)
http://VUBOX/web/stream.m3u?ref=#####&device=phone (transcoded)
http://VUBOX/web/stream.m3u?ref=##### (original)
Using this method transcoded and original stream differ only in a single parameter.
This would also eliminate the need to configure the streaming port at all.
PS: I am also interested in transcoding. I want to stream over WLAN but have a lot of disturbing WLANs in my neighborhood. Most of the time my WLAN is too slow for streaming without transcoding.
Unfortunately I couldn't make it work with the image I use. Maybe I'm dumb... Since my time is limited and I'm not willing to test every image out there, I need your help.
What do I need from you? Easy!
Post your STB brand and model, image you use (OpenPLi, openATV, Vti, etc.) and (redacted) URL you use for streaming and/or transcoding.
Please post the complete URL and just redact IP/username/password if applicable. The more information the better.
Thanks.
Hi!
I dont really know how to get the info you need but i thing i got this correct :-)
I have a DM800HD Clon box (Sim 2.01).
I run this BlackHole image:
http://www.satsupreme.com/showthread.php...ost1169795
This is what i get when i copy the stream link in open webif:
http://192.168.xx.xx:25420/web/stream.m3...name=Sjuan
is this enough?
//Crall
Transcoding is not supported by all boxes, on vu plus duo2 original is on port 8001, transcoded versions on 8002/8003/8004/ etc... transcoding settings are set via web-GUI.
@
Crall, many thanks
@
kidomonster, I know transcoding is not supported by all STBs. I also know not all STBs capable of transcoding use the 8002/3/4/whatever port. And no, you don't always have to setup transcoding before using it. Many images use on demand URL parameters like:
Code:
http://vuduo2/transcoding?bitrate=5000000&automode=Off&framerate=50000&resolution=720p&encoder=1
Confusion comes from all the different implementations. Some developers decided their particular implementation is
the shit instead of agreeing/following a standard.
That is why I need help. It's impossible to test all images and hardware combinations for me. But the more information I get the better.
Maybe you should stick to one type of implementation and use (stb)model mapping, coding level then stays the same, how the stb is told what to do depends on a chosen mapping (command and messaging).
[vuplusduo2]
notranscodinguri=':8001/?'
transcodeuri='/transcoding?'
bitrate='bitrate='
etc.....
@ h.udo, Good to hear that you are working on the VU+ add-on.
I have some issues / future request for the current add-on such as radio is only received for favorites folder and Picons are not updated when a new version of the Picon is added to my STB.
Where can I official register these issues / future requests ?
(2015-11-13, 12:08)dr88dr88 Wrote: [ -> ]and Picons are not updated when a new version of the Picon is added to my STB.
This is most likely an issue with twistedweb (the webserver in enigma2), try a ssh init 4/init 3 (or reboot enigma2), or see the return code with "curl -i ipbox/picon/picon_name.png" ea. twistedweb not detecting file update.
Untested workaround: remove picon, reload kodi or request picon with your webbrowser/curl, if you get a 404 then place new picon.
(2015-11-12, 16:10)h.udo Wrote: [ -> ]I need your help to identify a few things. It came to my attention that many STBs can handle transcoding easily(?).
Unfortunately, transcoding parameters are not the same for all boxes (different hardware capabilities) and, to make matters worse, are implementation dependent. Meaning it's up to the image developers to implement it the way they want...
Needless to say, that led to a lot of different implementations. And a nightmare from a developer point of view.
(2015-11-13, 00:36)h.udo Wrote: [ -> ]Confusion comes from all the different implementations. Some developers decided their particular implementation is the shit instead of agreeing/following a standard.
That is why I need help. It's impossible to test all images and hardware combinations for me. But the more information I get the better.
Suggest that you bring this core fragmentation issue this to attention of the OE-Alliance lead developers, or at least with the OpenATV (openAAF) and OpenVix teams, to ask them to drive this core issue within the OE-Alliance as an favour for the Kodi team. As it sound, setting common standards and preventing core fragementation like this is one reason for the OE-Alliance existance.
One of the problem is that OE-Alliance have not existed that many years yet and before it the teams that now belong to it was all working with their own code base without any collaberation but now they all at least share the same code base for the core, and do so as open source on GitHub
https://github.com/oe-alliance
http://wiki.et-view-support.com/index.ph...Hauptseite
http://www.opena.tv/
http://www.world-of-satellite.com/
http://linux-tv.com/oe-alliance-openvix-...w-oe-core/Quote:What is OE-Alliance?
OpenATV and OpenVix had the idea to create a common build environment for the new OE-CORE and work together to optimize this environment.
Whats is OE-Core?
OE-CORE is a build environment by OpenEmbedded. DreamMultimedia calls their fork OE 2.0, and OpenPli calls their fork Pli 3.0.
All teams was using almost the identical build environment, so why not creating something together? The answer is the OE-Alliance.
Since we have a name now, we created a GIT repository quickly and the integration can be started.
The OE-Alliance is the base for each team, which is interested in building an OE-CORE image. We have discussed this already with several teams and they quickly agreed to work together.
We think that our new companionship should be visualized, so we created a logo. We call it the Seal.
The seal contains one golden star for each team which is part of the OE-Alliance. Currently representing the following teams: (25.05.2013)
openATV (OpenAAF), OpenViX, OpenMips, Egami Team, odin-support, xtrend-support, Technomate, HDF-Team, SIF-Team, MixOS, Octagon, openSPA , Axas , MiniCat-TV , openSWF, Team Red, HDFreaks, OpenDroid , openXTA beyonwiz.
Because the OE-Alliance is the build environment, each team will continue to provide his own team image. As you know each team maintains his own Enigma and his own skin, which makes the difference of each single team image.
For those with technical interest: You can track all changes and improvements in the OE-Alliance GIT from now on.
Each coder is welcome to join, each team, too.
@
kidomonster the problem is that Kodi stores the icon internally so when a update version comes from the STB Kodi will not update it new icons for new channels are coming in fine.
That is why I said use Curl, Kodi will probably get a 304 even if the source has changed so its not a Kodi issue but the webserver inside enigma2. Does enigma2 have 'touch'? that might work as well to get twistedweb to see the new file.
Currently I am unable to stream within Kodi. I get the notification "Importing guide from clients" but it's so slow and puts a big strain on the Satellite box which pretty much becomes unresponsive when kodi is doing this.
My stream address might actually be
http://192.168.*.***/web/stream.m3u?ref=1:0:19:1B1D:802:2:11A0000:0:0:0:&name=BBC%20One%20HD
That's what I got from openwebif via my laptop.
This is the stream address for channel 5
http://192.168.*.***/web/stream.m3u?ref=1:0:1:1E15:809:2:11A0000:0:0:0:&name=Channel%205
Again, debug log, please.
I can't see why stream isn't working without it.
Hi h.udo
it is a bit longer time ago, when I asked here for an add-on update with transcoding and timeshift support.
So I am really happy about this thread.
Can you please paste here a link to your github-project? it would be easier to follow the activities...
What can I add:
I have an mutant hd2400 on my own. The mutant uses the same transcoding-functionality as quadbox or xtrend.
The logic here is really simple:
A "normal" link to the TV-stream looks like this:
http://192.168.*.***:8001/1:0:19:1B1D:802:2:11A0000:0:0:0
If you will use transcoding, it has to look like this:
http://192.168.*.***:8001/1:0:19:1B1D:802:2:11A0000:0:0:0:?bitrate=5000000?width=720?height=576?framerate=25000?interlaced=0?aspectratio=0
The parameters are described by their names:
bitrate: (number in bit)
width / height (up to 1280 x 720) with actual devices.
framerate: up to 50000 (= 50 fps)
interlaced: 0/1 deinterlace/interlace
aspectratio: 0=auto, 1=4:3, 2=16:9
I tested this with simple iptv client. I made an full export of my receivers favourites-list (using webif) and append on all the channels the parameters above.
Works well with all channels.
If there is an interest on more details - please tell me here.
SaEt9000