Re: zvbi-atsc-cc device node conflict

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> That's promising but no cigar:
>
> cat test-cat3.mpeg > zvbi-atsc-cc --ts
>
> just feeds the output of the cat into a file called zvbi-atsc-cc (not
> surprisingly).

Hehe. Sure, it was my mistake. Piping syntax what you tried
later is exactly what I thought :-)

>
>  cat test-cat3.mpeg | zvbi-atsc-cc --ts
>
> also doesn't work. zvbi-atsc-cc's --ts switch is designed to "Decode a DVB
> Transport Stream on stdin", so if the file created with
>
>  cat /dev/dvb/adapter0/dvr0 > test-cat3.mpeg
>
> qualifies as a DVB Transport Stream, then there's a way to pipe it to
> zvbi-atsc-cc.  How do we get the syntax for this?
>

Of course I can be wrong as I have exactly zero experiences of using
zvbi tool, but I think command line option --ts should tell that
data are not comming from dvr device but from stdin. Dunno
why it not works for you. May be it needs some additional options?

/Honza
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux