43 replies to this topic

[pop_eye]

Anyone knows if the sat-ip ATV code working with vtuner DM v1 boxes ? (dvb-api 5.4)

After looking at the code I see there are at least two versions for vtuner interface.

 

Is this only for dvb-api 5.0 ?

#if HAVE_NO_MSG16
            DEBUG(MSG_MAIN,"MSG_SET_PROPERTY old Mode\n");
            setProperty(&msg);
#else
            DEBUG(MSG_MAIN,"MSG_SET_FRONTEND skip..\n");
#endif

Edited by pop_eye, 25 September 2015 - 17:57.

[Erik Slagter]

I can't get it to work anyway. The tuner is tuned, the pid filters is set, streaming is started but no data is sent over RTP. I already hated RTP before, but now I do even more. It's all made far too complex. The concept is interesting and good: using a well-defined standard and also filter each pid from the demux indepedently so pids can be shared between clients. This makes is all very very complex and now it just doesn't work, probably because drivers of enigma stb'es are minimally implemented, usually only the operations enigma uses are implemented. I am convinced that if you make something simple, a manually set up 1:1 mapping from client virtual tuner to server tuner, it can work very well.

[pop_eye]

Yes, it is working with the original vtuner server implementation (1:1 as you mentioned)

I am sure that it is working with vuplus since they have added sat-ip support in the drivers.

[malakudi]

@Erik: the protocol also supports http. Unfortunately the satipclient software only support RTSP/RTP.

[neku]

Can someone provide this as ipk or put it on the feed / add it to the buildserver? 

Edited by neku, 26 September 2015 - 23:29.

[Erik Slagter]

@Erik: the protocol also supports http. Unfortunately the satipclient software only support RTSP/RTP.

Yes I know. Indeed.

[Erik Slagter]

Yes, it is working with the original vtuner server implementation (1:1 as you mentioned)

I am sure that it is working with vuplus since they have added sat-ip support in the drivers.

I have it more or less working now, but the sound is all choppy, mostly on SD channels. If you make a recording and play that, it's all fine. I have experimented with smaller and larger rtp packets, with the size of the writes to the vtuner device (smaller and larger), but all to no avail. I am now beginning to suspect it's a bug in the VU+ vtuner driver. I am not sure how USB tuners are supposed to work in that perspective.

[malakudi]

@Erik: The issue with sound on VU+ is known and has been reported to VU+. A new driver is expected to fix the issue. On Edision OS Mini (similar hardware to VU+ Zero) it works OK.

Which server are you using? Minisatip?

 

edit: I tried today with an old DM800SE. It doesn't work at all.

In dmesg I get messages like:

vtuner56 set mode to 6 unsupported

vtuner56 set mode to 5 unsupported

etc

 

So for now it works with problems on VU+ and it works correctly on OS Mini. Very limited support for enigma2 boxes.

Edited by malakudi, 27 September 2015 - 16:51.

[pop_eye]

I also tried with an old DM800SE latest dvb modules and satipclient.

23:37:32.284 dvb/frontend.cpp:1680 setFrontend setting frontend 1
FE_SET_PROPERTY failed: Invalid argument
23:37:32.287 dvb/frontend.cpp:1329 tuneLoopInt [SEC] sleep 500ms
23:37:32.554 dvb/frontend.cpp:727 feEvent (1)fe event: status 10, inversion off, m_tuning 1
23:37:32.554 dvb/dvb.cpp:1569 frontendStateChanged OURSTATE: ok
23:37:36.557 dvb/scan.cpp:360 PATready got pat
23:38:36.559 dvb/scan.cpp:333 SDTready got sdt -1

@Malakudi - Something is missing from satipclient vtuner code. FE_SET_PROPERTY failed: Invalid argument

It might be that since delsys does not exist in dvb-api 5.4 (DMM modules) something else is needed to get property cache working.

 

http://www.dream-mul...4524#post144524

struct dtv_property p[10];
                        struct dtv_properties cmdseq;
                        cmdseq.props = p;
                        p[0].cmd = DTV_CLEAR;
                        p[1].cmd = DTV_DELIVERY_SYSTEM, p[1].u.data = system;
                        p[2].cmd = DTV_FREQUENCY,       p[2].u.data = parm.frequency;
                        p[3].cmd = DTV_MODULATION,      p[3].u.data = modulation;
                        p[4].cmd = DTV_SYMBOL_RATE,     p[4].u.data = parm.u.qpsk.symbol_rate;
                        p[5].cmd = DTV_INNER_FEC,       p[5].u.data = parm.u.qpsk.fec_inner;
                        p[6].cmd = DTV_INVERSION,       p[6].u.data = parm.inversion;
                        if (system == SYS_DVBS2)
                        {
                                p[7].cmd = DTV_ROLLOFF,         p[7].u.data = rolloff;
                                p[8].cmd = DTV_PILOT,           p[8].u.data = pilot;
                                p[9].cmd = DTV_TUNE;
                                cmdseq.num = 10;
                        }
                        else
                        {
                                p[7].cmd = DTV_TUNE;
                                cmdseq.num = 8;
                        }
                        if (ioctl(m_fd, FE_SET_PROPERTY, &cmdseq) < 0)

Edited by pop_eye, 27 September 2015 - 22:56.

[Erik Slagter]

I doubt very much whether this is going to work on DMM, due to their ancient DVBapi.

 

I do have it working on mut@nt though.

Edited by Erik Slagter, 30 September 2015 - 13:43.

[pop_eye]

Please find attached satipclient bb for dreamboxes including enigma2 satip plugin.

Has been tested succesfully (no tearing) with server: minisatip/0.5.50

 

Enjoy

Attached Files

•  satipclient-dreambox-linux3.2.tar.gz   1.77KB   27 downloads
•  enigma2-plugin-systemplugins-satipclient_2.0_mips32el.ipk   15.32KB   23 downloads

Edited by pop_eye, 24 July 2016 - 05:05.

[pop_eye]

Compilled package

Attached Files

•  satipclient_1.0+git5+aea7de9-r0_dm800se.ipk   29.96KB   37 downloads

[littlesat]

For openpli?

[pop_eye]

Yes, bb with source included.

Edited by pop_eye, 24 July 2016 - 13:12.

[Lost in Space]

you call a pyo file the source .... OK ....

[WanWizard]

So, no, so source included. A pyo is clearly no source, unless you're good with a binary editor and the python token parser...

[pop_eye]

I am not a Openpli facilitator.

Someone needs to do some leg work to get this into the build system.

If you don't want it, you can srap it.

 

I am not calling anything. Who wants to understand - it will

Edited by pop_eye, 25 July 2016 - 21:59.

[littlesat]

We're opensource minded and support that...

[Rob van der Does]

I think every participator in this thread is aware that the sources are available @ https://github.com/o...ce/satip-client

At least I can't see any 'closed files' in there.

[littlesat]

And there I cannot see any phython stuff... But when the ipk works it can be used, until we change something unexpectically...