Digital Devices Octopus NET CT/2 Erfahrungen? (1 Viewer)

[KayDiefenthal]

think have found a other Problem with TunerDetector and Describe Message
i become there a Status 404 " Stream not found " what is clear there is no Setup Play before send

with other words so you cant get the Frontend Types and their Counts

the spec say this

If no session has been previously setup on the SAT>IP server (and thus no stream has been created), the
response to the DESCRIBE request will be error message 404 (stream not found).

 

[FreakyJ]

which branch do you testing?
If it is the mm working branch, yeah there is a SAT>IP Bug, but mm already fixed it locally

 

[KayDiefenthal]

no of your branches i have a litte test make here and there i m fallen over this Problem
then Comes me the idea look in tunerdetector from mp(mm working branch) how there it is used

and i saw the same as my code

 

[mm1352000]

If no session has been previously setup on the SAT>IP server (and thus no stream has been created), the
response to the DESCRIBE request will be error message 404 (stream not found).

Yep, this is true.

We prefer to use X_SATIPCAP.
If X_SATIPCAP is not available we try the DESCRIBE.
If DESCRIBE fails we assume 2 satellite tuners.

DESCRIBE can only work if some other client is using the server. That was my design/intention, because I do not see how we can send a SETUP request (tune request) if we don't know what type of tuner it is. It is like a chicken and egg problem (which comes first?)...

 

[KayDiefenthal]

ok then was it a known bug than i have nothing say

PS satellite Count 2 is one to much

Smart CX 05 Mirage or was it Smart CX 02 Mirage?has only one

 

[mm1352000]

ok then was it a known bug than i have nothing say

I'd call it a design limitation rather than a bug.
What would you do to solve it? Would you send a "fake" SETUP, or...???

PS satellite Count 2 is one to much

Unfortunately SAT>IP does not make X_SATIPCAP mandatory, so sometimes we simply have to guess. Most [good] hardware these days has two tuners, so I guessed "two satellite tuners". Sometimes we will be right; sometimes we will be wrong.

IMO better to guess a higher number than a low number.
If we guess the low number then the user might not get to use some of his/her tuners. Not good.
If we guess the high number then the user can simply disable the tuners that don't exist. Not perfect... but okay.

Smart CX 05 Mirage or was it Smart CX 02 Mirage?has only one

So this one doesn't support X_SATIPCAP?

 

[KayDiefenthal]

the smart cx 2 and 5 both have one tuner and useabel as sat>ip Transmitter
ok yes they have the X_SATIPCAP field in the DeviceDescription but that should not say that all other sat reciver with sat>ip function that have too

there prefer i the Low number to be save

 

[Helios61]

Hallo!
Ich stehe kurz vor einem Umstieg auf Kabel (UnityMedia). Wäre der DD Octopus NET C2T2/2 - Kabel>IP Netzwerktuner da eine Alternative). Wird Sat>IP bereits von MP unterstützt. Funktioniert das CI Interface mit UnityMedia. Sind also einige Fragen, hab mich halt mit DVB/C etc.. noch gar nicht weiter auseinandergesetzt. Könnt ihr bitte helfen? Erde wohl das 3play PLUS 120 von Unity Media bestellen!

Gruß
Helios

 

[KayDiefenthal]

satip ja in m2 mit tve 3.5
sonst nur der Umweg über m3u dann ginge es auch im mp1.9
das mit dem ci wird wenn nur über die mitgegebenen Parameter gehen aber das hat das manko das kein MDT geht und wird von dd wohl auch nicht mehr kommen

 

[KayDiefenthal]

mal eine andere frage zum SatIp Tuner detector
reagiert der auch auf Notify Messages ?
spiele da auf ssdp:alive bzw ssdp:byebye an
denn wenn ssdp:byebye empfangen wird sollten doch alle tuner von device x einen Kill bekommen um die Rtsp, Rtp und Rtcp Kommunikation zu stoppen
wäre ja nicht nur im RTCP der fall wenn der ein RTCPPacketByeBye eintrudelt