<div dir="ltr">On 10 March 2013 13:30, Karl Dietz <span dir="ltr"><<a href="mailto:dekarl@spaetfruehstuecken.org" target="_blank">dekarl@spaetfruehstuecken.org</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 10.03.2013 08:31, mythtv . wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have put the mythtv packages of the pi forums onto my Raspberry Pi and<br>
now have it running and recognising my master backend. I am now trying<br>
to tune DVB-S via my Tevii S660 on there.<br>
<br>
I know the Tevii works as I have had it running with tvheadend fine and<br>
I have copied the firmware onto the pi and the logs are showing it<br>
loaded and mythv recognises everything as expected.<br>
<br>
The only problem is that when I go to tune from a known multiplex the<br>
signal strengths flicks up and down rapidly and the tuning appears to<br>
fly through remarkably fast...faster than I have ever known and faster<br>
than normal by a factor of 10-100. It would be good if it could work<br>
this fast :-)<br>
</blockquote>
<br></div>
Can we see the log file please? I'm expecting something about<br>
mythtv-setup requesting auto-detection of a transmission parameter that<br>
your device/driver is not able to auto detect. That leads to very quick<br>
round-trips with some "unsupported parameter" instead of actual tuning.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have not changed the defaults but have never had a problem before so<br>
this is something in this particular setup. now I realise that I am<br>
using unofficial mythtv packages so it could even be in this particular<br>
build itself but before I start chasing my tail, has anyone seen this<br>
sort of behaviour before or any hints on where to start. Extending the<br>
timeouts doesnt seem to have any effect.<br>
</blockquote>
<br></div>
Above you said *this* tuner device works with tvheadend. Have you ever<br>
used *this* tuner device with mythtv? Maybe the device you used with<br>
mythtv in the past does support auto detection of more parameters and<br>
thus "just worked" without manually specifying any parameters.<br>
Try to manually specify the parameters that are referred as unsupported<br>
for auto detection in the log file.<br>
<br>
Regards,<br>
Karl<br>
<br>
PS: I think that running DVB-S2 in and out to disk/net over a single<br>
USB-Port is a waste of time. Better directly get a DVB-S2 networked<br>
device and run an ethernet cable to the device/dish.<br>
<a href="http://www.linuxtv.org/wiki/index.php/DVB-S2_Networked_Devices" target="_blank">http://www.linuxtv.org/wiki/<u></u>index.php/DVB-S2_Networked_<u></u>Devices</a><br>
Sadly the linuxtv device lists don't seem to be well maintained in that<br>
area. Maybe someone who researches available options can update the<br>
articles.<div class="HOEnZb"><div class="h5"><br>
______________________________<u></u>_________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/<u></u>listinfo/mythtv-users</a><br>
</div></div></blockquote></div><br></div><div class="gmail_extra" style>Karl,</div><div class="gmail_extra" style><br></div><div class="gmail_extra" style>Thanks, when I get a few minutes to fire it up again I will grab the logs. </div>
<div class="gmail_extra" style><br></div><div class="gmail_extra" style>Take your point about DVB-S2. Currently I'm just sticking to DVB-S. S2 was a bit choppy on tvheadend and I figured for that very reason. I have actually ordered a MOI but currently they are using tvheadend on it. Therefore either if MythTV could talk directly to it or I could get MythTV to run on it I can do what I want. SO I do figure if I can get the pi working then the MOI is a later ARM device so theory states it *should* be possible!</div>
<div class="gmail_extra" style><br></div><div class="gmail_extra" style>Thanks again</div><div class="gmail_extra" style><br></div><div class="gmail_extra" style>Martin</div></div>