Pierre-
In Debian, first blacklist the DVB modules in the /etc/modprobe.d/blacklist file:
# DVB Modules
blacklist dvb-ttpci
blacklist bttv
blacklist bt878
blacklist dvb-usb-gp8psk
# end DVB Modules
Then look in /etc/udev/rules.d. The files there control module loading. I created a new file 010_DVB.rules and inserted the following information there (derived from udevinfo) :
KERNEL=="dvb*", ATTRS{vendor}=="0x1131", SYMLINK+="dvb-nexus", PROGRAM="/bin/sh
-c 'K=%k; K=$${K#dvb}; printf dvb/…
[View More]adapter0/%%s $${K#*.}'", ACTION=="add", NAME="%c"
KERNEL=="dvb*", ATTRS{serial}=="00221", SYMLINK+="dvb-gpix0 PROGRAM="/bin/sh -c
'K=%k; K=$${K#dvb}; printf dvb/adapter1/%%s $${K#*.}'", ACTION=="add", NAME="%c"
KERNEL=="dvb*", ATTRS{serial}=="00529", SYMLINK+="dvb-gpix1 PROGRAM="/bin/sh -c
'K=%k; K=$${K#dvb}; printf dvb/adapter2/%%s $${K#*.}'", ACTION=="add", NAME="%c"
As you can see, I have one Nexus FF card and two genpix USB adapters. My UDEV lines identify each device specifically, assign the dvb device node in /dev, and create a symlink with a identifiable device name (I use this in other init scripts to verify the device is present). Then I load the modules with an init script in /etc/init.d. The script loads my LCD driver, runs setpci to set latency for my nexus card, then loads the Nexus and two Genpix modules. The init script also makes it simple to unload all of the drivers without a reboot using "/etc/init.d/DVBsetup unload".
So there you go. A combination of blacklisting the modules, a UDEV script, and a startup script and you have full control of your /dev nodes and the boot-time load order of the modules.
Hope that helped!
-Todd
[View Less]
Op Do, 22 januari, 2009 21:27, schreef Jouni Karvo:
> Goga777 kirjoitti:
> -- SNIP --
> Good to know. The include and linking parameters for autogen.sh solved
> the compilation problems, and were probably my main message, though.
> xine-lib 1.2 hg is (I guess) compatible with an older version of ffmpeg
> than the repository one.
>
Strange. I compiled x264, ffmpeg and xinelib 1.2 from the repositories
like last weekend, and I didn't encounter any problems at all with the
…
[View More]compilation. And it works without problems with vdr-xine 0.90 and the
xineliboutput CVS with VDR 1.7.0.
I used the following configure and autogen.sh on a Xubuntu 8.04
configuration running on a Core2Quad 6600 config with an X86-64 kernel:
x264:
./configure --enable-pic --enable-shared --enable-pthread --enable-asm
--extra-cflags="-mtune=native -march=native -mfpmath=sse -O4 -pipe"
ffmpeg:
./configure --prefix=/usr --enable-shared --enable-gpl --enable-postproc
--enable-libmp3lame --enable-libvorbis --enable-pthreads --enable-swscale
--enable-libx264 --extra-cflags="-mtune=native -march=native -mfpmath=sse
-O4 -pipe"
Xine-lib 1.2
./autogen.sh --prefix=/usr --disable-dxr3 --enable-w32dll
--with-w32-path=/usr/local/lib/win32
Regards,
Niels Wagenaar
[View Less]
hi,
I just compiled the hg xine-lib 1.2 with SVN ffmpeg. In case someone is
interested in the same, these are the options required for xine-lib:
./autogen.sh --with-external-ffmpeg
CPPFLAGS="-I/usr/local/include/libavcodec
-I/usr/local/include/libavdevice -I/usr/local/include/libavformat
-I/usr/local/include/libavutil -I/usr/local/include/libpostproc
-I/usr/local/include/libyasm -I/usr/include"
FFMPEG_LIBS="-L/usr/local/lib -lavcodec -lavformat -lavdevice -lavutil -lz"
After this, a simple …
[View More]make + make install works.
To get xine-ui to compile, I needed to
* change the order of the lines starting datadir= and datarootdir= in
/usr/local/lib/pkgconfig/libxine.pc, and give
* give the pkgconfig-parameter: ./configure
PKG_CONFIG_PATH="/usr/local/lib/pkgconfig"
...and again, then a simple make + make install will work.
Seems to work now - haven't tested H.264 yet, though.
yours,
Jouni
[View Less]
I'm getting tons of messages like...
----
Jan 21 18:16:47 lassehome vdr: [4716] [input_vdr] vdr_plugin_write: PES too long (17843 bytes,
max size 8192 bytes), data ignored !
Jan 21 18:16:48 lassehome vdr: [4716] [input_vdr] get_buf_element: big PES (50251 bytes) !
Jan 21 18:16:48 lassehome vdr: [4716] [input_vdr] vdr_plugin_write: PES too long (50251 bytes,
max size 8192 bytes), data ignored !
Jan 21 18:16:48 lassehome vdr: [4716] [input_vdr] get_buf_element: big PES (15743 bytes) !
Jan 21 18:…
[View More]16:48 lassehome vdr: [4716] [input_vdr] vdr_plugin_write: PES too long (15743 bytes,
max size 8192 bytes), data ignored !
Jan 21 18:16:48 lassehome vdr: [4716] [input_vdr] get_buf_element: big PES (13100 bytes) !
Jan 21 18:16:48 lassehome vdr: [4716] [input_vdr] vdr_plugin_write: PES too long (13100 bytes,
max size 8192 bytes), data ignored !
----
VDR-1.7.3, xinelibout-1.0.3, drivers from http://linuxtv.org/hg/v4l-dvb/
Whats up duck ?
[View Less]
Hi all,
Anybody here is familiar with xinilibout code?
Or maybe it's a generic concept of plugins that I don't really know...
What is assigned to "input_vdr->f.input_control"? I couldn't find
initialization place.
Don't know if it makes a different, but vdr-sxfe is run with --lirc switch.
I hate pointers to functions!
static void process_xine_keypress(input_plugin_t *input,
const char *map, const char *key,
int repeat, int release)
{
/* from UI --> …
[View More]input plugin --> vdr */
LOGDBG("Keypress: %s %s %s %s",
map, key, repeat?"Repeat":"", release?"Release":"");
if(input) {
vdr_input_plugin_t *input_vdr = (vdr_input_plugin_t *)input;
if(input_vdr->f.input_control) {
input_vdr->f.input_control(input, map, key, repeat, release);
} else {
LOGMSG("Keypress --- NO HANDLER SET");
}
} else {
LOGMSG("Keypress --- NO PLUGIN FOUND");
}
}
Thanks.
[View Less]
>> I tried to look at the old subtitle plugin and how it
>> was done there but couldn't see how to apply that to
>> the subtitle handling that vdr does.
>
>I suppose you're talking about dvb subtitles.
>Per chance, are you seeing the problem on ITV3 (Eurobird 1/Astra 2)?
Yes, I am talking about the dvb subtitles.
Here the subtitles are in sync when watching live. But when
I try to watch a recording I get the subtitles 6 seconds too
early. If I understood it …
[View More]correctly the reason for this is known.
This explains the reason:
http://www.linuxtv.org/pipermail/vdr/2008-October/018072.html
but not the cure :)
Regards,
Josce
[View Less]
Hello all,
Please help me with remote control configuration since I'm breaking my head
on a wall for more than a week already. RC is the only thing at the moment
that stops me using the VDR as my main TV source.
I've bought a nifty (and cheap) remote and a nice USB receiver. Looks like a
clone of MCE remote. It has a small joystick to control the mouse.
The USB receiver pass keyboard and mouse events to the system, so I can use
it instead of my keyboard without any LIRC configuration.
BUT, I …
[View More]do want to use LIRC since I want to bound one of the buttons for
other tasks (such as switching to XBMC or running vdr-sxfe to pass sound to
my sound system instead of the TV).
irw works ok.
I've set /etc/lircrc to pass the commands to vdr-sxfe and ircat shows them
successfuly.
I've added some commands such as LIRC.Volume+ and LIRC.Volume- manually to
remotes.conf, but it doesn't really help.
I can run vdr-sxfe with --lirc and see that it receives the codes direcly
without my lircrc configuration, but it will miss many features since some
of the RC buttins send sequnce of keys, which can be catched using lircrc
configuration.
Without specifying --lirc, vdr-sxfe seems to receive the keyboard commands
instead the commands from LIRC.
Can anyone help me please?
People who have the original MCE remote, does your IR receiver also pass
keyboard commands to the system?
I saw that as soon as there is a connection to lircd (such as with irw or
ircat) the keyboard events are not passed the system any more and that's
good, but vdr-sxfe doesn't connect unless I'll use the --lirc switch.
I'm stuck with that.
Any help will be appreciated.
Thanks.
[View Less]
I'm looking at moving from Italy to the US in the summer and am trying
to spend my time (while not highly preoccupied about health insurance,
jobs, houses, shipping etc) trying to think through taking my VDR setup
and Dreambox over to the US.
I currently have a couple of Hauppauge DVB-S cards (a Nexus and a Nova)
and a Hauppauge DVB-T card in the setup for digital terrestrial. I am
wondering in the US if I should go with ATSC or Dish/Direct TV (or
both). I'm aiming for Rockford, Illinois …
[View More]which has ATSC coverage. I
have three vomp boxes hanging off the VDR server which I was planning to
take with me. These currently connect with RGB Scart to my TV's. Then
the dreambox 800 connects with HDMI.
So, would the DVB-T card just work with ATSC or is it fundamentally
different (like DVB-C is different to DVB-S). In which case should I get
a USB ATSC dongle or two?
How do you connect an RGB Vomp box to an American TV or should I get a
couple of Scarted LCD's before I leave here? Is anything available with
Scart in the US?
My cousin says that a hotel near here is selling off it's 20" TV's for
$25 each, is it worth it (I'm guessing thanks to the digital switch off)?
If I go down the sat route, can I just stick a dish or direct tv card in
the phoenix reader I use for Sky Italia and decode it with vdr-sc /
CCcam? (Whatever happen I would be wanting a valid sub to watch what I
want to.)
The dreambox should display HD, as long as I have the rights to view it?
Should I stick with Sat with that or go on the search for an ATSC card?
Am I just overcomplicating life? Would I be better off just buying some
ATSC set top boxes when I get there. Vomp/VDR was the only satisfying
way of watching UK tv in Italy in any quality for us.
Thanks for your ideas..
--
Latest news on http://www.stpixels.com/view_blog.cgi?user=66685
Rob Davis
[View Less]
Hi all,
as my hardware is shipping (went for the ASUS M2N78Pro, GeForce 8300
with an Athlon X2 4850e, hopefully that'll work with VDPAU and HD
videos), it's now time to choose a DVB-S/2 card.
I consider the TT 3200 and with a slight preference the Haupauge
HVR-4000 (drivers in the kernel since 2.6.28 seems a bit more
comfortable). The only point I'm unsure about is the Haupauge WinTV
CI-module USB. Does anyone know about its linux compatibility?
Or do you recommend the TT 3200 if I need an …
[View More]CI module?
And the second question is about the preferred distribution to use VDR
with. Are there any distributions optimized for VDR and fast boot times?
(Yes I know [1], but that didn't help me with choosing one optimized for
short boot times.) LinVDR seemed to be such, but the last version is now
4 years old. I personally have experiences with Gentoo and Debian, so
that would be my choices if no one has a better option worth trying.
Greetings
-Sascha-
[1]http://www.vdr-wiki.de/wiki/index.php/%C3%9Cbersicht_Software#Distributionen
[View Less]