Hello VDR readers,
I try to use pass through with softdevice.
When I use the following options I get always the same error after
start a 5.1 file:
# ac3play: sound open: no such file or directory.
I start the vdr with:
-P"softdevice -vo dummy: -ao alsa:ac3=iec958:AES0=0x02,AES1=0x82,AES2=0x00,AES3=0x2#"
or with the options in the setup.conf:
softdevice.AC3Mode = 1
softdevice.AlsaAC3Device = iec958:AES0=0x02,AES1=0x82,AES2=0x00,AES3=0x2
softdevice.AlsaDevice = default
When I run a 5.1 …
[View More]file with ac3dec all
works fine.
What must I do to get the pass through?
--
Best regards Sebastian
ICQ: 264706583 | MSM: sebo(a)blinzeln.de | Skype: sebo_de
E-Mail: sebo(a)blinzeln.de | Web: www.blindzeln.de
[View Less]
Hello list,
I'm building a VDR machine with Gentoo and VDR 1.4.6. I'm going to use
VDR with the smartcard of the Dutch Canal Digitaal.
I already have a Common Interface slot, and now I need to buy a CAM.
Accoording to
http://www.vdr-wiki.de/wiki/index.php/Conditional_Access_Modul there are
some CAM's which are working with VDR. On the
http://gathering.tweakers.net/forum/list_message/27016439#27016439 forum
the Canal Digitaal MediaGuard CAM
(http://webshop.canaldigitaal.nl/article.asp?…
[View More]articleId=15434) was
described as "not very reliable", and I can't find it on the VDR wiki as
well. The Matrix and Aston from the gathering.tweakers.net is found on
the wiki, but is not supported by VDR.
On the wiki are the following CAM's which support SECA and SECA 2 and
are supported by VDR:
AlphaCrypt Twin, Diabol Cam / Dragon Modul (Rev. 4.1) / T-Rex, Reality
Cam, Super Joker, Zeta blau, Irdeto Access.
My question to you all is: Has anyone one of the above CAM's working
with a standard VDR ?
[View Less]
Hi,
With vdr 1.4.5 + dvd, dvdselect and subtitles plugins I sometimes get the
following
when vdr tries to set the System time.
May 31 20:23:35 localhost vdr: [3405] switching to channel 1
May 31 20:23:35 localhost vdr: [3405] timer 1 (3 2056-2210 'News') set to
event Thu 31.05.2007 21:00-22:00 'News'
May 31 20:23:38 localhost vdr: [3413] System Time = Thu May 31 20:23:38 2007
(1180632218)
May 31 20:23:38 localhost vdr: [3413] Local Time = Thu May 31 20:19:37 2007
(1180631977)
May 31 20:21:…
[View More]01 localhost vdr: [3405] PANIC: watchdog timer expired -
exiting!
Could vdr turn off the watchdog before it sets the system time, if that is
the problem?
Josce
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
[View Less]
Hi,
When I switch from any channel to channel 1 ( ARD / Das Erste ). it
happens sometimes that the vdr-??fe freezes.
I have tried vdr-fbfe and vdr-sxfe, and xineliboutput 1.00rc2 and also
the cvs version.
The error was not always the same:
with vdr-fbfe I have to kill and restart it, with vdr-sxfe the screen
blanks on channel 1 and I can zap to other channels which were fine, but
back to 1 gets a blank screen. After restarting vdr-sxfe everything's
fine again.
Any hints what's causing …
[View More]this problem ?
--
Helmut Auer, helmut(a)helmutauer.de
[View Less]
Trying to get a Genpix working with VDR.
I thought my troubles started when Reinhard posted his new
vdr-1.5.12-h264-syncearly-framespersec-audioindexer-fielddetection.diff
cause I got compile errors, (should of known better).
But after digging back thru all the old patches I could find I believe this
has been wrong for awhile.
What is/was wrong was that the ‘switch (frontendType)‘ function did not open
and close the ‘{‘ ‘}’ properly (thankz Reinhard for pointing it out) after
the patch.
…
[View More]The original code is like this
switch (frontendType) {
case FE_QPSK: { // DVB-S
The patched code looks like this
switch (frontendType) {
case FE_QPSK: // DVB-S
case FE_DVB_S: // DVB-S
case FE_DVB_S2: // DVB-S
As you can see the last ‘{‘ is missing and a ‘}’ had tobe removed later down
in the code to make things happy. That is why I wonder how the patch has
been working in the past.
I tried to add the ‘{‘ in after the S2 and leave the removed 1 in but it
wouldn’t compile, (figured that be too easy).
What I have done is put the original ‘case FE_QPSK: { // DVB-S’ routine back
into dvbdevice.c and have added a new ‘case FE_DVB_S: { // DVB-S’ that
mirrors ‘case FE_QPSK: { // DVB-S’ routine and made a new ‘case FE_DVB_S2: {
// DVB-S’ routine under the switch.
I am no coder by any means but can cut and paste with the best of them. It
does seem to patch and compile fine but really unsure if what I did will be
ok.
Was wondering if someone with a little more knowledge than me could take a
look @ the patch and see if it all looks ok.
Thankz
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.503 / Virus Database: 269.16.9/1155 - Release Date: 11/27/2007
8:30 PM
[View Less]
Hi,
I'm pleased to announce the long awaited release 0.8.0, which integrates
the vdr-xine-network patch. You can find it on my homepage:
http://home.vr-web.de/~rnissl
Excerpt from HISTORY:
2007-10-24: Version 0.8.0
- Frame duration was not set correctly in xine-lib for H.264
frames, causing frame drops an non fluent playback.
- Added network patch (thanks to Tobias Grimm for supplying it).
Although I had planned to optimize it to just use one port and
only two sockets, I decided …
[View More]to release it in its current state
instead of waiting further years. I've just modified it to use
a more xine-like MRL netvdr://host:port#demux:mpeg_pes where
port is optional (defaults to 18701). The fifo MRL should now
be written vdr://tmp/vdr-xine/stream#demux:mpeg_pes, although
a single slash will still work, too.
- Updated et_EE.po (thanks to Arthur Konovalov for supplying
the file).
- Fixed a bug in vdr-xine's buffer handling for live TV mode
which got most noticeable when switching back from a H.264
channel to a MPEG2 channel, especially when the machine was
not capable of playing the H.264 stream in real time. As the
buffer was not cleared when switching channels, old H.264
data was sent to xine instead of new MPEG2 data, which caused
xine to incorrectly switch to H.264 mode. This behavior could
lead to a crash in FFmpeg later.
- Fixed OSD handling in vdr-xine as certain subtitles could cause
a memory corruption in xine (thanks to Arthur Konovalov for
providing sample recordings).
Enjoy.
Bye.
--
Dipl.-Inform. (FH) Reinhard Nissl
mailto:rnissl@gmx.de
[View Less]
Hi mailing list,
using analogtv I get from video out of my dvb card blue faces. How
can I solve this?
My configuration with problem:
Lifeview FlyDVB trio
Technotrend S-2300
modprobe saa7134 oss=1
modprobe saa7134_oss
modprobe dvb-ttpci
vdr-1.5.11 + AnalogTV patch (from e-tobi.net repository)
analogtv 1.00-11 (with mp1e from same distribution patched for
analogtv)
I've read that sometimes blue face can be corrected by changing Y, Cr, Br
with Y, Br, Cr, but. how to do so? There is …
[View More]a patch for mp1e?
The problem seems to be caused by a wrong video format used by saa7134
module and mp1e.
My other machine, with bt878 based card and xineliboutput, shown the right
picture.
Regards, Eddi
[View Less]