266 replies to this topic

[theparasol]

What I make of it its work in progress and a way to let some more advanced users participate in testing it and give feedback.

[sundtek]

@Sundtek
I suggest it is ugly to patch E2 to support a special hardware. Principally this is not done!!! Unless there is an extreme good reason? Or is this just an expiremtal way?

It adds a plugin interface to E2, for someone else doing that it's also easier to implement a network stack or other things through it. Basically there's nothing specific to our devices in that patch it can be extended in another way for other features.

Although some things I noticed which are pretty good for us we can easily profile the tuner performance that way and improve bottlenecks from the tuners (eg. reading signalstrength depending on the devices might take some time or not).

[robbedoeske]

Zijn hier al vorderingen?

[littlesat]

Sundtek made a solution that needs a change to E2. As far I understand we cannot accept this change (which is currently a change for just one Trend of a DVB-USB stick why?????).

When Sundtek just follows the "rules" like other DVB USB sticks do, this is not required!!!

[sundtek]

Our driver is operating system and kernel version independent and that is why things work a little bit different, basically that is what customers want.


The modification is very small and does not add any extra protocol change on API level, it uses all the commands as they are which are sent by enigma2.

Another thing which I noticed in those source files there are several exceptions for other tuners in it regarding the signal strength and other statistics. The argument that there are no special things in there is foul.

The modification is around 150 lines of code not interfering with other devices.

On the other side Dream already updated their Interface to allow faster zapping.

We have around 10 different tuners (even the existing devices have several flavors, eg different tuners, different demodulators and so on) on the market which are using those mechanisms so it's not about a single tuner only, we have several new tuners coming up which are also using those drivers.

I would appreciate if you could cooperate instead of knocking down improvements for many people out there, we try to support everyone as far as possible.
I think it would be a benefit for everyone out there to cooperate a little bit more instead of ignorance.

Edited by sundtek, 6 May 2012 - 14:58.

[sundtek]

Aside of that one even the Linux Media Maintainer advised to do things in Userspace rather than passing things through the kernel when it's not needed.

We also support virtualizing our tuners via network

This is a mail from the video 4 linux maintainer
----

If you want to do the networking code at userspace, why do you need a kernel
driver after all? The proper solution is to write an userspace library for that,
and either enclose such library inside the applications, or use LD_PRELOAD to
bind the library to handle the open/close/ioctl glibc calls. libv4l does that.
As it proofed to be a good library, now almost all V4L applications are using
it.
----

the problem with the regular old USB drivers is that they register some entries in sysfs which we don't want to "fake".
Another point is that other images do not include the interface which was added to e2 in openpli, so we also need to support
the old way of this interface.

Even from license level this is no argument as we do that on system level and the interface is according to the GPL license "System Library Exemption".
The interface only picks up the system commands and forwards it via sockets to the driver Server.

The driver server runs on Linux, Mac, FreeBSD and upcoming also Windows, making it possible to stream from all those systems to the settopbox.

Please rethink your points, we would really like to cooperate and we can even provide samples for your developers to test those things.

[sundtek]

Another example would be HDHomerun tuners which might benefit of this interface. It's not specific to our tuners only.

[fjorger]

To speed up zapping with our tuners:

1. OpenPLi-2.1-beta-dm800se-20120420.zip
2. our driver (as documented in our support forum), configure it.
3. log in with telnet and run:

cd /
wget http://sundtek.de/support/openpli-2.1-beta-dm800se-20120420.tar.gz
tar xvzf openpli-2.1-beta-dm800se-20120420.tar.gz

reboot
Zapping should be faster now with all our devices, it's still in experimental stage and will get some more updates next week.

The file on our server contains precompiled e2 and some custom driver.
The e2 patch is available http://sundtek.de/su.../e2-plugin.diff

@sundtek

Hello

Yes, with the attached file the "Fail to tune" has gone. Now channels appear.
Unfortunately a side-effect has happened.

When the box (DM800SE) is put to standby, the blue light says on forever , so the tuner continues to be in use.
Is there a way to overcome this problem?

Thanks in advance,
Regards,

fjorger.

[fjorger]

Upon experimenting a bit further (and after updating the driver again),

I noticed that if (in standby) I unplug the Sundtek stick for one second and plug it back again everything stays ok, and the Blue light goes off a few seconds after setting the receiver to standby.
Unfortunatly upon rebooting enigma, the problem comes back again .
But now I know (If I unplug it and plug it again) everthing stays okay (until the next reboot)

Regards,

fjorger.

[sundtek]

Upon experimenting a bit further (and after updating the driver again),

I noticed that if (in standby) I unplug the Sundtek stick for one second and plug it back again everything stays ok, and the Blue light goes off a few seconds after setting the receiver to standby.
Unfortunatly upon rebooting enigma, the problem comes back again .
But now I know (If I unplug it and plug it again) everthing stays okay (until the next reboot)

Regards,

fjorger.

After digging further into it, we have an update upcoming which fixes all that and also takes the advantage of fast zapping without modifying OpenPLI or any other Image.
We'll just do some more testing and update it within the next 0-2 days. Best thing is that it works with other images.
Standby functionality did not work due some backward compatibility issues with the old interface, that's also solved now (we support the old mechanism and another new one now).

Edited by sundtek, 11 May 2012 - 10:50.

[satdvb]

En in het nederlands? Of zit ik nu in het verkeerde forum te kijken

[Roodkapke]

Over 2 dagen een mogelijke fix van/voor sundtek.

[satdvb]

Aha

Dus ze hebben openPli overal voor niets af lopen zeiken dat ze hun patch niet over wouden nemen begrijp ik, gevalletje foutje bedankt

[littlesat]

After digging further into it, we have an update upcoming which fixes all that and also takes the advantage of fast zapping without modifying OpenPLI or any other Image.
We'll just do some more testing and update it within the next 0-2 days. Best thing is that it works with other images.
Standby functionality did not work due some backward compatibility issues with the old interface, that's also solved now (we support the old mechanism and another new one now).

Very good news... and thanks!!!

[vertaling]
Na verder uitdiepen komt er binnenkort een update met oplossingen zodat je ook de voordelen heb met snel zappen zonder OpenPli of elk ander image te modificeren. We moeten nog iets meer testen en verwachten een upgrade binnen 0 tot 2 dagen.
Het grote voordeel is dat het ook met alle oude images werkt.
De standby functionaliteit werkte niet door de backwards compatibiliteit met de oude interface. Dat wordt nu ook opgelost (het oude mechanisme en het nieuwe mechanisme gaan beide werken >ik denk dat ze hiermee de DVBAPI bedoelen<
[/vertaling]

[kooleracer]

Weet iemand hoe ik de driver moet downloaden, want via de site krijg ik een 403 forbidden error. Ik kan de driver nergens anders vinden? En via de sundtek controlcenter krijg ik dezelfde error.

Alvast, bedankt.

Edited by kooleracer, 11 May 2012 - 15:38.

[sundtek]

Weet iemand hoe ik de driver moet downloaden, want via de site krijg ik een 403 forbidden error. Ik kan de driver nergens anders vinden? En via de sundtek controlcenter krijg ik dezelfde error.

Alvast, bedankt.

We just updated the driver! That is the reason for 403. Please try again.

[Pimsat]

Ik ben benieuwd naar de ervaringen met deze laatste drivers van Sundtek met OpenPLi. Met VTI 4.1 werken deze niet op mijn Vu duo en twee sundteks. Ik krijg een keer beeld maar zodra ik ga zappen gaan de DVB-c kanalen op zwart. Heb snel maar een recente backup teruggezet en het werkt weer met de oude drivers. Zal nog eens proberen met een enkele sundtek.


I'm wondering what experiences users have with the latest drivers from Sundtek with OpenPLi. With VTI 4.1 they don't work on my Vu duo and two sundteks. At first I get a picture but a soon as I switch to other DVB-c channels they go black. I restored with a recent backup and it works again with the old drivers. Will try again with a single sundtek stick.

[sundtek]

Ik ben benieuwd naar de ervaringen met deze laatste drivers van Sundtek met OpenPLi. Met VTI 4.1 werken deze niet op mijn Vu duo en twee sundteks. Ik krijg een keer beeld maar zodra ik ga zappen gaan de DVB-c kanalen op zwart. Heb snel maar een recente backup teruggezet en het werkt weer met de oude drivers. Zal nog eens proberen met een enkele sundtek.


I'm wondering what experiences users have with the latest drivers from Sundtek with OpenPLi. With VTI 4.1 they don't work on my Vu duo and two sundteks. At first I get a picture but a soon as I switch to other DVB-c channels they go black. I restored with a recent backup and it works again with the old drivers. Will try again with a single sundtek stick.

We just updated dual DVB support with the new mechanism, please update and try again.

[Pimsat]

@Sundtek: I installed latest OpenPli and sundtekdrivers and (for) now its working! Also with dual DVBc tuners.

FYI, this morning I also tried with VTI and one Sundtek DVB-c and that wasn't working. I'll stick with PLi now to test it a couple of days. Thanks for your help.

[sundtek]

@Sundtek: I installed latest OpenPli and sundtekdrivers and (for) now its working! Also with dual DVBc tuners.

FYI, this morning I also tried with VTI and one Sundtek DVB-c and that wasn't working. I'll stick with PLi now to test it a couple of days. Thanks for your help.

Maybe you picked the old driver for VTI in the morning, we updated the driver 2-3 times during that day.
So far we got some good results from several Settopbox systems.