You may also use git log to see commit messages. After version 0. Before version 29 the 0. What's in a number? Numbering releases is extremely arbitrary, even more so in open source, even many commercial projects select version numbers out of the air and on the basis of how it will affect sales. Perceived 'wisdom' in the commercial world is that releases containing new features get a major version number and cost more, those receiving just bug fixes get minor numbers and cost less.
In a project like MythTV where every release contains a new feature we'd be on version MythTV is very stable, but it cannot be said that the developers consider it to be finished, and the version numbering reflects that.
Whenever the developers decide it's time to change the version numbering system they will. Because it's run by people donating their spare time. If you're impatient you can roll up your sleeves to help things move faster by contributing code. Most Linux distributions create packages from the current -fixes branch so you can benefit from post-release bugfixes.
You are running different versions of MythTV on your frontend and backend. This occurs when a protocol change is implemented as part of a MythTV release. Update your systems to the same version to prevent this problem. This means that all parts of MythTV mythtv, mythplugins, and myththemes should be installed from the same revision or release version. Therefore, when using packaged versions of MythTV, it is considered best that the same distribution be used on all systems.
Note, also, that there are multiple branches of development. At a minimum, these include 0. Components from different branches should not be mixed. Therefore, even if you acquire a specific revision from both 0. Generally different revisions of the 0.
Therefore, if you must use different distributions or use multiple different platforms and plan to use packages, use the 0. If a backup of the mythconverg database was not made before upgrading, a downgrade will likely be impossible without recreating the database thereby losing all recordings, recording history, settings, etc.
If a pre-upgrade database backup is available, restore that backup. In the process, you will lose all information about recordings that occurred since the pre-upgrade backup was made. While it may seem that MythTV works fine after downgrading versions, any data being added to the mythconverg database is likely being corrupted.
And--if nothing else--new data is being inserted into the database in the old format. Therefore, running MythTV with the "upgraded" database after downgrading versions is a time-bomb.
While MythTV may work fine now with the older version, it will surely fail when you upgrade later. So, the longer it is run in this broken state, the more data will need to be fixed or the more data will be lost upon later upgrades. Therefore, regardless of whether it seems to be working, the pre-upgrade database from your backup should always be restored when downgrading MythTV versions. Strictly speaking, no, it is not absolutely necessary for some features.
Certain functionality i. TV relies on it - it's certainly not needed for use as a simple media player installation without TV features. Long term design goals 0. If you don't mind a challenge, then no, but you need to consider whether the hassle of starting mythbackend at the right times is worthwhile. If you want to shutdown the computer completely you might use Wake On Lan or a bios wakeup timer, but this can be complicated and unreliable.
MySQL is required for the frontend and the backend. It stores all the data they need to run and to do things, so yes, you will need it running whenever the backend or frontend are being used, which typically is all the time see previous question.
A tried and true rule: Get it working outside of MythTV before you try to get it working inside. MythTV isn't an operating system. It requires working components to work. You would never try installing a PVR application on Windows before you got your video card, capture card, and audio system working perfectly. Don't try to do it on Linux.
It will save you innumerable hours of barking up the wrong tree and generally make your MythTV experience better. The Mac Mini is Apple's small form factor computer. It has the benefit of looking extremely nice and being extremely small.
While it does have a fan, this is generally regarded to be so quiet that it is not an issue. Both the backend and frontend can run under either OS. Another option is building your own system. There are many articles on the web about building low-power, quiet, small systems.
Additional information is available at Choosing Frontend Hardware. Yes, but running a virtualized backend is not recommended when using a PCI-based tuner, due to timing issues. When asking for support, always specify any hypervisor or other form of virtualization being used to avoid wasting others' time. See Recording Digital Cable. A few different ways, and it depends on your specific hardware and the provider. Yes, as a basic frontend.
All core frontend features work, including LiveTV, scheduling, and watching recordings. Most MythTV plugins, however, do not work and would need additional patches to operate in Windows. For those who need an alternative to the lengthy and sometimes painful process of building MythTV on Windows, your best options are:. If you would like to forgo compiling MythTV from source, there are packages available for a variety of linux distrubutions. You can find a list of available third party packages in the wiki, along with a handful of howtos for getting MythTV installed in your favorite distro.
Set the share to "visible" but not "writable" to avoid having recordings deleted. The name of the share is used by windows, you could call it "recordings". Now check if your Windows machine can see the recordings directory because there is little point in continuing if it can't. Give it a few minutes, finding new shares can be slow as it discovers clients, figures out who is the master, etc. One way to see the share is to enter the following in the Windows Explorer address bar:.
Another way is to click on the Start Menu, click Run, and type that into the run command. The easiest way is to modify one file and at the prompt, first change to the includes directory, make a backup of the file, then edit it:.
Next time you run mythfrontend. Try running mythtv-setup. After the changes just start the MythInstaller. Solution: In mysql. Andrei - I can't find this information - could you please dig out your mysql. I had more problems with the import libraries than without them. One of the changes I made to qmake's mkspec is to stop generating them. Solution: This might have been caused by the original configure.
Compile the uic. During QT compilation, the process is halted due to a Makefile not existing with the following error:. Solution: Create a dummy Makefile in the folder than doesn't have one with the following commands. This isn't working because during compiling process script writes new Makefile over the last one. I spent hours trying to figure this out. I think this was also a problem of earlier Cygwin build attempts.
For whatever reason, during the build of qt I had a problem with uic. Solution: This should be fixed by the mysql. Looks like it can't find the mysql library libmysql.
Follow the steps precisely in the MySQL section above particularly the reimp section to create libmysql.
Solution: Looks like the qt patch I used the combined patch is missing a change to the qt I just edited the Makefile manually and changed -lmysql. Solution: The 'pr' command is missing from your mingw install, installing "additional components" into your MSYS install will fix this see earlier steps above for hints.
The additional component is "coreutils". I have compiled all of the dependencies and such but when I go to run the configure script for myth I get:. This problem has been resolved in SVN as of
0コメント