Black Hole Vu+ Solo2 2.0.2 - Meoboot Revenge

A

akhbar

Vu+ Newbie
I qoute from the mail the team sent out when BH 2.0.0 oe2 was released:
-"The Black Hole Image 2.0.0 is completely new and based on the new Vu+ OE. We used the name OE 2.0 only to maintain a tradition started by DMM, but in reality OE 2.0 does not mean anything. We could call it OE 3.0 or 4.0.
This is because the new version of OE doesn't have a numbering system, as it is updated continuously and is dynamically linked to the new Vu+ OE"

-"The Black Hole image is now fully upgradeable online. With this function, you can now keep the Black Hole image installed up to date. For example, the release of new drivers from Vu+ and also in the daily work that is done by the team in their Vu+ Git. The Black Hole team will follow the daily development work of Vu+, and will provide a regular update of the image."

This is apparently utterly nonsense?
 
Mito

Mito

Administrator
akhbar said:
I qoute from the mail the team sent out when BH 2.0.0 oe2 was released:
-"The Black Hole Image 2.0.0 is completely new and based on the new Vu+ OE. We used the name OE 2.0 only to maintain a tradition started by DMM, but in reality OE 2.0 does not mean anything. We could call it OE 3.0 or 4.0.
This is because the new version of OE doesn't have a numbering system, as it is updated continuously and is dynamically linked to the new Vu+ OE"

-"The Black Hole image is now fully upgradeable online. With this function, you can now keep the Black Hole image installed up to date. For example, the release of new drivers from Vu+ and also in the daily work that is done by the team in their Vu+ Git. The Black Hole team will follow the daily development work of Vu+, and will provide a regular update of the image."

This is apparently utterly nonsense?
Click to expand...
Please don't spam and don't mar this thread!
Matrix has already replied to you.
 
Matrix10

Matrix10

Administrator
mouad99 said:
I DON T UNDERSTAND WHY
THERE ISN T ANY SYNCHRONIZATION BETWEEN THE BACKDROP AND THE POSTER in BH 2.0.2
Click to expand...

I'm not using this plugin
If something is not working properly ,Ask the plugin author, not us.

I do not see any problem with the image

Plugin is installed correctly and working

shot1.jpg
 
cyborgpunte

cyborgpunte

Vu+ User
My wife had some complaints about the new 202 image
The arrowkeys around the ok button
they works exactly opposite as they did day before yesterday
- Can't we have same functionality every week 24/7 as others

LOL she had RC 180 degrees wrong

and thanks for new version
 
Mito

Mito

Administrator
cyborgpunte said:
My wife had some complaints about the new 202 image
The arrowkeys around the ok button
they works exactly opposite as they did day before yesterday
- Can't we have same functionality every week 24/7 as others

LOL she had RC 180 degrees wrong

and thanks for new version
Click to expand...

:D
 
V

VANT

Vu+ User
on earlier version (2.0.0/2.0.1) i have problem with roll off parameter for some tp...You says that is not your code but vu...
OK i test oryginal VUPlus image (vuplus-image-vusolo2-20130314182723_usb.zip) and on this image "roll off - auto" work ok. Can You fix this ?
 
Matrix10

Matrix10

Administrator
VANT said:
on earlier version (2.0.0/2.0.1) i have problem with roll off parameter for some tp...You says that is not your code but vu...
OK i test oryginal VUPlus image (vuplus-image-vusolo2-20130314182723_usb.zip) and on this image "roll off - auto" work ok. Can You fix this ?
Click to expand...

I not see roll off - auto in orginal and VTI image Solo2
and coding is also the same in orginal/VTI/BH image in ScanSetup.py
not only this coding but file is the same.

self.scan_sat.rolloff = ConfigSelection(default = defaultSat.get("rolloff", eDVBFrontendParametersSatellite.RollOff_alpha_0_35), choices = [
(eDVBFrontendParametersSatellite.RollOff_alpha_0_35, "0.35"),
(eDVBFrontendParametersSatellite.RollOff_alpha_0_25, "0.25"),
(eDVBFrontendParametersSatellite.RollOff_alpha_0_20, "0.20")])
Click to expand...
 

Attachments

  • shot1.jpg
    shot1.jpg
    712.9 KB · Views: 47
V

VANT

Vu+ User
roll-off to auto we can set also in dreamset/dreambox edit etc., not only in image, but only on BH we have gs after roll-off is set to auto.
 
Matrix10

Matrix10

Administrator
VANT said:
roll-off to auto we can set also in dreamset/dreambox edit etc., not only in image, but only on BH we have gs after roll-off is set to auto.
Click to expand...

Then I'll test when I have time.
I doubt it's the same coding,but with software is all possible.
we shall see.

Do you have a channel on Astra 19E for Test ?
 
Shiro

Shiro

BH-C
VANT said:
Now i generally use HB 13E, so i don't know for Astra 19E, but change this parameter for any channel using dreamset, and test.

In this topic i start write about this problem and i put crashlog
http://www.vuplus-community.net/board/threads/black-hole-vu-solo2-v-2-0-1-oe-2.11298/#post-81522
Click to expand...

Yes this is a bug of enigma2 not of Bh,
you have it in Bh because Bh use the E2 funcion "ConvertToHumanReadable" located in enigma2 lib/python/tools/Treansponder.py
In this function the key RollOff_auto is missed,

but ok we can fix
 
V

VANT

Vu+ User
still gs
Code: 
AUDIO_CONTINUE - ok
not pauseable.
[AutoRes] service changed
Traceback (most recent call last):
  File "/usr/lib/enigma2/python/Navigation.py", line 43, in dispatchEvent
    x(i)
  File "/usr/lib/enigma2/python/Components/ServiceEventTracker.py", line 38, in event
    func[2]()
  File "/usr/lib/enigma2/python/Blackhole/BhEI.py", line 144, in __start
  File "/usr/lib/enigma2/python/Tools/Transponder.py", line 45, in ConvertToHumanReadable
    eDVBFrontendParametersSatellite.RollOff_auto : _("Auto")}[tp["rolloff"]]
AttributeError: type object 'eDVBFrontendParametersSatellite' has no attribute 'RollOff_auto'
(PyObject_CallObject(<bound method Navigation.dispatchEvent of <Navigation.Navigation instance at 0x17e6080>>,(5,)) failed)
getResolvedKey config.plugins.crashlogautosubmit.sendAnonCrashlog failed !! (Typo??)
resolve: resolve ${sysconfdir}/enigma2/settings
resolve: -> /etc/enigma2/settings
getResolvedKey config.plugins.crashlogautosubmit.addNetwork failed !! (Typo??)
resolve: resolve ${sysconfdir}/enigma2/settings
resolve: -> /etc/enigma2/settings
getResolvedKey config.plugins.crashlogautosubmit.addWlan failed !! (Typo??)
resolve: resolve ${sysconfdir}/enigma2/settings
resolve: -> /etc/enigma2/settings
]]>
  </enigma2crashlog>

now all hd channel give gs....
 
Shiro

Shiro

BH-C
VANT said:
still gs
Code: 
AUDIO_CONTINUE - ok
not pauseable.
[AutoRes] service changed
Traceback (most recent call last):
  File "/usr/lib/enigma2/python/Navigation.py", line 43, in dispatchEvent
    x(i)
  File "/usr/lib/enigma2/python/Components/ServiceEventTracker.py", line 38, in event
    func[2]()
  File "/usr/lib/enigma2/python/Blackhole/BhEI.py", line 144, in __start
  File "/usr/lib/enigma2/python/Tools/Transponder.py", line 45, in ConvertToHumanReadable
    eDVBFrontendParametersSatellite.RollOff_auto : _("Auto")}[tp["rolloff"]]
AttributeError: type object 'eDVBFrontendParametersSatellite' has no attribute 'RollOff_auto'
(PyObject_CallObject(<bound method Navigation.dispatchEvent of <Navigation.Navigation instance at 0x17e6080>>,(5,)) failed)
getResolvedKey config.plugins.crashlogautosubmit.sendAnonCrashlog failed !! (Typo??)
resolve: resolve ${sysconfdir}/enigma2/settings
resolve: -> /etc/enigma2/settings
getResolvedKey config.plugins.crashlogautosubmit.addNetwork failed !! (Typo??)
resolve: resolve ${sysconfdir}/enigma2/settings
resolve: -> /etc/enigma2/settings
getResolvedKey config.plugins.crashlogautosubmit.addWlan failed !! (Typo??)
resolve: resolve ${sysconfdir}/enigma2/settings
resolve: -> /etc/enigma2/settings
]]>
  </enigma2crashlog>

now all hd channel give gs....
Click to expand...

yes need more work
 
You must log in or register to reply here.
Top