Thanks Samir!
So… for a while now… MythTV hasn’t been commercial flagging any shows nor has it been compressing shows.
The log displays “NVR::doAudioThread() This Unix doesn’t support device files for audio access. Skipping???
Other times, when I bother to look, the log displays some hex number when trying to find a codec.
For months I’ve been searching why these error messages are being produced… Finally, I saw a thread on the MythTV forum.
Apparently, disabling oss during compilation (–disable-oss) breaks the Nuppel Video Recorder sound options. So, even if the ‘backend’ doesn’t have sound hardware you still need to compile the source with it.
DUMB!!!!!
I use a dedicated backend. It has no keyboard and no mouse connected to it. I didn’t bother setting up sound because… The system is in my garage! I figured, there was no reason to compile sound for MythTV since the system that it was used on didn’t have sound. When sound is compiled, when using the myth-setup, the system hangs until it times out – a real bother.
Yep, I understand your pain! MythTV is an excellent PVR… but it has a long way to go before “Version 1.0” if you ask me! Why they even offer as a complie time option to disable OSS when it clearly needs it is beyond me.
I also don’t like the way Myth Protocol was designed… First, it isn’t documented. Second, it maintains no backward compatibility whatsoever, so you _have_ to use the same version of the backend and frontend across the entire mythtv setup. Third, it provides no means of being a “frontend” to the database, so the frontends have an _additional_ dependency on MySQL libraries (which just causes even more problems). Combined, all these limitations makes it nearly impossible to write a front-end for multiple platforms/embedded platforms.
If you ask me, I think they need to rework the protocol to something entirely XML-RPC based… (although they could stream the video using any other method since that would be a huge bottelneck). XML-RPC libraries are already written for nearly every platform you can think of, and provides an extendible means of adding new features w/o breaking backward compatibility.
I’d love to implement these features myself and contribute back to the community, but I simply don’t have the time (as of yet)… and given the attitudes of some of the devs, they’d probably just yell at me for doing something so “bloated” (even though I bet I could get it to perform quite well and more reliably).
I agree totally!
MythTV finally went through about 100 shows and commercial flagged them in under 10 hours. Not bad. Considering it’s only using one of four procs…
It’d be nice when v1.0 will allow for better threading… so I won’t have three procs just sitting there idling – warming my garage.
Just tell it to allow up to 4 simultaneous jobs… ?
Speaking of which, my garage hit 90 degrees yesterday! I was at the park and started getting SMS messages of the condition!