[vdr-plugin-satip] this and that

That i didn´t read the README

Changed it to :

S19.2E  1
S19.2E  2
S19.2E  3
S19.2E  4

today i tried to get the satip plugin working on a headless server, same vdr version, pluginversion, sources.conf, channels.conf, but i don´t get a connection.
dlns discover doen´t work so i added the server via plugin option.
there is just few log:

Dec 31 09:56:43 vdr: [31945] no DVB device found
Dec 31 09:56:43 vdr: [31945] initializing plugin: satip (1.0.0): SAT>IP Devices
Dec 31 09:56:43 vdr: [31945] SATIP: Adding server '192.168.0.66|DVBS2-4|SatIP'
Dec 31 09:56:43 vdr: [31945] SATIP: Creating device CardIndex=0 DeviceNumber=0 [device 0]
Dec 31 09:56:43 vdr: [31945] SATIP: Creating device CardIndex=1 DeviceNumber=1 [device 1]
Dec 31 09:56:43 vdr: [31945] starting plugin: satip
Dec 31 09:56:43 vdr: [31945] SATIP: Using CURL 7.38.0 rtsp

svdrpsend plug satip INFO

Zitat

220 SVDRP VideoDiskRecorder 2.1.6; Wed Dec 31 10:00:26 2014; UTF-8
900-SAT>IP device: 0
900-CardIndex: 0
900-Stream: connection failed
900-Signal: lock=0 strength=-1 quality=-1
900-Stream bitrate: 0 kB/s
900-Buffer bitrate: 0 kB/s
900-Buffer usage: 0/1024 kB (0.0%)
900-Channel: Das Erste HD;ARD:418000:C0M256:C:6900:6010=27:6020=deu@3,6021=mis@3;6022=deu@106:6030;6031=deu:0:11100:41985:1051:0
900-Active pids:
900 Active section filters:
221 closing connection

Alles anzeigen

clear to see that connection failed seems to be the problem but i don´t know how to fix. tried restart of all devices as i found that in de different thread but no change.
i can ping the satip server from the vdr. i also tried to check port 1900 seemes to work, too...

difference in log to my other vdr is the message "SATIP#0 tuner thread started (pid=4628, tid=4708, prio=high)" is missing

any ideas how to proceed?

Can you try the 0.3.3 version for your project? For me, the 0.3.3 works very well, unfortunately missing the option to include two Boxes for Satip. Somehow 1.0.0 is more buggy.

Otherwise take this: https://code.google.com/p/satip/

This works perfectly!

Regards

tried that version, same thing. Semmes that the communication is interrupet by _something_ i already disabled firewall rules but no changes.. i´d like to send a curl request from the command line but i don´t know a really comparable request. maybe i have a port conflict, but i don´t know wich port i need to search for.

Have you ever tried this kind?

See my posting above! This works if you dont need more then 4 devices.

You can debug RTSP communication by issuing a command:

svdrpsend plug satip trac 0x12

..disabling the tracing:

svdrpsend plug satip trac 0

The used bitmasks are described in log.h and the tracing mode can also be set straight from the startup via a command-line option (-t).

fnu

Yes sir Octopus you repeat yourself. Watch to TVHeadend. The Boxes works there and the Firmware is the same.

Regards

Zitat von zwick der agent

For me, the 0.3.3 works very well, unfortunately missing the option to include two Boxes for Satip. Somehow 1.0.0 is more buggy.

The 0.3.3 wasn't a fully spec compliant and I've corrected those in the 1.0.0. Now, you'd need to provide the RTSP communication of both 0.3.3 and 1.0.0, so we can spot the differencies.

rofafor

I'll try it. Where should I post the result? Here in the Thread or via PN?

Regards

Zitat von rofafor

You can debug RTSP communication by issuing a command:

Code

svdrpsend plug satip trac 0x12

..disabling the tracing:

Code

svdrpsend plug satip trac 0

The used bitmasks are described in log.h and the tracing mode can also be set straight from the startup via a command-line option (-t).

Tried this but still nothing happens. I i wouldn´t see the output in the log and the menu i would think it is not loading..

Zitat

Tried this but still nothing happens.

Yes here the same Problem.

Regards

Zitat von zwick der agent

fnu

Yes sir Octopus you repeat yourself. Watch to TVHeadend. The Boxes works there and the Firmware is the same.

Regards

+1

... and Android-, and Windows-Clients working also with the GSSBOX.

Maybe this Project should renamed from vdr-plugin-satip to vdr-plugin-octopusnet?

Zitat von 3PO

Maybe this Project should renamed from vdr-plugin-satip to vdr-plugin-octopusnet?

Thanks, will do! I didn't dare to do this by myself, but now there's a public demand.

Tvheadend has plenty of device specific configuration parameters that I want to avoid.

Rofa

R.I.P, SAT>IP with VDR! [Blockierte Grafik: http://imageshack.com/a/img850/5417/cyss.gif]

Heee keep calm please. This is a good project and your work is great, i ´ll try to understand the problem. I´d like to help if I knew how.

Regards

fnu

Zitat

with the crappy cheap devices

Really? Where do you help? Is this your help? Thanks!

what happend here? we had a constructive discussion can we return to topic?