Hi,
https://bugs.launchpad.net/ubuntu/+source/vdr/+bug/45721
In the Debian package (and Ubuntu of course) is a patch included, which removes the following line from channels.conf.terr:
Ch 14 (TV):481833:I0C23D0M64B8T2G32Y0:T:27500:2840:2841:2843:0:0:8800:0:0
Can anybody confirm, this line is invalid? Which will be the right line?
Would nice to get rid off this patch or have a valid channels.conf.terr upstream... :)
Regards, Lars.
On 10.02.2013 21:47, Lars Hanisch wrote:
Hi,
https://bugs.launchpad.net/ubuntu/+source/vdr/+bug/45721
In the Debian package (and Ubuntu of course) is a patch included, which removes the following line from channels.conf.terr:
Ch 14 (TV):481833:I0C23D0M64B8T2G32Y0:T:27500:2840:2841:2843:0:0:8800:0:0
Can anybody confirm, this line is invalid? Which will be the right line?
Would nice to get rid off this patch or have a valid channels.conf.terr upstream... :)
Maybe I should completely remove all channels.conf* files from the source archive? The existing ones are already rather old, and I can't possibly keep them up to date, anyway.
Any opinions?
Klaus
Am 10.02.2013 22:32, schrieb Klaus Schmidinger:
On 10.02.2013 21:47, Lars Hanisch wrote:
Hi,
https://bugs.launchpad.net/ubuntu/+source/vdr/+bug/45721
In the Debian package (and Ubuntu of course) is a patch included, which removes the following line from channels.conf.terr:
Ch 14 (TV):481833:I0C23D0M64B8T2G32Y0:T:27500:2840:2841:2843:0:0:8800:0:0
Can anybody confirm, this line is invalid? Which will be the right line?
Would nice to get rid off this patch or have a valid channels.conf.terr upstream... :)
Maybe I should completely remove all channels.conf* files from the source archive? The existing ones are already rather old, and I can't possibly keep them up to date, anyway.
Any opinions?
I don't use them, so no objections from me.
Lars.
On Sun, Feb 10, 2013 at 1:32 PM, Klaus Schmidinger Klaus.Schmidinger@tvdr.de wrote:
Maybe I should completely remove all channels.conf* files from the source archive? The existing ones are already rather old, and I can't possibly keep them up to date, anyway.
If they're not going to be kept up-to-date then they don't really serve any purpose since an outdated channels.conf is useless. People will just have to channel scan themselves anyways so why bother keeping outdated files in the source? I see no harm in removing them.
On 11.02.2013 05:04, VDR User wrote:
On Sun, Feb 10, 2013 at 1:32 PM, Klaus Schmidinger Klaus.Schmidinger@tvdr.de wrote:
Maybe I should completely remove all channels.conf* files from the source archive? The existing ones are already rather old, and I can't possibly keep them up to date, anyway.
If they're not going to be kept up-to-date then they don't really serve any purpose since an outdated channels.conf is useless. People will just have to channel scan themselves anyways so why bother keeping outdated files in the source? I see no harm in removing them.
On second thought, I guess I won't touch that area at this time, so close to version 2.0. I'll drop these files after version 2.0, once automatic transponder scanning will be implemented.
Kalsu
Am 2013-02-11 12:40, schrieb Klaus Schmidinger:
On 11.02.2013 05:04, VDR User wrote:
On Sun, Feb 10, 2013 at 1:32 PM, Klaus Schmidinger Klaus.Schmidinger@tvdr.de wrote:
Maybe I should completely remove all channels.conf* files from the source archive? The existing ones are already rather old, and I can't possibly keep them up to date, anyway.
If they're not going to be kept up-to-date then they don't really serve any purpose since an outdated channels.conf is useless. People will just have to channel scan themselves anyways so why bother keeping outdated files in the source? I see no harm in removing them.
On second thought, I guess I won't touch that area at this time, so close to version 2.0. I'll drop these files after version 2.0, once automatic transponder scanning will be implemented.
In this case it would be a good idea to delete this line Lars mentioned from channel.conf.terr that lets the vdr crash.
Gerald
On 11.02.2013 12:54, Gerald Dachs wrote:
Am 2013-02-11 12:40, schrieb Klaus Schmidinger:
On 11.02.2013 05:04, VDR User wrote:
On Sun, Feb 10, 2013 at 1:32 PM, Klaus Schmidinger Klaus.Schmidinger@tvdr.de wrote:
Maybe I should completely remove all channels.conf* files from the source archive? The existing ones are already rather old, and I can't possibly keep them up to date, anyway.
If they're not going to be kept up-to-date then they don't really serve any purpose since an outdated channels.conf is useless. People will just have to channel scan themselves anyways so why bother keeping outdated files in the source? I see no harm in removing them.
On second thought, I guess I won't touch that area at this time, so close to version 2.0. I'll drop these files after version 2.0, once automatic transponder scanning will be implemented.
In this case it would be a good idea to delete this line Lars mentioned from channel.conf.terr that lets the vdr crash.
I just tried that line with my VDR. It gives me an "Error in channel settings", but it doesn't crash. Does it actually *crash* for you?
Anyway, I'll remove that line.
Klaus
Am 11.02.2013 13:12, schrieb Klaus Schmidinger:
On 11.02.2013 12:54, Gerald Dachs wrote:
Am 2013-02-11 12:40, schrieb Klaus Schmidinger:
On 11.02.2013 05:04, VDR User wrote:
On Sun, Feb 10, 2013 at 1:32 PM, Klaus Schmidinger Klaus.Schmidinger@tvdr.de wrote:
Maybe I should completely remove all channels.conf* files from the source archive? The existing ones are already rather old, and I can't possibly keep them up to date, anyway.
If they're not going to be kept up-to-date then they don't really serve any purpose since an outdated channels.conf is useless. People will just have to channel scan themselves anyways so why bother keeping outdated files in the source? I see no harm in removing them.
On second thought, I guess I won't touch that area at this time, so close to version 2.0. I'll drop these files after version 2.0, once automatic transponder scanning will be implemented.
In this case it would be a good idea to delete this line Lars mentioned from channel.conf.terr that lets the vdr crash.
I just tried that line with my VDR. It gives me an "Error in channel settings", but it doesn't crash. Does it actually *crash* for you?
Not for me, I just stumbled over this patch in the debian package and the old entry in the Ubuntu bug tracker. The original poster can't start his vdr with this line, but I think it will not crash.
So whatever, if it gets removed, everything should be fine. :)
Lars.
Anyway, I'll remove that line.
Klaus
I think it touches some bigger problem - the need of scanning. I don't like scan and I doesn't see any need to do it myself on dvb-s (dvb-t works ok). Scanning is full of problems. There aren't unified version of (x)zap (I use command line only). Quality of scan is different on different cards and takes time. You need fresh transponder list or you ends up with incomplete channel list. Channel names are often silly and doesn't match real names. Your channels aren't grouped in any usable way (channels you pay are often from multiple providers). You often need to look for proper channel (there are dosen of Disney channels for example). Channels are randomly sorted so you need to manually sort it. You ends up with ton of useless channels like "arabic sex" and you need to dig channels you need. What I would like to have is scraper for KingOfSat which is probably most up-to-date sat channels database. I would prefer to filter this database by provider, sat name etc and produce channels.conf based on it. There would be need to keep some preferences, like list of FTA channels, sorting etc but that way making fresh channels.conf would be fast, easy, and productive. Marx
Am 2013-02-15 08:49, schrieb Marx:
What I would like to have is scraper for KingOfSat which is probably most up-to-date sat channels database. I would prefer to filter this database by provider, sat name etc and produce channels.conf based on it. There would be need to keep some preferences, like list of FTA channels, sorting etc but that way making fresh channels.conf would be fast, easy, and productive.
Sounds interesting, go for it.
Gerald