Update to .20

Due to current unstability of .18, problems I have read about in .19 I would be lothed to try to incorporate it as this time. Unless someone with lots of energy/skill/time steps forward :)

I have been using Cardoe's patchset from .19-fixes on my gentoo backend, and manually compile the same for my frontend on ubuntu. I'll see if I can take a look at the source package and properly build the debian way.

I've created some packages I'd like people to test out. Add this repo to your /etc/apt/sources.list, I have amd64 and i386 packages prebuilt as well as a source package available:

#mario's mythtv repo
deb http://home.eng.iastate.edu/~superm1 dapper main
deb-src http://home.eng.iastate.edu/~superm1 dapper main

tried out your packages mario...
it installs fine...except Livetv stops working...

ivtv installed and mplayer /dev/video0 plays alright...

Gonna try to reset mythtv with myth-setup... and see if that helps..

dear mario,

it works..needed to rerun mythtv-setup, because my old settings were still there...

when can we see some updates for the plugins?? because I would love to see mythtv back in ubuntu, it would make a kick ass media center...

maybe something like ubuntu-mythtv meta-package...
with ivtv-drivers...??

I'll see what i can do to get some plugins generated.

I ran the 0.19 release briefly on Breezy, and I wouldn't recommend using this in Dapper, as it has mild issues.

Having said that, what I would recommend is using packages built from the 0.19-fixes branch, which seem to have fixed all the major issues with the 0.19 release, and will eventually become 0.19.

If mythtv stays at 0.18.1 then maybe Ubuntu is going to replace Debian as the out-of-date-as-hell distribution of choice ;-)

The 0.19-fixes packages I have been running are from thehunter.ws .. maybe it would be worth contacting the maintainer of that repository for any build details or whatever else he might have gained (but use the most up-to-date revision from mythtv.org's 0.19-fixes)?

Did I say mild issues? I meant 'issues, to put it mildly' :)

Well the reasoning I was looking for this particular revision of the fixes branch was to guarantee it could sync up with a gentoo backend (like what I have).

A quick update: the official 0.19.1 is imminent (apparently). Of course, with mythtv's history, that could mean anything :D

It'd be REALLY nice if this could be squeezed into Dapper, especially since it's not in main.

If nothing else, when .19.1 comes out, I'll roll new packages with it. Its not that hard provided I have the source put together here.

@Mario: thanks for your effort, would you mind throwing .19.1 (once it's out) to revu? (see https://wiki.ubuntu.com/MOTU/Packages/REVU)

Mario: have you made any progress on creating these packages? I'm willing to step in and start building them packages so that they can be tested and released. I think it's important that this be included in Edgy at the very least, if not for updating dapper repos (since they will be "officially supported" for so long)

I made some progress on the plugins packages, but upgraded my network to
svn, and no longer have a build environment that works with stable. (Hence
why I haven't upgraded my package here anymore - just my local svn) At that
point, I just checkinstalled the plugins and mytharchive. I think the best
thing to do right now, is to pull a copy of the fixes branch and then adapt
a versioning scheme on the package to show the svn revision of -fixes
checked out. If you want to take over building off of the fixes branch,
just comment out the patch that I was applying, and you should be able to
build using the debian directory created in my source package.

On 7/12/06, David Overcash <email address hidden> wrote:
>
> Mario: have you made any progress on creating these packages? I'm
> willing to step in and start building them packages so that they can be
> tested and released. I think it's important that this be included in
> Edgy at the very least, if not for updating dapper repos (since they
> will be "officially supported" for so long)
>
> --
> Update to .19
> https://launchpad.net/bugs/32169
>

--
Mario Limonciello
<email address hidden>

Mario: have you made any progress on creating these packages? I'm willing to step in and start building them packages so that they can be tested and released. I think it's important that this be included in Edgy at the very least, if not for updating dapper repos (since they will be "officially supported" for so long)

Sorry for the duplicate comment. Hit refresh on accident.

I'll talk to mdz (previous maintainer) and see if I can start to headup building fresh .19 packages for the repos.

That would be great. Certainly grab the debian directory I used, I had a
few things that had to be changed to fit .19 better.

On 7/12/06, David Overcash <email address hidden> wrote:
>
> Sorry for the duplicate comment. Hit refresh on accident.
>
> I'll talk to mdz (previous maintainer) and see if I can start to headup
> building fresh .19 packages for the repos.
>
> --
> Update to .19
> https://launchpad.net/bugs/32169
>

--
Mario Limonciello
<email address hidden>

On Wed, Jul 12, 2006 at 07:45:10PM -0000, David Overcash wrote:
> Sorry for the duplicate comment. Hit refresh on accident.
>
> I'll talk to mdz (previous maintainer) and see if I can start to headup
> building fresh .19 packages for the repos.

I think Christian Marillat may be updating these packages now; you should
get in contact with him.

--
 - mdz

mdz, I was just about to go find you on IRC to talk about this... thanks for the heads up. If you need to ask or tell me something I'm usually in #ubuntu-motu and #ubuntu-devel in terms of dev channels as FunnyLookinHat.

According to this post http://marc.theaimsgroup.com/?l=mythtv-dev&m=115646357906758&w=2 by the lead mythtv developer, v0.20 will be coming out in 2 weeks. Is there any change this could make it's way into Edgy (it's got quite a lot of new feature that seem really neat)?

If not, then what's the status on 0.19? Is it looking like it'll make the cut?

My personal take on this is that we really don't know for certain if myth-0.20 will make it through all the hoops before Edgy freezes. It has to be released and then packaged by debian-multimedia (marillat) before it can be considered for edgy. 0.19, on the other hand, is available from debian-multimedia right now and builds cleanly on edgy (according to Bug #56536). There are also requests (Bug #51680) to have it backported to dapper which could happen now if it were brought into edgy.

On the other hand maybe there is time. I would certainly prefer to have 0.20 in edgy but perhaps the best way for that to happen is to stay on the ball with myth and backport it from edgy+1.

See also https://launchpad.net/distros/ubuntu/+source/mythtv/+bug/58212 :)

I have recently rebuild the following debian-multimedia mythtv packages:
- mythtv_0.19-0.10
- mythplugins_0.19-0.6
- myththemes_0.19-0.0

They all build cleanly in an edgy pbuilder. I have been using rebuilds of slightly older versions of these packages on my dapper mythtv system without problems for a few months now. The upgrade from the 0.18.1 ubuntu packages also went smoothly. So I think it is worthwile to try to get these packages into edgy. Does anybody know what's needed to get a MOTU to look at getting these packages into edgy?

You will have to submit them to REVU. Go on IRC and join #ubuntu-motu
and they can direct you to someone who will walk you through it.

Additionally, you can check out:
https://wiki.ubuntu.com/MOTU

On 9/4/06, Jordy Potman <email address hidden> wrote:
> I have recently rebuild the following debian-multimedia mythtv packages:
> - mythtv_0.19-0.10
> - mythplugins_0.19-0.6
> - myththemes_0.19-0.0
>
> They all build cleanly in an edgy pbuilder. I have been using rebuilds
> of slightly older versions of these packages on my dapper mythtv system
> without problems for a few months now. The upgrade from the 0.18.1
> ubuntu packages also went smoothly. So I think it is worthwile to try to
> get these packages into edgy. Does anybody know what's needed to get a
> MOTU to look at getting these packages into edgy?
>
> --
> Update to .19
> https://launchpad.net/bugs/32169
>

--

---------------------------------------------------------
http://www.funnylookinhat.com
AIM: FunnyLookinHat
ICQ: 40145621
MSN: <email address hidden>
IRC: irc.freenode.net
---------------------------------------------------------

First, thanks for all the hard work on these packages.

Second, is there any chance we could get version .20 of mythtv in Ubuntu (via something like backports or just the Edgy release)?

Using Mario's 0.20 packages here, the overall upgrade went smoothly except for two issues:

One, upgrading mythtv-database still won't go because it's trying to connect to the wrong mysql server (it provides the IP of an old server I'm no longer connecting to). I've edited /etc/mysql/my.cnf and /etc/mythtv/mysql.txt. Anything I'm missing here?

Second problem is much more substantial; the video playback is extremely zoomed in and I can't seem to get it zoomed out. It's tough to get my bearings looking at the image, but it seems like it zooms into the top right corner of the screen when watching a recording or livetv. I haven't tweaked any settings since 0.19, so what could be the issue here? Changing the over/underscan only seems to help resize teh image, not zoom it in or out. On the bright side though, the thumbnail of recordings does show the correct dimensions so the video is being grabbed correctly, just displaying wrong in fullscreen.

This mythtv-database related problem - its a backend only machine? So
mythbackend is not starting off the right server?

The zooming in problem, there are some aspect ratio settings that might be
your first thing to look at.

On 9/13/06, Scott Ferguson <email address hidden> wrote:
>
> Using Mario's 0.20 packages here, the overall upgrade went smoothly
> except for two issues:
>
> One, upgrading mythtv-database still won't go because it's trying to
> connect to the wrong mysql server (it provides the IP of an old server
> I'm no longer connecting to). I've edited /etc/mysql/my.cnf and
> /etc/mythtv/mysql.txt. Anything I'm missing here?
>
> Second problem is much more substantial; the video playback is extremely
> zoomed in and I can't seem to get it zoomed out. It's tough to get my
> bearings looking at the image, but it seems like it zooms into the top
> right corner of the screen when watching a recording or livetv. I
> haven't tweaked any settings since 0.19, so what could be the issue
> here? Changing the over/underscan only seems to help resize teh image,
> not zoom it in or out. On the bright side though, the thumbnail of
> recordings does show the correct dimensions so the video is being
> grabbed correctly, just displaying wrong in fullscreen.
>
> --
> Update to .20
> https://launchpad.net/bugs/32169
>

--
Mario Limonciello
<email address hidden>

Well I looked more into this. For the database thing, mythtv-database will
generate a password and store it in /etc/mythtv/mysql.txt. Modify your
local ~/.mythtv/mysql.txt to match this.

On 9/13/06, Scott Ferguson <email address hidden> wrote:
>
> Using Mario's 0.20 packages here, the overall upgrade went smoothly
> except for two issues:
>
> One, upgrading mythtv-database still won't go because it's trying to
> connect to the wrong mysql server (it provides the IP of an old server
> I'm no longer connecting to). I've edited /etc/mysql/my.cnf and
> /etc/mythtv/mysql.txt. Anything I'm missing here?
>
> Second problem is much more substantial; the video playback is extremely
> zoomed in and I can't seem to get it zoomed out. It's tough to get my
> bearings looking at the image, but it seems like it zooms into the top
> right corner of the screen when watching a recording or livetv. I
> haven't tweaked any settings since 0.19, so what could be the issue
> here? Changing the over/underscan only seems to help resize teh image,
> not zoom it in or out. On the bright side though, the thumbnail of
> recordings does show the correct dimensions so the video is being
> grabbed correctly, just displaying wrong in fullscreen.
>
> --
> Update to .20
> https://launchpad.net/bugs/32169
>

--
Mario Limonciello
<email address hidden>

Aye, I changed the ~/.mythtv/mysql.txt as well, both are identical.

As far as the aspect ratio, all I could find was pressing W during playback. Is there a way I can manually tweak these? I was poking in the Edit Keys section of Mythsetup but couldn't find anything that would give me what I needed, and I plowed through the Setup menus a few times with no luck.

By default I believe it tries to "fill" the screen, and hence your zoom.
Under the page that lets you set output resolutions for different input
resolutions, you can change the default aspect ratio (what controlled by W).

On 9/13/06, Scott Ferguson <email address hidden> wrote:
>
> Aye, I changed the ~/.mythtv/mysql.txt as well, both are identical.
>
> As far as the aspect ratio, all I could find was pressing W during
> playback. Is there a way I can manually tweak these? I was poking in
> the Edit Keys section of Mythsetup but couldn't find anything that would
> give me what I needed, and I plowed through the Setup menus a few times
> with no luck.
>
> --
> Update to .20
> https://launchpad.net/bugs/32169
>

--
Mario Limonciello
<email address hidden>

Aye, the problem here is that in changing the aspect ratio nothing happens. I need to zoom out, not in, and by setting to just a standard 4:3 all I see is a very zoomed in view of the top left corner. If it helps diagnose, the OSD is also zoomed in. Attempting to set different video settings for both GUI and playback has no effect whatsoever, except on the GUI part.

Any ideas yet on forcing mythtv-database to connect to the right server when it configures? To answer your initial question, this is a backend/frontend but was formerly just a frontend. For whatever reason, even with a correctly set /etc/mysql/my.cnf and /etc/mythtv/mysql.txt (as well as ~/.mythtv/mysql.txt) it's still getting the IP of the old backend from somewhere.

Your zoom problem sounds like an XV bug to me. I seem to recall having something similar happen once with another program.

Rejecting as duplicate