ISDB-T devices: Difference between revisions

From LinuxTVWiki
Jump to navigation Jump to search
(minor clean ups; remove info to other article)
Line 1: Line 1:
== Supported Hardware ==
== Supported Hardware ==


Currently, There are three drivers that support ISDB-T: dibcom dib0700 and pt1 driver, and commercially bundled drivers for Empia solutions.
Currently, There are three drivers that support ISDB-T:
* Open Source

The dib0700 implements the new DVBS2API to allow finer control at the ISDB-T parameters.
** the dibcom dib0700 and pt1 drivers. The dib0700 implements the new DVBS2API to allow finer control at the ISDB-T parameters.
* Closed Source

** the commercially bundled drivers from [[Sundtek]] for USB devices based upon [[EMPIA_Technology|Empia]] chipsets. The Sundtek solution support both the S2-API as well as the Legacy DVBv3 API
The Empia/Sundtek based Linux USB solutions support both, S2-API as well as the Legacy DVBv3 API and also include backward compatibility for ~4 year old Linux systems which are currently on the market, an installation does not require any recompilation and usually can be done within seconds due to the kernel independency. They also provide a player with channel scanning ability which supports H264/AAC as well as multiple character sets.


== How to make it work with the current dvb-apps version ==
== How to make it work with the current dvb-apps version ==

Revision as of 17:57, 26 September 2009

Supported Hardware

Currently, There are three drivers that support ISDB-T:

  • Open Source
    • the dibcom dib0700 and pt1 drivers. The dib0700 implements the new DVBS2API to allow finer control at the ISDB-T parameters.
  • Closed Source
    • the commercially bundled drivers from Sundtek for USB devices based upon Empia chipsets. The Sundtek solution support both the S2-API as well as the Legacy DVBv3 API

How to make it work with the current dvb-apps version

Some changes are needed at dvb-apps in order to support the new DVBS2API parameters for ISDB-T. While those changes aren't implemented there and at the userspace apps, you need to use the DVB-T format.

In the case of ISDB-T, the current implementations (Brazil and Japan) use 6 MHz bandwidth with the same ISDB-T Frequency Table. In the future, this is likely to change.

For the device to work, the first step is to seek for the existing channels. This is done by running the 'scan' application:

 scan FrequencyTable >channels.conf

Then, a DVB-T userspace application can be used to play the stream. In the case of Brazil, the application needs to support H.264 for video, HE-AAC for audio, and PMT tables at the mpeg-ts. Currently, only vlc and the newest development versions of mplayer are known to support. However, some stream types are known to not work with none of those two applications, due to some existing bugs.