1748 replies to this topic

[SpaceRat]

Please replace openvpn_2.1.3.bb in ./openpli-oe-core/meta-openembedded/meta-networking/recipes-support/openvpn using the attached openvpn_2.3.2.bb in order to finally bump the openvpn version to 2.3.2.

This will enable users on IPv6-only resp. DS-lite connections to establish OpenVPN connections using IPv6 as carrier network (Payload can still be IPv4-only).

The update doesn't harm anyone, just updating the client doesn't change the behaviour:

netstat -n
tcp        0      0 192.168.1.16:44433      88.77.xxx.yyy:1194      ESTABLISHED

It will only switch to IPv6/Dual-Stack mode if any tcp/udp-directive is changed to tcp6/udp6, e.g. (Inside <client>.conf):

proto tcp-client

to

proto tcp6-client

Result:

netstat -n
tcp        0      0 2001:db8:affe:0:2bf:ecff:fec0:c0f7:1194 2001:db8:abcd:1234::2:1194 ESTABLISHED

Attached Files

•  openvpn_2.3.2.bb.zip   864bytes   14 downloads
•  openvpn_2.3.2-r0_mips32el.ipk   247.87KB   27 downloads

[mirakels]

openvpn2.3.2 pushed. build and installed fine om my local setup.

 

Please test tomorrow...

[Taapat]

Maybe this will interest some.
I have seen that satellite operators such as Viasat program time in EPG is not the same as the real program start and end time. Different is a few minutes, but when I record manually, not by timer, sometimes record file name is not correct, because it comes from the name of the previous program, which by the EPG information still ends after a few minutes.
Therefore, I create a small workoraund in which, if the current event is executed more than 80%, for recording is used the info from the next event.
I do not know, maybe it should be used if it is executed more than 90%, or about this needs to show a messagebox, but maybe that the such be ok.

--- a/lib/python/Screens/InfoBarGenerics.py
+++ b/lib/python/Screens/InfoBarGenerics.py
@@ -2033,6 +2033,11 @@ class InfoBarInstantRecord:

   if event is not None:
    curEvent = parseEvent(event)
+   position = (curEvent[1]-curEvent[0])*0.8
+   curtime = int(time())
+   if curtime > position: # current event ending soon, therefore use next
+    nextevent = epg.lookupEventTime(info["serviceref"], event.getBeginTime(), +1)
+    curEvent = parseEvent(nextevent)
    info["name"] = curEvent[2]
    info["description"] = curEvent[3]
    info["eventid"] = curEvent[4] 

Attached Files

•  0001-Use-the-next-event-for-the-record-name-if-current-en.patch   1016bytes   1 downloads

Edited by Taapat, 17 March 2014 - 19:58.

[Taapat]

Sorry, in the previous post, I forgot to add the start time in calculating, and verifying if nextevent exists.
Here is the correct patch.

 

--- a/lib/python/Screens/InfoBarGenerics.py
+++ b/lib/python/Screens/InfoBarGenerics.py
@@ -2033,6 +2033,12 @@ class InfoBarInstantRecord:

   if event is not None:
    curEvent = parseEvent(event)
+   position = ((curEvent[1]-curEvent[0])*0.8)+curEvent[0]
+   curtime = int(time())
+   if curtime > position: # current event ending soon, therefore use next
+    nextevent = epg.lookupEventTime(info["serviceref"], event.getBeginTime(), +1)
+    if nextevent is not None:
+     curEvent = parseEvent(nextevent)
    info["name"] = curEvent[2]
    info["description"] = curEvent[3]
    info["eventid"] = curEvent[4] 

 

Attached Files

•  0001-Use-the-next-event-for-the-record-name-if-current-en.patch   1.04KB   0 downloads

[athoik]

Also don't forget to add patches on dreambox dvbmediasink http://openpli.org/f...e-6#entry411712

 

PS. VU also need to recreate patch or stick with a previous SRCREV.

[littlesat]

Why using .8 times and not an absoluut difference (e.g. 5 or 10 minutes?).

[WanWizard]

That would go very wrong when you want an instant recording of a program that only lasts 10 min... Using a percentage would make the cut-of point small too...

[littlesat]

So in fact this is never good....

[Taapat]

Everyone has their own experiences for the record, I do not know how their used by others, but only referring to my experience, I usually try to record a program completely, and think that a possibility of that someone wants to record the final minutes of the program is much smaller, than someone wants to record program which by EPG information has not yet begun.
Probably need discuss about the percent, but as I WanWizard wrote- use percentage is much better than defined minutes.
Perhaps, need to implement more code, and add addition message box with confirming, if the name will be changed?

[littlesat]

I think we should sleep on it... What if the next event is only 2 or 5 minutes???

[mirakels]

Maybe add a selection with the current and next (and maybe next next) event  to the screen that pops up after manual record so the user can select the proper event.

The selection can be a drop down list or a radiobutton list...

[Persian Prince]

[VideoEnhancement] add entry vertical_dejagging, smooth

 

http://code.vuplus.c...1eff882daa89b4e

[Rob van der Does]

[VideoEnhancement] add entry vertical_dejagging, smooth

 

http://code.vuplus.c...1eff882daa89b4e

Can be used for all boxes, as it read proc's. So no hardware specific plugin, just an amendment to the existing version for all boxes.

[Erik Slagter]

[VideoEnhancement] add entry vertical_dejagging, smooth

 

http://code.vuplus.c...1eff882daa89b4e

Can be used for all boxes, as it read proc's. So no hardware specific plugin, just an amendment to the existing version for all boxes.

proc = driver = hardware

[littlesat]

En waarvoor zijn deze nieuwe procs perse nodig? Krijg je er beter beeld me of zo (waarom dan niet meteen default?)

[Rob van der Does]

 

[VideoEnhancement] add entry vertical_dejagging, smooth

 

http://code.vuplus.c...1eff882daa89b4e

Can be used for all boxes, as it read proc's. So no hardware specific plugin, just an amendment to the existing version for all boxes.

proc = driver = hardware

Exactly.

[mirakels]

this is added in the drivers since this month...

But what does it do??? there are 2 new configuration items:

 

             "Scaler vertical dejagging"
             "Smooth"
 

[littlesat]

Het upscalen nog vlekkiger maken als je daar aan sleutelt??

Edited by littlesat, 19 March 2014 - 11:04.

[Rob van der Does]

this is added in the drivers since this month...

But what does it do??? there are 2 new configuration items:

 

             "Scaler vertical dejagging"
             "Smooth"
 

pep_scaler_vertical_dejagging = Toggle the vertical scaler dejagging.

smooth = Enable smoothing filter to control the dithering process.

 

You can google for more details. I did, but it seems to be rather complicated stuff and I won't pretend to understand that.

 

And as I said before: you can add this to the video enhancement plugin for all boxes. If the proc entry isn't there, it won't show in the plugin.

Edited by SatKiekerd, 24 March 2014 - 09:30.

[mirakels]

Ah, so "Toggle the vertical scaler dejagging." means that dejagging through the vertical scaler is enabled or disabled.

 

So that only leaves the question what does dejagging invole? Googling on 'vertical scaler dejagging' reveals lots of patent documents without much explanation...