El 04/08/15 a las 05:25, Klaus Schmidinger escribió:
> On 04.08.2015 08:12, Christian Rodriguez wrote:
>> Hello everyone! I'm from Argentina, and up to last month I've been
>> using VDR 1.7.262 with an ISDB-T USB adapter. It works really good,
>> but the last week I've been trying to upgrade to VDR 2.2 and I've
>> found a problem with ISDB-T cards: they are not supported.
>> As I'm really interested in using VDR, I was digging inside the code
>> and found a partial solution for this problem: as ISDBT is the same
>> as DVBT, I've changed the way delivery system is queried. My changes
>> are applied in a cloned repo at github:
>> https://github.com/chrodriguez/vdr/commit/dadbca57c2dc55c1c53b4fa8f68b56728ab72ddd#diff-8fe0655a5feb333a97bf3a2a8b451546R1294
>> That's the only change I've made. Now I can enjoy my fresh upgraded
>> VDR installation!!
>> I think a better refactor should be made, but for now it's working
>> perfectly deployed as a docker container:
>> https://registry.hub.docker.com/u/chrodriguez/vdr
> If it works for you this way, I'll adopt this change in the next version.
> Surely there should be a better implementation, since ISDB-T has several
> tuning parameters of its own. But since there is no such signal here I
> can't
> implement/test this myself. Somebody with the proper
> hardware/signal/knowledge
> would have to do that.
I've tried to follow vdr code, and I think I shall add specific code to
dvbdevice.c, specially:

 * GetRequiredDeliverySystem
 * cDvbTuner::SetFrontend
 * cDvbDevice::QueryDeliverySystems
 * cDvbDevice::ProvidesSource

Is there any developer guide for VDR so I can read it before trying to
understand directly from code? I have the proper HW & signal...


> Klaus

Lic. Christian A. Rodriguez

vdr mailing list

Reply via email to