I know that this has been brought up before, but would it be possible to revisit the issue with SNR and strength units of measure being inconsistent across frontends? I know that we don't always know what the units of measure are for some frontends, but perhaps we could at least find a way to tell applications what the units are for those frontends where it is known? For example, if we had a call that returned the units that the frontend is expecting to return the SNR in (e.g. dB, %, etc), applications would know how to handle it (and for those cases where we really don't know what the units are, the call can return "unknown" so the application just represents the value on a linear scale). I know we probably can't agree on what units the SNR field should return, but if we could at least agree on a way where the frontend can tell us what the units are, the field could actually be useful to applications. This approach would be backward compatible because we wouldn't be expecting any of the frontends to change how they return the underlying data - it would only have to add an additional call implemented to return what units that data is in. Right now the fields are pretty useless to applications. For example, with Kaffeine the data shows up great with my HVR-950 (which returns a percentage), but when it said 0% with my Pinnacle 801e, as a user I thought something was broken (the s5h1411 returns data in dB). Devin -- Devin J. Heitmueller http://www.devinheitmueller.com AIM: devinheitmueller _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
