Project

General

Profile

Picture un watchable; multiple failures.

Added by Mark Hula over 11 years ago

Hi all,

After a complete re-install got tvheadend working!. 100% signal strength; all mux's found!
But when trying to view I simply get:

Feb 26 18:16:32 TS: Sony CXD2820R/West: 706,000 kHz/ITV: MPEG2VIDEO #520: Corrupted PES header, 98 duplicate log lines suppressed
Feb 26 18:16:33 TS: Sony CXD2820R/West: 706,000 kHz/ITV: Transport error indicator, 49866 duplicate log lines suppressed
Feb 26 18:16:33 TS: Sony CXD2820R/West: 706,000 kHz/ITV: MPEG2VIDEO
#520: Continuity counter error, 13080 duplicate log lines suppressed
Feb 26 18:16:33 TS: Sony CXD2820R/West: 706,000 kHz/ITV: MPEG2AUDIO @ #522: Continuity counter error, 534 duplicate log lines suppressed

Many every second! ;-(
using a pctv nanostick t2 - it can't be signal dropout so some driver problem????

thanks in advance


Replies (5)

RE: Picture un watchable; multiple failures. - Added by Prof Yaffle over 11 years ago

What system are you using, what kernel version, what are you using to watch the stream, what tvheadend version, and so on? Is your connection sound, have you tested it on another tuner?

Can't promise to be able to help you, but there's not a lot to go on here. All I can say is that I have the same stick and use it regularly record programmes.

RE: Picture un watchable; multiple failures. - Added by Mark Hula over 11 years ago

Hi,

Ok! :-)
I did a fresh install again and everything seems to work. The only issue is HD is unwatchable.
PC nanostick t2 tuner running under Ubuntu. 100% signal strength on all channels. Latest tvheadend as of today (2.3.1 I think).

Please ask if you require more info.

thanks

RE: Picture un watchable; multiple failures. - Added by Prof Yaffle over 11 years ago

Glad you made some progress. If you're still having problems and need to shout for help, a bit more information around what you're doing would be useful: the fact that the HD channels are unwatchable could mean very many things (starting with what you mean by "unwatchable"!) - whether you're streaming them over 802.11b wifi from a low-powered back end, using its ancient 5400 rpm discs while it's busy with other things, for example, or whether tvh is running on the same core i7-K box as XBMC, all off a top-end SSD drive. The more information you give, the more likely it is that someone can either spot the weak link or else draw a comparison with their system(s).

RE: Picture un watchable; multiple failures. - Added by Mark Hula over 11 years ago

:-)
Sorry, I didn't want to wade in with tons of info :-)))
OK!
Well it's a dual cored amd , radeon gfx ; mini itx - so should be capable of the HD streaming.
Streams HD movies off nas via ethernet fine - so again proves it is worthy :-)

The HD channel starts (though it does buffer for a few seconds) and then maybe lasts 2/3 seconds before picture completely breaks up; tvheadend client then can't connect and the system crashes.

Do you wish too see xbmc.log or the output via the tvheadend web ui (:9981)?

Your help is really appreciated!!
When it does work (like with SD) it is very slick!!

Cheers

RE: Picture un watchable; multiple failures. - Added by Prof Yaffle over 11 years ago

Yeah, I think log files would be a good place to start. Pastebin 'em or put them in xbmclogs and maybe someone can take a look - I'll see what I can divine, but it may need some more skilled assistance than dumb l'il'ol me.

As a matter of interest, have you any other PCs in the house with which you could test streaming? It would help eliminate tvheadend - if the problem is with XBMC in some way then you can switch forums and save time here, at least.

In VLC:

Media -> Open network stream -> http://address_of_your_tvheadend_system:9981/stream/channelid/channel_number

If you get a login prompt, add a user in the Access Control tab - no name, no password, IP address range as you need, streaming enabled.

If you can't find the number for a channel, you can get it by clicking on an event in the EPG and hovering over the Play link - look for the JavaScript message in your browser.

    (1-5/5)