From: Oliver Endriss <o.endriss@gmx.de>
To: Marko Ristola <marko.ristola@kolumbus.fi>
Cc: linux-media@vger.kernel.org, Jaroslav Klaus <jaroslav.klaus@gmail.com>
Subject: Re: TS discontinuity with TT S-2300
Date: Sun, 27 Jun 2010 20:25:38 +0200 [thread overview]
Message-ID: <201006272025.39822@orion.escape-edv.de> (raw)
In-Reply-To: <4C277496.7050508@kolumbus.fi>
On Sunday 27 June 2010 17:56:06 Marko Ristola wrote:
> 27.06.2010 15:37, Oliver Endriss wrote:
> > Hi,
> >
> > On Sunday 27 June 2010 01:05:57 Jaroslav Klaus wrote:
> >
> >> Hi,
> >>
> >> I'm loosing TS packets in my dual CAM premium TT S-2300 card (av7110+saa7146).
> >>
> >> I use dvblast to select 4 TV channels (~ 16 PIDs) from multiplex,
> >> descramble them and stream them to network. Dvblast reports TS
> >> discontinuity across all video PIDs only (no audio) usually every
> >> 1-3 minutes ~80 packets. But sometimes it goes well for tens of
> >> minutes (up to 1-2hours). Everything seems to be ok with 3 TV channels.
> >>
> >>
> > The full-featured cards are not able to deliver the full bandwidth of a
> > transponder. It is a limitaion of the board design, not a firmware or
> > driver issue.
> >
> I noticed that saa7146 uses dvb_dmx_swfilter_packets().
Yes.
> I planned using of that function too for
> Mantis 16K buffer delivery, but I found out that
> hardware delivers sometimes additional bytes (corrupted partially lost
> packets?)
> between the full sized 204 byte packets:
>
> Jun 26 16:20:37 koivu kernel: demux: skipped 49 bytes at position 3379
> Jun 26 16:20:37 koivu kernel: demux: skipped 18 bytes at position 9868
> Jun 26 16:20:37 koivu kernel: demux: skipped 30 bytes at position 10090
> Jun 26 16:20:38 koivu kernel: demux: skipped 14 bytes at position 7208
> Jun 26 16:20:38 koivu kernel: demux: skipped 114 bytes at position 7426
Are you sure that Mantis driver delivers garbage, not partial packets?
Please note that the dvb_dmx_swfilter[_204]() routines must accept
partial packets, i.e. the rest of the packet will be dellivered with the
next call.
> So dvb_dmx_swfilter(_204)() is needed to skip
> these unwanted bytes. With simple usage of
> dvb_dmx_swfilter_packets() the rest of the buffer
> would have been lost. I wrote a faster version of these
> functions, also for 188 sized packets today:
> "Re: [PATCH] Avoid unnecessary data copying inside
> dvb_dmx_swfilter_204() function"
dvb_dmx_swfilter_packets() expects complete TS packets from the driver.
The saa7146 does so. It does not deliver garbage data. (Otherwise this
would have been noticed a long time ago. The ttpci drivers are the
oldest DVB drivers and are very well tested.)
CU
Oliver
--
----------------------------------------------------------------
VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/
4 MByte Mod: http://www.escape-edv.de/endriss/dvb-mem-mod/
Full-TS Mod: http://www.escape-edv.de/endriss/dvb-full-ts-mod/
----------------------------------------------------------------
next prev parent reply other threads:[~2010-06-27 18:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-26 23:05 TS discontinuity with TT S-2300 Jaroslav Klaus
2010-06-27 12:37 ` Oliver Endriss
2010-06-27 15:23 ` Jaroslav Klaus
2010-06-27 15:56 ` Marko Ristola
2010-06-27 18:25 ` Oliver Endriss [this message]
2010-06-27 20:51 ` Marko Ristola
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=201006272025.39822@orion.escape-edv.de \
--to=o.endriss@gmx.de \
--cc=jaroslav.klaus@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=marko.ristola@kolumbus.fi \
/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