No worries really, at least you are trying to be helpful, which is always
appreciated. Hopefully one of the more senior/knowledgable of the myth
developers (or anyone else that's seen this problem and fixed it themselves)
will see that that's exactly what I'm trying to do to, and encourage it by
t
First off, MythTV is really cool. Thanks to everyone working on it.
I upgraded to SVN 7809 and noticed the following in my backend log:
(in orange: "This is not an error" message)
I didn't notice anything bad happen when watching the show.
Hope this helps. If you need any more info let me kn
Buzz wrote:
This is what I did prior to running configure: and yes, I've been developing
on linux a while ( I started on slackware with kernel just prior to 1.0 :-)
)
My fault, I am no linux guru and only been using Linux seriously for as
long as I am using MythTV.. I will stay quiet now..
This is what I did prior to running configure: and yes, I've been developing
on linux a while ( I started on slackware with kernel just prior to 1.0 :-)
)
* I read the README's in the SVN.
* I joined the -dev (and -user) lists and mostly lurked for 3 months,
listening carefully.
* I overviewed the
Buzz wrote:
I, for one, was actually inspired by Isaac's big 'this breaks livetv' commit
to actually try and start using SVN/head and see if there were
simple/outstanding issues that I could tackle, and give-back.
I found building SVN of mythtv+plugins+themes, and organising all the the
depe
I, for one, was actually inspired by Isaac's big 'this breaks livetv' commit
to actually try and start using SVN/head and see if there were
simple/outstanding issues that I could tackle, and give-back.
I found building SVN of mythtv+plugins+themes, and organising all the the
dependancies to be q
Well for all of you MythGame users out there I just commited
some code that adds back in metadata gathering when you do a
game scan. However now there is data for a lot more gametypes
than before.
Rather than use the old catver.ini, or the SQLite tosec database
or even the many dat files out
I?m curious to know the relative stability of the head. I know live-tv
is broken, I don?t particularly care, as it didn?t work all that well
for me before. I was always in the habit of recording, then watching
pseudo-live anyways.
Yes, I do read the dev & commits list, and from that perspect
Oh well, c'est la vie.WOn 11/9/05, andrew burke <[EMAIL PROTECTED]> wrote:
> And I would argue that it is easier for you to "svn update -r 7738" (and> using a LiveTV working build) than it is for everyone else to fork another> branch. If you don't like a rapidly developing source tree, use stable.
andrew burke wrote:
Pulling a branch is pretty easy:
svn copy svn+ssh://.../trunk svn+ssh://.../livetvbroken
and then the merge would have been:
svn merge svn+ssh://.../livetvbroken svn+ssh://.../trunk
truck is mainly for developers working on current code, and if guys
keeps bitching abo
On Nov 9, 2005, at 5:48 PM, andrew burke wrote:
And I would argue that it is easier for you to "svn update -r
7738" (and
using a LiveTV working build) than it is for everyone else to fork
another
branch. If you don't like a rapidly developing source tree, use
stable.
People wouldn't have
andrew burke wrote:
Doesn't seem all that difficult to me.
Oddly enough keeping up on the developers list when using svn doesn't
seem difficult to the rest of us.
___
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailma
> And I would argue that it is easier for you to "svn update -r 7738" (and
> using a LiveTV working build) than it is for everyone else to fork another
> branch. If you don't like a rapidly developing source tree, use stable.
People wouldn't have to fork, only Isaac would have had to work in his o
On Wednesday 09 November 2005 08:15 pm, Neil wrote:
> Having a rather frustrating time with the myth backend protocol at the
> moment!
>
> Been looking at these docs:
> http://www.mythtv.info/moin.cgi/MythProtocol_5f14
>
> Have coded a socket to the appropriate port on the backend server, and
> sen
On 11/10/05, Neil <[EMAIL PROTECTED]> wrote:
> Having a rather frustrating time with the myth backend protocol at the
> moment!
>
> Been looking at these docs:
> http://www.mythtv.info/moin.cgi/MythProtocol_5f14
>
> Have coded a socket to the appropriate port on the backend server, and
> send the f
On Wednesday 09 November 2005 07:54 pm, Wylie Swanson wrote:
> I do subscribe to mythtv-dev and mythtv-cvs -- and I am happy enough with
> Issac's "didn't feel like it" answer -- not that it matters. I am more
> excited to see the LiveTV work done than worry about temporary sacrifice.
> And I would
Having a rather frustrating time with the myth backend protocol at the
moment!
Been looking at these docs:
http://www.mythtv.info/moin.cgi/MythProtocol_5f14
Have coded a socket to the appropriate port on the backend server, and
send the first command:
22 MYTH_PROTO_VERSION 19
to which the
I do subscribe to mythtv-dev and mythtv-cvs -- and I am happy enough with Issac's "didn't feel like it" answer -- not that it matters. I am more excited to see the LiveTV work done than worry about temporary sacrifice. And I would argue that it is easier for you to "
svn update -r 7738" (and usi
On Wednesday 09 November 2005 07:31 pm, Jeremy Muhlich wrote:
> Isaac, why didn't you create a branch to do your disruptive live tv
> work? "You should subscribe to mythtv-dev if you want to run the svn
> head" isn't a good enough reason. Branching in svn is really, really
> easy and would have a
Isaac, why didn't you create a branch to do your disruptive live tv
work? "You should subscribe to mythtv-dev if you want to run the svn
head" isn't a good enough reason. Branching in svn is really, really
easy and would have avoided a lot of problems here.
-- Jeremy
_
This has been opened as a bug in trac and closed again as wontfix.
We will just have to wait until the transition in mythweb is over.
Alternatively, you can go into the .osx-packager/src/myth-cvs/
mythplugins and update each folder individually. Then, you can use
the --nocvs flag for osx-
Hi
I am unable to checkout the mythplugins trunk anymore from svn. I'm
pretty sure the reason is that there are 2 different directories with
the same name but different caps. The filesystem used by MacOS is case
insensitive and detects a conflict.
mac-mini:~/.osx-packager/src/myth-svn root#
I have a few questions for the DVB developers:
1. Have you considered triggerring of recording start/stop times by
the
updating of EITpf tables? The BBC are using reactive (i.e. triggered
from
the playout automation server) EITpf triggering on Mux1 and MuxB
which
means that EITpf always rolls
On 11/9/05, Cory Papenfuss wrote:
> OK.. a few issues/questions.
>
> - It appears that the program now looks through the whole file before
> actually writing anything... takes up CPU before the output file grows.
Yes. This is needed to find the PTS discrepencies. I tried to find a
way tha
OK.. a few issues/questions.
- It appears that the program now looks through the whole file before
actually writing anything... takes up CPU before the output file grows.
- Missing '\n' on the help for the new -m option.
- I like the out%d.yuv with the larger debug. Easier to see whi
Yet another update.
Robin Gilks ran into an interesting problem of streams being
corrupted, which turned up to be another bug in replex when updating
GOP timestamps (basically there is a corner case where a GOP will be
falsely detected in the middle of an imageit has a probablility of
occuring
Re: Who is working on MythVideo?
Remove Highlighting [
In reply to]
On 10/31/05, Ian Caulfield wrote: >
>
On Mon, 31 Oct 2005, Devan Lippman wrote: > > > I have a patch to myth that will ahow season/episode in the recordings
> > viewer. Data is captured from tv.com <
http://tv.com
>
Will this change enable 2 frontends to watch the same channel without
taking up 2 video inputs ? That is something I would like to see added.
I have a "cable" box hooked up to my composite input and 2 frontends
cannot watch the same channel through it.
- Tommi
Isaac Richards wrote:
In abou
On Wednesday 09 November 2005 12:13 pm, Wylie Swanson wrote:
> While it probably doesn't matter since the ticket was closed as invalid
> without backtrace -- I do not see the same behaviour with 7812.
Probably the same issue as #597, anyway.
Isaac
___
m
While it probably doesn't matter since the ticket was closed as invalid without backtrace -- I do not see the same behaviour with 7812.On 11/9/05, MythTV
<[EMAIL PROTECTED]> wrote:#624: mythweb recorded programs screen crashes mythbackend
---+---
30 matches
Mail list logo
