Jump to content


Member Since 29 Apr 2011
Offline Last Active 19 Mar 2022 13:21

#1438442 Russian EPG

Posted by rhinoceros on 16 March 2022 - 19:13

Why not keep EPG for channels that you personally do not like so that everybody else can see for themselves how bad the programs are on these channels ? I always thought that this personal freedom was one of the values in Europe ? Whoever does not like these programs, please do not look !


But suppression of information from and about the enemy is not always helpful. Think about investigators, journalists or anyone else that may have a different opinion than you. To have a different opinion was also always a distinguishing mark in a free democracy. Freedom of the press is now no longer existing in Europe.


Censorship has been decided at the highest level in the European union while that was always the privilege of oppressive regimes and the people of Europe always looked down on those.


Personally I find it frequently useful to listen to others that have a different opinion. For this reason I have a parabola on a rotor. I can decide myself which satellite has programs that are of interest to me even though I may not at all agree with the opinions aired by these programs. A little bit personal freedom has been left for me. Not even the European authorities can take that away from me. They would if they could.


Censorship has started also on the internet. I am sorry to see that happening. I am also sorry to see so much fake news appearing. If I wanted to be a customer, I could buy some fake news for the price of about $6 per item, included pictures, videos, reviews and thousands of likes and followers in social media. If there have to be signed documents, the cost may go up to about $10 per item. But the quality of such news production is already so good that it is impossible to detect as fake just by online research.


Lastly, I believe it would be more productive if we could keep this technical forum free from opinions, politics and religion. There are certainly better places to discuss about those, no doubt, extremely important topics.

#541873 Open PLi 2.1 project-x error

Posted by rhinoceros on 10 April 2016 - 14:38

DBDBurn is here:




There are some dependencies but I think they are all in the feed now, except bdremux. You should be able to find that here:



#495641 Are there still people that use motorised installations ?

Posted by rhinoceros on 23 June 2015 - 18:40


2) Auto Tune (you mean Auto focus) is not functioning with USALS in my opinion.


Auto focus has nothing to do with USALS, does not need it and does not know about it. If new auto focus position is accepted you can store it in a diseqc 1.2 memory index. If you keep using USALS for that sat, of course, you would not use the newly stored value since that is only for diseqc 1.2

#490289 Blindscan for all models

Posted by rhinoceros on 7 May 2015 - 09:12

Very interesting tool for scan...


Interesting indeed. I tried a scan on Astra 2, 28.2E with my box, an et9000. It found almost all transponders that are on lyngsat and that had actual data at the time of scan. But on this sat there are several cases where 2 transponders exist on the same frequency but with different polarisation. This blind scan found only 1 of the 2. Apart from that only 2 or 3 other trs were missed. A very good result compared to the blind scan binary from the manufacturer !


The total scan time was 36 minutes.

#256035 Improved version of blind scan for ET9x00 only

Posted by rhinoceros on 19 February 2012 - 13:43

Rhinoceros, I didn't post my code to compete with yours.

That is clear, I didn't see it that way either, but the thread is confusing now. When someone reports something on the blind scan without specifying which one, we are all confused. Personally I think what should happen is that we update the built-in blind scan and we should have your version as a separate plugin in the feed. Each user to decide for himself which one he wants to use and when. In fact, I believe your version warrants a separate thread alltogether for discussion, since it is much more involved. Please, consider opening a separate thread for it.

I found out that on a cold start (the first run), the binary has a high probability of missing a quite a few transponders.

No one has mentioned that to me and I don't have an ET9x00 to test with. It doesn't make any sense though as it is just a piece of software that is being "cold started" on each run. Maybe it is hardware related, I don't know. What I have noticed though is that sometimes a run doesn't find anything however many times you do it and the only way to cure this is to restart the receiver (or switch to a different tuner).

Oh, it is definitely hardware related. As you say the software doesn't change between runs. But if a receiver restart produces different result thereafter, there is still a software issue ...

Anyway you refer to it as a fix, i.e. a matter of right and wrong and that is not the case, more it is a matter of opinion or a matter of what better suits one user over another, and the easiest way to deal with that is to give the user the option to decide if there should be a delay.

That's fine but then you should give the user an option. It can be a bit more clever than what your Vantage does. If you know it is a motorised installation you could estimate the time it takes to reach position and you could know when you are already on position. See my Positioner Setup plugin for an example of how to do that.

Without an option to wait you would have to move to another plugin, such as the Positioner Setup and move your dish somehow. But that is very inconvenient as you could easily loose your position upon leaving the Positioner Setup (if you are not careful that is).

The waiting issue and my observation on first run results led me to hit two problems in one blow. I use a first run of the binary.That one also sets the tuner parameters. The run takes just a little over 1 minute. I called it the focusing stage. That one minute is enough to move the vast majority of motors even from one extreme end to the other. You could also always switch to high power if you have concerns there. The real scan then starts on the second and subsequent runs. I found it very important to reset all the tuner parameters just before each run. That solved quite a few of the earlier instabilities and I do no longer have to reset the tuners by a hardware reset. I also prevented the user from aborting a blind scan one started. Also to prevent tuner upset and the need to restart. Agreed, it is full-automatic operation and the user is required to exercise some patience. But with the way the built-in blind scan is now, I never had to restart the box. I could always succesfully do the service scan and return to normal operation without any gui or box restart. That's important from a useability perspective. In fact, I see that as a requirement. After all, a restart requires more patience ...

If you could improve your support for motorised installation, I believe that would be a big help to users with such an installation. Thanks for your efforts.

#255034 Improved version of blind scan for ET9x00 only

Posted by rhinoceros on 15 February 2012 - 13:43

It might be more convenient when you put such source code to github or so.... ;)

Oeps, this would largely exceed my small skill set ...

#254804 Improved version of blind scan for ET9x00 only

Posted by rhinoceros on 14 February 2012 - 17:48

This is an update to the blindscan plugin for ET9x00 only!

First, a thanks is in order to the PLi team for using open source. Remember that work like this is possible only because we have access to that. With closed-source, developments like these would be very difficult to do if not impossible.

Second, the original version is by ET (www.et-view.com). Thanks to ET for this blind scan plugin. Here is an update since the plugin is not very robust, especially in a motorised installation.

Third, this is software, therefore there are bugs. Please have patience and tell me about them.

If you want to restore your present system, make a backup of this file since it will be overwritten:
/usr/lib/enigma2/python/Screens/ ScanSetup.pyo

Install the attached package and restart e****2. Done.

This package is only for testing purposes only.

[*]The blind scan frequently does not run to completion and suffers from other robustness issues, such as tuner hang after scan completion. The robustness is significantly improved.
[*]Both bands and polarisations can now be selected individually or together for the same run. No need to run the blind scan several times each for one band or polarisation.
[*]Frequency and symbol rate values are rounded to multiples of 1000.


The blind scan is Ku band only.

The binary executable is by ET and seems to work fine. It is fairly fast but occasionally misses transponders. Perhaps better results can be achieved by limiting the symbol rate range in the scan. Select one rate or a small range only. I have not tested this myself, though.

There is a focusing stage in the beginning. This is necessary to achieve better robustness and in order not to loose transponders in the start of the scan. Please be patient.

Once a blind scan has started you cannot interrupt it. You will need to wait until completion, which might take up to 5 minutes or so if both bands and polarisations are selected. As soon as the transponder scan is complete and the service scan starts you can press the ‘back’ or ‘esc’ button if you don’t want to continue. Nothing will be saved in that way.

Rounding of frequency and symbol rates means that some 5 significant digits are available for each. More digits are technically insignificant and do not occur in technical publications.

Attached Files

#254701 Are there still people that use motorised installations ?

Posted by rhinoceros on 14 February 2012 - 11:59

OK, here it is. Please check my comments below.

First, a thanks is in order to the PLi team for using open source. Remember that work like this is possible only because we have access to that. With closed-source, developments like these would be very difficult to do if not impossible.

Second, thanks to the original developers of the Positioner Setup plugin and all other bits and pieces that are needed. I kept the original screen designs as much as possible. The rotor calculation is just copied from the existing source with only slight modifications. The logging module is copied from the xmltv plugin (EPGImport) also with slight alterations. A thanks to all those developers as well.

Third, this is software, therefore there are bugs. Please have patience and tell me about them.

If you want to restore your present system, make a backup of these files since these will be overwritten:

Install the attached package and restart e****2. Done.

This package is only for testing purposes. The changes to the first two of the above files should be done by the PLi team if and when this plugin is accepted. Diff's are in the zip.

One word of caution. Don’t use Power Measurement if your box does not support it. The ET9X00 or its drivers apparently do not support Power Measurement.

[*]The motor index field now allows numeric input instead of just a selection which was cumbersome to use with indices going up to 50 or so.
[*]There was a performance issue with the tuning screen as it was using the scanner screen. The required code is now isolated and tuning selection works much faster. The disadvantage is that there is some code now in duplicate. But this is only the satellite parameter section which is fairly static anyway.
[*]The tune screen now correctly points to the satellite and transponder of the currently playing service. Previously, the default was manual transponder and on change to predefined, you had no idea which transponder had been used. The tuning screen now identifies the correct transponder as predefined – if indeed it is.
[*]The motor index field is now correctly filled-in after selection of the satellite. Previously you had to go through the tuner setup screen, work your way to the bottom and find out what your motor index was. Switching screens this way is time consuming as it reallocates the tuner and channels each time.
[*]Fields are added to specify an X coordinate for the gotoX command. This field is automatically set according to the satellite tuned but can, of course, be filled in manually as well.
[*]A gotoX command is added under the yellow button (USALS use).
[*]The auto-focus function is added under the red button.
[*]USALS calibration is added under the red button.
[*]Additional parameters are added in the advanced satellite section of the tuner setup screen to specify the detailed characteristics of the rotor is use. The parameters are global, i.e. the same for all satellites. (Only one rotor supported.)
[*]A log function is added under the ‘info’ button to log the details of all steps and measurement values, including the exact diseqc parameters. All actions are also shown to the user in the screen.

Some words as user guide. The rotor parameter defaults are for the rotor I use, but I believe these are reasonably universal. If you don’t know yours, leave them at the defaults. The rotor speeds are in degrees/sec and are only used to estimate the movement time. The ‘step size’ is in degrees/step and is more critical as it determines the actual resolution used in the position calculations. Use your own if you know it.

The requirement for using auto-focus is that you have a signal that the tuner locks on. The stronger the better. The search range is artificially limited to +/- 5 degrees on the orbit. The calculation is fairly accurate. It uses the weighted average, not the maximum signal position. If you don’t trust it, press the ‘info’ button, look at the signal levels measured, draw a plot and judge for yourself. There should not normally be more than 1 step between the center of the beam and the maximum signal position. Calculate the auto-focus position and store the result in the motor index. There is no bias in the search directions as that is randomised. If you recalculate the auto-focus position several times in a row you should find the same position each time. If not, you have hysterese on the rotor which probably means wear and tear. Consider replacement of the rotor.

The gotoX (USALS) command is really a benefit. Previously, the only way to use gotoX was to set a satellite to use USALS, start a manual service scan, abort and make sure your position did not move. That works much easier now with direct support for gotoX. Just fill-in the coordinates you want and press the button.

The USALS calibration is a way to determine a misalignment – if any – on your rotor installation. Especially useful if your rotor setup is difficult to reach as it is in my case. You will need at least three measurements, one on each opposite side of your rotor range and one in the center. If you have significantly different readings on the opposites, there is something wrong with you setup. But even if your elevation is fine and your pole is quite vertical you might still have a longitude shift. What I do is check if I have the same deviation on each end of the rotor range and – if yes – apply the opposite shift to the site longitude. That way I am spot-on over the entire range and the USALS position is just the same as the manually determined auto-focus position. I now have a calibrated range from 45 E to 45 W using USALS only.

The requirement for using the calibration is that your target is within +/- 10 degrees on the orbit. A totally artificial limit, of course, but just to prevent inadvertent full-scale moves. Again no bias in the search directions.

Lastly, the present plugin has a license that I am not happy with as it favours one company in particular. I would not agree to publish my modifications under exactly that license since I would not want to name any company in particular. Everyone the same rights or no one any rights. The mention of this company in the license file is legally speaking meaningless anyway.

Please, consider this version of the plugin as a test version and let me know your experience.

Attached Files

#236217 Media Player toont geen tags met cyrillische caracter set

Posted by rhinoceros on 3 December 2011 - 13:45

Dank je voor je begrip voor mijn probleem. Wat de code van mediaplayer betreft: helemaal mee eens. Ik heb eerlijk gezegd niet het idee dat het aan gstreamer ligt. De mp3 files zijn ook goed. Ook de tags. Heb ik gecontroleerd op verschillende spelers. Als ik tijd heb zal ik eens kijken of ik wat vinden kan in de code van mediaplayer. Het voornaamste probleem is toch wel wat ik genoemd heb in een ander draadje. De onbetrouwbaarheid bij het afspelen. De tags kan ik nog zeggen ach laat maar, maar dat het afspelen nog steeds niet erg betrouwbaar is, dat is wel hinderlijk.

#229010 AutoResolution

Posted by rhinoceros on 5 November 2011 - 11:16

Bij mijn tv (pioneer plasma) heb ik veel sneller beeld met een delay van 0.

Wat de diff's betreft, ik begrijp het probleem wel, maar ik heb alleen een notebook met windows. Ik had eigenlijk niet het plan om heel veel tijd te investeren. Het produkt OpenPLi is wel erg goed intussen. Voor een eenvoudige gebruiker als ik is er niet zo veel aan te merken. Mijn excuses bij voorbaat. Als het nodig is zal ik graag kijken of het me lukt om me dit eigen te maken.

#228330 Screen saver

Posted by rhinoceros on 2 November 2011 - 08:52

De 'VCR Scart' functie in het menu is uitstekend geschikt als screen saver voor plasma tv
toestellen. Ik heb enkel de boodschap op het VFD gewijzigd in 'Press OK ...'. De ET9000
heeft toch niet zo veel fuktionaliteit voor VCR en het schermpje is maar 1 regel in
tegenstelling tot de Dreams. Ik wijzig daarom ook de naam in het menu naar 'Screen saver'.
Er is wel een neveneffekt. De analoge audio uitgang van de ET9000 wordt als pass-through
geschakeld. Tenminste de analoge audio op de VCR Scart ingang wordt hoorbaar op de analoge
audio uitgang van de ET9000.

De patch is bijgevoegd als diff bestand tezamen met de base-line versie(s).
Attached File  Scart.zip   1010bytes   3 downloads

#228328 Blindscan

Posted by rhinoceros on 2 November 2011 - 08:49

Er is een bug met blindscan. Aan het einde blijft het rauwe kanaal actief. Daardoor moet de
gehele plugin verlaten worden en een actief kanaal geselecteerd worden voordat een volgend
kwadrant gescand kan worden. Dit is ook gecorrigeerd in 'ScanSetup.py'.

De patch is bijgevoegd als diff bestand tezamen met de base-line versie(s).
Attached File  ScanSetup.zip   11.5KB   7 downloads

#228325 Partitionering en alignment harde schijf

Posted by rhinoceros on 2 November 2011 - 08:46

De partitionering kan gerust op sektor 8 beginnen voor alle groottes. In het 'sfdisk'
commando heb ik daarom de optie -uS toegevoegd zonder iets anders aan te passen. Dat heeft
het beoogde effekt. Overigens is het niet juist dat alleen schijven van 200 GB of meer een
sektor alignment nodig hebben. WD heeft ook schijven van 160 GB die 4K sectoren hebben.

De patch is bijgevoegd als diff bestand tezamen met de base-line versie(s).
Attached File  Harddisk.zip   7.26KB   8 downloads

#228319 AutoResolution

Posted by rhinoceros on 2 November 2011 - 08:39

Waarom is de delay_switch_mode altijd nodig. Ik heb deze op 0 gezet.

De patch is bijgevoegd als diff bestand tezamen met de base-line versie(s).
Attached File  AutoResolution.zip   4.08KB   12 downloads

#228318 Bug in TimerSanityCheck

Posted by rhinoceros on 2 November 2011 - 08:38

Er zit een lelijke bug in 'TimerSanityCheck.py'. Dit probleem is te zien bij het toevoegen
van een timer maar ook bij direct recording in InfoBarGenerics. Aan het einde wordt de
simultimer getest. Wanneer de lijst minder dan 2 elementen heeft gaat het fout. De bug is
dat dit geen bug is. Er is weliswaar een kanaal dat niet geselecteerd kan worden. Maar dat
is een konflikt als en alleen als er een overlap is. Wanneer simultimer maar 1 timer heeft
dan is er dus geen overlap en ook geen konflikt.

De patch is bijgevoegd als diff bestand tezamen met de base-line versie(s).
Attached File  TimerSanityCheck.zip   2.95KB   11 downloads