267 replies to this topic

[Huevos]

Then offer us a good plugin....

Originally done by Andy a few years ago and then I did a major rewrite on it to its current form about 3 years ago.

 

And then Dima ported it for OpenPLi months ago.

 

http://forums.openpl...n-et9000/page-3

Edited by Huevos, 14 January 2015 - 15:49.

[Erik Slagter]

Does it support both xtrend and vuplus blindscan binaries?

[athoik]

Regarding the Dreamboxes most new boxes I think they support blindscan.

The python part is still open: http://git.opendream...d770cb99299617e

 

Do you think python part is enough or there are "hidden" parts in their closed enigma2?

 

PS. There are blindscan utils but from the python part I can understand that there are used only for cable scanning.

[Huevos]

Does it support both xtrend and vuplus blindscan binaries?

The version on OE-A supports a lot of brands. Dima cut it back to just Vu and Xtrend.

 

Dima's version should at least support Vu Solo SE, Solo2, Uno, Ultimo, Duo2, Et9x00.

 

Not really sure if there are binaries for any other models at this time.

[Erik Slagter]

What version should we offer then?

 

It would help greatly if it was in the e2openplugins, of course! At least somewhere where we can fetch "source code" from. I don't want yet ANOTHER binary 3rd party plugin.

 

Athoik, you need to have a closed source binary that talks directly to the tuners. I don't know how DMM implemented this, they could very well have added that code to enigma2 itself (which would be better, but also means we can't use it in any way).

 

The only feasible solution, imho, is that someone goes snooping on the i2c busses and reverse engineering the protocols... If that is known, we could build the generic code in enigma2 and handle the tuner-specific code using a plugin/package/whatever (better not in enigma2). Then you'd have no conflicts, like you have now (enigma2/linux-d4l and the blindscan binary talking to the tuner at the same time and interfering).

[Huevos]

W

 

It would help greatly if it was in the e2openplugins, of course!

I thought that was the whole point Dima porting it to OpenPLi. But for some reason after he posted the files they never got committed to E2 plugins.

 

Main difference between his version and ours is that his doesn't use the branding module. And there may have been a few minor commits to ours in the mean time.

Edited by Huevos, 15 January 2015 - 20:13.

[Rob van der Does]

Then you'd have no conflicts, like you have now (enigma2/linux-d4l and the blindscan binary talking to the tuner at the same time and interfering).

As fr as I know the OE-A version doesn't have that kind of issues. At least I never encountered them.

[littlesat]

A Dutch transponder changed from DVB-S QPSK 5/6 27500 to DVB-S2 PSK 2/3 29900... and my tuner found automatically the new sympol rate....

 

So for this tuner probably "manually" scan polarization and frequency might be enough....

 

In this case the ET10K

 

[edit]

Symbol rate is still something that should be scanned... It was the auto FastScan that adjusted that parameter.

 

 

As fr as I know the OE-A version doesn't have that kind of issues. At least I never encountered them.

 

Probably your box did not start a recording at the moment the blindscan was ongoing...  

Edited by littlesat, 16 January 2015 - 08:12.

[Rob van der Does]

You can be sure I'm not going to do a blindscan when a recording is imminent. Just as I don't update the box or carry out experiments then.

[Erik Slagter]

I thought that was the whole point Dima porting it to OpenPLi. But for some reason after he posted the files they never got committed to E2 plugins.
 
Main difference between his version and ours is that his doesn't use the branding module. And there may have been a few minor commits to ours in the mean time.

I don't remember having been supplied with a set of clean source files or a diff against the OEA repo. Or even better a complete e2openplugins repo It would greatly help.

Edited by Erik Slagter, 16 January 2015 - 09:21.

[Erik Slagter]

You can be sure I'm not going to do a blindscan when a recording is imminent. Just as I don't update the box or carry out experiments then.

That's the whole issue. At some time you're having two parties talking to the same tuner, without one knowing of the other. This will surely give problems, if you are going to interleave i2c byte strings from two sources. That's why blindscanning should be in the driver and should be accessed from enigma2 and not from a plugin.

[Huevos]

 

Then you'd have no conflicts, like you have now (enigma2/linux-d4l and the blindscan binary talking to the tuner at the same time and interfering).

As fr as I know the OE-A version doesn't have that kind of issues. At least I never encountered them.

 

Sometimes the binary produces complete nonsense. The OE-A plugin filters that on line 835.

https://github.com/o...n/src/plugin.py

[Huevos]

 

I thought that was the whole point Dima porting it to OpenPLi. But for some reason after he posted the files they never got committed to E2 plugins.
 
Main difference between his version and ours is that his doesn't use the branding module. And there may have been a few minor commits to ours in the mean time.

I don't remember having been supplied with a set of clean source files or a diff against the OEA repo. Or even better a complete e2openplugins repo It would greatly help.

 

Erik can you please read the thread from last March (all 3 pages). It should answer a lot of questions. There's an IPK to Dima's code but for some reason the .py is no longer there.

 

http://forums.openpl...indscan-et9000/

[littlesat]

The best solution here should be if a box manufacturer added some features in their drivers for this feature... And stop using the extra binary... But it seems we can wait forever for a real good structured "blindscan" feature...

Edited by littlesat, 16 January 2015 - 11:49.

[Huevos]

The best solution here should be if a box manufacturer added some features in their drivers for this feature... And stop using the extra binary... But it seems we can wait forever for a real good structured "blindscan" feature...

Yes, but not a reason for not selecting this plugin, as the other one uses that system also.

[Huevos]

Dima73, can you post the py file as it seems to have disappeared from the other thread. The IPK is here.

 

http://forums.openpl...e-3#entry411803

[Dimitrij]

Dima73, can you post the py file as it seems to have disappeared from the other thread. The IPK is here.

 

http://forums.openpl...e-3#entry411803

I do not understand ...
Sources in this package, what's the problem?

[Huevos]

 

Dima73, can you post the py file as it seems to have disappeared from the other thread. The IPK is here.

 

http://forums.openpl...e-3#entry411803

I do not understand ...
Sources in this package, what's the problem?

 

Erik says He wants to add to E2-plugins.

 

And wouldn't it be better having this built in to the image rather than the current offering?

[Dimitrij]

F1/F3 ET8000/8500/10000/7x00 is no blindscan support.

[athoik]

DMM as well (although it might be possible).