On Mon, 28 May 2001, Ralph Metzler wrote:
> > plaing back with 0.0.4 .
>
> Just for the audio underflow problem such re-arranging could be
> enough. It is probably a lot less overhead than a complete re-muxing.
>
>
> > It is professional quality really, after more the 15 tapes produced th
Uwe Freese writes:
> - -recorded a TV production (series, talk show,...) that is
> "interlaced"
>
> - -converted with "mplex -t DVD ..." into a vob file (mplex from
> mpegtools that comes with the DVB drivers package)
>
> - -in the resulting video I have the video fields in this order:
Uwe Freese wrote:
>
> An important question for me is if VDR makes a difference between
> interlaced and progressive material when storing it in vdr files and
> if mplex makes this difference.
VDR simply reads the data from the driver, does a little repacking and
stores it into a file. On replay
-BEGIN PGP SIGNED MESSAGE-
Hello,
I noticed a really strange thing with "interlaced" videos recorded
with VDR:
- -recorded a TV production (series, talk show,...) that is
"interlaced"
- -converted with "mplex -t DVD ..." into a vob file (mplex from
mpegtools that comes with the DVB d
Stefan Huelswitt writes:
> maybe I'm a bit impatient, but this tunning problem makes my VDR
> box nearly unusable and I wanted to ask if any of the developers
> is working on this (never saw a note about).
Not really (I don't have this card) but I accept patches.
The tuning is all open source
>> .) would it be possible to see if a channel can.t be encrypted?
>> i mean: sometimes VDR (or the as*on CAM) hangs, and i can.t
>> tell which one. so i have to restart the drivers, for the
>> CAM to reset. if VDR would check the transfer to/from the CAM,
>> it could tell me if there is a problem
Hi all,
maybe I'm a bit impatient, but this tunning problem makes my VDR
box nearly unusable and I wanted to ask if any of the developers
is working on this (never saw a note about).
Just to remember, the problem is that i only have a 50% chance
of getting a tuned channel (doesn't matter if VDR
Jan Panteltje writes:
> > > 3. Audio "chopped" during replay
> >
> > These will be fixed in the next version.
> > Some channels really seem to have a big offset between audio and
> > video and if the video buffer is too small, the audio for the video
> > data at the buffer exit sometimes h
Szymon Polom wrote:
>
> This message has been forwarded to the right list :) ->
>
> Original Message
> Subject: [linux-dvd] video scrambling
> Date: Mon, 28 May 2001 11:11:06 +0200 (MET DST)
> From: Michal Jeczalik <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> CC: [EMAIL PROTEC
Johannes Schoeller wrote:
>
> ideas for VDR:
>
> .) it would be great when audio was muted during channel
> switching, because now you sometimes have a squeaking sound
> when the channel is syncing. if the volume is turned up,
> i think my ears will collapse. :))
Actually VDR tries to do that:
Jan Panteltje wrote:
>
> On Mon, 28 May 2001, Ralph Metzler wrote:
>
> > Klaus Schmidinger writes:
> > > 1. Audio loss with Pause/SlowMotion/Continue
> > >
> >
> > See my reply in my last mail (a few minutes ago).
> >
> >
> > > 2. Audio loss during normal replay
> > >
> > > 3. Audio "choppe
Ralph Metzler wrote:
>
> Klaus Schmidinger writes:
> > > adjusted the buffer until the dropouts went away. If they still occur
> > > I will have to reclaim more memory.
> >
> > Arghh, that's too bad. The OSD is already quite a compromise as it is.
> > Making it even smaller will hurt VDR qui
On Mon, 28 May 2001, Ralph Metzler wrote:
> Klaus Schmidinger writes:
> > 1. Audio loss with Pause/SlowMotion/Continue
> >
>
> See my reply in my last mail (a few minutes ago).
>
>
> > 2. Audio loss during normal replay
> >
> > 3. Audio "chopped" during replay
>
> These will be fixed
Carsten Fehlhaber writes:
> Does anybody have an idea, what chip on the new Hauppauge card is responsible for IR
>receiving without
The AV7110.
> to have to debug the original Windows software first?
Good luck :-)
> Maybe it is adressable over i2c too so the LIRC i2c haupauge driver has
Deti Fliegl writes:
> I would like to change the CURRENT variable of the DVB/driver/Makefile
> to
> CURRENT:=$(shell head -1 /usr/include/linux/version.h|( read i j k; echo
> $$k|sed s/\"//g))
>
> This installs the modules into the directory of the kernel they were
> compiled for. Maybe th
=?iso-8859-1?Q?Michael_Klo=DF?= writes:
>
> Hello,
>
> do anyone have a working DVB-C card with driver DVB-0.9 ?
>
> Is no problem to see video with "tuxview" on my computer.
> But there is absulut nothing on my TV. No video or text displayed
> with vdr-8.0pre7. I only read mails with s
Klaus Schmidinger writes:
> > adjusted the buffer until the dropouts went away. If they still occur
> > I will have to reclaim more memory.
>
> Arghh, that's too bad. The OSD is already quite a compromise as it is.
> Making it even smaller will hurt VDR quite a bit.
>
> I know you at conv
Matthias Weingart writes:
> > These will be fixed in the next version.
> > Some channels really seem to have a big offset between audio and
> > video and if the video buffer is too small, the audio for the video
> > data at the buffer exit sometimes has not arrived yet -> audio underflow.
> >
hi klaus (+all)
ideas for VDR:
.) it would be great when audio was muted during channel
switching, because now you sometimes have a squeaking sound
when the channel is syncing. if the volume is turned up,
i think my ears will collapse. :))
.) would it be possible to see if a channel can.t be e
Hi all,
I have Suse 7.1 and just downloaded the sources to kernel 2.4.5
I built i2c and v4l as modules.
When I try to compile the DVB driver from CVS I get:
dvb.c: In function `vid_register':
dvb.c:4411: too few arguments to function `video_register_device_Recfe1c4b'
dvb.c: At top level:
dvb.c:
Sorry,
you're right. I was tricked by the error message...
rh
-Ursprüngliche Nachricht-
Von: Tim Lapawa [mailto:[EMAIL PROTECTED]]
Gesendet: Montag, 28. Mai 2001 12:19
An: Hakenes Rolf
Betreff: RE: [linux-dvb] AW: can not open device /dev/ost/qpskfe0
I have tried it with O_RDWR, but
This message has been forwarded to the right list :) ->
Original Message
Subject: [linux-dvd] video scrambling
Date: Mon, 28 May 2001 11:11:06 +0200 (MET DST)
From: Michal Jeczalik <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Hello!
We have a problem
Hi Tim,
you cannot open the "/dev/ost/qpskfe0" with O_RDWR set...just O_RDONLY
Regards,
rh
-Ursprüngliche Nachricht-
Von: Tim Lapawa [mailto:[EMAIL PROTECTED]]
Gesendet: Montag, 28. Mai 2001 11:19
An: [EMAIL PROTECTED]
Betreff: [linux-dvb] can not open device /dev/ost/qpskfe0
Hello l
Hello,
is there a way to translate the ".dvbrc" information from DVB/apps in
the vdr formate "channels.conf" ?
Michael Kloss
___
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as
subject.
Hello,
do anyone have a working DVB-C card with driver DVB-0.9 ?
Is no problem to see video with "tuxview" on my computer.
But there is absulut nothing on my TV. No video or text displayed
with vdr-8.0pre7. I only read mails with same problems.
I ask Klaus Schmidinger about that and he think t
Hallo!
Has anyone tried to use the Siemens-card driver via JNI
with JAVA?
Pros and cons appreciated.
Ciao, Guenter
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as
subject.
Hi
I would like to change the CURRENT variable of the DVB/driver/Makefile
to
CURRENT:=$(shell head -1 /usr/include/linux/version.h|( read i j k; echo
$$k|sed s/\"//g))
This installs the modules into the directory of the kernel they were
compiled for. Maybe the commandline can be simplified - but
Hi!
driver: siemens 0.9 20010428
cpu: amd k6-2 500 32mb Ram
when I make insmod I have the following error.
dvb.o unresolved symbol kernel_flag
what else should I have in the kernel?
the kernel is the one in the redhat7.1 with no changes kernel-2.4.2-2
Thank you in advance!
--
Info:
To
Hello list,
this small test program fails in opening the device /dev/ost/qpskfe0.
I tried to play a little bit with the API, but already the first step
became a dilemma.
>int main()
>{
> int fd_frontend=open("/dev/ost/qpskfe0", O_RDWR);
> if(fd_frontend == -1){
>perror("Can not open device
Hello!
Does anybody have an idea, what chip on the new Hauppauge card is responsible for IR
receiving without
to have to debug the original Windows software first?
Maybe it is adressable over i2c too so the LIRC i2c haupauge driver has to be modified
only?
Carsten
--
Info:
To unsubscribe
On different Suse installations with different kernels I get this or
very similar errors when I do ./autogen.sh in /tuxzap.
The needed packages are installed, the *.m4 files are in the right
directories, I tried all the help I got, I'm at the end of my knowledge.
Please help me.
Jörg
**Warning**:
On Mon, 28 May 2001, Ralph Metzler wrote:
> [EMAIL PROTECTED] writes:
> > I'm still "playing" to get my TT-DVB-C Budget running. Still I'm not
> > really able to get the tuner working. What I found: the frequency scale
> > used for DVB-C and for DVB-S differs by a factor of 1000 - is this a bu
Ralph Metzler wrote:
>
> See my reply in my last mail (a few minutes ago).
>
> > 2. Audio loss during normal replay
> >
> > 3. Audio "chopped" during replay
>
> These will be fixed in the next version.
> Some channels really seem to have a big offset between audio and
> video and if the vide
Ralph Metzler wrote:
>
> Klaus Schmidinger writes:
> > Ralph Metzler wrote:
> > >
> > > Klaus Schmidinger writes:
> > > > If I do the following ioctl() calls while replaying a "multiplexed PES"
> > > > recording (done with VDR 0.80pre5) through the /dev/ost/video device
> > > > the audio
34 matches
Mail list logo
