<div class="gmail_quote">On Fri, Jan 23, 2009 at 2:25 PM, <span dir="ltr"><<a href="mailto:scott@tbwifi.ca">scott@tbwifi.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="Wj3C7c">> <a href="mailto:scott@tbwifi.ca">scott@tbwifi.ca</a> wrote:<br>
>>> On Jan 23, 2009, at 10:45 AM, <a href="mailto:scott@tbwifi.ca">scott@tbwifi.ca</a> wrote:<br>
>>><br>
>>>> Hi,<br>
>>>><br>
>>>> I am running 0.21 fixes on a Mandriva 2008.1 box with an Asus M2N-<br>
>>>> Sli MB.<br>
>>>> My satellite receiver is an Expressvu 4100 (Dish). I am having<br>
>>>> trouble<br>
>>>> getting my ir blaster arrangement to work consistently. Oddly if I<br>
>>>> request a channel number using the script from the command line<br>
>>>> everything<br>
>>>> works fine. Also if I manually key in a channel number and hit enter<br>
>>>> using the keyboard while watching live tv in the frontend, it works<br>
>>>> too.<br>
>>>> The issues seem to always occur with programmed recordings. Is it<br>
>>>> possible for the database to be scrambled somehow causing this? Does<br>
>>>> anyone have any other tips to look for?<br>
>>> It's possible that the permissions aren't appropriate for the use that<br>
>>> is running mythbackend. Try logging in as that user and executing the<br>
>>> channel change script from the command line. At least, without backend<br>
>>> log files or more of a description of what "trouble...to work<br>
>>> consistently" means that would be where I would start.<br>
>>><br>
>><br>
>> My mention of success running commandline entries was done using the<br>
>> mythtv user, and permissions aren't a problem.<br>
>><br>
>> The trouble I mention seems to usually be missed digits or what appears<br>
>> to<br>
>> be that. If the intended program is on 210, sometimes two digits get<br>
>> through and the sat box just assumes an error and flips to a totally<br>
>> non-related default. On one occasion last night it seems to flip to a<br>
>> three digit channel correctly, but not the channel that was expected.<br>
>> As<br>
>> I mentioned, if I key in 210 in the frontend using the keyboard, I get<br>
>> tuned to 210. I'm not sure if this is something people have run into<br>
>> before.<br>
>><br>
>> Take note that about 50% of the recordings do get recorded correctly.<br>
>><br>
>> I cannot guarantee that my commandline successes are a fluke, but they<br>
>> do<br>
>> seem to show an almost flawless success rate.<br>
><br>
> You might want to look into the timing of the numerals being sent by the<br>
> blaster, but since the script works from the command line this is<br>
> probably not the problem.<br>
><br>
> In any case, you might try inserting delays and see what happens, or<br>
> reduce the delay if you are using them now.<br>
><br>
<br>
<br>
</div></div>I've played with those timings extensively and have also tried adding<br>
variations of requesting the guide first, adding cancels, and selects You<br>
name it, I've done some serious muddling in the script with little or no<br>
improvement.<br>
<br>
One thing I did wonder is how one requests a longer illumination time as<br>
opposed to the delays inbetween.<br>
<br>
<br>
I should also note that I am feeding the signal from the satellite box in<br>
through the coax input of a PVR-350 if that provides and ideas for anyone.<br>
</blockquote></div>Scott, <br><br>If it works 100% of the time from the command-line, then there is no reason for it to not work from myth. <br><br>Go into "Live TV" and switch between a bunch of channels - does it work fine then? If it does, then there's no reason for timed recordings to fail.<br>
<br>So if that works perfectly, I'd start looking into what other things would cause interference with the IR signal. Things like bright sunlight, or a fluorescent light close by (or in some cases, even across a room), - anything that could interfere with the IR signal or cause erroneous IR detections. <br>
<br>I found that the only times I miss channel changes are if my track light is moved and aimed right into my receivers, thus flooding the poor receiver's IR detector with light (including IR light). (My receivers and myth server are on shelves up near the ceiling, and if I move the track light to illuminate the inside of my myth box, it floods the receivers too, so I have to remember to move it away from them when I'm done...)<br>
<br>Oh yeah, you can also try raising the lirc "min_repeat" value -- if it's "2" now, put it to "3" or "4". That basically simulates you holding down the number key on the remote a little longer. <br>
<br>J-e-f-f-A<br>