'svn info' iirc
- ciaran
On 05/10/05, Adam Egger <[EMAIL PROTECTED]> wrote:
> On 10/5/05, Ciaran <[EMAIL PROTECTED]> wrote:
> > Yup, me too, mythbackend doesn't survive the night currently,
> > unfortunately I stupidly forgot to check my current svn revision
> > before doing an update this morning
On 10/5/05, Ciaran <[EMAIL PROTECTED]> wrote:
> Yup, me too, mythbackend doesn't survive the night currently,
> unfortunately I stupidly forgot to check my current svn revision
> before doing an update this morning, but it was the most recent
> version as of 7am (GMT) yesterday :)
By the way, is t
Yup, me too, mythbackend doesn't survive the night currently,
unfortunately I stupidly forgot to check my current svn revision
before doing an update this morning, but it was the most recent
version as of 7am (GMT) yesterday :)
- Ciaran
On 04/10/05, Mark <[EMAIL PROTECTED]> wrote:
> Stuart Auchter
I use over the air signals with this card just fine. I don't
have cable, but I have seen references that a lot
of the cable channels are scrambled. Only a few of them are
can be decoded with MPEG2 software. This may be the
problem you are experiencing. I posted this to the mythTV
list so that m
What about having an entry/setting in the database that causes mythbackend
to go into a suspended/holding/no-go state untill the setting is removed
from the database.
Of course, the first thing that mythtv-setup should do when run is put that
flag in, and remove it when it's done?
When the
What would be really good would be a technical overview of how myth actually
works, with links pointing to the various 3rd party dependicies home pages. I
personally have found it hard to glean this type of info.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf
:)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
[EMAIL PROTECTED]
Sent: Wednesday, 5 October 2005 3:32 AM
To: mythtv-commits@mythtv.org
Subject: [mythtv-commits] mythtv commit: r7389 by danielk
Author: danielk
Date: 2005-10-04 17:31:32 +000
On Tue 4 October 2005 20:24, Daniel Kristjansson wrote:
> I could just add the warning to mythtv-setup if we detect the backend
> running. But I loathe the idea of adding another slow startup dialog
> to mythtv-setup. Would anyone object to putting the two existing
> queries into one dialog with a
On Tue, 4 Oct 2005, Daniel Kristjansson wrote:
On Wed, 2005-10-05 at 00:44 +0100, Ian Caulfield wrote:
Hi,
I've updated to svn 7389, and nothing seems to happen when the backend
tries to tune - doing some digging, it looks like (as all the PMTs for the
mux are transmitted on the same mux) the
On Tue, 4 Oct 2005, Daniel Kristjansson wrote:
On Wed, 2005-10-05 at 00:44 +0100, Ian Caulfield wrote:
Hi,
I've updated to svn 7389, and nothing seems to happen when the backend
tries to tune - doing some digging, it looks like (as all the PMTs for the
mux are transmitted on the same mux) the
On Wed, 2005-10-05 at 00:44 +0100, Ian Caulfield wrote:
> Hi,
>
> I've updated to svn 7389, and nothing seems to happen when the backend
> tries to tune - doing some digging, it looks like (as all the PMTs for the
> mux are transmitted on the same mux) the PMT for the wrong program is
> being p
Hi,
I've updated to svn 7389, and nothing seems to happen when the backend
tries to tune - doing some digging, it looks like (as all the PMTs for the
mux are transmitted on the same mux) the PMT for the wrong program is
being picked up, and no further ones are considered. The DTVSignalMonitor
On Mon, 03 Oct 2005 12:17:58 +0100, Stuart Auchterlonie wrote:
> I think this is a root cause of a number of other problems that some
> people have been seeing. What I would like to do is as follows
>
> 1) Contruct a PMT under all circumstances and pass it through 2) Add
> handling to cope with PM
On Tue, 04 Oct 2005 09:47:12 +0100, John Pullan wrote:
> On 04/10/05, Martin Ebourne <[EMAIL PROTECTED]> wrote:
>> I've stopped working on it though because it's against 18.1 and I can
>> see there's been lots of changes. I'm waiting for the DVB code in svn to
>> stabilise before I upgrade and fini
Daniel Kristjansson wrote:
Can you also try changing that whole block to:
triggerEventSleep.wakeAll();
lock.mutex()->unlock();
usleep(50);
triggerEventSleep.wakeAll();
triggerEventLoop.wait(3 /* ms */);
lock.mutex()->lock();
Daniel Kristjansson wrote:
Can you try changing:
triggerEventLoop.wait(3 /* ms */);
on about line 1234 to
triggerEventLoop.wait(1000 /* ms */);
And tell me if that fixes things for you.
-- Daniel
Yep, that fixes it. Five minutes of going into/out of live TV on various
channels works
Stuart Auchterlonie wrote:
Anyone else seeing memory leaks with 7384???
Mine have improved since 7385, but still pretty bad.
Had to turn off EIT scanning so they would run overnight tonight.
In about an hour or so top would say using 50% of 512Mb, without EIT it
hovers around 8%.
When I was
I could just add the warning to mythtv-setup if we detect the backend
running. But I loathe the idea of adding another slow startup dialog
to mythtv-setup. Would anyone object to putting the two existing
queries into one dialog with a checkbox for each?
I just thought of displaying a warning me
Anyone else seeing memory leaks with 7384???
Stuart
___
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
And what should one consult when the HOWTO cannot help? I was told
the
-user channel and mailing list. The problem is that these places are
populated largely by the blind leading the blind, resulting in bad
advice.
They really aren't that blind. There's only a few cases where mythtv-
se
On Tuesday 04 October 2005 03:43 pm, Daniel Kristjansson wrote:
> On Tue, 2005-10-04 at 15:40 -0400, Daniel Kristjansson wrote:
> > Can you try changing:
> > triggerEventLoop.wait(3 /* ms */);
> > on about line 1234 to
> > triggerEventLoop.wait(1000 /* ms */);
> >
> > And tell me if that fi
On Tuesday 04 October 2005 03:24 pm, Daniel Kristjansson wrote:
> On Tue, 2005-10-04 at 19:12 +0100, Dave Just wrote:
> > > Do people run mythtv-setup that often anyway?
> >
> > I have the machine running my frontend launch mythtv-setup when it
> > first goes into X,
> > before entering a loop of r
On Tue, 2005-10-04 at 15:40 -0400, Daniel Kristjansson wrote:
> Can you try changing:
> triggerEventLoop.wait(3 /* ms */);
> on about line 1234 to
> triggerEventLoop.wait(1000 /* ms */);
>
> And tell me if that fixes things for you.
Can you also try changing that whole block to:
On Tue, 2005-10-04 at 23:40 +1000, Jon Whitear wrote:
> I've updated to 7387, and recompiled with --compile-type=profile. The
> behaviour has changed somewhat. Re/entering live TV now works most of
> the time (judging from the limited testing I've done so far.) Sometimes,
> when I try live TV t
On Mon, 2005-10-03 at 21:08 -0600, Endaf Jones wrote:
> Daniel Kristjansson wrote:
> > You need to set atscsrcid to 80*256 + 6 for this channel, not
> > 16*256 + 6.
> Here are all the bits you requested. For reference, the
> satellite/transport info for PBS on AMC 3 is at
> http://www.lyngsat.c
On 04/10/05, Daniel Kristjansson <[EMAIL PROTECTED]> wrote:
> On Tue, 2005-10-04 at 19:35 +0100, John Pullan wrote:
> > I've just noticed that browse mode from within live tv can still get
> > the frontend locked up if you are daft enough to try and tune to an
> > off air channel. Channel numbers a
On Tue, 2005-10-04 at 13:46 -0400, Daniel Kristjansson wrote:
> On Tue, 2005-10-04 at 18:00 +0100, Bob Ham wrote:
> > If this really is bad advice, I think it should be noted by the
> > aforementioned people what "help" is available, and that the
> > determination of some particular developers to
On Tue, 2005-10-04 at 19:12 +0100, Dave Just wrote:
> >
> > Do people run mythtv-setup that often anyway?
>
> I have the machine running my frontend launch mythtv-setup when it
> first goes into X,
> before entering a loop of re-launching mythfrontend. I found this
> was quite handy when I wa
On Tue, 2005-10-04 at 19:35 +0100, John Pullan wrote:
> I've just noticed that browse mode from within live tv can still get
> the frontend locked up if you are daft enough to try and tune to an
> off air channel. Channel numbers and "up" & "down" seem to work just
> fine.
So if you type in the off
On 04/10/05, John Pullan <[EMAIL PROTECTED]> wrote:
> On 04/10/05, Dave Just <[EMAIL PROTECTED]> wrote:
> > >>
> > > I can do the recorder side for DVB if someone makes
> > > VideoOutput work with non-video MPEG's.
> >
> > This would be certainly be excellent for us in the UK, especially as
> > (I'
I've just noticed that browse mode from within live tv can still get
the frontend locked up if you are daft enough to try and tune to an
off air channel. Channel numbers and "up" & "down" seem to work just
fine.
--
John
___
mythtv-dev mailing list
mythtv
On 04/10/05, Dave Just <[EMAIL PROTECTED]> wrote:
> >>
> > I can do the recorder side for DVB if someone makes
> > VideoOutput work with non-video MPEG's.
>
> This would be certainly be excellent for us in the UK, especially as
> (I'm guessing) we can
> get listings from the excellent BBC radio tim
I can do the recorder side for DVB if someone makes
VideoOutput work with non-video MPEG's.
This would be certainly be excellent for us in the UK, especially as
(I'm guessing) we can
get listings from the excellent BBC radio times service
www.radiotimes.com
used by tv_grab_uk_rt. I'd be
Do people run mythtv-setup that often anyway?
I have the machine running my frontend launch mythtv-setup when it
first goes into X,
before entering a loop of re-launching mythfrontend. I found this
was quite handy when I was
adding channels/cards and could configure by just rebooting the
On Tue, 2005-10-04 at 13:39 -0400, Isaac Richards wrote:
> On Tuesday 04 October 2005 01:31 pm, [EMAIL PROTECTED] wrote:
> > Author: danielk
> > Date: 2005-10-04 17:31:32 + (Tue, 04 Oct 2005)
> > New Revision: 7389
> >Changeset: http://cvs.mythtv.org/trac/changeset/7389
> >
>
Thanks for the reply Daniel.
This should only be the case if you have experimental EIT scanning
enabled. DVB on-demand is still working but the the EIT Scan is
continuous My hope is that someone will step in and improve on
this situation. Perhaps doing a scan every few hours, or just before
On Tue, 2005-10-04 at 18:00 +0100, Bob Ham wrote:
> I'd just like to point out, for those who are so dogged about where
> questions get asked, that I was told by a member of #mythtv-users that
> it was fine to run mythtv-setup at the same time as mythbackend; the
> only issue being that mythbackend
On Tuesday 04 October 2005 01:31 pm, [EMAIL PROTECTED] wrote:
> Author: danielk
> Date: 2005-10-04 17:31:32 + (Tue, 04 Oct 2005)
> New Revision: 7389
>Changeset: http://cvs.mythtv.org/trac/changeset/7389
>
> Modified:
>
>trunk/mythtv/docs/mythtv-HOWTO.sgml
>
> Log:
>
> Add
On Mon, 2005-10-03 at 08:39 -0400, Daniel Kristjansson wrote:
> On Mon, 2005-10-03 at 12:46 +0100, Dave Just wrote:
> > Also, if I run mythtv-setup while the backend is running,
> > I see "Could not open card #0!".
> Don't do that! You can screw up MythTV by running mythtv-setup
> while the backen
Adam Egger wrote:
If you have enough RAM you try to compile with --compile-type=profile.
It behaves like a release build (so it's fast) and it can be debugged.
It just needs lots of memory to compile :)
I've updated to 7387, and recompiled with --compile-type=profile. The
behaviour has changed
On 04/10/05, Martin Ebourne <[EMAIL PROTECTED]> wrote:
> On Mon, 03 Oct 2005 16:30:03 +0100, Stuart Morgan wrote:
> > On Mon 3 October 2005 15:49, Daniel Kristjansson wrote:
> >> > But Issac has said many times that it can't be a plugin so I doubt he
> >> > would accept any solution that was.
> >>
On 10/4/05, Jon Whitear <[EMAIL PROTECTED]> wrote:
> This is with a 'make distclean' using a non-debug build. Was the
> backtrace I provided last time useful? If so, I'll rebuild with debug
> and run another one.
If you have enough RAM you try to compile with --compile-type=profile.
It behaves li
This should fix the "deadlock" that people have been getting
when exiting and re-entering LiveTV quickly.
Doesn't fix it for me, I'm afraid. I have updated to 7384 on both ends,
and I'm getting the same behaviour. Here's the frontend log:-
2005-10-04 18:08:29.648 Read(): reqd=128000, rcv
Yep, it looks like the backend is deadlocked. Can you update to
7372, repeat this in gdb and then hit "Ctrl-C" and get me the
results of "thread apply all bt". I'd like to know where each
thread is.
Here's one from 7386.
mythbackend.log.bz2
Description: Binary data
backend_deadlock.txt.bz2
David Engel wrote:
> Would the proponents of adding soft padding to the scheduler please
> try this patch and provide feedback. If nobody responds, I'll have
> to assume it's not really that important after all and consider the
> whole issue closed.
Thanks for the patch, David. I apologize for
On Mon, 03 Oct 2005 16:30:03 +0100, Stuart Morgan wrote:
> On Mon 3 October 2005 15:49, Daniel Kristjansson wrote:
>> > But Issac has said many times that it can't be a plugin so I doubt he
>> > would accept any solution that was.
>>
>> Yep, he's been very clear on this, and I agree with him. It sh
46 matches
Mail list logo
