Problems with multistream channels #160
Labels
Comments
|
Hi @patacalas Yes the parameters isi and plsc are not parsed at the moment |
Barracuda09
added
enhancement
good first issue
|
Hi @patacalas Were are these parameters isi and plsc defined (or from which program is this rtsp uri come from) because they are not part of the SAT>IP specification. |
|
Hi @Barracuda09
These params are not from SAT>IP specifications, but I guess it should be improved to meet new standards from DVB-S2. I did a Google search and it seems that minisatip added multistream support a few years ago It would be great if SatPI could handle multistream transponders as there are more and more channels using this technology. |
|
Hi @patacalas Could you try this version if you have the time? Many thanks, |
|
Hi @Barracuda09
|
|
I've tested another transponder and it worked, and sometimes it returns the correct stream (in previous version of SatPI was impossible to tune in different streams on the same transponder).
Later, I've tried to tune stream 36 but it returned the wrong channels (channels from stream 35 again). I think the problem with transponder 12466V is PLS Mode Gold and PLS Code = 0, so the plsc param is not forwarded. Thanks for your prompt response. |
|
Hi @patacalas Could you give me a RTSP setup cmd from 16APSK request? |
|
Hi @Barracuda09 For example, when you tune 12111V DVB-S2 16APSK 31400 2/3 PLS GOLD 262140 StreamID 1 it requests So, I guess the problem should be also fixed in Enigma2 satip client plugin. I will Google search for satip plugin support. I did some additional tests and discovered some bugs that I hope could be easily fixed. Thanks for your support. |
|
Hi @patacalas I think I still need to look into the multistream... as this is most likely not correct. The 16apsk should be working but forgot something. I will have a look tonight. Thanks for your feedback and testing |
|
Hi @Barracuda09 I've forgotten something in last message. I think SatPI need to restart the tuner or something like that to apply the correct multistream tuning params. Thanks |
|
Hi @patacalas Could you please try this if you have the time: Many thanks! |
|
Hi @Barracuda09
I've also tested the issue while zapping between channels with different stream ID on the same transponder, and I still need to tune in to a different transponder to work. Thank you very much for your excellent work. |
|
So that means nothing of the tuning parameters (freq. pol ect) change only the stream ID? |
Were is this showing, in SatPI or what do you mean precise? Is this still not good in SatPI? |
Multistream transponder example. Same frequency, polarization, FEC,... but different stream ID (check red arrows) to tune in different channels. |
|
Yes I think I have an Idea what the problem is. |
Captured traffic from client receiver shows incorrect rtsp requests with mtype=qpsk param, but SatPI is working fine and tuning 16ASPK transponders even with incorrect modulation request. I think Enigma2 Sat>IP client should be updated to handle new modulation params. |
|
Hi @patacalas Could you please try this version: |
|
Hi @Barracuda09 The stream id param is working as expected but I think that there is a problem with delay while searching for new channels. The client receiver says "no channels found" and, a little bit later, services name and ids are displayed on SatPI log. Maybe my client is too laggy and limited by processor specs as SatPI is working under VPN encryption (ZeroTier). My receiver Vu+Solo SE (OpenVix image) shows services list on signal finder. Can I set a higher timeout in Enigma2 configuration when searching for channels? Probably the last SatPI version works fine for Sat>IP in local network. |
|
Again thanks for testing. Did scaning work in previous versions? I know scaning with my Vu+ Uno DVB-S2 is problematic, because the 'low' bitrate during scaning takes a long time. So the SAT>IP client time-out before receiving the data. |
Hi @Barracuda09. Channel search worked almost fine on previous versions. About 90% success in normal transponders and 40-50% on multistream transponders (sometimes I need to repeat scanning again and again to get successfully channel search). Tomorrow I will compare tuning times between SatPI versions and post results here. |
|
It could be because it is an debug version I added here. Edit: |
|
Hi @Barracuda09 The signal finder works as follows on my receiver.
A couple of seconds after entering the tuning parameters TSID and ONID are displayed and service list button appears. When tuning multistream transponders via SatPI it takes about 16s to appears (as expected because of the timings showed on logfile).
At least, that's what happens in all versions except the last one. Important timestamps from previous version Thu Jul 28 10:01:04.8044 2022 > I typed tuning params Important timestamps from last version Thu Jul 28 09:55:49.5685 2022 > I typed tuning params LOG from previous version--------------LOG from last version--------------Edit: |
|
Hi Does it make any difference to lower the DVR buffer size in SatPI (In frontend tab)? |
|
I've tried different values of DVR buffer, but changing that value doesn't make any difference. |
|
What if you tune to a freq without isi and plsc does that work faster? |
|
Yes, normal transponders work faster. |
|
Ok, so that makes me think there is no logic error in reading the data. I have to try to check this myself. But my setup is only Astra 19.2 and 23.5 at the moment. |
Barracuda09
added a commit
that referenced
this issue
Jul 30, 2022
|
Hi @patacalas I have committed the changes. This is a different version then the files attached here. |
|
Hi @Barracuda09 I was wondering if you can share the latest version compiled for ARM here. It's hard for me to compile the code on my Linux receiver. I would be happy to test the latest version with 9ºE multistream channels. Thanks in advance |
|
Hi @patacalas Sure, here is the version: Thanks for testing! |
Barracuda09
added
Fixed
Testers Wanted
Barracuda09
added a commit
that referenced
this issue
Jan 20, 2024
Barracuda09
added a commit
that referenced
this issue
Jan 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi! I'm trying to tune in Italian multistream channels from Eutelsat 9ºE via SatPI and I've just encountered some problems.
My SatPI server is installed on a Gigablue UHD Quad 4k (with PnP DVB-S2x multistream tuner) and my client is a Vu+ Solo SE.
As you can see in the following pictures, I can tune some channels.
The first issue is about modulation. Some transponders use 16APSK modulation, but SatPI seems to ignore it. I checked the log when tuning 16APSK channels and it shows QPSK. So, I can only tune 8PSK transponders like 12466V and 12341V.
LOG
rtsp://192.168.194.39:554/stream=109?fe=10&src=1&freq=12380&pol=v&msys=dvbs2&sr=31400&fec=34&ro=0.35&mtype=qpsk&plts=off&isi=25&plsc=262140
The second issue is about stream number param. SatPI seems to ignore stream number, it always returns the same channels (channels from first stream) even with different Stream ID. As you can see in lines above, the stream "isi" param seems to be parsed.
I would be grateful if you could fix these problems. Nowadays, there are more and more satellite TV channels using multistream technology.
Thanks in advance.
The text was updated successfully, but these errors were encountered: