From: Antti Palosaari <crope@iki.fi>
To: Marx <acc.for.news@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: pctv452e
Date: Wed, 11 Jul 2012 13:00:34 +0300 [thread overview]
Message-ID: <4FFD4EC2.8090702@iki.fi> (raw)
In-Reply-To: <gsivc9-6u6.ln1@wuwek.kopernik.gliwice.pl>
On 07/11/2012 09:25 AM, Marx wrote:
> On 11.07.2012 01:13, Antti Palosaari wrote:
>> All these tests shows your device is running as it should.
> There are errors in almost every case, they are absent in your example.
> Is it ok?
You mean these:
[mpeg2video @ 0x8d47940] mpeg_decode_postinit() failure
[mp3 @ 0x8d4a5c0] Header missing
[mpegts @ 0x9f1e900] max_analyze_duration reached
[mpegts @ 0x9f1e900] Estimating duration from bitrate, this may be
inaccurate
[mpegts @ 0x9cc7900] PES packet size mismatch
Those are OK. It is live video stream and thus having no header to tell
info about stream content. ffmpeg is forced to read raw stream and guess
used codes where may happen sometimes few problems.
If you see correct picture when opening that stream in video player it
is correct. It is likely happen if ffmpeg can detect it.
>> Test VDR again to see if it breaks.
> VDR unfortunatelly doesn't work saying "frontend 0/0 timed out while
> tuning to channel 21, tp 211116" and "ERROR: streamdev: protocol
> violation (VTP) from 127.0.0.1:38551". In fact I cannot play any stream
> directly via VDR, but it can be caused by some incompatibility between
> VDR and the newest kernel.
> VDR reads EPG properly so there is something wrong with it.
> But it's probem not for this list.
Add more tuning delay to VDR.
> Today test works like yesterday.
>
> I will wait and test again later.
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2012-07-11 10:00 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 16:04 pctv452e Steve Hill
2012-07-04 16:22 ` pctv452e Antti Palosaari
2012-07-04 18:46 ` pctv452e Marx
2012-07-04 18:53 ` pctv452e André Weidemann
2012-07-04 19:01 ` pctv452e Antti Palosaari
2012-07-05 13:14 ` pctv452e Marx
2012-07-05 14:23 ` pctv452e Antti Palosaari
2012-07-06 6:13 ` pctv452e Marx
2012-07-06 9:34 ` pctv452e Antti Palosaari
2012-07-06 11:04 ` pctv452e Marx
2012-07-06 18:24 ` pctv452e Antti Palosaari
2012-07-06 22:23 ` pctv452e Marx
2012-07-07 0:00 ` pctv452e Antti Palosaari
2012-07-07 23:07 ` pctv452e Marx
2012-07-08 12:32 ` pctv452e Antti Palosaari
2012-07-09 6:24 ` pctv452e Marx
2012-07-09 8:42 ` pctv452e Antti Palosaari
2012-07-09 16:44 ` pctv452e Marx
2012-07-09 17:38 ` pctv452e Antti Palosaari
2012-07-09 17:46 ` pctv452e Antti Palosaari
2012-07-10 6:39 ` pctv452e Marx
2012-07-10 9:33 ` pctv452e Antti Palosaari
2012-07-10 21:08 ` pctv452e Marx
2012-07-10 23:13 ` pctv452e Antti Palosaari
2012-07-11 6:25 ` pctv452e Marx
2012-07-11 10:00 ` Antti Palosaari [this message]
2012-07-09 18:21 ` pctv452e poma
2012-07-10 6:43 ` pctv452e Marx
2012-07-10 15:51 ` pctv452e poma
2012-07-10 15:58 ` pctv452e Devin Heitmueller
2012-07-10 22:54 ` pctv452e poma
2012-08-03 16:56 ` pctv452e Steve Hill
-- strict thread matches above, loose matches on Subject: below --
2012-07-02 16:33 pctv452e Steve Hill
2012-07-03 7:46 ` pctv452e Marx
2012-07-03 23:04 ` pctv452e Antti Palosaari
2012-07-04 7:51 ` pctv452e Marx
2013-07-06 13:29 ` pctv452e Antti Palosaari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FFD4EC2.8090702@iki.fi \
--to=crope@iki.fi \
--cc=acc.for.news@gmail.com \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).