Slow tuning in Sage7

[taylormadearmy]

Hi All,

I'm finding tuning / changing channels is far slower (between 5-10 seconds versus 2-3 seconds) in Sage7 than it was for me in Sage6. I'm using several DTV-T Hauppague sticks.

Is there anything obvious for me to try before I submit a support request?

Thanks
T

[andypitt]

Hi,

I am having this exact same problem using a Hauppauge PCI DVB-T Card, any feedback on this?

Andy

[bsung]

My HD PVR is slower too. BUT, it does seem to be more stable. Since v7, I haven't had it lock up yet. Granted, I've been messing around with things so I've been rebooting everything much more frequently.

[Mark SS]

DVBT tuning is far slower for me in the beta, often 10+ seconds rather than a consistent 1-2 in v6. I'm also seeing a black screen, without 'No Signal' message, on occasions which then results in a full UI crash when pressing stop.

Gathered logs and sample files last night, will submit a bug report tonight. Do so also as the more examples Sage have to work with, the better chance of identifying the problem and fix.

[taylormadearmy]

Originally Posted by Mark SS

DVBT tuning is far slower for me in the beta, often 10+ seconds rather than a consistent 1-2 in v6. I'm also seeing a black screen, without 'No Signal' message, on occasions which then results in a full UI crash when pressing stop.

Gathered logs and sample files last night, will submit a bug report tonight. Do so also as the more examples Sage have to work with, the better chance of identifying the problem and fix.

Thats exactly what I am seeing. Will post some logs when I get a chance. Do you know if there is any particular logs that support are after for this issue?

T

[jamesdisco]

I'm seeing this too, sometimes a change is quick other times it can take so long the no signal comes up and then a picture appears after that.

[Mark SS]

Originally Posted by taylormadearmy

Do you know if there is any particular logs that support are after for this issue?

Make sure debug logging is enabled which will produce sagetv_<n>.log files. If you experiance UI crashes you should find hs_err files in the SageTV directory also. Copy any recordings that cause failures out of your recording directory in case Sage ask you to upload examples.

[taylormadearmy]

I found the slow reason, the stream presents a "visually impaired commentary" audio in stream description, but there is no data available. SageTV wait that audio data till timeout.

Here is an update http://download.sage.tv/users/qian/7.0.10/TSSplitter.ax.
because I don't have stream data, I*didn't test it, count on you to test.

Possible fix from sage support. Its late so I have only briefly tested but certainly improves things for me.

Let us know if it helps you..

T

[teedublu]

uh uh,

Didn't help with "no signal" for me.

Still have a few channels that won't tune at all in Sage7b10 w/ that new (6/10) TSSplitter, and a few others that sometimes tune to the wrong channel -- so far the wrong ch is always the same wrong one. All is well in HDHR QuickTV

TW

[Mark SS]

Tried the new TxSplitter.ax. Every channel I tried responded with video playback error, couldn't tune any.

[taylormadearmy]

Originally Posted by teedublu

uh uh,

Didn't help with "no signal" for me.

Still have a few channels that won't tune at all in Sage7b10 w/ that new (6/10) TSSplitter, and a few others that sometimes tune to the wrong channel -- so far the wrong ch is always the same wrong one. All is well in HDHR QuickTV

TW

Oh dear
I trust you have filled out a support request? Do let us know what you hear back.

As I said I did not have much time to test this fix but it did seem to helped a bit.

I'll test more and submit more logs when I get time later this week.

I think I may also have seen an issue with the wrong channel beeing tuned. Which channels u seeing the issue with?

T

[Mark SS]

Much improved in 7.0.11, probably close to tuning speed in v6.