VDR und Skystar2 als 2 Karte läuft

Zitat

Original von SvenS
Hi,

hast Du eine DXR3 oder eine andere KArte mit Hardware MPEG Decoder? Wenn nicht muckt VDR rum will sagen momentan geht das nicht ohne.

bye

Sven

Alles anzeigen

Doch mit dem Xine-Plugin, aber ob nun genau diese Karte, weiß ich auch nicht.

MFG Ronny

Ja aber nur die Funktion, habe die Hardware nicht.

http://www.vdrportal.de/board/thread.php?threadid=5432&sid=

In der ML gab es jedenfalls ein paar User das richtig am laufen haben (mit nur ner passiv card).

Was ich bis jetzt hier gesehen habe, war es flüssig, stimmt ist erst (0.0.2) aber was will wer machen der keine Active Card sein eigen nennt?

Der sieht ohne Xine-Plugin sowas: no primary found!

Memed hat ja auch schon was dazu gepostet:

http://www.vdrportal.de/board/thread.php?threadid=5205&sid=

Werde mir auch mal die Hardware besorgen müssen.

MFG Ronny

Was ist denn das für eine Karte? Skystar2 .......... hat die nen MPEG Chip drauf oder nicht? Im Makefile steht doch was mit drinnen b2c2 ist das die?

CARDS = av7110
#CARDS += margi
#CARDS += em8300
CARDS += b2c2

Sorry habe aber auch den Pfaden verloren, glaube mal im Topic gelesen zu haben:

VDR und Skystar2 als 2 Karte läuft

Und nicht:

VDR und Skystar2 läuft

MFG Ronny

Würde mich aber trotzdem vorher schlau machen ob eine "Skystar" langt.

Nova konnte ich in der ML schon lesen, müßte doch aber das selbe sein, die hat auch keinen MPEG Chip, glaube schon das das geht.

Habe es wie folgt installiert:

http://www.vdrportal.de/board/thread.php?threadid=5432&sid=

Steht auch alles in der README des Plugins.

MFG Ronny

Zitat

Original von In Flames
Hab das jetzt ehrlich gesagt nicht ganz gblickt was ich damit machen muss, ist doch ne RPM, oder? dass geht doch automatisch.

Ich denke das ist dieser hier, oder?

http://linuxberg.proxad.net/preview/161269.html

Danke

Alles anzeigen

As you can read these lines, you've successfully extracted the tar archive of VDR plugin xine.

Usually, the contents of this package should be below the PLUGINS subdirectory of VDR. I've installed VDR in directory "/soft/src/VDR", so the files of this package reside in directory "/soft/src/VDR/PLUGINS/src/xine".

To compile and use this plugin, you must get a recent CVS version of xine. Go to the project homepage of xine which is http://xine.sf.net. After entering the main page, look for downloads and then for CVS. Follow the instructions in this page and checkout at least module "xine-lib". You might also need a recent version of a GUI for xine, so checkout module "xine-ui". I've checked out both modules and they reside in directory "/soft/src/xine-lib" and "/soft/src/xine-ui" respectively.

Next, you have to extend xine-lib to support a media resource location (mrl) named "vdr:". Change to the parent directory of module "xine-lib", e. g. in my case "/soft/src". Then apply the patch supplied with this distribution. In my case, the command looks like that: "patch -d. -p0 < /soft/src/VDR/PLUGINS/src/xine/input-plugin/xine-lib.patch". Now change to the directory below module "xine-lib" where the sources for input plugins reside, e. g. "/soft/src/xine-lib/src/input", and create symbolic links to the sources of the new input plugin for xine. In my case the command is: "ln -s /soft/src/VDR/PLUGINS/src/xine/input-plugin/input_vdr.* .".

It's time now, to build xine-lib. Change back to the directory of module "xine-lib", e. g. "/soft/src/xine-lib" and run "./autogen.sh". This will create all the files which configure needs, and finally runs configure. If you need special options for configure, you can specify them as command arguments to autogen.sh. E. g. in my case, I run the following command: "./autogen.sh --prefix=/soft/xine-lib-cvs --enable-debug". But usually it's sufficient to just run "./autogen.sh". As xine supports a lot of media, it also requires a lot of libraries to compile all modules. Please see the file "config.log" and the xine documentation to get all the required components for the plugins you want to build. After configure was run (automatically from autogen.sh), the commands "make" and "make install" should provide you with a recent version of module "xine-lib". After that, you can go to the directory of module "xine-ui" and repeat the steps for building the standard GUI for xine. Please test the newly compiled xine with a sample MPEG file, to see if it works. Be careful, that not any previously versions of xine respectively the plugins gets loaded.

The next step should be to build the VDR plugin. Change the directory to VDR, e. g. "/soft/src/VDR", and type "make plugins". This should compile my plugin for VDR.

To test the plugin, the filesystem must be prepared first. Change to your "video" directory, e. g. "/video", and make a directory "xine", e. g. "md xine". Next, change to the newly created directory and create four fifos, e. g. "mkfifo device0.vdr device1.vdr device2.vdr device3.vdr". You'll need one fifo per device and the plugin currently supports four devices.

REQUIREMENTS: for the initial release of my plugin, you must already have a configured input device, e. g. your keyboard or your remote control. Furthermore, you must have a working configuration, so that VDR supplies a live video to my device. If you cannot fulfill these requirement, you won't see anything in the xine window, because xine is showing an OSD only after a stream has been startet. For now, I haven't created a stillframe stream (e. g. with VDR logo), that I could supply to xine on connect to VDR, to make the OSD visible e. g. for teaching the remote control to VDR.

For a first run, go to the VDR directory (e. g. "/soft/src/VDR") and type "./runvdr -Pxine" to have VDR load my plugin. Now, at any time, you can use xine to connect to any of the above mentioned fifos. The MRL looks like this: "vdr://video/xine/device0.vdr#demux:mpeg_pes". Although my plugin supplies four devices, only the first one will receive the live picture and OSD of VDR, while the others receive nothing, at least for now.

I hope, this file is sufficient to get the stuff working