Er zijn 2051 reacties in dit onderwerp

[Raider05]

Thanks for the response. Actually it is a little bit different. Plugins are located in subfolders of Plugins folder. But the way they are called is generally (because this is not the only way) described in plugin.py file for each plugin in its directory. Calling PluginDescriptior with appropriate arguments decides if plugin appears in menu, extensions selection, movie selection etc.
You are righ that in many cases it is enough just to copy the plugin to the right folder. The only thing you have to do is restart enigma or you can do it programatically by calling plugins.readPluginList from Components.PluginComponent but it is more complicated.
You are also right that some plugins are also visible in Menu | Settings | Systems. The problem is that I can see some plugins in local/e2/lib/enigma2/python/Plugins folder and I do know that they should be in Menu | Plugins but they aren't...
However I will try what you suggest and report if it helped.
Thanks again.
Regards.

Oh, and forgot some plugins are visible only when you
BlueButton, on the keyboards - F4

[sek1973]

@Raider09: thanks again.
I think I have found the reason. I checked all missing plugins. They appear in menu or plugin menu only when certain conditions are fulfilled. For example OSDPositionSetup is checking path:

if path.exists("/proc/stb/fb/dst_left"):
  from Plugins.Plugin import PluginDescriptor
  return [PluginDescriptor(name = "OSD position setup", description = "Compensate for overscan", where = PluginDescriptor.WHERE_PLUGINMENU, fnc = main),
	 PluginDescriptor(name = "OSD position setup", description = "", where = PluginDescriptor.WHERE_SESSIONSTART, fnc = startup)]

So it seems that everything is alright now and I have an almost perfect environment to test and debug my work.
By the way. What do you mean by:

make
make install

I suppose I have to install something extra? I haven't installed scripts for making an image. Are they required?
Regards.

[Raider05]

@sek1973, it is
Compile and install plugin for PC.
In most cases it boils down to copying the plugin folder (for example PermanentClock) in the folder
/ usr/local/e2/lib/enigma2/python/Plugins/Extensions. But some plugins (BitrateViewer) to compile (launch make) bitratecalc.cpp.
Yes, the path to change, not in the PC folder / proc / stb
I am writing here with regards to that enigma2-pc, images for DreamBox and etc. never i'm not compile

PS: Sorry for me bad english

[sek1973]

Raider09: thanks again. "make" and "make install" commands doesn't work. I searched my system for "make" file but there aren't any. Do I have to install something?

[betacentauri]

@sek1973: Raider05 refers to post 378. There he told you how to get new plugins. To build these plugins you'll have to use make.
For make see http://linux.about.c...lcmdl1_make.htm. If you wanna build plugins you should know what make do...

[sek1973]

@betacentauri: Thanks again and forgive my lack of experience in linux environment, please - as I pointed earlier it's new to me...
It's quite difficult to recognize all those dependencies at once - what belongs to the system and what is connected with enigma. I really do read other threads and google before asking - I thought make is connected with buiding an image because it was mentioned in dedicated image-building thread.
I'm an old "windows" programmer. I started python programming a few weeks ago, when I have noticed enigma powered STB potential and I'm willing to help to improve and develop the software.
I know some of my questions, perhaps majority of them could be trivial - if there is other place I should ask them let me know.
I just hope my work will be useful...
Regards and please don't be angry.

[betacentauri]

I'm really not angry!
It was only a bit surprising, because in one post I could see that you have coding experiences. So I thought that you'll "have to know" what make is.
Well you can compile things on unix/linux without make. But this is quite unusual...

The best place for questions is a good question I don't know. This is not "my" thread or "my" forum. If it is about openpliPC then put it in here. Otherwise you can try to open a new thread or send a pm to me (if I have time, I try to answer, if you don't have tooooo much questions ).

[betacentauri]

I have a new patch (already available in git):
Some channels didn't work (e.g. WDR Bonn here in Germany). I have fixed that. The problem was that the xine-lib was also reading PAT and PMT packets.
But xine-lib cannot process all "types" of PAT, PMT packets (e.g. big packets which are spanned over more than one pes packet). So xine-lib couldn't decode pids and video/audio wasn't visible.

With this patch I have also fixed the problem with audio channel switching.

And the patch for archlinux is in the git.

Best regards,
Betacentauri

Veranderd door betacentauri, 24 januari 2012 - 22:23

[kerven]

Hi,

If somebody succeed to cleared channels with OScam I would be happy to have the right setup. I saw that OScam is doing what it should but I don't see the channel unscrambled, only FTA channels works. I use vtuner.
r6256 | corsair | 2012-01-18 09:02:59 +0100 (Mi, 18. Jan 2012) | 2 Zeilen

fixed udp long answertimes (>3000ms)

------------------------------------------------------------------------
r6253 | docman | 2012-01-17 13:27:39 +0100 (Di, 17. Jan 2012) | 1 Zeile

Added documentation for
Thanks,

Pr2

hello

may be with oscam 'linux pc" with DVBAPI .

http://www.oscam.to/wbb3/index.php?page=Thread&threadID=160&pageNo=61&highlight=vdr+dvbapi

New OSCam-1-20-unstable-svnrr6256 compiled by @kant@, dax, linch, ulc, gianni8127

WEBIF : on
HAVE_DVBAPI : on <<<<<<<
WITH_STAPI : off
IRDETO_GUESSING : on
CS_ANTICASC : on
WITH_DEBUG : on
CS_WITH_DOUBLECHECK : off
CS_LED : off
QBOXHD_LED : off
CS_LOGHISTORY : on
MODULE_MONITOR : on
WITH_SSL : on
WITH_SSLv3 : on
WITH_LB : on
CS_CACHEEX : on
LCDSUPPORT : on
IPV6SUPPORT : off
ETC.....

LINK for download.. inside..

---------------------

[betacentauri]

in skin.xml (for all skins)

Unless I change the second line from:

<resolution bpp="32" xres="1280" yres="720"></resolution>
to:

<resolution bpp="32" xres="1920" yres="1080"></resolution>

I do not get a full screen (even if I toggle full screen within enigma2)

As a reference I have the same problem with xine but there I fix it by adding
--geometry 1920x1080+0+0 to the xine command line

Is there some way to do the same with enigma2 ?

Hi casacristo,

yes, I can see the problem. But only changing the resolution in the skin is from my point of view not enough. You'll also have
to change the offsets, positions, sizes,... (please correct me if I'm wrong, I never made a skin).

What is that you supposed to archieve with changing resolution?
If you have a full-hd LCD then use normal skin and resize window or use fullscreen. This scales the osd to the window size
(--geometry 1920x1080+0+0 also scales, or not?).

I'll try to find a real full-hd skin and test with that. If there are problems I'll try to fix them.

Regards,
Betacentauri

[Pr2]

Hi,

Thanks for your interest in my problem.

@Betacentauri: I currently rebuilding my environment to test your patch.

@Kerven: my OScam is compiled with DVBAPI and is working fine, it even upgrade my card (EMM) on my server during my test but no cleared picture. I hope that betacentauri patch is the solution.

Pr2

[betacentauri]

I'll try to find a real full-hd skin and test with that. If there are problems I'll try to fix them.

I found a full hd skin. There are no such problems with that skin.

[Pr2]

Hi,

Patch doesn't work for me to display a cleared image with OScam.
If somebody make OpenpliPC working with OScam or any other emu, please let me know.

Thanks,

Pr2

[betacentauri]

Pr2 and I have found the trick to unscramble channels with the openpliPC.
You need to create a kernel module. These are the steps to do:

cd enigma2/dvbsoftwareca
make
sudo cp dvbsoftwareca.ko /lib/modules/`uname -r`/misc
// If directory doesn't exist, create it
sudo depmod -a
sudo modprobe dvbsoftwareca

And you also need an installed/configured softcam (sorry, I cannot help here!).

That's not my code!
We have to thank cougar for developing it and nobody9 for building openpliPC!!!

Regards,
Betacentauri

Veranderd door betacentauri, 25 januari 2012 - 22:13

[Pr2]

Hi,

Just some few tips for people that use vtuner.

-> It is useless to autoload dvbsoftwareca at PC boot, because vtunerc.i686 must be running before: sudo modprobe dvbsoftwareca
-> OScam needs to be compiled with DVBAPI enabled (be carefull for people that use easy-build it automatically disable DVBAPI for the i686 executable even if you enable it!).
-> OScam needs to be run as root: sudo oscam -c /path/to/your/config
-> start OpenpliPC: sudo /usr/local/e2/bin/enigma2

When you close enigma2 and that you restart it it will no longer works!

To reenable everything properly (without rebooting the PC) follow those steps:

- stop enigma2
- stop oscam
- stop vtunerc

Type:

sudo rmmod dvbsoftwareca

- start vtunerc again: sudo vtunerc.i686 -f s2

Type:

sudo modprobe dvbsoftwareca

You can check that dvbsoftwareca is running fine by doing:

ls /dev/dvb/adaptor0

You should see: ca0 demux0 dvr0 frontend0
ca0 is the one created by dvbsoftwareca

start oscam: sudo oscam -c /path/to/your/config
start enigma2: sudo /usr/local/e2/enigma2

You will retrieve the good working between OScam and OpenpliPC without rebooting your PC.

So it is advices to create a small script that will start and stop properly all the module associated with openpliPC to ease your life.

Pr2

Veranderd door Pr2, 25 januari 2012 - 22:30

[Raider05]

With this patch I have also fixed the problem with audio channel switching.

@betacentauri, thanks
Now I can not test the software as it works, SAT is not connected at work, but when you view the my entries I have crash enigma2

video_overlay:No spare subtitle event slots

Movies look without any problems. And now working XINE_PARAM_VO_ZOOM_X XINE_PARAM_VO_ZOOM_Y?

[Raider05]

@betacentauri,
and please change it

[betacentauri]

Now I can not test the software as it works, SAT is not connected at work, but when you view the my entries I have crash enigma2

video_overlay:No spare subtitle event slots

Movies look without any problems. And now working XINE_PARAM_VO_ZOOM_X XINE_PARAM_VO_ZOOM_Y?

Hi Raider05,

sorry, I don't understand your sentence: "but when you view the my entries I have crash enigma2". What is "my entries"? Is it the filelist where you can see the recorded files?

I have nothing changed for these parameters (XINE_PARAM_VO_ZOOM_X, XINE_PARAM_VO_ZOOM_Y).
(I think I'll have to read the thread from beginning... you have most probably posted the problem before).

At first I wanna fix another problem with window resizing (sometimes window changes size many times a second).
Afterwards I'll look at your problems.

Regards,
Betacentauri

[Raider05]

@betacentauri,
sorry, I incorrectly wrote
I want play my recorded files, it is't the filelist.

Thanks for the earlier

[casacristo]

Thanks for the arch patch and audio switch, I will test the new git tomorrow.
As for the resolution, well selecting full screen (or F11) do not work as intended (it crashes the whole thing)
and --geometry 1920x1080+0+0 has no effect.
You are right that editing the skin.xml and putting 1920x1080 there is far from perfect as the offset are all wrong, but at least you get full screen video.
I have searched in vain for a native full-HD skin that would run native at 1920x1080 hence no enigma2 scaling would be needed.

in skin.xml (for all skins)

Unless I change the second line from:

<resolution bpp="32" xres="1280" yres="720"></resolution>
to:

<resolution bpp="32" xres="1920" yres="1080"></resolution>

I do not get a full screen (even if I toggle full screen within enigma2)

As a reference I have the same problem with xine but there I fix it by adding
--geometry 1920x1080+0+0 to the xine command line

Is there some way to do the same with enigma2 ?

Hi casacristo,

yes, I can see the problem. But only changing the resolution in the skin is from my point of view not enough. You'll also have
to change the offsets, positions, sizes,... (please correct me if I'm wrong, I never made a skin).

What is that you supposed to archieve with changing resolution?
If you have a full-hd LCD then use normal skin and resize window or use fullscreen. This scales the osd to the window size
(--geometry 1920x1080+0+0 also scales, or not?).


I'll try to find a real full-hd skin and test with that. If there are problems I'll try to fix them.

Regards,
Betacentauri