Reply to thread

Message

<blockquote data-quote="Karyudo" data-source="post: 1038116" data-attributes="member: 65921">Posted in the SageTV forum, but no answer (yet?) from mikep, the author of SageChanger.In the meantime, I'm fiddling with a third-party MS-compatible IR transceiver and one IR blaster, and getting pretty good -- but not perfect -- results:• Two back-to-back shows with pre- and post-padding, on different channels, were correctly padded and spread across the two Colossuses.• Two back-to-back shows with pre- and post-padding, on the same channel, were correctly padded from one Colossus. HOWEVER, when the second show started, the IR blaster unnecessarily blasted the STB with the same channel number, which shows up on the OSD. And because the Colossus is recording from the analog output, the OSD turns up in the &quot;this is part of the show&quot; portion of the first show's recording. Not ideal.I figure the behaviour flowchart for when there are two recordings set should be something like:Are the two shows back-to-back?If no, then &lt;existing MP behaviour&gt;If yes, then......Is there pre- and/or post-recording padding?If no, then &lt;existing MP behaviour&gt;If yes, then......Are the back-to-back shows on the same channel?If no, then &lt;existing MP behaviour, which I already know is to find another tuner/source&gt;If yes, then IR blast channel number at start of first show; record first show; DO NOT blast channel number; record second show. (This would work with one or more tuners/sources.)I don't know where this behaviour is coded, and I don't know how to code it. But if MP were modified to handle this sub-sub-sub-case elegantly, I sure would appreciate it!</blockquote>

[QUOTE="Karyudo, post: 1038116, member: 65921"] Posted in the SageTV forum, but no answer (yet?) from mikep, the author of SageChanger. In the meantime, I'm fiddling with a third-party MS-compatible IR transceiver and one IR blaster, and getting pretty good -- but not perfect -- results: • Two back-to-back shows with pre- and post-padding, on different channels, were correctly padded and spread across the two Colossuses. • Two back-to-back shows with pre- and post-padding, on the same channel, were correctly padded from one Colossus. HOWEVER, when the second show started, the IR blaster unnecessarily blasted the STB with the same channel number, which shows up on the OSD. And because the Colossus is recording from the analog output, the OSD turns up in the "this is part of the show" portion of the first show's recording. Not ideal. I figure the behaviour flowchart for when there are two recordings set should be something like: Are the two shows back-to-back? If no, then <existing MP behaviour> If yes, then... ...Is there pre- and/or post-recording padding? If no, then <existing MP behaviour> If yes, then... ...Are the back-to-back shows on the same channel? If no, then <existing MP behaviour, which I already know is to find another tuner/source> If yes, then IR blast channel number at start of first show; record first show; DO NOT blast channel number; record second show. (This would work with one or more tuners/sources.) I don't know where this behaviour is coded, and I don't know how to code it. But if MP were modified to handle this sub-sub-sub-case elegantly, I sure would appreciate it! [/QUOTE]

Verification