you also need an Mg_cfg file.
Posts by KiddaC
-
-
-
-
All the site is doing is returning torrent downloads for a particular ip address. Anyone that used, i say used (does anybody really download torrents anymore)... knew downloading torrents left a trace and could be linked to your ip address.
And if you really need to download torrents, always use a proxy or vpn to download. What ever you are after downloading there is a lot better alternatives than torrents nowadays.
I personally think that site is a bit dodgy. To test a VPN all you have to do is go onto any of the other hundreds of whats my ip address websites. For example...https://www.iplocation.net/find-ip-address
or use a proxy judge
Test it without your vpn running, test it again once your vpn is running. If its different your vpn is working.
-
Rather you than me pauldb.
Just to add on what aime_jeux has said.
RunningText.py is a standard component on openvix and openatv, don't think it comes as standard on openpli.Yes you can't use my custom components in this if its to be standalone skin, people would have to specifically install my slyk1hd skin otherwise this skin will crash.
And as for the colours just look in my slyk1hd skin.xml and use the hex values. i.e #00000000, you cant use named colours like un551a8b, skydarkblue etc.
That is why you have black jaggies around your text. The backgroundColor needs to be blue. Your current colour values are unrecognised and that is why they are coming out black.
Config screen, try using font and secondfont to get the config list elements the same size left and right.
-
<screen name="RemoveTimerQuestion"
as found on channel select... record button... start recording... record button... stop recording... second pop up.
this uses the same autoresize code as messagebox above. So amend with above code.
-
<screen name="MessageBox" ....
and
<screen name="MessageBoxSimple" ....
as found on record button, start recording.
and once recording has started... try restart your gui.
if your messagebox screen in your skin uses
<applet type="onLayoutFinish">self.autoResize()</applet>
change it to below to be scalable until the image builders update their autoresize functions. ( i think this will work )
Python
Display More<applet type="onLayoutFinish"> from enigma import getDesktop, eSize, ePoint import math desktop_w = getDesktop(0).size().width() desktop_h = getDesktop(0).size().height() count = len(self.list) width = int(0.40625 * desktop_w) itemheight = 25 if desktop_w == 3840: scale = 3 elif desktop_w == 1920: scale = 1.5 else: scale = 1 if not self["text"].text: textsize = (width, 0) listsize = (width, int(math.ceil(itemheight*scale)*count)) if self["ErrorPixmap"].visible or self["QuestionPixmap"].visible or self["InfoPixmap"].visible: self["list"].instance.move(ePoint(int(math.ceil(65*scale)), 0)) wsizex = textsize[0]+int(math.ceil(65*scale)) else: self["list"].instance.move(ePoint(0, 0)) wsizex = textsize[0] self["list"].instance.resize(eSize(*listsize)) else: textsize = self["text"].getSize() if textsize[0] < textsize[1]: textsize = (textsize[1],textsize[0]+10) if textsize[0] > width: textsize = (textsize[0], textsize[1]+int(math.ceil(itemheight*scale))) else: textsize = (width, textsize[1]+int(math.ceil(itemheight*scale))) listsize = (textsize[0], int(math.ceil(itemheight*scale)*count)) self["text"].instance.resize(eSize(*textsize)) if self["ErrorPixmap"].visible or self["QuestionPixmap"].visible or self["InfoPixmap"].visible: self["text"].instance.move(ePoint(int(math.ceil(65*scale)), 0)) else: self["text"].instance.move(ePoint(10, 10)) if self["ErrorPixmap"].visible or self["QuestionPixmap"].visible or self["InfoPixmap"].visible: self["list"].instance.move(ePoint(int(math.ceil(65*scale)), textsize[1])) wsizex = textsize[0]+int(math.ceil(65*scale)) else: self["list"].instance.move(ePoint(0, textsize[1])) wsizex = textsize[0] self["list"].instance.resize(eSize(*listsize)) wsizey = textsize[1]+listsize[1] wsize = (wsizex, wsizey) self.instance.resize(eSize(*wsize)) self.instance.move(ePoint((desktop_w-wsizex)/2, (desktop_h-wsizey)/2)) </applet>
-
<screen name="ChoiceBox" ....
if your choicebox screen in your skin uses
<applet type="onLayoutFinish">self.autoResize()</applet>
change it to below to be scalable until the image builders update their autoresize functions.
Inner applet code must be flush to the left in your xml code.
i.e
not
New code
Python
Display More<applet type="onLayoutFinish"> from enigma import getDesktop, eSize, ePoint desktop_w = getDesktop(0).size().width() desktop_h = getDesktop(0).size().height() itemheight = self["list"].getItemHeight() count = len(self.list) if count > 12: count = 12 width = self["list"].instance.size().width() if width < 0 or width > desktop_w: width = int(0.40625 * desktop_w) if not self["text"].text: # move list textsize = (width, 0) listsize = (width, itemheight * count) self["list"].instance.move(ePoint(0, 0)) self["list"].instance.resize(eSize(*listsize)) else: textsize = self["text"].getSize() if textsize[0] < textsize[1]: textsize = (textsize[1], textsize[0] + 10) if textsize[0] > width: textsize = (textsize[0], textsize[1] + itemheight) else: textsize = (width, textsize[1] + itemheight) listsize = (textsize[0], itemheight * count) # resize label self["text"].instance.resize(eSize(*textsize)) self["text"].instance.move(ePoint(10, 10)) # move list self["list"].instance.move(ePoint(0, textsize[1])) self["list"].instance.resize(eSize(*listsize)) wsizex = textsize[0] wsizey = textsize[1]+listsize[1] wsize = (wsizex, wsizey) self.instance.resize(eSize(*wsize)) # center window self.instance.move(ePoint((desktop_w-wsizex)/2, (desktop_h-wsizey)/2)) </applet>
also add in an itemHeight to the ChoiceBox screen.
<screen name="ChoiceBox" ...
<widget name="list" ... itemHeight="30" ... />
then in skin.xml add in the parameter values if they don't already exist by the skin designer.
for example
<parameter name="ChoicelistDash" value="x,y,w,h"/>
<parameter name="ChoicelistName" value="x,y,w,h"/>
<parameter name="ChoicelistIcon" value="x,y,w,h"/>
which in one of my skins will be
<parameter name="ChoicelistDash" value="0,2,800,30"/>
<parameter name="ChoicelistName" value="45,2,800,30"/>
<parameter name="ChoicelistIcon" value="10,3,25,25"/>
A quick way of testing your choice box is to press the record button on live tv.
-
Have you tried faffing with the audio settings like ac3 downmix etc. (box audio settings, not plugin audio settings)
-
Have you possible tried downloading iptv player plugin. Once you run that it updates all the video codecs and relevant files for playing video.
It might help you... it might be a completely different problem. ;)
-
My skins override plugin browsers with parameters in the skin.xml file.
for example.
<parameter name="PluginBrowserIcon" value="15,8,150,60" /> <!-- plugins main icon -->
<parameter name="PluginBrowserName" value="180,5,45" /> <!-- plugins name -->
<parameter name="PluginBrowserDescr" value="180,42,30" /> <!-- plugins description -->
<parameter name="PluginBrowserDownloadIcon" value="15,0,90,75" /> <!-- plugins + - boxed icon -->
<parameter name="PluginBrowserDownloadName" value="120,5,45" /> <!-- plugins download name - see font alias PluginBrowser0 -->
<parameter name="PluginBrowserDownloadDescr" value="120,42,30" /> <!-- plugins download description -see font alias PluginBrowser1 -->
So if these parameter values don't exist in the skin your converting you would have to manually add them.Skinners should be taking advantage of the parameter values as there purpose is to override the default sizes set in the python components.
-
Enigma2 1080 Skin Converter (Version 1.04)
Welcome to my Enigma2 skin converter.
Please note, although this program attempts to automate the process as much as possible, some manually tweaks will always be needed.
Also if upsizing a skin, the graphics are naturally going to look softer and less sharp. Recreate them higher res or ask the skin author. :S
How to use.
Install a skin of your choice on your box then via ftp or samba download the skin folder to your computer.
Select an input folder. Select an optional output folder. Press the convert button of your choice. Note that if you select the same input and output folder this will overwrite all the files, so make sure you are working on a backup folder if this is the case.
You can manually select which elements you want to convert, but unless your are testing the functionality of the program, it is highly recommended to keep everything selected.
There is a test checkbox bottom right, that will fill all the converted values to "00000". This makes it easy to see what elements will actually be changed before you do your proper conversion.
On selecting this test option the program will display an error after the conversion as no valid skin size will be found. This is expected behaviour.
The program works by looking in skin.xml for the vres value to determine the size of the skin. If this cannot be found then it will ask you to manually select the size of the skin to work with. This means you can convert non standard skin folders that might not live in the same root folder. For example Vix Common folders.
On manually selecting a size, after the conversion it will again ask you to input the size. (as it reloads the skin when finished) This second message request will be the size after you converted it.
Finally upload the contents of your converted folder back to your box.
---
Let me know if you find any bugs or strange behaviour.Also note that this program cannot resize elements that are sized in python components or for skins that are built via plugins or scripts.
---
please see additional notes on the following posts to amend paramaters, autoresize() applet, choice and message boxes.
Enjoy.
Not bad for a 1 week project ;)
-------------------------------------------------------------------------------
Version 1.01
Fixed center, start, end position offsets.
Fixed Clock/Record/Zap icons on EPGs.
Version 1.02
Added in corrupt PNG message.
Version 1.03
?
Version 1.04
Removed 4K option. There is no need for it and its confusing people
Allowed fonts with numbers and hyphens in the name to be included.
Added in png:n,n used on some old skins for the progress slider.
-
linuxsat forum is slow at the moment. has been for weeks.
Well I have checked this chaps line, it isn't actually active. So nothing we can do at this moment.
-
you dont rush do you. chop chop I am a busy man.
Click the double speech bubble icon top right. plus sign. Participant KiddaC. Send message.
-
Just pm me your line details, I will check your line is active and send you the correct CCcam.cfg file to use if it is working.
This is going to be a long day otherwise.
-
and if you get it working dont be posting screen shots of your line details. Otherwise it will soon stop working ;)
-
Your line provider won't care as long as its not being abused.
any line in theory can be converted for use in mgcams, cccams or oscams.
It's just a matter of preference of what softcams software you use.
Tomorrows lesson. How to put your line into oscams ;)
-
Converting a Nline for use in CCcam
Your nline might come in the following format.
CWS_KEEPALIVE = 300
CWS_INCOMING_PORT = 21000
CWS = server.com 12345 username password 01 02 03 04 05 06 07 08 09 10 11 12 13 14 # 0000
To convert for use with CCams remove the top 2 lines and replace the last CWS with N:
N: server.com 12345 username password 01 02 03 04 05 06 07 08 09 10 11 12 13 14 # 0000
-
Thats usr/keys (but I presume that was a typo)
and the name of the file is the correct case. It is case sensitive.
CCcam.cfg
and your format is
C: domain.com port username password
or
N: domain.com port username password 01 02 03 04 05 06 07 08 09 10 11 12 13 14
and you created it in a plain text program like notepad or notepad++
-
your CCcam.cfg file goes in usr/keys folder
press yellow button on the above screen. Then select server. And see if you line is shown and is active (green), already used (blue), or inactive (red).
Also you are on a FTA channel on the above screen shot, so you won't be getting any ECM data.