Am 07.09.2016 um 19:59 schrieb VDR User <user.vdr@xxxxxxxxx>: >> It is broken (see below). Have you ever used dvbv5 tools with vdr format >> output or did you know a "VDR user" who is using dvbv5-scan and not wscan? > > In my experience the v4l scanner, wscan, and VDR's internal scanner > has never worked well (for NA). I use nscan, which has easily been the > most successful of the scanners. An additional benefit to nscan is you > only supply a single transponder on the command line and it will > populate a channel list for the entire sat. You don't need to supply > an entire list of transponders to scan. > > As far as other VDR users, of which I know many being a long time > user, they tend to use whatever works best for them. > >>> Well, the libdvbv5 VDR output support was written aiming VDR version 2.1.6. >>> I've no idea if it works with VDR 1.6.0. > > It's not uncommon to find VDR users who run versions as old as 1.6.0*. > Some are completely satisfied leaving their perfectly stable system be > with no concern about updating it. > >> Since these bugs are from the beginning and no one has rejected, >> I suppose, that these VDR 1.6.0 users are using wscan and not the >> dvbv5 tools. IMHO the VDR format has never been worked, >> so we can't break backwards compatible ;) and since there is wscan >> widely used by old vdr hats, we do not need to care pre-DVB-[T|S]-2 >> formats. > > Instead of making that kind of assumption, why not ask VDR users > directly on the VDR mailing list? > >> As I said, it might be more helpful to place vdr in a public >> repository and to document channel's format well. It is always a >> hell for me to dig into the vdr sources without a version >> context and an ambiguous documentation ... > > There is already a publicly available VDR repository offering the > current stable & developer versions, along with all previous versions: > http://www.tvdr.de/download.htm ?? these are tarballs, where is the version control system? > >> Different formats (compare): >> * http://www.vdr-wiki.de/wiki/index.php/Channels.conf#Unterschiede >> * https://www.linuxtv.org/vdrwiki/index.php/Syntax_of_channels.conf#Differences > > It's best to refer to VDRs packaged documention. You can get the > channels.conf format definition with `man 5 vdr`. Good point, but I have only 2.2 installed, so where get I the backward informations .. should I extract all theses tarballs and read through them .. you see my point? >> VDR wiki recommends wscan >> * http://www.vdr-wiki.de/wiki/index.php/W_scan > > That wiki shouldn't be viewed as a main reference point in general but > especially for scanning. And the main ref is https://www.linuxtv.org ... which is not updated? > As mentioned earlier, people tend to use what > works for them. In NA/SA nscan tends to be the top choice. Europe/Asia > tends to be other scanners. What I said, nobody use the vdr format of dvbv5-tools, since it is broken and now, Chris and I want to fix it. > >> I think, there is much room left to support developers and users >> outside the vdr community ;) >> >> Would you like to test these patches from Chris and mine / Thanks >> that will be very helpful. > > I'd recommend posting to the VDR mailing list where you'll find more > people who use and would be affected by these changes. Additionally, > you could inquire at vdr-portal.de, which is one of the most supported > VDR forums for both users and developers. Chris and I want to patch something in v4l-utils which is broken and YOU make the assumption that our patches are not OK ... and now, # I have to ask someone other on a different projects ML and their portal? If you have a doubt about the patches from Chris and mine, make a test and if you see any regression it would be great to post your experience here ... thanks. -- Markus -- -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
