linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Manu Abraham <abraham.manu@gmail.com>
Cc: Antti Palosaari <crope@iki.fi>,
	Devin Heitmueller <dheitmueller@kernellabs.com>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Klaus Schmidinger <Klaus.Schmidinger@tvdr.de>
Subject: Re: [PATCH RFCv3] dvb: Add DVBv5 properties for quality parameters
Date: Thu, 3 Jan 2013 17:27:35 -0200	[thread overview]
Message-ID: <20130103172735.0aa1db6d@redhat.com> (raw)
In-Reply-To: <CAHFNz9+-ixyYpAE1egC_s=MSk+t+si-tLTR=T8GK9QoK=vdf5A@mail.gmail.com>

Em Fri, 4 Jan 2013 00:39:25 +0530
Manu Abraham <abraham.manu@gmail.com> escreveu:

> Hi Antti,
> 
> On Thu, Jan 3, 2013 at 9:04 PM, Antti Palosaari <crope@iki.fi> wrote:
> > On 01/01/2013 06:48 PM, Manu Abraham wrote:
> >>
> >> On Tue, Jan 1, 2013 at 8:30 PM, Mauro Carvalho Chehab
> >> <mchehab@redhat.com> wrote:
> >>
> >>> [RFCv4] dvb: Add DVBv5 properties for quality parameters
> >>>
> >>> The DVBv3 quality parameters are limited on several ways:
> >>>          - Doesn't provide any way to indicate the used measure;
> >>>          - Userspace need to guess how to calculate the measure;
> >>>          - Only a limited set of stats are supported;
> >>>          - Doesn't provide QoS measure for the OFDM TPS/TMCC
> >>>            carriers, used to detect the network parameters for
> >>>            DVB-T/ISDB-T;
> >>>          - Can't be called in a way to require them to be filled
> >>>            all at once (atomic reads from the hardware), with may
> >>>            cause troubles on interpreting them on userspace;
> >>>          - On some OFDM delivery systems, the carriers can be
> >>>            independently modulated, having different properties.
> >>>            Currently, there's no way to report per-layer stats;
> >>
> >>
> >> per layer stats is a mythical bird, nothing of that sort does exist. If
> >> some
> >> driver states that it is simply due to lack of knowledge at the coding
> >> side.
> >>
> >> ISDB-T uses hierarchial modulation, just like DVB-S2 or DVB-T2
> >
> >
> > Manu, you confused now two concept (which are aimed to resolve same real
> > life problem) - hierarchical coding and multiple transport stream. Both are
> > quite similar on lower level of radio channel, but differs on upper levels.
> >
> > Hierarchical is a little bit weird baby as it remuxes those lower lever
> > radio channels (called layers in case of ISDB-T) to one single mux!
> 
> That is not really correct. There is one single OFDM channel, the layers
> are processed via hierarchial separation. Stuffing exists, to maintain
> constant rate.
> 
> http://farm9.staticflickr.com/8077/8343296328_e1e375b519_b_d.jpg
> 
> When rate is constant within the same channel..
> (The only case what I can think parameters could be different with a
> constant rate,
> is that stuffing frames are unaccounted for. Most likely a bug ?)

What did you smoke? That picture has nothing to do with ISDB!

ISDB not only does hierarchical split. It also splits the OFDM carriers
into 3 layers, each layer with its own modulation, guard interval, inner
FEC, etc. Each of those layers behave as an independent channel,
providing different bit rates.


Cheers,
Mauro

  reply	other threads:[~2013-01-03 19:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-28 23:56 [PATCH RFCv3] dvb: Add DVBv5 properties for quality parameters Mauro Carvalho Chehab
2012-12-29 15:15 ` [linux-media] " Klaus Schmidinger
2012-12-29 16:36 ` Devin Heitmueller
2012-12-29 17:49   ` [linux-media] " Klaus Schmidinger
2012-12-29 19:49     ` Mauro Carvalho Chehab
2013-01-01 15:00   ` Mauro Carvalho Chehab
2013-01-01 16:48     ` Manu Abraham
2013-01-01 17:29       ` Mauro Carvalho Chehab
2013-01-01 19:08         ` Manu Abraham
2013-01-03 13:20           ` Mauro Carvalho Chehab
2013-01-03 15:18             ` [linux-media] " Klaus Schmidinger
2013-01-03 16:14               ` Mauro Carvalho Chehab
2013-01-03 16:29                 ` Mauro Carvalho Chehab
2013-01-03 21:33                   ` Antti Palosaari
2013-01-03 22:18                     ` Mauro Carvalho Chehab
2013-01-04  5:03                     ` VDR User
2013-01-04  5:30                       ` Manu Abraham
2013-01-06 17:03                     ` Mauro Carvalho Chehab
2013-01-06 17:43                       ` Antti Palosaari
2013-01-03 20:26             ` Manu Abraham
2013-01-03 15:34       ` Antti Palosaari
2013-01-03 19:09         ` Manu Abraham
2013-01-03 19:27           ` Mauro Carvalho Chehab [this message]
2013-01-03 19:32             ` Manu Abraham
2013-01-03 19:53               ` Mauro Carvalho Chehab
2013-01-03 20:39                 ` Antti Palosaari
2013-01-03 20:54                   ` Manu Abraham

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=20130103172735.0aa1db6d@redhat.com \
    --to=mchehab@redhat.com \
    --cc=Klaus.Schmidinger@tvdr.de \
    --cc=abraham.manu@gmail.com \
    --cc=crope@iki.fi \
    --cc=dheitmueller@kernellabs.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).