From: Martin Vidovic <xtronom@gmail.com>
To: Issa Gorissen <flop.m@usa.net>
Cc: linux-media@vger.kernel.org
Subject: Re: ngene CI problems
Date: Sat, 23 Apr 2011 13:37:47 +0200 [thread overview]
Message-ID: <4DB2BA0B.20906@gmail.com> (raw)
In-Reply-To: <4DB1FE58.20006@usa.net>
Hi Issa,
> Running a bunch of test with gnutv and a DuoFLEX S2.
>
I have a DuoFlex S2 running with CI, but not nGene based (it's attached
to Octopus card - ddbridge module).
> I would run gnutv like 'gnutv -out stdout channelname >
> /dev/dvb/adapter0/caio0' and then 'cat /dev/dvb/adapter0/caio0 | mplayer -'
> Mplayer would complain the file is invalid. Simply running simply 'cat
> /dev/dvb/adapter0/caio0' will show me the same data pattern over and over.
>
I suspect the problem is that reads/writes are not aligned to 188 bytes
with such invocation of commands. Maybe if you tried replacing 'cat' and
'>' with 'dd' (bs=188). Other important thing seems to be, to read from
the caio0 fast enough or real data is overwritten with null packets
(haven't proved it, but it looks this way on nGene).
Hope this helps.
Best regards,
Martin Vidovic
next prev parent reply other threads:[~2011-04-23 11:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 13:50 ngene CI problems Martin Vidovic
2011-04-22 22:16 ` Issa Gorissen
2011-04-23 10:19 ` Issa Gorissen
2011-05-03 6:48 ` Sébastien RAILLARD (COEXSI)
2011-04-23 11:37 ` Martin Vidovic [this message]
2011-04-23 12:11 ` Issa Gorissen
2011-04-23 12:39 ` Martin Vidovic
2011-04-23 13:29 ` Issa Gorissen
2011-04-23 17:40 ` Oliver Endriss
2011-04-23 18:56 ` Issa Gorissen
2011-04-23 19:14 ` Oliver Endriss
2011-04-23 19:52 ` Issa Gorissen
2011-04-23 23:08 ` Issa Gorissen
2011-05-11 18:59 ` Oliver Endriss
2011-05-12 11:30 ` Issa Gorissen
2011-05-12 20:28 ` Issa Gorissen
2011-05-12 22:34 ` Oliver Endriss
2011-05-22 12:48 ` Martin Vidovic
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=4DB2BA0B.20906@gmail.com \
--to=xtronom@gmail.com \
--cc=flop.m@usa.net \
--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