Posts by Marx2

    You did it! I've used those two only just to test and it automatically discovered all others and scanned them successfully. And now mystery is solved, as those channels are DVB-C channels. I had no idea that both standards are emitted at the same time on the same cable, but it explains everything. Thank you!

    I forgot to add that I've tried dvbv5_scan, but it needs initial data, and even if I've used some DE/PL data, it didn't found any channel :(

    But I can repeat that process, if you give me an example

    I've build & used t2scan, but yes, it didn't do much. I'll attach output in spoiler. I can play with some parameters, like longer timeouts, which has helped w_scan find more channels (more then 40). I'm surprised frequency isn't stable term, but it clarify the inconsistency between TV and card. Now the question is how should I proceed? I've tried multiple software: NextPVR was unreliable and found only a few channels, TVHeadend found many channels but not all (and I didn't found possibility to manually add missing), so I went back to VDR which I'm using for 10(?) years, because it gives me most control. I was thinking I can somehow use my TV as a source of truth, but if it isn't reliable source, what can I do to correctly scan and find all channels?

    Edit: By frequency I mean frequency of MUX. If I would be able to gather all MUXes initial scan data correctly set, I think scanning would find all channels


    I use local cable provider which deliver non-standard DVB-T frequencies.

    I have Samsung TV, and from what I can see, it scans channels on MUXes with frequencies: 506,514,522,530,538,546,554,562,570,578,586,594,602,610,618,626,634,642,650,658,666. Technician said it starts with 506000, and jumps by 8000, modulation 256QAM, 6900 transmission speed. In TV everything works.

    I have also quad DVB-T card identified as Silicon Labs Si2168. w_scan finds such frequencies:

    # T[2] <freq> <bw> <fec_hi> <fec_lo> <mod> <tm> <guard> <hi> [plp_id] [# comment]


    T 730000000 8MHz 5/6 NONE QAM64 8k 1/16 NONE # Imperium

    T 738000000 8MHz 5/6 NONE QAM64 8k 1/16 NONE # Imperium Cofdm

    T 746000000 8MHz 5/6 NONE QAM64 8k 1/16 NONE # Imperium Cofdm

    T 754000000 8MHz 5/6 NONE QAM64 8k 1/16 NONE # Imperium

    T 786000000 8MHz 5/6 NONE QAM64 8k 1/16 NONE

    T 794000000 8MHz 5/6 NONE QAM64 8k 1/16 NONE # IMPERIUM

    T 802000000 8MHz 5/6 NONE QAM64 8k 1/4 NONE # Emitel

    T 818000000 8MHz 5/6 NONE QAM64 8k 1/8 NONE # IMPERIUM

    T 826000000 8MHz 5/6 NONE QAM64 8k 1/16 NONE

    (and these are not all, for example there's missing 810000000 frequency, I can add it manually and it later works

    Those frequencies also works, I can scan them with w_scan getting for example such a channel:

    HGTV HD;TVN:738000:B8C56D0G16M64T8Y0:T:27500:532=27:850=pol@3,851=org:0;6031:0:4315:0:0:0

    On the other side the same channel read from TV (using Samsung channel editor from shows:

    At the end I have two different sets of channels: in TV and in computer tuner. Most channels are in both sources, but some of them are in TV only, and some in computer tuner only.

    I really don't understand, why they doesn't see the same frequencies.

    It looks like my provider emits on two sets of frequencies, and (at the same time) TV sees only one set, and computer card - second one.
    The other option is those frequencies are the same, but somehow re-mapped (but different QAMs suggest it's not true)

    I'd like have the same set of channels in both sources. Pls help me understand what's happening here.

    Thank you, I've spend some time reading about this card and unfortunately it has only one head for one system, so it can't be used as dual DVB-T tuner.

    Hello, what's current status of support of this card? I plan to use it as dual DVB-T card, but if it's possible, I would use it as DVB-S2 + DVB-T tuner. Because it's dual tuner, is it possible to use one tuner as DVB-S2 and the second one as DVB-T? If not, does it card works as dual DVB-T tuner?

    I'm looking for help with multiple vdr installations.
    I would like to have multiple vdr versions installed, and it should be easy to switch betewen them as needed.
    I think there are scripts which help to switch automatically but I cannot find them

    I have card from the title revision 2. after applying patches its recognized and works, Hovewer not so long. Suddenly it emits a bunch of messages to logs like bulk message failed or I2c transfer failed. Any help?

    May 25 19:10:38 wuwek kernel: [36651.999338] dvb-usb: bulk message failed: -19 (3/0)
    May 25 19:10:38 wuwek kernel: [36651.999351] dw2102: i2c transfer failed.

    Usually restarting VDR helps, but sometimes I have to replug USB.
    I use 3.2 kernel from Debian. I use linux-media-dkms from yavdr, but tried different patches but nothing helps.

    I'm trying to send to newsgroup about VDR on gmane server. On test newsgroup everything works ok. I'm confirming my email address and see my posts. Hovewer sending to VDR newsgroup do nothing - I doesn't see my posts. Is there another newsgroup server I could use?

    I have both packages installed, but I don't have on disc missing, hmmm....
    I use VDR 1.7.27 3yavdr0 lucid
    Ok. I have only debian packages, I need to instal them from yavdr repository, probably stable one.

    Ok I have libtntnet package from yavdr, but I still can't find any libtnt in /lib. I must doing something wrong.
    Ok, live is working!

    Its strange because I have in VDR.Conf 6419 as Svdrp port, yet VDR ignored it and listen on 2001. If vdaradmin is reconfigured to this port - it works.

    Anyway live really doesn't works because of missing library libtntnet as somebody has written - can you tell me on which package in Ubuntu this library is?

    I see there is new version of VDR together with vompserver plugin. Hovewer plugin doesn't work - uknown symbol. In Ubuntu it works?

    Vdradmin-am doesn't work with this VDR. I need some time to reconfigure out probably. Should it work with .27 VDR or is it abandoned?

    Actually I use debian unstable and yavdr testing with kernel 3.2 self compiled because of terratec cinergy s2 needs a patch and it works. Thanks for hint about vomp and live from stable yavdr repository - I'll try it.

    While vomp is intended not to work (anyway it doesn't play well with HD content) the only problem I have is live (to tell the truth I prefered Vdradmin-am but I'm trying to switch) so my problem isn't blocking. Its nice so many people are willing to help, thank you!

    I've pinned yavdr repository so I don't use packages from debian at all. I use this server several years and prefer debian over Ubuntu so reinstalling is no option. yes its true that now debian has .26 but its unpatched vanilla version so not for me. I've used etobi successfully 3 years or so, but its outdated now. And also most modern Ubuntu Pvr ppas are Ubuntu centric so its much easier to fit xbmc pvr and VDR and amd acceleration - I use zacate.

    There is no problem with running yavdr packages on debian. Incompatibility is between VDR and live plugin. E-Tobi repository doesn't have the newest VDR so I try to use yavdr. I see yavdr structure is rather compatible with e-Tobi, because simple upgrade made everything working. All configure files fit, and VDR works as it should
    Another reason to use yavdr is xbmc with Pvr which e-Tobi repository lacks.

    I installed vdr from yavdr today in debian and have 2 problems. Live plugin isn't compatible with (serious binary incompatibility) and there is no vomp plugin in repository. Any help?