twemperor said: ↑ EDIT: I should probably add that as a general behavior I've noticed, sometimes I'll have a problem tuning the same channel twice, that goes away when I have the tuner go to a different channel. Not completely repeatable, but I've noticed this a few times. Sounds like a similar sort of thing as I saw in Sigpi007's log files. No response from Ceton or Silicondust yet - understandable given it is/was still the weekend in your part of the world...
RDP would be fine, though TeamViewer is probably easier to set up (no firewall configuration or install required). Up to you. Just flick me a PM once you've had a chance to set it up and we'll take it from there.Let me know how you'd prefer to access my server (Windows RDP, or some other service?), and I'd be glad to let you look around.
I tried sending a private message, and the forum won't let me...RDP would be fine, though TeamViewer is probably easier to set up (no firewall configuration or install required). Up to you. Just flick me a PM once you've had a chance to set it up and we'll take it from there.Let me know how you'd prefer to access my server (Windows RDP, or some other service?), and I'd be glad to let you look around.
One thing I noticed is that when I re-scan, most of my channels are updated. On a couple of occasions where I looked close enough, it looks like the QAM frequency is changing. Is some of the tuning information expected to change in this setup? Could there be something in the tuning process that is not running if the tuner is already on a certain 'channel' (pre-loaded or not)? Some tuning information is not being requested, and is stale?twemperor said: ↑ EDIT: I should probably add that as a general behavior I've noticed, sometimes I'll have a problem tuning the same channel twice, that goes away when I have the tuner go to a different channel. Not completely repeatable, but I've noticed this a few times. Sounds like a similar sort of thing as I saw in Sigpi007's log files. No response from Ceton or Silicondust yet - understandable given it is/was still the weekend in your part of the world...
I used to get this issue regularly, but recently it has gone away. Not sure why. For the record though... I used to get the issue PRIOR to using the CableCard patch. I was just using a Hauppauge TV tuner and watching QAM channels that were in the clear.
When TV Server finds a channel in a scan, it either updates or creates a new channel. If you've scanned previously, you'd expect most of your channels to be "updates". That's not to say that any of the tuning details have actually changed.One thing I noticed is that when I re-scan, most of my channels are updated.
If TV Server thinks it is already tuned to a given channel then it does not attempt a retune. It just tells the tuner to start the stream. I'm aware that CableCARD tuners don't seem to like this, and that is what I contacted Ceton and Silicondust about. Still no response.Could there be something in the tuning process that is not running if the tuner is already on a certain 'channel' (pre-loaded or not)? Some tuning information is not being requested, and is stale?
I see three cases where channel change took more than 20 seconds. I think I know the cause and how to fix it, but I need some info about something. So, I've contacted Michael at Ceton and will let you know as soon as I have more info...Occasional minor lag here and there between channels, but nothing that is unexpected. On average... no more than 5 secs. Usually changing under 2 secs most of the time now.
Sorry still nothing. This is unusually slow. If I haven't received a response by the end of this week I will try to contact Ceton again via alternative routes...@mm... Any word back from Michael at Ceton for the lag issue?