Pr2

Duo 4K se has modular tuner may be you can purchase a non FBC VU+ tuner that support blindscan and plug it in (but check its compatibility first).

You can also have a look at external DVB-S2 USB tuner but then you should ensure that they are blindscan capable and that they are compatible with the Duo 4K se kernel version.

 

We should never assume anything when purchasing a STB, I have a VU+ Solo4K it has 2 cardreaders and 1 CI slot, I purchase later on the Duo 4K and was surprised to see that it has only one card reader. :-( (but 2 CI slots).

I purchase also other brand STB assuming that every dual tuners boxes are capable to perform Picture-In-Picture and stream but they are not.

 

Choosing the right STB is not an easy think, it is hard to find one that will fulfill all the requirements.

Vu+ is not supporting true MultiBoot nothing we can do about it. If you need to use MultiBoot you should have purchased a box that natively support it.
OpenMultiboot is just changing the mount point to allow to try other images but this can result in conflict between OE-Alliance images and OpenPli and this is what you experience here. Some image goes change some stuff in the common mounted part.
You cannot conclude anything about any image when using it with OpenMultiboot since you don't run the true full image.
I totally stop using OpenMultiboot due to all those problems.
If I want to test different image I flash them normally in the VU+ or I use the MultiBoot of the Gigablue Trio 4K.
So if you are unhappy with OpenPli feel free to use any other image that better fits your needs. That's the main advantage of our boxes.

Very good thing OpenMultiboot is not a true MultiBoot it just fake the folders so some image can corrupt the other one by writing into the common folders. Don't use it!

We don't know which box you have, what is your setup. Which provider you are watching, do you use a smartcard which softcam or do you use a pcmcia module.

I'd like to have LCD display on the STBs and that's why I am using VU+ Solo 4K and Vu+ Duo 4K for my daily usage.

To be really honest without you, I prefer the default LCD skin which already give me all the informations that I want and I'd like the current proportion.

So I could not find any benefits with your modified LCD skin.

Sorry it is a typo of course the file is:  channel_id_filter.conf

Hello,

 

I propose a new PR with the channel id filtering. I better describe the constraints that lead to implement this solution, it is slightly improved compared to the first version to avoid some confusing entries in log.

 

https://github.com/O...gimport/pull/53

 

This doesn't prevent to work on implementing the standard DVB language support into EPGImport so please view it as a Quick Win solution both solutions can live together.

 

End-users doesn't have to learn regex a simple cut and paste of the channel id will do the job (risk of false positive is really low and the log is clearly displaying the filtered "channel id" so debugging is easy). Moreover the content of this file for standard endusers will be explained by Doglover to easily fix there problem. Advanced users that test the solution already found benefits out of it. People can easily turn on/off one particular filter in the file since comments are allowed (line starting with a # are ignored).

The option to enable it or not on the custom.channels.xml is a specific request from Doglover.

 

I hope that it will be accepted because Doglover (Willy) is really waiting for it.

 

Regards,

 

Pr2

Who cares to have Kodi on VU+ device since we have no sound on them... Kodi without the sound is useless.

Hi,

 

I have created a new PR to improve EPGImport:

 

https://github.com/O...gimport/pull/50

 

If the same service reference is present several time during import for the same channel id it was added anyway. So we can have useless duplicate entries in the EPGImport that will just slow it down since the same data will be loaded twice.

 

This patch also add support for long description to each EPGImport parameters.

 

Be careful that skinners will need to enable it in there skins in order to display them so for screen name="EPGImportConfig" the widget name="description" should be added.

<screen name="EPGImportConfig" position="fill" title="EPG Import Configuration" flags="wfNoBorder">
...
         <widget name="description" position="30,570" size="720,300" itemHeight="38" font="Regular;30" valign="top"/>
.....
</screen>

Translators will also need to work on the newly generated .po files.

 

Pr2

Using language defined in the GUI won't probably solved the question here since you can decide to receive both french and english language so both will be loaded into memory and then which one will be displayed?

Does GMEPG take care of the language code, how does it handle the EPG when there are several languages available for the same service reference?

If it handles it properly no need for filtering in EPGImport just load all the possible languages for a multi-lingual channel using the same reference (but this will fill up the STB memory).

 

But then you should extend the number of preferred languages because 2 is very restrictive.

 

People doesn't have to learn regular expression they can just type the "channel id" name like it appears in the channels.xml but I propose my implementation. This PR is allowing users to have a full control on what is loaded into STB memory.

 

So sad that I ask for help in the development section of OpenPLi where I explain what I was doing and nobody answer me, now that the patch is ready and fully tested you reject it. I would have better invest my time in doing something else.

Hi,

 

Here is a trial to implement the feature requested by Doglover.

 

Forewords

 

The filtering is only possible on the channel id and is based on regular expression (regex). I will not fully explain here what the regex syntax is but just a few remarks;

If you want to fully exclude all the EPG for all the channel id from france you need to use this syntax:

 

.*\.fr

 

. replace any characters

* means that any characters can repeat anytime

\. is to match the .  remember . (alone) means any character for the regex.

fr is "fr"

 

You can also specify a specific channel id:

 

Discovery\.dk

 

This will exclude Discovery.dk  is you didn't mention \. then the regex will match Discovery(1 time any character)dk

But most of the time simply specifying Discover.dk should not cause trouble but in case of doubt and if you want to be sure to have a perfect match use the \. notation.

 

The filtering is not case sensitive (so the whole filter that you will set will be switched to lower case because it is what is also done for the channel id matching.

So Discovery\.dk is the same as DiscoVery\.DK so you don't have to care about the exact case of the channel id name.

 

So filtering on anything else than the channel id is not foreseen (it is not possible to filter on partial service reference nor on comments). Why?  Because the channels.xml file is processed in a true XML way meaning that every element is retrieved independently so this filter will is focusing on the channel id and nothing else (filter by reference is already implemented into EPGImport).

 

One line per filter a OR operation will be performed between every lines.

 

 

To test go into this folder on your STB:

 

/usr/lib/enigma2/python/Plugins/Extensions/EPGImport

 

There make a copy of the existing: EPGConfig.py

cd /usr/lib/enigma2/python/Plugins/Extensions/EPGImport
cp EPGConfig.py EPGConfig.py.ori

 

Then delete the EPGConfig.pyo file (optional).

 

 

Download this file:

 

https://raw.githubus...rt/EPGConfig.py

 

Then transfer it to your STB into: /usr/lib/enigma2/python/Plugins/Extensions/EPGImport

 

Then you need to create a filter file:  

 

/etc/epgimport/channel_id_filter.conf

 

With the filter that you want:

 

.*\.fr
.*\.be
discovery\.dk

 

This will exclude all the channel id ending with .fr and .be and also exclude discovery.dk

 

Reboot your box. You only need to reboot your box once to have it creating the EPGConfig.pyo file.

Later on you simply need to edit and change the /etc/epgimport/channel_id_filter.conf

Please don't trust the dragnan test he was using OpenATV as main image and OpenPLi with OpenMultiboot so he was using the OpenATV kernel that is patched to enable those device.
So you I can just confirm that it has never worked in OpenPLi.

You can try YAMP it is in the feed.

There is a plugin called epgimportfilter in the feed isn't it doing what you are requiring here?

Because in Openpli we don't install tools that many people don't need. It's up to you to install the plugin that you really need in OpenPLi.

That's one of the main difference between OpenPLi and the other images that pre-install many plugins.