On Fri, May 14, 2010 at 3:41 AM, Yeechang Lee <[email protected]> wrote:
> The 'bijou' respin of MythTV 0.23 is now available on atrpms-testing. > > The 20100505 release contains the following enhancements to ATrpms > 233: > > * Adjustments to ThreadedFileWriter's buffers. Significantly improves > recordings' integrity when destination disks are stressed, at the cost > of increased RAM usage. (That said, on my frontend/backend I've > recorded four HD streams at once without swapping.) My work. > * Three Hauppauge HD-PVR-related improvements. Two add signal > monitoring to HD-PVR tuning and also slightly benefit FireWire users > (#6719, #6611), while the third fixes an issue with h.264 LiveTV > (#6602). Users should, in theory, be able to get rid of any > post-change sleeps they put into their HD-PVR channel-change scripts. > * Automatically scale number of user jobs based on system load > (#2782). > * Fix for Jumppoints not working when OSD is present (#7939). > * Improved detection of audio tracks when transcoding (my variant on > #1841). > > If the 20100510 release (based on ATrpms 234) is available by the time > you read this, it also contains: > > * Avoid scheduling back-to-back recordings on the same card even if on > the same channel (#8429). Primarily of interest to multirec > users. "Always" enables this feature, while "Different Channels" and > "Never" are the preexisting options. > Thanks, YeeChang. I've been using multirec on the HDHomeRun with Time Warner cable's clear QAM channels. Can you explain how #8429 with the "Always" setting can be used to avoid problems? I'm not sure I understand the reasoning behind the "always" setting with multirec users. Is this for those users who run recordings past the end of the show? /Brian/
_______________________________________________ atrpms-users mailing list [email protected] http://lists.atrpms.net/mailman/listinfo/atrpms-users
