Hello,
On So, Jan 28, 2007 at 06:03:56 +0100, Michael Brueckner wrote:
> Am Sonntag 28 Januar 2007 17:59 schrieb Kartsa:
> > I thought I had the newest one? Where do I find a newer one? In the
> > README file there is http://www.xeatre.tv/community/burn/ which is
> > supposed to have the latest v
Sorry the cvs stuff does not work.
I have taken it from vdr-wiki.
Halim
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Hello,
Cddb is working fine but no cd-text output was shown.
I am using cdda-0.1.0.
Any ideas?
Halim
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Hello,
On Mo, Jan 29, 2007 at 06:43:40 +0100, Klaus Schmidinger wrote:
> Yes, I do plan to do this. Yesterday I've installed my DVB-S2 card in
> a test box, so hopefully I'll be able to start digging into this one
> of these days...
FF-Card???
Halim
___
Hi,
Open plugins Makefile
Search and replace VDRVERSION
with APIVERSION.
On Mi, Jan 31, 2007 at 11:26:20 +0100, [EMAIL PROTECTED] wrote:
> When I try to compile the mldkgui I get the following message:
> ERROR: plugin mldkgui doesn't honor APIVERSION - not compiled!
>
>
> Cheers
> H.Braun
>
Hello,
Today I spent a lot of time to find out what
is wrong there:
Here comes a small sylog output:
Feb 8 23:22:58 vdrbox vdr: [3480] info: Aufzeichnung gestartet
Feb 8 23:22:58 vdrbox vdr: [3516] file writer thread started (pid=3480,
tid=3516)
Feb 8 23:22:58 vdrbox vdr: [3517] recording thr
Hello,
My problem was not the audiorepackager(xxx).
I found some threads about these error in vdr-portal and
modified vdr to get some more debug output.
There were a lot of ts continuity errors reported through syslog.
My machine has a athlon xp 1500 cpu and runs on a asrock mainboard with
sis c
Hello
I found this in my syslog:
dvb-ttpci: __av7110_send_fw_cmd(): timeout
waiting for COMMAND
idle
dvb-ttpci: av7110_send_fw_cmd(): av7110_send_fw_cmd error -110
dvb-ttpci: av7110_fw_cmd error -110
What is the reason for this?
I am searching what causes my ts-continuity errors while recording
these values ok or not?
Can someone compare these output with the same card?
Thanks
--
Halim Sahin
E-Mail:
halim.sahin (at) t-online.de
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Hello,
>
> I have similar values (tt 2300):
> status 1f | signal aef8 | snr d66e | ber | unc | FE_HAS_LOCK
> status 1f | signal aef4 | snr d680 | ber | unc | FE_HAS_LOCK
> status 1f | signal aefb | snr d62f | ber | unc | FE_HAS_LOCK
> status 1
Hi,
On Mi, Feb 21, 2007 at 02:20:15 +0100, bastlir wrote:
> On Wednesday 21 February 2007 14:03, Halim Sahin wrote:
> > Hello,
> >
> > HMM what do you mean?
> > I am getting these errors on all transponders.
>
> I meant to test as well on channel with high bitrate
Hi,
Do you know the PLUGINS.html file in vdr's source tree?
Halim
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Hi,
On Mi, Feb 21, 2007 at 07:59:18 +0200, Kartsa wrote:
> Reinhard Nissl kirjoitti:
> >I had a look into the files you've provided me. It looks like some TS
> >packets get lost. You can simply check this on your own:
> >
> > od -Ax -t x1 -w188 -v ts_10973_11079_0xC0_004_116796_1000.log \
> >
201 - 213 of 213 matches
Mail list logo