Anyone running 0.22 trunk?

I've got it installed, and so far, it seems stable. I'm interested in it, cause I want to pick up a pair of HD-PVRs and get rid of my ComCrap DVR forever!

One problem I'm having is that I have an NVIDIA 9500GT. I'm trying to get VDPAU configured. (I've previously used 0.21-fixes from the Avenard repo and had VDPAU working fine.) I created the new profile, specified 'vdpau', as explained here:
http://avenard.org/media/MythTV_%26_VDPAU/MythTV_%26_VDPAU.html
(See the first question in the Quick F.A.Q. section.)

But, I still don't get VDPAU. Anyone had a similar problem w/ 0.22?

-Mark

Just switched to trunk this past weekend. And have two HDPVRs working (yeah!).

I'm using LinHES R6 so it was still pre-compiled for me. I'm assuming you checked out the source and built it yourself. So perhaps a configuration option?

I did not set any "resolution rules" when I added VDPAU as described in FAQ 1. I guess it's something you can try.

What is mythfrontend spewing out at run-time?

One more thing: Try no deinterlacing first.

Hi,

Heh, sorry, I should have mentioned, I'm on Ubuntu 9.04 and I'm using the Mythbuntu Weekly Builds to install 0.22 trunk, so, I did not build from source.
From what I read, VDPAU should be enabled in these builds.

I can provide mythfrontend output logs when I get home this evening.

Thanks!

-Mark

I've been using 0.22 svn for about the past six months. It's mostly stable. I still get the occasional "video frame buffering failed too many times" error, which doesn't happen with 0.21-fixes, but they are more rare with the latest code.

VDPAU works fine for me, but I build from source, I don't download prebuilt binaries.

-- Kevin

Just switched to trunk this past weekend. And have two HDPVRs working (yeah!).

somewhat OT:

is 1080i working on the HDPVR's yet?

Kevin,

Which NVIDIA card do you have?

What have you defined for your profile, to enable VDPAU?

-Mark

I'm using onboard NVIDIA 8200 video, on two different motherboards.

I'm at work now, so I don't have access to the profile settings I used. Basically, any profile setting works, as long as you specify VDPAU. I played around with the different de-interlacers. The most advanced one (don't remember what it's called) won't work on my IGP, it's too slow. I get choppy video. The other, less demanding de-interlacers work fine, though.

When I get home, I can give you my exact profile setup, if you like.

-- Kevin

Also, if you have an AMD CPU and are using onboard video, make sure you disable the ondemand CPU governor, or at least set the minimum frequency to 1.8 GHz, otherwise you'll get choppy video even with VDPAU enabled.

Is .22 compatible with .21 frontends (protocol wise). IOW's, can you run a .21 frontend box with a .22 server?

Is .22 compatible with .21 frontends (protocol wise). IOW's, can you run a .21 frontend box with a .22 server?

Nope. I tried. If you run a .22 frontend, you will need a .22 backend as well.

Here's what I get when mythfrontend starts up:
2009-08-06 19:39:18.496 mythfrontend version: trunk [Unknown] www.mythtv.org
2009-08-06 19:39:18.613 AudioPulseUtil: Suspend Success
2009-08-06 19:39:18.648 Using runtime prefix = /usr
2009-08-06 19:39:19.914 Empty LocalHostName.
2009-08-06 19:39:19.914 Using localhost value of jupiter
2009-08-06 19:39:20.072 New DB connection, total: 1
2009-08-06 19:39:20.120 Connected to database 'mythconverg' at host: localhost
2009-08-06 19:39:20.120 Closing DB connection named 'DBManager0'
2009-08-06 19:39:20.155 ScreenSaverX11Private: Gnome screen saver support enabled
2009-08-06 19:39:20.156 DPMS is active.
2009-08-06 19:39:20.162 Primary screen: 0.
2009-08-06 19:39:20.165 Connected to database 'mythconverg' at host: localhost
2009-08-06 19:39:20.166 Using screen 0, 1920x1080 at 0,0
2009-08-06 19:39:20.251 MythUI Image Cache size set to 20971520 bytes
2009-08-06 19:39:20.255 Enabled verbose msgs: important general
2009-08-06 19:39:20.568 The theme (defaultmenu) is missing a themeinfo.xml file
2009-08-06 19:39:21.618 The theme (defaultmenu) is missing a themeinfo.xml file
2009-08-06 19:39:21.704 Desktop video mode: 1920x1080 60 Hz
2009-08-06 19:39:21.848 Primary screen: 0.
2009-08-06 19:39:21.849 Using screen 0, 1920x1080 at 0,0
2009-08-06 19:39:21.850 Using theme base resolution of 1280x720
2009-08-06 19:39:21.862 LIRC, Error: Failed to connect to Unix socket '/dev/lircd'
eno: No such file or directory (2)
2009-08-06 19:39:21.862 JoystickMenuThread Error: Joystick disabled - Failed to read /home/mjb/.mythtv/joystickmenurc
2009-08-06 19:39:22.280 Using the OpenGL painter
2009-08-06 19:39:22.525 Loading base theme from /usr/share/mythtv/themes/MythCenter-wide/base.xml
2009-08-06 19:39:22.881 Loading base theme from /usr/share/mythtv/themes/default-wide/base.xml
2009-08-06 19:39:22.952 Loading base theme from /usr/share/mythtv/themes/default/base.xml
2009-08-06 19:39:22.998 Current Schema Version: 1238
2009-08-06 19:39:23.003 Connecting to backend server: 192.168.1.110:6543 (try 1 of 5)
2009-08-06 19:39:23.014 Using protocol version 45
2009-08-06 19:39:23.192 Registering Internal as a media playback plugin.
2009-08-06 19:39:23.294 Cannot load language en_us for module mytharchive
2009-08-06 19:39:23.352 Cannot load language en_us for module mythbrowser
2009-08-06 19:39:23.354 Registering WebBrowser as a media playback plugin.
2009-08-06 19:39:23.354 Cannot load language en_us for module mythbrowser
2009-08-06 19:39:23.526 Cannot load language en_us for module mythflix
2009-08-06 19:39:23.648 MMUnix::GetDeviceFile(/sys/block/sdb/bdi), Error - udevinfo failed to start!
2009-08-06 19:39:23.648 MMUnix::AddDevice() Error: failed to stat /dev/bdi,
eno: No such file or directory (2)
2009-08-06 19:39:23.657 MMUnix::GetDeviceFile(/sys/block/sdb/power), Error - udevinfo failed to start!
2009-08-06 19:39:23.657 MMUnix::AddDevice() Error: failed to stat /dev/power,
eno: No such file or directory (2)
2009-08-06 19:39:23.664 MMUnix::GetDeviceFile(/sys/block/sdb), Error - udevinfo failed to start!
2009-08-06 19:39:23.671 MMUnix::GetDeviceFile(/sys/block/sr0/bdi), Error - udevinfo failed to start!
2009-08-06 19:39:23.672 MMUnix::AddDevice() Error: failed to stat /dev/bdi,
eno: No such file or directory (2)
2009-08-06 19:39:23.679 MMUnix::GetDeviceFile(/sys/block/sr0/power), Error - udevinfo failed to start!
2009-08-06 19:39:23.679 MMUnix::AddDevice() Error: failed to stat /dev/power,
eno: No such file or directory (2)
2009-08-06 19:39:23.684 MMUnix::GetDeviceFile(/sys/block/sr0), Error - udevinfo failed to start!
2009-08-06 19:39:23.685 MonitorRegisterExtensions(0x100, gif,jpg,png)
2009-08-06 19:39:23.685 Cannot load language en_us for module mythgallery
2009-08-06 19:39:23.717 Cannot load language en_us for module mythgame
2009-08-06 19:39:23.781 Cannot load language en_us for module mythmovies
2009-08-06 19:39:24.043 MonitorRegisterExtensions(0x40, mp3,mp2,ogg,flac,wma,wav,ac3oma,omg,atp,ra,dts,aac,m4a)
2009-08-06 19:39:24.048 Cannot load language en_us for module mythmusic
2009-08-06 19:39:24.110 Cannot load language en_us for module mythnews
2009-08-06 19:39:24.233 Cannot load language en_us for module mythvideo
2009-08-06 19:39:24.355 Cannot load language en_us for module mythweather
2009-08-06 19:39:25.779 Loading window theme from /usr/share/mythtv/themes/MythCenter-wide/menu-ui.xml
2009-08-06 19:39:25.819 Loading menu theme from /usr/share/mythtv/themes/defaultmenu//mainmenu.xml
2009-08-06 19:39:25.820 Found mainmenu.xml for theme 'MythCenter-wide'
2009-08-06 19:39:25.823 Using NV NPOT texture extension
2009-08-06 19:39:36.618 Loading menu theme from /usr/share/mythtv/themes/defaultmenu//library.xml
2009-08-06 19:39:38.326 New DB connection, total: 2
2009-08-06 19:39:38.328 Connected to database 'mythconverg' at host: localhost
2009-08-06 19:39:38.444 Loading window theme from /usr/share/mythtv/themes/default-wide/recordings-ui.xml

2009-08-06 19:39:46.485 Loading window theme from /usr/share/mythtv/themes/default-wide/recordings-ui.xml


And when I actually play a program, I get:
2009-08-06 19:43:43.785 TV: Attempting to change from None to Watching WatchingRecording
2009-08-06 19:43:43.851 Using protocol version 45
2009-08-06 19:43:43.853 TV: StartPlayer(0, Watching WatchingRecording, main) -- begin
2009-08-06 19:43:44.875 mpegts_read_header: TS packet size = 188
2009-08-06 19:43:45.166 AFD: Opened codec 0xb230cc0, id(MPEG2VIDEO) type(Video)
2009-08-06 19:43:45.167 AFD: codec AC3 has 6 channels
2009-08-06 19:43:45.189 AFD: Opened codec 0xb379260, id(AC3) type(Audio)
2009-08-06 19:43:45.205 Opening audio device 'default'. ch 6(6) sr 48000
2009-08-06 19:43:45.206 Opening ALSA audio device 'default'.
2009-08-06 19:43:45.374 ALSA, Warning: mmap not available, attempting to fall back to slow writes.
2009-08-06 19:43:45.838 Mixer unable to find control PCM
2009-08-06 19:43:45.838 Mixer unable to find control PCM
2009-08-06 19:43:45.838 Mixer unable to find control PCM
2009-08-06 19:43:45.838 Mixer unable to find control PCM
2009-08-06 19:43:45.838 Mixer unable to find control PCM
2009-08-06 19:43:45.838 Mixer unable to find control PCM
2009-08-06 19:43:45.838 Mixer unable to find control PCM
2009-08-06 19:43:45.838 Mixer unable to find control PCM
2009-08-06 19:43:45.838 Mixer unable to find control PCM
2009-08-06 19:43:45.838 Mixer unable to find control PCM
2009-08-06 19:43:45.838 Mixer unable to find control PCM
2009-08-06 19:43:45.838 Mixer unable to find control PCM
2009-08-06 19:43:45.839 Mixer unable to find control PCM
2009-08-06 19:43:45.839 Mixer unable to find control PCM
2009-08-06 19:43:45.839 Mixer unable to find control PCM
2009-08-06 19:43:47.349 NVP(0): Forcing decode extra audio option on (Video method requires it).
2009-08-06 19:43:47.359 OSD Theme Dimensions W: 640 H: 480
2009-08-06 19:43:47.527 Unknown font: descriptfont in textarea: description
2009-08-06 19:43:47.775 WriteAudio: buffer underrun
2009-08-06 19:43:48.886 TV: StartPlayer(0, Watching WatchingRecording, main) -- end ok
2009-08-06 19:43:48.889 TV: Changing from None to Watching WatchingRecording
2009-08-06 19:43:48.889 OpenGLVideoSync()
2009-08-06 19:43:48.894 Realtime priority would require SUID as root.
2009-08-06 19:43:49.183 ScreenSaverX11Private: DPMS Deactivated 1
2009-08-06 19:43:49.400 Video timing method: SGI OpenGL

The line that reports "(MPEG2VIDEO)", I believe indicates that VDPAU is not in use.
When I ran 0.21 w/ VDPAU patches, I'd get something like "(MPEG2VIDEO_VDPAU)".

-Mark

Nope. I tried. If you run a .22 frontend, you will need a .22 backend as well.
I thought as much. Thanks.

somewhat OT:

is 1080i working on the HDPVR's yet?

Yes. And according to this page (http://www.mythtv.org/wiki/HDPVR) "native passthrough" output should work fine now too with the latest firmware, as changing "on the fly" is stable. Of course one needs to update the firmware on windoze.

I did a few 1080i recordings and they were fine. But I put my DirecTV boxes in 720p since all my screens are 720p.

Watching LiveTV has not been very reliable on my system. We don't do that much in our house so it's not really a problem for us. But I have seen changing channels three or four times will core dump mythfrontend. I haven't taken the time to check into it any further.

I noticed LinHES has made a new svn snapshot and I'll install it tonight.

The line that reports "(MPEG2VIDEO)", I believe indicates that VDPAU is not in use.
When I ran 0.21 w/ VDPAU patches, I'd get something like "(MPEG2VIDEO_VDPAU)".

Yes I think you are right. I'll check my log tonight to verify.

You probably have done this but make sure you disable the compositing extension of Xorg. "nvidia-xconfig --no-composite" or edit your xorg.conf file. Also enable "OpenGL VSync" in the MythTV playback setup. I think your log says you have it set but I thought I would just mention it just in case.

I was hoping the log would give more of a hint...it looks like Myth is just deciding to use something other than VDPAU.

Anyone have a crystal ball to gaze into and see when .22 will be released?

guesstimations will also be accepted :D (and appreciated)

Thanks!

It's really hard to say. Personally I did not want to wait any longer. I've been wanting the HDPVR ever since it was announced so I could record HD from the satellite box over the component instead of 480i over s-video. And with football coming up I decided to see how stable trunk was (so far so good!)

If you keep an eye on the roadmap (http://svn.mythtv.org/trac/roadmap), when it gets near the open tickets will be moved to 0.23 from 0.22. When that happens a release should follow soon. It really hasn't changed much the last few weeks...a few more bugs, a few more fixes but staying around 75%.

The other thing you can do is look here:
http://svn.mythtv.org/trac/query?status=accepted&status=assigned&status=infoneeded&status=infoneeded_new&status=new&status=started&groupdesc=1&group=priority&order=priority&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&milestone=0.22

....for how many tickets have a priority of "Major" or higher. Right now, that number is 22. It may not sound like much, but, these statuses don't change very often, and that number is actually higher now than I've ever seen it in the past several months. I've seen it as low as 16.

I suspect it's going to be a while.....

-Mark

PS Meanwhile, it's only been a few days for me, but 0.22 trunk is (so far) surprisingly stable.

I suspect it's going to be a while.....


The reason I ask is I am hoping to setup a HTPC this fall/winter and am kind of hoping it will be released by then. Of course time will tell when!

I will keep half an eye on the roadmap and Magor + Critical bugs.

Thanks!

Looks like end of September:

http://pdavila.homelinux.org:8080/blog/?p=351

does anyone happen to have instructions on how to upgrade from 0.21 to 0.22-trunk?

If your distro doesn't have 0.22 binaries, then you'll have to compile it. See here (http://www.mythtv.org/docs/mythtv-HOWTO.html) and here (http://www.mythtv.org/wiki/VDPAU).

Note that your database will be updated, and you won't be able to revert it, so it's a good idea to back it up.

Many of us here have compiled mythtv before, so let us know if you run into any snags.

Thanks Mythmaster,

I am using mythbuntu. Is there a way to get precompiled files from mythbuntu rather than compiling myself?

I've found this guide: http://vanvalkinburgh.org/blog/646
but I am getting "file no longer exists" when trying to download

Looks like end of September:

http://pdavila.homelinux.org:8080/blog/?p=351

Thanks for the info!

I wonder if it will finished in time for Ubuntu 9.10? (release date 2009-10-29)

I think it's hilarious all those who think there's an actual schedule. I've said here a thousand times that the devs are happy with the MythTV system as it is, and there is very little improvement in 0.22 over 0.21. There have been so many battles and are now so many standoffs that there will be no more progress. It is, what it is.

I am sticking with fixes, after my experiences with trunk, until further notice.

I I've said here a thousand times that the devs are happy with the MythTV system as it is, and there is very little improvement in 0.22 over 0.21. The one improvement I'm looking for is a fix to a problem where dvds freeze or does not show the background image on menu screens. Apparently that is fixed in 0.22 (via ffmpeg).

Thanks Mythmaster,

I am using mythbuntu. Is there a way to get precompiled files from mythbuntu rather than compiling myself?

I've found this guide: http://vanvalkinburgh.org/blog/646
but I am getting "file no longer exists" when trying to download

I believe Mythbuntu has weekly builds.

http://www.mythbuntu.org/auto-builds

I don't use mythbuntu myself so can't say much more than that.

I think it's hilarious all those who think there's an actual schedule. I've said here a thousand times that the devs are happy with the MythTV system as it is, and there is very little improvement in 0.22 over 0.21. There have been so many battles and are now so many standoffs that there will be no more progress. It is, what it is.

I am sticking with fixes, after my experiences with trunk, until further notice.

There are always features in new versions of software that appeal to at least a subset of users. I happily skipped 0.21 because with the new stuff included I didn't see the need to upgrade. But for example, storage groups was a feature many users were clamoring to have. So to them 0.21 was critical. I want 0.22 for the HD-PVR support, simple as that.

I suppose you are laughing over a Free Software project having a release schedule. Granted they won't do a release until it's ready, but it does look reasonable that they are shooting for a September time frame.

.... There have been so many battles and are now so many standoffs that there will be no more progress. It is, what it is.

....

Sounds like it might be time to fork the project, if one group has updates they think are actually valuable enough to justify a fork.

djb61230, HD-PVR support is available in -fixes if you enable that compile option. But if trunk's working for you, great. When I tried it over a couple months it was a trainwreck.

Mac I've been calling for this until I'm blue in the face, particularly hoping for JVA to lead a fork. But he has a new kid and is busy with those (less) important things now. XBMC is working on a frontend for the Myth backend, and I'm looking forward to that. They also have a full PVR in the works, but that's a ways away.

The effective, creative, and non-political Myth devs have gone away (from the sh*tstorms), and the project is deadlocked. For the remaining devs Myth is about good enough to do what they want, and the couple of Kings Of The Hill block any real improvements, and so it's stuck. 0.22 has been codgitating for years now with no real improvement; the answer is always "it's ready, when it's ready". I am just trying to be happy with what we've got, and harvesting tons of videos in pure transport stream.

djb61230, HD-PVR support is available in -fixes if you enable that compile option. But if trunk's working for you, great. When I tried it over a couple months it was a trainwreck.



I probably would have used the 21-fixes binaries if I had been running 21. Since I was on 20-fixes it made more sense to me to go to the trunk. LinHES R6 made it painless to use SVN builds and I thought helping the new LinHES with bug reports and helping other users would be more useful.

I ran in test mode for a few weeks and switched it over to my "production" system about a month ago. There have been issues from time-to-time but overall pretty stable, with new builds each week. Definitely no show stoppers which you must have run into a few months earlier.

You obviously have been watching the project closely for a while to have the wish it was forked. I have just been impatient and unaware of any internal issues. To tell you the truth I have thought about writing my own system, but when you break it down there is a lot to it. Quite a daunting task actually. Even forking is a huge commitment - it's probably why forking generally doesn't happen too often.

I think it's hilarious all those who think there's an actual schedule. I've said here a thousand times that the devs are happy with the MythTV system as it is, and there is very little improvement in 0.22 over 0.21. There have been so many battles and are now so many standoffs that there will be no more progress. It is, what it is.

I am sticking with fixes, after my experiences with trunk, until further notice.

I have been keeping tabs on this as I am looking at setting up a HTPC this fall/winter and would very much like to install the latest version rather then having .22 come out right after I install .21 and have to go through the setup process twice!

I am not worried about an exact date, but if it is going to be 6-9 months out yet I will just setup .21 If less then three months from now I will wait. At this point I am hoping I can wait for .22. I guess time will tell.

djb61230, HD-PVR support is available in -fixes if you enable that compile option. But if trunk's working for you, great. When I tried it over a couple months it was a trainwreck.


I've been using builds from the trunk for about 6 months now. There are some bugs, sure, (a couple of which I've fixed myself) but this isn't a released product. I'd hardly call it a train wreck. And the latest is certainly much more stable than it was 6 months ago.

Mac I've been calling for this until I'm blue in the face, particularly hoping for JVA to lead a fork. But he has a new kid and is busy with those (less) important things now. XBMC is working on a frontend for the Myth backend, and I'm looking forward to that. They also have a full PVR in the works, but that's a ways away.

The effective, creative, and non-political Myth devs have gone away (from the sh*tstorms), and the project is deadlocked. For the remaining devs Myth is about good enough to do what they want, and the couple of Kings Of The Hill block any real improvements, and so it's stuck. 0.22 has been codgitating for years now with no real improvement; the answer is always "it's ready, when it's ready". I am just trying to be happy with what we've got, and harvesting tons of videos in pure transport stream.

You sure do like to put a lot of your demands on people who are volunteering to produce free software for you to use. I'm sure they'd be happy to accept patches from you for any features you want that they haven't implemented themselves yet.

0.22 has been cogitating for years now with no real improvement? 0.21 was released in March of last year. 0.22 has several new features, including totally rewriting the UI engine, making it easier to make pretty skins like XBMC. I've been working on my own MediaStream-inspired skin for a while now. But it's going slow, because I'm not a graphic designer, I'm a software engineer.

And given that people have been wanting a new released version for a while now, doesn't it make sense that they should have a feature freeze, and only be working to fix bugs to get a releasable product? Do you follow the myhtv-dev and mythtv-commits mailing lists? I do. There has been plenty of work taking place to achieve exactly that.

Finally, even if they get fed up with people complaining that what they do isn't good enough, and if they just quit and never produce another version of the software, so what? What obligation do they have? Are you going to be grateful for the software they have given you, or are you going to demand they stop their whining and get back to work? You have this attitude like they owe you something. What do they owe you?

Demands?! What demands? If you follow the listservs you wouldn't have heard a word out of me. I am just following what's happening and HATE the politics. The project is moribund as a result of the politics and mashing down of the creative, who are the true progressives.

Oh, 'plenty of work taking place'? There has been no substantive improvement, in the sense that XBMC has made improvements, for at least two years because the factions are ossified. Where is the feature to conveniently archive a show to an archive directory? Why is H.264-TS handling such a mess? Where is R5000 support? Why doesn't commercial scanning use all methods? Why is the setup system such a convoluted mess? If you step back and look at it with a fresh perspective it is terribly non-intuitive for the n00b.

'You're sure they'd be happy to accept patches for any features you want that they haven't implemented themselves yet?' Reeally? Have you ever submitted a patch for Myth or looked at ones that have been submitted? A very large percentage of legitimate patches, bugs and feature requests are slammed Invalid within hours of being opened. I've tried and tried but have given up. The ethos is you must kowtow to The Few, and not make any waves; you are only there to be a small gear in the Big Machine.

Where in the world did you get the idea I think they owe me anything?! I have been a dyed-in-the-wool open software type for as long as I can remember, having run Debian exclusively for 12 years. I have helped countless ppl do wonderful things with their systems, with no expectation other than an occasional thanks. Don't you know who I am? No sir. My objection is to the decline from advancement, into politics; from the value of all, to the value of only the meanest.

I won't hear to it. It is the death of the project.

You've been bashing the MythTV project for months every chance you get. I'm sick of hearing it.

Yes of course the setup is convoluted. Yes of course it is missing many nice features. That's irrelevant. You complaining that it isn't the way you like it or doesn't have the features you want. You're comparing progress made with that of other projects, like XBMC. To compare progress means you have some expectation of them "measuring up". If they don't measure up, they fail. That's the totally wrong attitude to take with on open source project done on a spare time, volunteer basis.

When I said plenty of work taking place, I meant fixing bugs to get a .22 release out. Not about adding new features. Over the last 6 months, there have been approximately 1490 commits to the code base. That averages to about 8 per day. That sounds like a lot of work to me.

With regard to which features they choose to implement, and which ones they don't, it is a universal truth with all open source software, that the features that are most important to the developers doing the work are the features that get implemented first.

As for submitted patches being rejected, I just went over to the bug tracking database, and did some queries. Since the beginning of time, they have rejected 102 patches as "invalid", and accepted 1418. Reading through the ones that were marked invalid, I agree that they should be invalid. I didn't read through every one, only the most recent dozen or so. If you happen to have an example of a patch that was submitted and (wrongfully) rejected, I'd be interested in seeing it, but I don't expect you to go hunting to dig one up.

-- Kevin

Here is a significant patch which has been rejected for political reasons:
http://svn.mythtv.org/trac/ticket/4752
... I am ambivalent whether to explain the background to you, as it's unlikely to make any difference. And there are many others. You are only agreeing with the rejections to support your own position.

Am I angry about having numerous bugs and suggestions rejected out-of-hand, and getting my face torn off every time I go on the Myth IRC to give input for the good of the project? Yes of course I am. But that does not change the truth that substantive improvement has halted, and that devs' main focus now is slapping down suggested improvements. Try making a substantive improvement sometime; you will not like what happens, I assure you. Except for a few new features, there is no real improvement in 0.22 over 0.21, enough to justify a new rev number. At this rate we are centuries away from 1.0 .

Am I applying the XBMC yardstick to Myth? Of course I am. It's the only way I can clearly convey the petrification in Myth that's happened as a result of the political climate. Good ppl are pissed on and turned off, witness JYA, for God's sake. Did you happen to notice the sh*tstorm he endured over a long period of time for daring to backport VDPAU to -fixes? Apparently not. Unconscionable. I call this a Social Crime.

Myth works and I use it, but I also see how it could be so much better. If you are accepting of the status quo Kevin, and can do with the limitations even knowing what is possible, I feel sorry for you. We are two different ppl, remember.

OK, you guys. I'm calling the police. I did it. They'll be here shortly...

tvlJc8ilD5o

Uh oh, is this going in my Permanent Record?

(For those of you under 40, this was a threat occasionally made by elementary school teachers before you were born)

Back to the topic:

I am using the 0.22 trunk on my Zotac ION board. The only bug that I see is this:

Sometimes bringing up the Program Guide during LiveTV, then exiting, the LiveTV program is no longer displayed. I can hear the audio, but no video. I Ctrl+Alt+d to get the desktop, then Alt+Tab to bring up MythTV. The video is now displayed. Sometimes when I check, there are four mythfrontends listed as running. This may be related.

As for the MythTV developers, here is MY opinion:

They all bow down to the almighty Isaac Richards. He has an army of "Yes Men". If something isn't blessed by King Isaac, then it is beaten down until it dissapears. I have found at least one thing that is dismissed, that I wish was implemented:

To have a LiveTV option where everything IS NOT saved to the hard drive. They refuse to even consider this, even though people (were) constantly asking for it. Their reply was that this is a DVR program, and recording is what it does. If you don't like it, start a fork and make your own version!

Another thing I dislike is the way Schedules Direct was rammed down our throats. Any discussion of using a screen scraper instead of Schedules Direct is quickly squashed. I have decided to use the EIT program guide instead, but it routinely gives incorrect program info. My digital converter will give the correct info, so it is MythTV that is screwing it up. I won't waste my time reporting any bugs, as I am not one of the "Yes Men Army". They usually just say "Don't be cheap and use Schedules Direct instead". I don't think that they actually want the EIT data to work correctly, so that you have to use Schedules Direct, but that is just my opinion.

Yes, Isaac has done a lot to make MythTV the usable application that it is today. I thank him for that.

FYI when I was recording OTA only, EIT worked quite well with 0.21-fixes. I made the settings a certain way though. Maybe it would pay to export your database and downgrade to -fixes. Same with the busted channel scan problem somebody else has.

Trunk was a royal mess when I tried it for a couple of months; then again I use the features extensively. Maybe a casual user wouldn't notice the problems so much.

And with the current state of affairs, I'm afraid to try anything they're actively muggering with. I think they're as messed-up and confused as General Motors. Often the only thing that can break someone down... is themself.

The EIT problem I've had for several versions. It also is on different systems/hardware, so that isn't the cause.

The listings of the programs themselves is good. It is the program details that it gets mixed up. It will have the details of a completely different program! It doesn't hurt anything, and programs set to record will still record. I have my main MythTV getting program info with a screen scraper, and a ftp server running to export the program data to my other MythTV boxes. I will import that data to this unit, eventually. It is still in "build mode" though, so EIT is sufficient.

FYI when I was recording OTA only, EIT worked quite well with 0.21-fixes. I made the settings a certain way though. Maybe it would pay to export your database and downgrade to -fixes. Same with the busted channel scan problem somebody else has.

Trunk was a royal mess when I tried it for a couple of months; then again I use the features extensively. Maybe a casual user wouldn't notice the problems so much.

And with the current state of affairs, I'm afraid to try anything they're actively muggering with. I think they're as messed-up and confused as General Motors. Often the only thing that can break someone down... is themself.

My take...

.22 is the same mess that .21 was about 2 months before it's release. Nothing I see in the bug database is a show-stopper. For people with large scale systems (5+ backends, 1000+ programs recorded) the .22 mythbackend runs about 10x better because of the improvements in IPC and database functions. EIT and the channel scanner rewrite is still a mess but better (DVB is iffy but ATSC is pretty good now). The mythfrontend is still fragile but useable.

But are you running 0.21-fixes or 0.22 WH? fixes worked fine for me. Not sure about the impact of your screen-scraper, but you need very specific settings for EIT. I have to go to work, but will try and remember and post next morn.

I'm using 0.22 trunk on this one, for the VDPAU support. Previous versions I used with the EIT were 0.20 and 0.21. Shouldn't the fixes for previous version be in the trunk of the next version?

I don't try to use EIT and scraper data at the same time. Although it seems that the EIT can be enable just for the channels that don't have external data availavble. That's cool. :cool:

I believe these are what I had to make EIT work right.

In mythtv-settings|General|{4th window} you want Timeout 5, Crosssource UNchecked, and Backendidle 60.

You want Myth to hold the card all the time so it can collect EIT info, so in mythtv-settings|CaptureCards|DVB:0|RecordingOptions UNcheck Open on demand, and check Use for active EIT scan.

In mythtv-settings|VideoSources|OTA|Listingsgrabber you want Transmittedguideonly.

If you have all these settings and the descriptions are still messed up, I recommend downrevving to -fixes. It worked fine for me, although you only get a couple days of Guide.

Several aspects and benefits of trunk are in -fixes, but by no means all. To me, -fixes is the best of both worlds. I add JYA's VDPAU patch as well as R5000 patch, a length and mythcommflag patch for H.264, compile, and it works quite well. Of course to add these patches to the actual SVN would hurt the devs' feelings, so it will never be done.

Those settings are what I have. Most of them are the default settings.

I am going to be setting up another ION board, the POV atom330. I'll try the --fixes on that one. I had to fiddle with this one to get the Hauppauge HVR-950Q USB tuner to work correctly. So, I am just going to leave it for now. If it works, don't break it!

Thanks for the help, anyway. :)

To have a LiveTV option where everything IS NOT saved to the hard drive. They refuse to even consider this, even though people (were) constantly asking for it. Their reply was that this is a DVR program, and recording is what it does. If you don't like it, start a fork and make your own version!

Another thing I dislike is the way Schedules Direct was rammed down our throats. Any discussion of using a screen scraper instead of Schedules Direct is quickly squashed.

I can see their argument in these cases. My guess is that having "real" live TV breaks one of their basic assumptions - that video always comes from a file. Perhaps to us outsiders it seems a simple thing...but maybe to do it is not so simple.

I also think that having a source for reliable guide data was the way to go. Scraping just sucks and long time users remember the days when scraping broke and the hassles involved. I can see them happy to see those days gone since scraping often broke "terms of service" on the web sites. As a user I'm glad I have a legit source and happy to pay $20 a year.

I believe these are what I had to make EIT work right.

In mythtv-settings|General|{4th window} you want Timeout 5, Crosssource UNchecked, and Backendidle 60.

You want Myth to hold the card all the time so it can collect EIT info, so in mythtv-settings|CaptureCards|DVB:0|RecordingOptions UNcheck Open on demand, and check Use for active EIT scan.

In mythtv-settings|VideoSources|OTA|Listingsgrabber you want Transmittedguideonly.

FWIW, EIT will work fine using the card with on demand. I've built several this way and they all worked. Setting myth to lock the cards in will cause some cards not to work properly because they don't have time to intialize at boot time before myth tries to take them over.

Maybe someone knows the fix for this. I have upgraded to 0.22 from source and I briefly get teh channel info before a black screen (and then crash) with live TV. I am using VDPAU and have tried other playback methods. I can see in the log an error about A/V playback decoder. Any help would be greatly appreciated.

This sounds similar to what mine was doing, until I made some adjustments. What dvb card are you using?

Also, make sure that MythTV has permissions to the folder that the video is stored in.

Uh oh, is this going in my Permanent Record?

(For those of you under 40, this was a threat occasionally made by elementary school teachers before you were born)

Now I remember. Yes. Yes, it will... :)

gproa6vzgws

quick question...when watching LiveTV, what button would you press to have it start recording the LiveTV show, if it was not a scheduling recording? I used to just press the record button on my DirectTV remove and that took care of it, is there something similar in MythTV? Thanks.

It's whatever button you want it to be. I believe the default is the r button on the keyboard. On my remotes I always use the record button to send the r. Well, not really, but it gets interpreted as the r in lircrc.