Hello,
I have an older vdr-recording which contains two audio-tracks (german
and english) and also AC3. (AC3 switches the format, see the attached
logfile).
I want to keep all this stuff on a dvd, but when I remultiplex the file
with replex I get only the german audio track.
Using pvastrumend
On Fri, Mar 19, 2004 at 08:39:41PM +, Andrew de Quincey wrote:
> On Friday 19 March 2004 20:32, John Murdoch wrote:
> > On Thu, 18 Mar 2004 23:03:48 +0200, Pasi Kärkkäinen wrote:
> > > > This sounds interesting. What frontend?
> > >
> > > saa7146: register extension 'budget dvb'.
> > > saa7146_
On Sat, Mar 20, 2004 at 11:45:27PM +0100, Nico wrote:
> Pasi Kärkkäinen wrote:
>
> >On Thu, Mar 18, 2004 at 11:03:48PM +0200, Pasi Kärkkäinen wrote:
> >
> >
> >>On Thu, Mar 18, 2004 at 06:21:26PM +0100, Johannes Stezenbach wrote:
> >>
> >>
> >>>Pasi Kärkkäinen wrote:
> >>>
> >>>
> I'm
On Saturday 20 March 2004 23:07, Johannes Stezenbach wrote:
> Andrew de Quincey wrote:
> >
> > But why does it break DISEQC as well?
>
> DiSEqC is implemented using a timer irq in the firmware.
Well, this will work only if there is no other interrupt load.
Otherwise the timer interrupt processin
Klaus Schmidinger wrote:
>
> From what I can see in the driver source, on AV7110 based cards
> the actual DiSEqC signal is generated fom inside the firmware.
> But since the firmware hasn't changed between the latest DVB driver
> and dvb-kernel (at least as far as i know) I would assume that
> the
Pasi Kärkkäinen wrote:
On Thu, Mar 18, 2004 at 11:03:48PM +0200, Pasi Kärkkäinen wrote:
On Thu, Mar 18, 2004 at 06:21:26PM +0100, Johannes Stezenbach wrote:
Pasi Kärkkäinen wrote:
I'm using WinTV Nova-t PCI DVB-T budget card with linuxtv-dvb-1.1.0 driver
on Linux 2.4.24.
If I run vd
Guido Fiala wrote:
> Am Saturday 20 March 2004 00:27 schrieb Johannes Stezenbach:
> > Things are not so easy, because some kinds of messages are first
> > pushed into a message queue and executed later. So the last
> > command from the PC might not be the one which caused the ARM crash.
> >
> > Spe
Hello Andreas,
Andreas Share wrote:
>
> > > > Cool. The Root/Dpram in your 2003-11-08 DVB snapshot is the same as
> the
> > > > ones I extracted from dvb-ttpci-01.fw.gz currently on the website. So
> its
> > > > definitely not that; I just wanted to make ABSOLUTELY sure it wasn't
> some
> > > > b
On Thu, Mar 18, 2004 at 11:03:48PM +0200, Pasi Kärkkäinen wrote:
> On Thu, Mar 18, 2004 at 06:21:26PM +0100, Johannes Stezenbach wrote:
> > Pasi Kärkkäinen wrote:
> > >
> > > I'm using WinTV Nova-t PCI DVB-T budget card with linuxtv-dvb-1.1.0 driver
> > > on Linux 2.4.24.
> > >
> > > If I run vdr
Andrew de Quincey wrote:
>
> But why does it break DISEQC as well?
DiSEqC is implemented using a timer irq in the firmware.
And "hardware" section filters cause some ARM CPU load
(as do TS filters).
Of course, while tuning there is no signal and the load
should be zero. But some frontends just
> > > Cool. The Root/Dpram in your 2003-11-08 DVB snapshot is the same as
the
> > > ones I extracted from dvb-ttpci-01.fw.gz currently on the website. So
its
> > > definitely not that; I just wanted to make ABSOLUTELY sure it wasn't
some
> > > build issue. I'm assuming your 2003-11-08 snapshot wor
On Saturday 20 March 2004 20:41, Andrew de Quincey wrote:
> On Saturday 20 March 2004 19:29, Helmut Auer wrote:
> > I only tested for about 10 minutes now with switching hw_sections from 0
> > to 1 and vice versa.
> > It looks like diseqc is much better with hw_sections=0 !
> > Anyway once or twice
On Saturday 20 March 2004 21:15, Johannes Stezenbach wrote:
> Andrew de Quincey wrote:
> > > > Cool. The Root/Dpram in your 2003-11-08 DVB snapshot is the same as
> > > > the ones I extracted from dvb-ttpci-01.fw.gz currently on the
> > > > website. So its definitely not that; I just wanted to make
Andrew de Quincey wrote:
>
> > > Cool. The Root/Dpram in your 2003-11-08 DVB snapshot is the same as the
> > > ones I extracted from dvb-ttpci-01.fw.gz currently on the website. So its
> > > definitely not that; I just wanted to make ABSOLUTELY sure it wasn't some
> > > build issue. I'm assuming y
Hello Klaus,
Klaus Schmidinger wrote:
>
> Andrew de Quincey wrote:
> >
> > On Saturday 20 March 2004 16:42, Klaus Schmidinger wrote:
> > > Andrew de Quincey wrote:
> > > > > >From the Dpram checksums I can say that the first one is the one from
> > > > >
> > > > > 2003-09-05, and the second one i
On Saturday 20 March 2004 19:29, Helmut Auer wrote:
> Andrew de Quincey wrote:
> >>>Cool. The Root/Dpram in your 2003-11-08 DVB snapshot is the same as the
> >>>ones I extracted from dvb-ttpci-01.fw.gz currently on the website. So
> >>> its definitely not that; I just wanted to make ABSOLUTELY sure
Andrew de Quincey wrote:
Cool. The Root/Dpram in your 2003-11-08 DVB snapshot is the same as the
ones I extracted from dvb-ttpci-01.fw.gz currently on the website. So its
definitely not that; I just wanted to make ABSOLUTELY sure it wasn't some
build issue. I'm assuming your 2003-11-08 snapshot wo
YEY!! It works.
Thanks for your help, Jeremy & Andrew.
Mike.
now just gotta get that winmodem working...
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as
subject.
You can get it from: http://www.hauppauge.de/sw_nova-pci215a.htm
Download the .exe to a PC, extract the drivers and find ttlcdacc.dll.
---Original Message---
From: Mike Kenyon
Date: 03/20/04 16:55:23
To: [EMAIL PROTECTED]
Subject: [linux-dvb] Fwd: Re: Nova T USB
> For 2.6
On Monday 15 March 2004 00:00, Oliver Endriss wrote:
> On Sunday 14 March 2004 20:55, Andrew de Quincey wrote:
> > Hmm, I'm having a very odd DVB-S problem on one client site only. The
> > cards are TT DVB-S budget SU1278-TUA5059 cards. I've tested the drivers
> > before I messed with them, but the
On Saturday 20 March 2004 16:55, Mike Kenyon wrote:
> > For 2.6.3, you'll need to _not_ use the in-kernel drivers, and use the
> > latest from CVS instead; it should support it. I think dvb-kernel release
> > 1.1.1 should support it as well, but the CVS one has several speedups to
> > tuning.
>
>
> > Cool. The Root/Dpram in your 2003-11-08 DVB snapshot is the same as the
> > ones I extracted from dvb-ttpci-01.fw.gz currently on the website. So its
> > definitely not that; I just wanted to make ABSOLUTELY sure it wasn't some
> > build issue. I'm assuming your 2003-11-08 snapshot works for y
Andrew de Quincey wrote:
>
> On Saturday 20 March 2004 16:42, Klaus Schmidinger wrote:
> > Andrew de Quincey wrote:
> > > > >From the Dpram checksums I can say that the first one is the one from
> > > >
> > > > 2003-09-05, and the second one is the one which is in the 2003-11-08
> > > > driver pac
> For 2.6.3, you'll need to _not_ use the in-kernel drivers, and use the latest
> from CVS instead; it should support it. I think dvb-kernel release 1.1.1
> should support it as well, but the CVS one has several speedups to tuning.
Thanks to both respondants.
Ok, I've done as you suggested
On Saturday 20 March 2004 16:42, Klaus Schmidinger wrote:
> Andrew de Quincey wrote:
> > > >From the Dpram checksums I can say that the first one is the one from
> > >
> > > 2003-09-05, and the second one is the one which is in the 2003-11-08
> > > driver package in my VDR FTP archive.
> >
> > So w
Andrew de Quincey wrote:
>
> > >From the Dpram checksums I can say that the first one is the one from
> >
> > 2003-09-05, and the second one is the one which is in the 2003-11-08
> > driver package in my VDR FTP archive.
>
> So which is the one you tried in the 1.1.0 driver that had the same firm
Am Samstag, 20. März 2004 17:07 schrieb Siegfried Goericke:
> Am Freitag, 19. März 2004 20:01 schrieb Johannes Stezenbach:
> > Siegfried Goericke wrote:
> > > 2. tune with dvbtune 0.3 or 0.5 (no diffs): dvbtune -c 0 -f 10773250
> > > -p H -s 22000 -n 251
> >
> > Unfortunately I cannot tune to that
> >From the Dpram checksums I can say that the first one is the one from
>
> 2003-09-05, and the second one is the one which is in the 2003-11-08
> driver package in my VDR FTP archive.
So which is the one you tried in the 1.1.0 driver that had the same firmware
version?
I'm trying to help you:
On Saturday 20 March 2004 15:34, Klaus Schmidinger wrote:
> Andrew de Quincey wrote:
> > Incidentally, even though the firmwares used by 1.0.0 and 1.1.0 have the
> > same version number, they are _not_ the same.
> >
> > 1.0.0 had two seperate files, Dpram and Root
> > 1.1.0 has a combined file, dvb
On Sat, 20 Mar 2004 16:35:37 +0100
Klaus Schmidinger <[EMAIL PROTECTED]> wrote:
>
> I believe the file http://linuxtv.org/download/dvb/dvb-ttpci-01.fw.gz now
> contains the latest firmware version (the previous file was not gzipped).
>
> Klaus
FYI there's a tool in the scripts folder of the dvb
Andrew de Quincey wrote:
>
> On Saturday 20 March 2004 15:26, Andrew de Quincey wrote:
> > Incidentally, even though the firmwares used by 1.0.0 and 1.1.0 have the
> > same version number, they are _not_ the same.
> >
> > 1.0.0 had two seperate files, Dpram and Root
> > 1.1.0 has a combined file,
Andrew de Quincey wrote:
>
> Incidentally, even though the firmwares used by 1.0.0 and 1.1.0 have the same
> version number, they are _not_ the same.
>
> 1.0.0 had two seperate files, Dpram and Root
> 1.1.0 has a combined file, dvb-ttpci-01.fw
>
> However the file format of dvb-ttpci-01.fw is ob
On Saturday 20 March 2004 15:26, Andrew de Quincey wrote:
> Incidentally, even though the firmwares used by 1.0.0 and 1.1.0 have the
> same version number, they are _not_ the same.
>
> 1.0.0 had two seperate files, Dpram and Root
> 1.1.0 has a combined file, dvb-ttpci-01.fw
Actually maybe I have a
Incidentally, even though the firmwares used by 1.0.0 and 1.1.0 have the same
version number, they are _not_ the same.
1.0.0 had two seperate files, Dpram and Root
1.1.0 has a combined file, dvb-ttpci-01.fw
However the file format of dvb-ttpci-01.fw is obvious:
4 byte magic
4 byte number (proba
Andrew de Quincey wrote:
>
> > This change was done to avoid glitches in recordings on the primary device
> > in case the channel is switched.
> > Does it change anyting (DiSEqC wise) if you comment that line out?
>
> No idea, sorry, I only have budget cards; I'm just suggesting things.
I tried
> This change was done to avoid glitches in recordings on the primary device
> in case the channel is switched.
> Does it change anyting (DiSEqC wise) if you comment that line out?
No idea, sorry, I only have budget cards; I'm just suggesting things.
--
Info:
To unsubscribe send a mail to [EMA
Andrew de Quincey wrote:
>
> > the actual DiSEqC signal is generated fom inside the firmware.
> > But since the firmware hasn't changed between the latest DVB driver
> > and dvb-kernel (at least as far as i know) I would assume that
> > the actual signal the firmware generates should still be the
Andreas Oberritter wrote:
...
I don't know the system you mention above, but if it does not offer more
space than http://www.msi-computer.de/produkte/produkt.php?Prod_id=279 ,
then such a rev. 2.1 card won't fit. They are too long.
You were right - almost.
I have a rev 1.3 card and there is not a
> the actual DiSEqC signal is generated fom inside the firmware.
> But since the firmware hasn't changed between the latest DVB driver
> and dvb-kernel (at least as far as i know) I would assume that
> the actual signal the firmware generates should still be the same.
> Unless, of course, some oth
Sometimes when i have vdr running there is a process called "kdvb-fe-0:0"
that consumes around 30-35% cpu.
What is that does that process do? And why does it take so much cpu?
When i record with my bt878 card i don't have much cpu left for other
things, so this process causes problems.
--
Inf
[ N.B. I sent similar message to vdr-list a couple of days ago. As the
problem is probably (?) hw-based, I thought of this as a more
appropriate list to post to and hence the list change. ]
I've been having trouble with my VDR system. Right now I am suspecting
my Hauppauge DVB-C full-featured car
Johannes Stezenbach wrote:
>
> Andrew de Quincey wrote:
> > its not the firmware.
> > its not the frontend driver (that was a different issue).
> >
> > well, pretty obvious where it has to be really; must be a card setup problem
> > in the OSS code. I'll have a closer check over the next few days.
Kenneth =?iso-8859-1?q?Aafl=F8y?= writes:
> On Saturday 20 March 2004 02:04, Ralph Metzler wrote:
> > Kenneth Aafløy writes:
> A problem with your mail client Ralph?
>
> > > Maybe Ralph has some insight into wether it breaks the original KNC1
> > > card?
> >
> > I am the wrong person to
Kenneth Aafløy wrote:
>
> Hi,
>
> I was wondering about when the DVB branch will be phased out of development?
>
> Essentially, it's not really needed anymore, since the 1.1.0 release is out,
> or are you just keeping it around for incompatability reasons?
>
> What about just tarring up the DVB
> Am Friday 19 March 2004 21:57 schrieben Sie:
> > just insert some debug printk´s in av7110_before_after_tune() before the
> > two firmware calls, and one printk in SetPIDs() and you see you got
several
> > calls from this 2 funktions, especialy without signal.
> > You could also insert in __av71
Mike;
How old is your Nova-t USB?
I had one that I bought last year that has the Alps tdmb7 tuner. I've been trying to get this to work over the last couple of weeks and reached the same point as you. The modules load OK but you can't tune in to anything.
Hauppauge changed the tuner
Am Saturday 20 March 2004 00:27 schrieb Johannes Stezenbach:
> Things are not so easy, because some kinds of messages are first
> pushed into a message queue and executed later. So the last
> command from the PC might not be the one which caused the ARM crash.
>
> Specifically COMTYPE_PIDFILTER com
Am Friday 19 March 2004 21:57 schrieben Sie:
> just insert some debug printk´s in av7110_before_after_tune() before the
> two firmware calls, and one printk in SetPIDs() and you see you got several
> calls from this 2 funktions, especialy without signal.
> You could also insert in __av7110_send_fw_
48 matches
Mail list logo
