As of yesterday evening 0.22 has passed into the branch (from trunk). This is the stage before 'tagged' and beta release. You can run the 0.22 branch, but I recommend the 0.22-fixes as it will be updated with bugfixes faster. (which will be needed) There's no longer a need to apply JYA's VDPAU patches as it's built-in.

A warning: once you upgrade to 0.22anything your database schema will be changed permanently. You should back up your existing database before trying 0.22, in case you want to revert.

Here's my procedure:
$ sudo -i
# cd /usr/local/src
# mysqldump -u mythtv -pmythtv mythconverg -c > mythtv_backup.sql && tar -cjf cygnus-mythtv_mysql.tar.bz2 mythtv_backup.sql --remove-files
# svn co http://svn.mythtv.org/svn/branches/release-0-22-fixes/ mythtv-fixes-0.22.-R19
{get build# at end}
# mv mythtv-fixes-0.22.-R19 mythtv-fixes-0.22.{build#}-R19
{get latest R5000 patch for trunk and put in mythtv-fixes-0.22.{build#}-R19}
# cd mythtv-fixes-0.22.{build#}-R19/mythtv
# patch -p0 < ../r5000_r19.patch
{In libs/libmythtv/r5000device.cpp add #include <algorithm>}
{In libs/libavcodec/golomb.h add #include "limits.h"}
# ./configure --enable-proc-opt --enable-vdpau --enable-xvmc-opengl --enable-opengl-video --enable-opengl-vsync --enable-ffmpeg-pthreads --enable-xvmc --enable-xvmc-vld --enable-xvmc-pro --enable-glx-procaddrarb --enable-libfaad --enable-libfaac --enable-libmp3lame --enable-libxvid --enable-libfftw3 --disable-xvmcw --disable-directfb --disable-joystick-menu --disable-ivtv --disable-firewire --disable-dbox2 --disable-hdhomerun --disable-audio-oss
# make -j 4
{To build MythTV on a multi-CPU machine (or with distcc), specify "-j numjobs". Two concurrent jobs is recommended for a single CPU system. Do not set the number of jobs too high}
# make uninstall
# make install

# cd ../themes
# ./configure
# make
# make uninstall
# make install

# cd ../mythplugins
# ./configure --enable-all --enable-opengl --disable-mythphone --disable-aac
# qmake mythplugins.pro
# make -j 4
# make uninstall
# make install
{MythWeather needs libxml-parser-perl libxml-perl libxml-libxml-perl libxml-simple-perl libdate-manip-perl libsoap-lite-perl libimage-size-perl}

Correction, on the Myth config line:
./configure --enable-proc-opt --enable-vdpau --enable-nonfree --enable-opengl-video --enable-opengl-vsync --enable-ffmpeg-pthreads --enable-xvmc --enable-xvmc-vld --enable-xvmc-pro --enable-glx-procaddrarb --enable-libfaad --enable-libfaac --enable-libmp3lame --enable-libxvid --enable-libfftw3 --disable-amd3dnow --disable-amd3dnowext --disable-xvmcw --disable-directfb --disable-joystick-menu --disable-ivtv --disable-firewire --disable-dbox2 --disable-hdpvr --disable-hdhomerun --disable-audio-pulse --disable-audio-oss
Of course you'll want to make some changes if you don't have the same hardware I have.

This is great news! I'll have to check it out once I have some time. It was great that JYA officially joined the MythTV Dev Team.

Cheers,
Kermee

Oh man... if I wasn't going to be on a business trip for two weeks I'd hop all over this. If I did I can imagine the phone calls I'd be getting from home about the TV not working when little bugs show up!

Is HDHomerun multirec included in .22-fixes?

Yeah, I'm fixing to go to the San Juan Islands for 4 days, so I'm waiting. I upgraded my client computer, but of course Myth there now complains that the database schema is 30 revisions out-of-date!

Plugins won't compile, but I'm sure that's some missing include I have to analyze in-depth.

Is HDHomerun multirec included in .22-fixes?
No ideaer. I have the R5000. Commercial flagging works on the pure H.264 transport stream, but not lossless remux for removing commercials. Errors out every time, and Alan's retired now.

There is no support for H.264 commercial flagging in 0.22. iamlindoro says "patches most welcome", but they've rejected Alan's patches so many times he's pissed now.

PHA!

Warning: MythTV 0.22 has now been "unbranched". Do not try to use it. They jumped the gun.

PHA!

Warning: MythTV 0.22 has now been "unbranched". Do not try to use it. They jumped the gun.

Heh.... Glad I didn't hop on it!!!

I'll be in Idaho Falls / West Yellowstone for two weeks for conferences on the next generation high temp nuclear reactors. I don't feel like remote administrating my HTPC from there every time it hickups!

The San Juans are beautiful... Have fun!

Is that 'high-temp' fusion? Next-gen tokamuk?

If fission, that doesn't sound good...

But yer a lucky dog!

Fission. The next generation is far beyond what most people think. Much lower waste output, helium used as the coolant (helium does not transport radioactivity), can be very small scale.... In the grand scheme of things one of the safest and most efficient forms of power generation. I provide the actual graphite core of the reactor. Pretty interesting...

At any rate, I had heard .22 was targeted for Sept/Oct. This must be a first step in that release. I remember seeing it was put in the Freeze not too long ago (with one or two exceptions). I'm really looking forward to giving this a try.

What are the major changes expected for .22?

What are the major changes expected for .22?

hdpvr support, completely redone GUI that seems to be one of the most advanced out there with everything configurable (main thing that slowed down the .22 release), fixed channel scanner, vdpau support, bux fixes, sure there is more but those are the important ones to me.

What are the major changes expected for .22?

What blackoper said, but this is a full rewrite from using QT3 to QT4, so you can expect delays and problems just like with KDE going from 3 to 4.

I just set up two ION based systems. In the first one I used the SVN version of 0.22. It seems to be pretty stable, but the plugins aren't all yet available. But, very few crashes.

On the second system I used 0.21 plus the fixes, at quantumstate's recommendation. Not only do most of the plugins not compile, the ones that do crash MythTV!

From my perspective, the 0.22 SVN is more stable than 0.21 + fixes. I am going to use 0.22 SVN on both of them. I just hope the plugins can be added at some time in the future.

Paul I've said many times before you must have the following libs installed for plugins to compile & install on 0.21-fixes:
libxml-parser-perl libxml-perl libxml-libxml-perl libxml-simple-perl libdate-manip-perl libsoap-lite-perl libimage-size-perl

And if mythplugins fails build the problem may be that /etc/alternatives/qmake points to qt3 rather than qt4

./configure --enable-all --enable-opengl --disable-mythphone --disable-aac
qmake mythplugins.pro
make -j 4
make uninstall
make install

Thanks, quantumstate. In spite of all of the prerequisites that I had already installed, I still needed all of those except libxml-parser-perl.

I doubt if I will try 0.21-fixes again. 0.22 trunk is working pretty good for me. Some of the plugins may not have compiled, but it didn't exit with an error. I don't know if the prerequisites are the same for 0.22 plugins, but I may try and compile them again.

One plugin that I used a lot is mythstream, but I see that is not an official plugin.

http://home.kabelfoon.nl/~moongies/streamtuned.html

Yes, you have to manually comb through the plugins compile in order to find problems, as errors are not fatal. (convenience, I guess)

I am timid to try 0.22 again, after past bad experiences and excoriation from developers. If enough ppl report decent operation I will try it.

Thanks for the mythstream ref. I'll check it out.
Ah, I see mythstream is an internet radio app. I prefer streamtuner, as it engages streamripper to record and label all songs. Works great!

I wasn't able to compile mythstream. It does exit with errors.

Is streamtuner a MythTV plugin? Or do you have to exit Myth to run it.

I just noticed the mythstream snapshot on the top of the page. That wasn't what I tried to compile.

I'll have to give that version a try.

The SVN version of mythstream exits with an error faster that the 0.18 version!

Streamtuner & Streamripper are standalone apps in the repository.

Stupid question: why is MythTV still at version 0.xx? It's been out for a while. Shouldn't it at least be a little closer to version 1.0 than it is?

Stupid question: why is MythTV still at version 0.xx? It's been out for a while. Shouldn't it at least be a little closer to version 1.0 than it is?

Why?
http://en.wikipedia.org/wiki/Software_versioning

Stupid question: why is MythTV still at version 0.xx? It's been out for a while. Shouldn't it at least be a little closer to version 1.0 than it is?
Yes it should.

I've complained about the slow pace and the reasons for it numerous times here, but it doesn't make any difference.

Oh, I wasn't complaining. Just curious. I don't even use Myth. Just seemed odd that interfaces are being over hauled and such and so many people are using it as well as it being pretty stable and out for a while that it hasn't reached version 1.0 yet.

Usually, from what I've seen, developers don't really worry about changing the interface of things much at least until it's passed version 1.0. Just seems odd is all. But I probably don't understand it correctly (not the first time in my life ;) ).

I doubt they ever do a 1.0 - I think the devs view it a century long beta project hehe

It's branched again!!!

At last look there were only 22 bugs on the list before release...

Eh;
You guys go ahead and let me know...

Every 0.21-fixes release I've tried after 21594 has been utterly unable to handle video inconsistencies without crashing. And no 0.22 I've tried could handle H.264 transport streams (DishNetwork) properly for time-based operations -or- commercial skip. And Alan has stopped working on the R5000-HD patch. I may be stuck in Amish times.

It hit RC-1 this evening! I think I'll give it a compile tomorrow to see if everything makes clean and then install this weekend.

Hopefully the new version is ready fro Primetime. I'd like to ditch windows on my HTPC if Myth would work w/o too much manual configuration.

Hopefully the new version is ready fro Primetime. I'd like to ditch windows on my HTPC if Myth would work w/o too much manual configuration.
Ready for primetime? I've been using it exclusively since 2005, version 0.18 IIRC, and it's always worked fine for me. I'm curious what your definition of "ready for primetime" is.

Ready for primetime means I can install it and have it just work w/o having to do a lot of manual configuration. Have you been able to get sleep support to work? How about Dolby digital/hdtv tuner?

Ready for primetime means I can install it and have it just work w/o having to do a lot of manual configuration. Have you been able to get sleep support to work? How about Dolby digital/hdtv tuner?
Even the old Tivo S1 I used to own didn't work without some configure during setup. What the heck does sleep supoort have to do with MythTV? That's a function of the OS and hardware. And I haven't tried it since my master runs 24/7 and I don't want it to sleep. It's not just a MythTV backend. It also runs my other servers. Every HDTV tuner I've used works. I'm not sure about Dolby sound, and couldn't care less. The fatcs are is that is has been recording HDTV for me for over 4 years and I dumped my Tivo soon after installing it. So if it can (and does) replace a Tivo, I'd call it more than ready for prime time. BTW, my Tivo didn't have a sleep mode either.

I'm not enough of a "geek" to get Myth to work. I had one challenge after the other and just gave up on it. I tried XP media center and had a lot of problems with it also (AKA not ready for prime time either). I decided to give W7MC a try and it just worked after installation and basic setup. Sure there are DRM issues I'm dealing and I'd like to switch to Myth once it can work w/o having to be totally geek.

For any software to be ready for primetime it should be easy to setup. If Myth ever evolves to the point where ALL the setup can be done w/o any terminal commands it will be ready for primetime IMHO. Ubuntu does setup w/o terminal, it IS ready for primetime IMHO.

Ready for primetime means I can install it and have it just work w/o having to do a lot of manual configuration. Have you been able to get sleep support to work? How about Dolby digital/hdtv tuner?

No sleep for me, my servers run 24/7. Dolby digital works through spdif without a problem for me, and I'm currently using 3 different QAM/ATSC tuners. You have to do some configuration if you want it to work like you want it to. But out of the box and after about 15 minutes I can have mythtv about 80-90% the way I want it (and i'm pretty particular). It would work well for my family at that point, but then i tweak it to be perfect for me. I'm using well supported hardware and having been using myth since 2006, so I'm sure it's quicker for me than many. On the flipside, the installs are better than they used to be too...

I found i had to spend similar time configuring windows media center applications (GBPVR, mediaportal, MCE, etc) to get them the way I wanted too. But cost of OS/software with my many computers and the feature set of mythtv has made me stick with myth (and no DRM). The feature I want most from windows media center is cable card support - but not at the cost of the DRM that comes along with it, or the computer I have to buy (and not build) to use it.

Okay, that was longer than I was planning.

I have used sleep on my laptop though (running Ubuntu Jaunty).

For any software to be ready for primetime it should be easy to setup. If Myth ever evolves to the point where ALL the setup can be done w/o any terminal commands it will be ready for primetime IMHO. Ubuntu does setup w/o terminal, it IS ready for primetime IMHO.
I built stand alone boxes for my grown kids using Mythbuntu 9.04. Not once did I have to use the terminal iirc. Each box had 2 HDTV tuners.

Servicetech, I'll save you some time and tell you that Myth will never be as you describe. Development has slowed to a crawl as it does exactly what the devs want, and that is the test.

Well, I've been running .22-fixes since Friday. So far so good. No issues at all that are showstoppers. No crashes!

VDPAU integration is working well and I'm looking for a chance to play with HDHomerun multirec...