Mailing List Archive: MythTV: Mythtvnz

MythTV upgrade, bleeding code, ready for tester

1 2 3 4

View All

Index | Next | Previous | View Threaded

jyavenard at gmail

Jun 23, 2009, 7:41 AM

Post #1 of 83 (4192 views)
Permalink

MythTV upgrade, bleeding code, ready for tester

Hi

Ok, here is my new attempt at bringing Mythtv 0.21 up to date, with
playback features similar to what's running in trunk but without any
of the new and fancy MythUI which unfortunately, isn't ready yet for
mainstream use.

This build is based on 0.21-fixes with quite significant changes, the
main ones being:

* FFmpeg has been updated to the version available in trunk. This adds
big improvement with h264 playback, and it should support much more
format and codec. All the videos I've tried so far have played rather
well
* Various improvements across the board, it should handle more nicely
when playback is failing.
* Various VDPAU improvements (I haven't released those patches yet).
In particular, the video corruption seen on some 720p channels should
have been fixed.

I haven't published this information on the main mythtv mailing list,
as I know it would result in flaming by some individuals.

I've only tested the frontend side, not the backend. While I'm pretty
sure it shouldn't break anything, you never know... If some people are
willing to risk it, I would appreciate. I will tomorrow when I have
more time.

I haven't experienced a single crash or "Failure to init video" when
changing channels rapidly, no matter how fast I try to change them

I've noticed that the 720p channels will not play nicely if you have
the AC3 upmixer activated with the "Linear" upmixing conversion, it
must be on "Passive". No clue why.

I have a built with the latest ffmpeg , but there are still issues ,
so not releasing anything yet.

Now: how to get it..

I've built packages for Jaunty (Ubuntu 9.04) only. To access those
packages, you need to enable the "bleeding" repository.
Add "bleeding" to the component of my repository, or add the following
line to your apt.conf :
deb http://www.avenard.org/files/ubuntu-repos jaunty testing

I've named the version 0.21.5 to avoid confusion in the future with
the other standard packages.

Let me know how it goes.. If things go well, I will move those
packages to testing in the future and build them for all platforms.

Jean-Yves

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

tortise at paradise

Jun 23, 2009, 12:41 PM

Post #2 of 83 (4087 views)
Permalink

Re: MythTV upgrade, bleeding code, ready for tester [In reply to]

That's very nice Jean-Yves, thank you. I am sure we all look forward to testing this.

>>> I've named the version 0.21.5 to avoid confusion in the future with the other standard packages.

One small thing, before it gets disseminated widely the naming if it might be better as something like 0.21.05.

I say this because it seems milestone 0.21.1 is still coming. (http://svn.mythtv.org/trac/roadmap) so calling yours 0.21.5, despite
your best intentions, is likely to cause confusion.

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

Aaron.Drysdale at provencocadmus

Jun 23, 2009, 3:08 PM

Post #3 of 83 (4076 views)
Permalink

Re: MythTV upgrade, bleeding code, ready for tester [In reply to]

Hi

I will happily test this once its available on Intrepid. It sounds like
it addresses a number of problems I'm having, and I'm already running
out of your test repository. Nothing ventured, nothing gained in my
opinion.

Out of curiosity, why would anyone flame you for doing this? Or am I
better off not asking?

Aaron

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

nick.rout at gmail

Jun 23, 2009, 3:24 PM

Post #4 of 83 (4095 views)
Permalink

Re: MythTV upgrade, bleeding code, ready for tester [In reply to]

On Wed, Jun 24, 2009 at 10:08 AM, Aaron Drysdale <
Aaron.Drysdale [at] provencocadmus> wrote:

> Hi
>
> I will happily test this once its available on Intrepid. It sounds like
> it addresses a number of problems I'm having, and I'm already running
> out of your test repository. Nothing ventured, nothing gained in my
> opinion.
>
> Out of curiosity, why would anyone flame you for doing this? Or am I
> better off not asking?

Probably better off not asking, and I don't want to generate a lot of
debate. Here is but an example:

http://www.gossamer-threads.com/lists/mythtv/users/382941#382941

Short answer: "by associating your backport|fork|patch farm with our project
you are introducing new bugs and generating a lot of support requests which
distracts the devs from the real work of finishing 0.22"

Please, its not a view I subscribe to, I applaud JYA's efforts, but no I am
not interested in a long debate about it on this list.

Thanks.
NR

jyavenard at gmail

Jun 23, 2009, 5:13 PM

Post #5 of 83 (4084 views)
Permalink

Re: MythTV upgrade, bleeding code, ready for tester [In reply to]

Hi

2009/6/24 Nick Rout <nick.rout [at] gmail>:
> Short answer: "by associating your backport|fork|patch farm with our project
> you are introducing new bugs and generating a lot of support requests which
> distracts the devs from the real work of finishing 0.22"

Note that this is coming from a non-developer who somehow believes he is ...

I later got email from devs saying that this person does not represent
their view or themselves in any ways ...

Regarding an intrepid build, the bleeding repository contains several
packages that you may not want to install like Alsa 1.0.18 and 1.0.19.
Pretty much all the packages I needed to get my hardware working...
So updating using bleeding on intrepid will require some caution ...

Jean-Yves

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

jyavenard at gmail

Jun 23, 2009, 5:14 PM

Post #6 of 83 (4084 views)
Permalink

Re: MythTV upgrade, bleeding code, ready for tester [In reply to]

Hi

2009/6/24 Tortise <tortise [at] paradise>:
> One small thing, before it gets disseminated widely the naming if it might be better as something like 0.21.05.

Well, it's too late :)

>
> I say this because it seems milestone 0.21.1 is still coming. �(http://svn.mythtv.org/trac/roadmap) so calling yours 0.21.5, despite
> your best intentions, is likely to cause confusion.

I can't see a 0.21.1 ever coming, there's no branch created nor
anything that could lead to the creation of such version

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

Aaron.Drysdale at provencocadmus

Jun 23, 2009, 5:17 PM

Post #7 of 83 (4082 views)
Permalink

Re: MythTV upgrade, bleeding code, ready for tester [In reply to]

> Regarding an intrepid build, the bleeding repository contains several
> packages that you may not want to install like Alsa 1.0.18 and 1.0.19.
> Pretty much all the packages I needed to get my hardware working...
> So updating using bleeding on intrepid will require some caution ...

I won't even attempt to install this yet. Just giving my support for
what you're doing, and hoping that its available out of the test
repository as soon as possible on other platforms so I can help to test
this (and selfishly - reap its benefits.)

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

Douglas.Pearless at pearless

Jun 23, 2009, 5:21 PM

Post #8 of 83 (4079 views)
Permalink

Re: MythTV upgrade, bleeding code, ready for tester [In reply to]

Have you put these up as I cannot see them yet?

Quoting Jean-Yves Avenard <jyavenard [at] gmail>:

> Hi
>
> Ok, here is my new attempt at bringing Mythtv 0.21 up to date, with
> playback features similar to what's running in trunk but without any
> of the new and fancy MythUI which unfortunately, isn't ready yet for
> mainstream use.
>
> This build is based on 0.21-fixes with quite significant changes, the
> main ones being:
>
> * FFmpeg has been updated to the version available in trunk. This adds
> big improvement with h264 playback, and it should support much more
> format and codec. All the videos I've tried so far have played rather
> well
> * Various improvements across the board, it should handle more nicely
> when playback is failing.
> * Various VDPAU improvements (I haven't released those patches yet).
> In particular, the video corruption seen on some 720p channels should
> have been fixed.
>
> I haven't published this information on the main mythtv mailing list,
> as I know it would result in flaming by some individuals.
>
> I've only tested the frontend side, not the backend. While I'm pretty
> sure it shouldn't break anything, you never know... If some people are
> willing to risk it, I would appreciate. I will tomorrow when I have
> more time.
>
> I haven't experienced a single crash or "Failure to init video" when
> changing channels rapidly, no matter how fast I try to change them
>
> I've noticed that the 720p channels will not play nicely if you have
> the AC3 upmixer activated with the "Linear" upmixing conversion, it
> must be on "Passive". No clue why.
>
> I have a built with the latest ffmpeg , but there are still issues ,
> so not releasing anything yet.
>
> Now: how to get it..
>
> I've built packages for Jaunty (Ubuntu 9.04) only. To access those
> packages, you need to enable the "bleeding" repository.
> Add "bleeding" to the component of my repository, or add the following
> line to your apt.conf :
> deb http://www.avenard.org/files/ubuntu-repos jaunty testing
>
> I've named the version 0.21.5 to avoid confusion in the future with
> the other standard packages.
>
> Let me know how it goes.. If things go well, I will move those
> packages to testing in the future and build them for all platforms.
>
> Jean-Yves
>
> _______________________________________________
> mythtvnz mailing list
> mythtvnz [at] lists
> http://lists.ourshack.com/mailman/listinfo/mythtvnz
> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>

hads at nice

Jun 23, 2009, 5:27 PM

Post #9 of 83 (4083 views)
Permalink

Re: MythTV upgrade, bleeding code, ready for tester [In reply to]

On Wed, 2009-06-24 at 10:13 +1000, Jean-Yves Avenard wrote:
> Note that this is coming from a non-developer who somehow believes he
> is ...

Please don't have this discussion here. Everyone has their own opinions,
let's just leave it at that.

--
http://nicegear.co.nz
New Zealand's Open Source Hardware Supplier

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

jyavenard at gmail

Jun 23, 2009, 5:42 PM

Post #10 of 83 (4072 views)
Permalink

Re: MythTV upgrade, bleeding code, ready for tester [In reply to]

Hi

2009/6/24 Douglas Pearless <Douglas.Pearless [at] pearless>:
> Have you put these up as I cannot see them yet?

Must be running Ubuntu jaunty and have enabled the "bleeding" repository.
http://www.avenard.org/media/Ubuntu_Repository/Ubuntu_Repository.html

There are definitely there ...

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

Douglas.Pearless at pearless

Jun 23, 2009, 6:18 PM

Post #11 of 83 (4076 views)
Permalink

Re: MythTV upgrade, bleeding code, ready for tester [In reply to]

Oops, forgot to add bleeding as a component in the software source. :-)

Quoting Jean-Yves Avenard <jyavenard [at] gmail>:

> Hi
>
> 2009/6/24 Douglas Pearless <Douglas.Pearless [at] pearless>:
>> Have you put these up as I cannot see them yet?
>
> Must be running Ubuntu jaunty and have enabled the "bleeding" repository.
> http://www.avenard.org/media/Ubuntu_Repository/Ubuntu_Repository.html
>
> There are definitely there ...
>
> _______________________________________________
> mythtvnz mailing list
> mythtvnz [at] lists
> http://lists.ourshack.com/mailman/listinfo/mythtvnz
> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>

ivstinivs at gmail

Jun 23, 2009, 7:02 PM

Post #12 of 83 (4083 views)
Permalink

Re: MythTV upgrade, bleeding code, ready for tester [In reply to]

Jean-Yves Avenard wrote:
> deb http://www.avenard.org/files/ubuntu-repos jaunty testing
>
>
I changed to jaunty bleeding, updated, shut down (because of Nova T-
500), booted up again

> Let me know how it goes.. If things go well, I will move those
> packages to testing in the future and build them for all platforms.
>
Brief test, run through channels, tv channels switched fine, audio only
channels, radio nz national and concert did not work first time (as per
usual) but did with second attempts. Will test further tonight.

Thank you very much, this is huge improvement since upgrade to Nvidia
185 and subsequent downgrade.

Cheers
Justin Hyde

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

markk at kc

Jun 24, 2009, 12:35 AM

Post #13 of 83 (4064 views)
Permalink

Re: MythTV upgrade, bleeding code, ready for tester [In reply to]

Wooo hoooo!

Upgraded frontend/backend pc a little while ago and did a few live tv
tests and it goes fantastically so far. I've had it exit out of tv once
changing channels but if it's occasional I don't think anyone at home
will worry about it.

Thanks for all your work making repos, without them I don't think I'd be
watching DVB-T in New Zealand.

Next task is to look into transcoding HD for my tv pc that doesn't have
a nvidia card - or look into a buying fanless card but I'm a little
worried about the heat and power draw (Asus p5e-v running with a 200W
external power supply so almost silent)

Cheers
Mark

On Wed, 2009-06-24 at 00:41 +1000, Jean-Yves Avenard wrote:
> Hi
>
> Ok, here is my new attempt at bringing Mythtv 0.21 up to date, with
> playback features similar to what's running in trunk but without any
> of the new and fancy MythUI which unfortunately, isn't ready yet for
> mainstream use.
>
> This build is based on 0.21-fixes with quite significant changes, the
> main ones being:
>
> * FFmpeg has been updated to the version available in trunk. This adds
> big improvement with h264 playback, and it should support much more
> format and codec. All the videos I've tried so far have played rather
> well
> * Various improvements across the board, it should handle more nicely
> when playback is failing.
> * Various VDPAU improvements (I haven't released those patches yet).
> In particular, the video corruption seen on some 720p channels should
> have been fixed.
>
> I haven't published this information on the main mythtv mailing list,
> as I know it would result in flaming by some individuals.
>
> I've only tested the frontend side, not the backend. While I'm pretty
> sure it shouldn't break anything, you never know... If some people are
> willing to risk it, I would appreciate. I will tomorrow when I have
> more time.
>
> I haven't experienced a single crash or "Failure to init video" when
> changing channels rapidly, no matter how fast I try to change them
>
> I've noticed that the 720p channels will not play nicely if you have
> the AC3 upmixer activated with the "Linear" upmixing conversion, it
> must be on "Passive". No clue why.
>
> I have a built with the latest ffmpeg , but there are still issues ,
> so not releasing anything yet.
>
> Now: how to get it..
>
> I've built packages for Jaunty (Ubuntu 9.04) only. To access those
> packages, you need to enable the "bleeding" repository.
> Add "bleeding" to the component of my repository, or add the following
> line to your apt.conf :
> deb http://www.avenard.org/files/ubuntu-repos jaunty testing
>
> I've named the version 0.21.5 to avoid confusion in the future with
> the other standard packages.
>
> Let me know how it goes.. If things go well, I will move those
> packages to testing in the future and build them for all platforms.
>
> Jean-Yves
>
> _______________________________________________
> mythtvnz mailing list
> mythtvnz [at] lists
> http://lists.ourshack.com/mailman/listinfo/mythtvnz
> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

jyavenard at gmail

Jun 24, 2009, 12:44 AM

Post #14 of 83 (4076 views)
Permalink

Re: MythTV upgrade, bleeding code, ready for tester [In reply to]

Hi

2009/6/24 Mark <markk [at] kc>:
> Wooo hoooo!
>
> Upgraded frontend/backend pc a little while ago and did a few live tv
> tests and it goes fantastically so far. �I've had it exit out of tv once
> changing channels but if it's occasional I don't think anyone at home
> will worry about it.
>
> Thanks for all your work making repos, without them I don't think I'd be
> watching DVB-T in New Zealand.
>
> Next task is to look into transcoding HD for my tv pc that doesn't have
> a nvidia card - or look into a buying fanless card but I'm a little
> worried about the heat and power draw (Asus p5e-v running with a 200W
> external power supply so almost silent)

Further to discussion with the MythTV author,

I've been asked not to distribute those packages and instead focus my
efforts on getting trunk suitable for release.

I agreed.

So I won't be continuing effort on 0.21 ..

I will do one more update of the VDPAU backport and try to get a 0.22
ready for generic use ASAP.

Jean-Yves

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

nick.rout at gmail

Jun 24, 2009, 1:45 AM

Post #15 of 83 (4068 views)
Permalink

Re: MythTV upgrade, bleeding code, ready for tester [In reply to]

On Wed, Jun 24, 2009 at 7:44 PM, Jean-Yves Avenard<jyavenard [at] gmail> wrote:
> Hi
>
> 2009/6/24 Mark <markk [at] kc>:
>> Wooo hoooo!
>>
>> Upgraded frontend/backend pc a little while ago and did a few live tv
>> tests and it goes fantastically so far. �I've had it exit out of tv once
>> changing channels but if it's occasional I don't think anyone at home
>> will worry about it.
>>
>> Thanks for all your work making repos, without them I don't think I'd be
>> watching DVB-T in New Zealand.
>>
>> Next task is to look into transcoding HD for my tv pc that doesn't have
>> a nvidia card - or look into a buying fanless card but I'm a little
>> worried about the heat and power draw (Asus p5e-v running with a 200W
>> external power supply so almost silent)
>
> Further to discussion with the MythTV author,
>
> I've been asked not to distribute those packages and instead focus my
> efforts on getting trunk suitable for release.
>
> I agreed.
>
> So I won't be continuing effort on 0.21 ..
>
> I will do one more update of the VDPAU backport and try to get a 0.22
> ready for generic use ASAP.

Does that mean you are closing your repo? (I could construe the above that:

(1) you have agreed not to distribute any packages; or

(2) you have agreed not to distribute 0.21.5 packages; or

(3) you have just agreed that you are going to do no more 0.21 work
and work on 0.22 but leave your repo intact "as is where is"

On any analysis it sounds as though you have become a mythtv "dev" -
which I think is great because you have a lot to offer (IMHO).

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

jyavenard at gmail

Jun 24, 2009, 2:58 AM

Post #16 of 83 (4059 views)
Permalink

Re: MythTV upgrade, bleeding code, ready for tester [In reply to]

Hi

2009/6/24 Nick Rout <nick.rout [at] gmail>:
> Does that mean you are closing your repo? (I could construe the above that:

No no ...

I will just not release 0.21.5

> (3) you have just agreed that you are going to do no more 0.21 work
> and work on 0.22 but leave your repo intact "as is where is"

Nothing like that was discussed.

I was just asked not to release the ffmpeg upgrade
>
> On any analysis it sounds as though you have become a mythtv "dev" -
> which I think is great because you have a lot to offer (IMHO).

Nothing like that.

Though I was left to understand that to become one , one step is
required, and that one way to be able to integrate in Myth all my
changes, is to become a developer myself.

Jean-Yves

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

Aaron.Drysdale at provencocadmus

Jun 24, 2009, 1:08 PM

Post #17 of 83 (4038 views)
Permalink

Re: MythTV upgrade, bleeding code, ready for tester [In reply to]

There may be good reasons for this, but for me this is disappointing. Now my system is left half working (not through any fault of yours I would add) and I know there is a fix available but not being distributed. Damn!

Any idea how far away 0.22 is from being released? I occassionally look online for this, but no one seems to be giving away any info.

Aaron

-----Original Message-----
From: Jean-Yves Avenard <jyavenard [at] gmail>
Sent: Wednesday, 24 June 2009 7:44 p.m.
To: MythTV in NZ <mythtvnz [at] lists>
Subject: Re: [mythtvnz] MythTV upgrade, bleeding code, ready for tester

Hi

2009/6/24 Mark <markk [at] kc>:
> Wooo hoooo!
>
> Upgraded frontend/backend pc a little while ago and did a few live tv
> tests and it goes fantastically so far. I've had it exit out of tv once
> changing channels but if it's occasional I don't think anyone at home
> will worry about it.
>
> Thanks for all your work making repos, without them I don't think I'd be
> watching DVB-T in New Zealand.
>
> Next task is to look into transcoding HD for my tv pc that doesn't have
> a nvidia card - or look into a buying fanless card but I'm a little
> worried about the heat and power draw (Asus p5e-v running with a 200W
> external power supply so almost silent)

Further to discussion with the MythTV author,

I've been asked not to distribute those packages and instead focus my
efforts on getting trunk suitable for release.

I agreed.

So I won't be continuing effort on 0.21 ..

I will do one more update of the VDPAU backport and try to get a 0.22
ready for generic use ASAP.

Jean-Yves

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

nick.rout at gmail

Jun 24, 2009, 2:14 PM

Post #18 of 83 (4041 views)
Permalink

Re: MythTV upgrade, bleeding code, ready for tester [In reply to]

On Thu, Jun 25, 2009 at 8:08 AM, Aaron Drysdale <
Aaron.Drysdale [at] provencocadmus> wrote:

> There may be good reasons for this, but for me this is disappointing. Now
> my system is left half working (not through any fault of yours I would add)
> and I know there is a fix available but not being distributed. Damn!
>
> Any idea how far away 0.22 is from being released? I occassionally look
> online for this, but no one seems to be giving away any info.

standard reply: when its ready :)

stevehodge at gmail

Jun 24, 2009, 5:44 PM

Post #19 of 83 (4037 views)
Permalink

Re: MythTV upgrade, bleeding code, ready for tester [In reply to]

On Thu, Jun 25, 2009 at 8:08 AM, Aaron Drysdale <
Aaron.Drysdale [at] provencocadmus> wrote:

> There may be good reasons for this, but for me this is disappointing. Now
> my system is left half working (not through any fault of yours I would add)
> and I know there is a fix available but not being distributed. Damn!
>

If your willing to test bleeding edge stuff for JYA, why not run trunk?

Cheers,
Steve

Aaron.Drysdale at provencocadmus

Jun 24, 2009, 5:50 PM

Post #20 of 83 (4031 views)
Permalink

Re: MythTV upgrade, bleeding code, ready for tester [In reply to]

>If your willing to test bleeding edge stuff for JYA, why not run
trunk?

First, I was waiting for it to hit "testing" not "bleeding" :) But fair
comment. I tried once to build from trunk. Managed to check it out, but
had compiler errors that I just didn't know how to correct.

And it needs to be fairly robust enough that my wife and kids can use it
with some degree of confidence, which so far JYA's repo has given me.

stevehodge at gmail

Jun 24, 2009, 6:01 PM

Post #21 of 83 (4037 views)
Permalink

Re: MythTV upgrade, bleeding code, ready for tester [In reply to]

On Thu, Jun 25, 2009 at 12:50 PM, Aaron Drysdale <
Aaron.Drysdale [at] provencocadmus> wrote:

> >If your willing to test bleeding edge stuff for JYA, why not run
> trunk?
>
> First, I was waiting for it to hit �testing� not �bleeding� :) But fair
> comment. I tried once to build from trunk. Managed to check it out, but had
> compiler errors that I just didn�t know how to correct.
>
Fair enough. I run Gentoo so I'm kind of used to building stuff from
source.

> And it needs to be fairly robust enough that my wife and kids can use it
> with some degree of confidence, which so far JYA�s repo has given me.
>
I think he's saying he's just not releasing the ffmpeg update (i.e. what he
was going to call 0.21.5), I don't think he's planning on taking down the
VDPAU backport repository.

Cheers,
Steve

Aaron.Drysdale at provencocadmus

Jun 24, 2009, 6:10 PM

Post #22 of 83 (4033 views)
Permalink

Re: MythTV upgrade, bleeding code, ready for tester [In reply to]

>I think he's saying he's just not releasing the ffmpeg update (i.e.
what he was going to call 0.21.5), I don't think he's planning on taking
>down the VDPAU backport repository.

I realize that, but in order to get it working reliably I've had to make
some compromises. The 720p channels just don't work properly currently,
so I have set it up to view live tv off my dvb-s tuner, so always
watching live TV in SD. Then I configured channel priorities in the
backend to ensure that recording on TV1 and TV2 (720p) preferred SD,
while all other channels preferred the HD tuner.

A bit of a hack, but it gives me a stable system. From Jean-Yves
comments, I thought all of this "messiness" would be done away with, and
I would be able to view all channels using my Nova-T 500, and enjoy HD
across all channels. So close...

jyavenard at gmail

Jun 24, 2009, 6:36 PM

Post #23 of 83 (4023 views)
Permalink

Re: MythTV upgrade, bleeding code, ready for tester [In reply to]

Hi

2009/6/25 Aaron Drysdale <Aaron.Drysdale [at] provencocadmus>:
> There may be good reasons for this, but for me this is disappointing. Now my system is left half working (not through any fault of yours I would add) and I know there is a fix available but not being distributed. Damn!

What current problem are you experiencing that left your problem half working?

>
> Any idea how far away 0.22 is from being released? I occassionally look online for this, but no one seems to be giving away any info.
>

Not sure to be honnest, I move to 0.22 last week-end for about 12
hours until I reverted back, too many segfault. Though I didn't spent
anytime experimenting nor looking where the crash was from.

Jean-Yves

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

jyavenard at gmail

Jun 24, 2009, 6:39 PM

Post #24 of 83 (4020 views)
Permalink

Re: MythTV upgrade, bleeding code, ready for tester [In reply to]

hi

2009/6/25 Steve Hodge <stevehodge [at] gmail>:
>
> If your willing to test bleeding edge stuff for JYA, why not� run trunk?
>

TBH, I'm pretty certain my "bleeding" repository is rather stable :)
and regarding MythTV, only playback and video encoding got modified,
and with code known to work well in trunk..
it wouldn't add much instability unless I made an error.

BTW, I upgraded my backend with it, and it's been problem-free so far.
I did get an "error to init video" on my frontend, but looking at the
log, the network connection went down at that time, to it actually
handled things quite well as usually my frontend would lock then

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

jyavenard at gmail

Jun 24, 2009, 6:41 PM

Post #25 of 83 (4030 views)
Permalink

Re: MythTV upgrade, bleeding code, ready for tester [In reply to]

Hi

2009/6/25 Aaron Drysdale <Aaron.Drysdale [at] provencocadmus>:
> I realize that, but in order to get it working reliably I�ve had to make
> some compromises. The 720p channels just don�t work properly currently, so I

By don't work, I guess you mean with some visual corruption like seen
in your recording of Wimbledon ?

That fix isn't even in trunk yet ...

This is something I will be pushing on my repository soon, as it
doesn't rely on a new ffmpeg

> have set it up to view live tv off my dvb-s tuner, so always watching live
> TV in SD. Then I configured channel priorities in the backend to ensure that
> recording on TV1 and TV2 (720p) preferred SD, while all other channels
> preferred the HD tuner.
>

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

1 2 3 4

View All

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads