rofafor:
In order to see if vtuner/satip-client has the same problems could you shortly explain what problems the Inverto-based receivers have and what "quirks" you use to come around these problems?
Thanks,
Darkstar.
rofafor:
In order to see if vtuner/satip-client has the same problems could you shortly explain what problems the Inverto-based receivers have and what "quirks" you use to come around these problems?
Thanks,
Darkstar.
In order to see if vtuner/satip-client has the same problems could you shortly explain what problems the Inverto-based receivers have and what "quirks" you use to come around these problems?
Nothing related to vTuner I guess. My plugin is using libcurl for RTSP communication and therefore it detects communication errors when Inverto devices strips the leading zeros out of session ids: the leading zeroes are returned only in SETUP responses but cannot be used in any further commands.
Hi,
if the satip Plugin is activated, i can find issuses like this in the Log:
Jan 25 07:49:34 [vdr] [6360] ERROR: can't set filter (pid=65535, tid=02, mask=FF): Das Argument ist ungültig
Jan 25 07:49:34 [kernel] DVB (dvb_dmxdev_filter_start): could not set feed
Jan 25 07:49:34 [kernel] dvb_demux_feed_del: feed not in list (type=1 state=0 pid=ffff)
Can someone explain me, what this Messages mean?
Hi,
pid=65535 look's bit strange.
CU
9000h
- 65535 (0xFFFF) is not a valid PID.
- "tid=02" is the PMT.
This means, the Messages come from somewhat who have to do with PMT datas.
Hi,
we had this already
[2.1.6] VDR versucht ungültige PID zu setzen
CU
9000h
I couldn't find that error here. Maybe server specific?
Nicht mit satip. Den o.g. Fehler habe ich gefunden und behoben.
I am also intrested in how to fix it. Currently i "swatch" the logs and unattach, unload the device/driver and reload/attach it. Waorks but not the best way
Zitat von »3PO«
Nicht mit satip. Den o.g. Fehler habe ich gefunden und behoben.
3PO: Could you please explain how to fix the problem without satip?
9000H, 3PO, TheChief, bolzerrr, Scorp
With respect to to the author of vdr-plugin-satip this thread has to keep in english language. Please correct your posts accordingly.
Regards
fnu
First of all, please excuse me for going somewhat off-topic here, but I really got lost now and I'm sure you will be able to help me.
I have VDR backend fully working with a single DVB-S2 and single DVB-T2 tuner. I need only one channel at once from each devices.
I'm not sure if SATIP plugin is the one I'm looking for. I would like to create ip streams out of my DVB-T device's reception. Is it possible with this plugin or I need to look elsewhere (if yes, then where)? I would like to access the ip stream of the dvb-t device on my local LAN and Internet when I'm not at home.
There are 4 muxes on DVB-t, I would need them all, but only one mux at a time, so no need to have 4 tuners I guess.
Thanks!
What you want is a SAT>IP server?
Take a look at minisatip:
https://github.com/catalinii/minisatip
What you want is a SAT>IP server?
Take a look at minisatip:
https://github.com/catalinii/minisatip
Yes, this was not clear to me, that satip plugin is for RECEIVING ip streams or it can create IP stream out of dvb source.
Basically yes, I need a server, and minisatip look something like that, thank you!
However, it seams that I will be better with streamdev server, then I will have reencode possibility too for over the WAN with EXT. Just to get a good externremux.sh config.
One more question: if you have a dvb-s tuner, why would you need IP streams in your local lan, what is the benefit of it over direct DVB-S device?
gurabli
If you have dvb-s tuner you need no satip but you can use this with more clients in your network. (iPad, VDR, etc.) and you need no satellite connection for this clients.
Hello,
my log is getting quite crowded:
2016-01-22T21:54:02.641665+01:00 9b5fd150dd16 vdr: [142] SATIP1: bool cSatipRtsp::Play(const char*) (rtsp://192.168.177.3/stream=1?addpids=5500&delpids=800) [device 0]
2016-01-22T21:54:02.641905+01:00 9b5fd150dd16 vdr: [142] SATIP1: bool cSatipRtsp::ValidateLatestResponse(long int*) result=ok [device 0]
2016-01-22T21:54:03.083018+01:00 9b5fd150dd16 vdr: [142] SATIP1: bool cSatipRtsp::Play(const char*) (rtsp://192.168.177.3/stream=1?addpids=5510&delpids=5500) [device 0]
2016-01-22T21:54:03.083200+01:00 9b5fd150dd16 vdr: [142] SATIP1: bool cSatipRtsp::ValidateLatestResponse(long int*) result=ok [device 0]
2016-01-22T21:54:03.381372+01:00 9b5fd150dd16 vdr: [168] SATIP1: virtual bool cPluginSatip::Service(const char*, void*)
2016-01-22T21:54:03.514906+01:00 9b5fd150dd16 vdr: [142] SATIP1: bool cSatipRtsp::Play(const char*) (rtsp://192.168.177.3/stream=1?addpids=5520&delpids=5510) [device 0]
2016-01-22T21:54:03.515112+01:00 9b5fd150dd16 vdr: [142] SATIP1: bool cSatipRtsp::ValidateLatestResponse(long int*) result=ok [device 0]
2016-01-22T21:54:03.856136+01:00 9b5fd150dd16 vdr: [142] SATIP1: bool cSatipRtsp::Play(const char*) (rtsp://192.168.177.3/stream=1?addpids=5530&delpids=5520) [device 0]
2016-01-22T21:54:03.856322+01:00 9b5fd150dd16 vdr: [142] SATIP1: bool cSatipRtsp::ValidateLatestResponse(long int*) result=ok [device 0]
2016-01-22T21:54:04.307468+01:00 9b5fd150dd16 vdr: [142] SATIP1: bool cSatipRtsp::Play(const char*) (rtsp://192.168.177.3/stream=1?addpids=5540&delpids=5530) [device 0]
2016-01-22T21:54:04.307645+01:00 9b5fd150dd16 vdr: [142] SATIP1: bool cSatipRtsp::ValidateLatestResponse(long int*) result=ok [device 0]
2016-01-22T21:54:04.417280+01:00 9b5fd150dd16 vdr: [159] SATIP1: virtual bool cPluginSatip::Service(const char*, void*)
2016-01-22T21:54:04.638430+01:00 9b5fd150dd16 vdr: [142] SATIP1: bool cSatipRtsp::Play(const char*) (rtsp://192.168.177.3/stream=1?addpids=5550&delpids=5540) [device 0]
2016-01-22T21:54:04.638660+01:00 9b5fd150dd16 vdr: [142] SATIP1: bool cSatipRtsp::ValidateLatestResponse(long int*) result=ok [device 0]
Display More
I can watch channels without problems. The only problem is the log. What could be the reason for this "verbosity"?
Greetings,
Hendrik
You have started the plugin with the trace (-t) option other than zero.
Thanks!
Does anyone have some sample configs for sources.conf in the following scenarios:
The README says "SAT>IP satellite positions (aka. signal sources) shall be defined via sources.conf. If the source description begins with a number, it's used as SAT>IP signal source selection parameter." But does this also imply some dedicated binding of a specific tuner device to a signal source?
I have an OctopusNet with 4 DVB-S2 tuners, connected to a multiswitch which has access to Astra 1 and Eutelsat Hotbird. I have one vdr server running on a NAS which is supposed to handle all recordings/timers and two "front end" vdr's attached to TVs. Since I cannot exclude the situation where all devices are being used at the same time I assign the number of tuners to be used by vdr (two tuners for the server, one tuner each for the clients).
On the front ends I currently use the following sources.conf which seems to work fine (despite having only one tuner):
When using the same config on the server (with two tuners), I cannot do parallel recordings on the same satellite position anymore, it looks like the tuners are bound to their specific source.
Hallo
My situation and questions are somehow similar. A big difference is that with my configuration the satip does not work at all.
satip Readme:
"SAT>IP satellite positions (aka. signal sources) shall be defined via sources.conf."
I (low IQ & high age) concluded:
Source ==> source characteristics
assigned frontend(s)
signal sources ==> diseqc-switch position (e.g. Position B, Option B)
My example:
- VDR with mixed configuration
- DVB-C (3)
- satip-plugin + DVBS-4 octopus
Binding sources to the ipsat-DVB-S2 tuners I configured diseqc.conf:
4 5:
S19.2E 11700 V 9750 t v W15 [E0 10 38 F0] ...
.
.
S28.5E 11700 V 9750 t v W15 [E0 10 38 FC] ...
6:
S15.0W 11700 V 9750 t v W15 [E0 10 38 F1] ...
.
S9.0E 11700 V 9750 t v W15 [E0 10 38 F4] ...
Display More
Switching the corresponding diseqc's I configured sources.conf:
I fear (literally translating) I am on the wrong steamer...
Some help would be highly aprecieated.
SpaghettiCoder
Those entries define the source type of the signal, not the frontend.
That syntax means something like "
If somebody wants to tune to S19.2E, the satip plugin should send a 'src=1' to the SAT>IP server.
If somebody wants to tune to S9.0E, the satip plugin should send a 'src=2' to the SAT>IP server."
That number is eqiv. to a diseqc switch or similar. It doesnt relate to the question 'how much tuners are able to tune S19.2E'.
Don’t have an account yet? Register yourself now and be a part of our community!