I've seen a number of comments on the boards about stability problems with 0.16. It's hard to tell how widespread/frequent the problems are - sounds like lockups mainly.

0.15 under R4V4.1 has been really stable for me.

So I want to try the not oft used here feature of phpbb and set up a poll

If you are using .16 and have previously used .15 please respond to this poll.

Both have soft spots, 0.16 fixed a number of known problems with 0.15 and 0.15.1, and added a few new ones.

- Frontend crash from hitting record while watching live TV (possibly fixed in CVS?) This is probably the same crash where the system asks if it can record something while you're watching live TV and it doesn't make the transition well.

- Commercial marking for some folks (fixed in CVS)

- ...

Neither one of these affects me enough to be a major problem. I was far more annoyed by the way MythWeather would lock the frontend up about one time in five in the older versions and how badly quotes in search strings or titles were handled.

I upgraded from R4V2 , 0.15.1 to R4V5, 0.16 and went from being rock stable to crashing twice per day. I have recently changed my ivtv driver and that seems to have fixed my problems.

my 2c

just a quick note that going from R4V2 to R4V5 is much different than just going to 0.16 from 0.15.1 the kernel changed significantly between those releases, and some of the changes unfortunately have cause some problems on certain configurations.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

The is another option.. CVS all/MOst cvs addition from the release of .16 have been bug fixes. and the two biggest ones are now fixed in cvs. I have been running .16 cvs and it is rock solid. I would do the upgrade soon as they are expecting new major code release in the next couple weeks. This will mean less stability as they start to incorperate the ui and mfd code into the cvs tree. but i can say enough how much better/stable cvs is at the moment compared to my .16 experience.

r4v5 has been very good to me. no crashes since i upgraded. my only problem is that sometimes the guide sometimes turns all dark gray while watching TV. however, pressing any button fixes it right away so no biggie.

Well, for whatever reason, I had all sorts of issues after I tried to upgrade from my R4V4 Myth box to R4V5 using the ISO image. My PVR-250 kept insisting on selecting composite input despite the mythtv-setup having it configured for s-video, and the menus that pop up on top of live TV kept showing up in dithered grey and were hard to read. After several days of fighting with it (including recompiling mythtv from the source and many versions of ivtv!), I just gave up and reformatted the drive.

Now, I'm up and running with R4V5 since I did a full install to the reformatted drive and the weird issues mentioned above are all gone. I did, however, make sure not to select the packages with xvmc support, since that's what I used when I did the upgrade -- and I wanted to be certain that wasn't the root of my problems. (I used the i686 packages with lirc support, but not xvmc.)

My opinion of R4V5 has improved dramatically since I did this fresh reinstall.... but I still had some things to "tweak" to get it functioning very well. For starters, I noticed that if I enabled the option to deinterlace the TV output, it seemed to cause my audio to randomly stutter and drop out. I tried several different "methods" of deinterlacing given in the menus, but none seemed to cure the audio issues. (I finally realized that in my configuration, this is sort of a non-issue anyway. I don't need this option at all for best results....) I also compiled up the 100z version of ivtv people were recommending in this forum as one of the most stable ones available, and it seemed to solve a couple live TV freezes/crashes I had initially.

The problem I'm seeing now, though, is occasionally, as I scroll through the guide, the front end immediately crashes/dies as I highlight one of the entries? I'm sure this is probably a result of corrupt guide data in the database - but it sure doesn't seem to handle it gracefully!

I've had significant stability issues of the back-end dying with : "QSettings::sync: filename is null/empty" as the very last line in the log, see the thread I've been in recently for more info, I have pulled it off of our main TV because my wife kept getting errors every time she went to try to use it.

I don't have time to revert back at this point, so I've just put the regular cable-box back on for now until there is a true fix or until I can revert back.

.16 IMHO must have been a rushed release. because i have had terrible issues with it. i would think that the issues are my setup, however after digging i have found them as known bugs, that are fixed after .16 was release in cvs. quick example being hitting R (to record program) freezes frontend. I think CVS is 100% more stable this go around, though i understand and agree with cesman not wanting it officialy in the knoppmyth release.