1 | I know some people are going to point and laugh because I'm running an
|
---|
2 | old version. Personally, I don't care. But I'm explaining why, here,
|
---|
3 | because I want this patch to be considered seriously regardless, even
|
---|
4 | though I won't have a tested version for trunk before the feature
|
---|
5 | freeze window closes. And I'm doing it here because having this
|
---|
6 | hashed out on the list is just a distraction.
|
---|
7 |
|
---|
8 | Note that, once 0.22 comes out, I'll probably transition to it.
|
---|
9 | Eventually. But not today.
|
---|
10 |
|
---|
11 | So why am I running such an old version, namely 0.18.1? Because it
|
---|
12 | works for me:
|
---|
13 | (a) This system is used as part of a research project. It's in
|
---|
14 | production. There is a ton of scaffolding written around it.
|
---|
15 | Disturbing that could disturb a lot of other things.
|
---|
16 | (b) I only ever record SD, never HD, and display it using a PVR-350
|
---|
17 | on an actual interlaced, analog, SD CRT. Later versions tend to
|
---|
18 | want to speak OpenGL and use widescreen themes. Now that 0.22
|
---|
19 | will support VDPAU, and hence perhaps deinterlacers that look as
|
---|
20 | good as my native interlaced, I might start running it. But only
|
---|
21 | if it still supports my existing SDTV setup, of course, if I can
|
---|
22 | find a card that can output interlaced and looks as good.
|
---|
23 | (c) Upgrading MythTV is very tricky for a production system, since:
|
---|
24 | (1) You can't ever go backwards.
|
---|
25 | (2) You need real hardware to test with.
|
---|
26 | (3) Some bugs are intermittent and won't manifest immediately.
|
---|
27 | This means, by the time you know you're in trouble, you're
|
---|
28 | screwed, unless you'd like to dump everything Myth's recorded
|
---|
29 | since the upgrade. Or unless you have a completely separate set
|
---|
30 | of hardware (including tuners! and cable boxes!) to run your test
|
---|
31 | with. So upgrading is only worth the pain and potential hassles
|
---|
32 | if it offers clear advantages. For what -I- do, so far, 0.18.1's
|
---|
33 | been good enough. Sometime soon, I'll jump to 0.22 when I can do
|
---|
34 | so without disturbing my production setup and then test it very
|
---|
35 | thoroughly before cutting over. That day has not yet arrived.
|
---|