nitrococuk you also better add opkg flag hold enigma2-plugin-extensions-jedimakerxtream in terminal.
:thumbup::thumbup:
Posts by nitrococuk
-
-
Display MoreDisplay More
I just figured out that one of my iptv providers doesnt support DVB(1) in live channels. I switched back to 5001. Why doesnt some providers support it ? What is the reason ?
Update on this:
Found the solution. Jedimaker is creating channels with the extension .m3u8 from the provider which doesn't work. The other one working has the extension of .ts formats.
I easily replaced all the .m3u8 in bouquets with the .ts by thanks to Notepad++ . And bang! they're working now by DVB(1).
Thats not a solution next time jedimaker updates bouquets it will it will put them back to .m3u8 you should look at the playlists.txt file in etc\enigma2\jedimaker folder to see what your provider urls end in you also said you had changed stream type in jedimaker to 5001.
3rd Update :
Found a permanent solution for this. I just went to " usr\lib\enigma2\python\Plugins\Extensions\JediMakerXtream " and edited the " globalfunctions.py " .
On the live bouquetstring code, you need to remove these yellow lines and save ;
bouquetString += '#SERVICE ' + str(jglob.live_type) + str(custom_sid) + str(protocol) + str(domain) + '%3a' + str(port) + '/' \
+ str(stream_type) + '/' + str(username) + '/' + str(password) + '/' + str(stream_id) + '.' + str(output) + ':' + str(name) + '\n'
bouquetString += '#DESCRIPTION ' + str(name) + '\n'
bx.categoryBouquetXml('live', bouquetTitle, bouquetString)
bx.bouquetsTvXml('live', bouquetTitle)
This will get rid of " /live/ " and the un-needed extensions like ".ts, .m3u8" from the stream urls . So, my enigma2 can play streams by DVB(1) now without a problem. So all the live urls in my bouquets look like this now ;
" #SERVICE 1:0:1:02ae:0002:0:0:0:0:0:http%3a//iptv.net%3a8080/username/password/2:HD beIN SPORTS 1 "
You can do the same for the VODs as well, but DVB(1) is not good for VODs. I suggest you to leave it 4097 or 5001 . Don't touch the codes.
For the questions, Jedimaker is doing her job great. No problem at all.
As you see above, it will preserve the url types next time it auto-updates the bouquets.
-
I just figured out that one of my iptv providers doesnt support DVB(1) in live channels. I switched back to 5001. Why doesnt some providers support it ? What is the reason ?
Update on this:
Found the solution. Jedimaker is creating channels with the extension like .ts, .m3u8 from the providers which some of them doesn't work.
I easily removed all the extensions (.m3u8,.ts) in bouquets by thanks to Notepad++ . I also removed " /live " quotes from the stream urls which I found out that it doesn't work for the streams from some providers. And bang! they're working now by DVB(1).
-
I just figured out that one of my iptv providers doesnt support DVB(1) in live channels. I switched back to 5001. Why doesnt some providers support it ? What is the reason ?
-
Display More
You are using service app now but in the correct way as i explain in some post above.
When you play a DVB 1 or 4097 it's the enigma2 player doing what it's intended for
As soon as you use a 5001 5002 stream service app kicks in and use the correct player needed for those streams
It's a common misstake that you should set the default player to gst or exteplayer3.
You only need that if you for some reason only use your enigma2 device for Streaming and all your streams are either servicetyp 5001 or 5002
Well, before that, when the serviceapp was enabled and you played "4097", I thought that serviceapp kicked in. And, when you opened DVB 1, I thought my enigma2 own playback system was dealing with it. My default player was always exteplayer3 in serviceapp settings. 4097 was ServiceMp3, 5001 was ServiceGst, I didn't even care about 5002.
Now, I've disabled the default player in serviceapp settings. It's all ok now.
I'm not technically good at this serviceapp thing. I might miss something, but it's working now and that is what I want.
-
nitrococuk , VOD and series normally 4097 you should actually try xstreamity for vod and series.
Would it be a bad idea to use 5001 for VODs ? I didn't see any difference when I opened them. They're playing well.
-
Hello friends,
Thank you for your help. I have disabled the serviceapp playback system and now I'm succesfully able to open live channels. :redface:
I had also enabled DVB(1) stream type for VODs, but I figured out that wouldn't work for those files so I switched back to 5001 for VODs. Now, they're working too :redface:
I don't know why I 've been using serviceapp so far. I thought the streams were playing better, but as I see now , that doesn't make any difference really.
thank you so much.
-
Hello,
I've a problem with this plugin. Please help if you can.
When I choose the DVB(1) for the stream type, I can create the bouquets without a problem, but as I try to open the channels in the bouquets, nothing plays. No stream is playing. I've found the reason for that is the channel reference number. For example, jedimaker is creating channels like this ;
"1:0:1:02ae:021c:0:0:0:0:0:http....."
This causes my Vu Zero+ not to play streams. When I change the reference numbers as below, I can open the channels ! ;
"1:0:1:0:0:0:0:0:0:0:http......"
It's a big problem to edit every single reference number. There's gotta be a way to do it easily.
Any suggestions ?
(P:S = When I choose 4097 or 5001 for the stream type, there will be no problem at all. However, I want to use DVB.)
