[mythtv-users] still can't lock to ABC in Canberra using myth on DViCO [xpost CLUG, mythtv-users]

[Lee McLaren]

On 28/03/2010 12:32 AM, Daniel Rose wrote:
> This is out of date, links don't work and it's for Tuggeranong anyway:
>
> http://www.mythtv.org/wiki/DVICO-Ultraview_Install_in_Australia
>
> This has been an ongoing problem for ABC in canberra with mythtv:
>
> http://www.gossamer-threads.com/lists/mythtv/users/323778
> http://www.mail-archive.com/mythtv-users@mythtv.org/msg31523.html
>
> This is an interaction between mythtv and the specific card that I have,
> or perhaps a range of DViCO cards.  I suspect that it is to do with the
> card not supporting a tune+offset.  The driver developer recommends that
> the card instead be tuned directly to the frequency desired.
>
> Using a different card, the problem goes away.
>
> Using VLC, the DviCO Dual Digiatal 4 (rev1) that have can tune all ABC
> stations perfectly.
>
> I expect that VLC is tuning directly, but that Myth is being a little
> more elegant and doing a tune+offset, which the driver does not properly
> support.
>
> On the other hand, it could be caused by some obscure kernel setting,
> the powers of the sun and the moon, who knows?
>
> Is anyone interested in following this up? Does it qualify as something
> that should be lodged at Mythtv's Trac?
>
> I note that it sort of has been:
>
>   http://svn.mythtv.org/trac/ticket/7302
>
> Has anyone tuning stations with offsets found a workaround, or does
> anyone tuning offset stations with Zarlink tuners had no trouble at all?
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>    
I use Dvico cards,

I have trouble tuning some channels, what is detected by a scan with 
Mythtv results in a picture that breaks up etc. I have to adjust the 
value for the multiplex frequency for it to work correctly, it only 
happens on one multiplex.

The correct working value is 184625000 but it is scanned as 184500000. 
You may want to try adjusting the frequency by a similar offset.

best regards