[vdr] Edit fails unexpectedly / Edit commands not queued. Why?
Dear Klaus and vdr folks. I experience one possible bug and one missing function in regard to cutting/editing recordings. First, if there is an uneven number of cutting marks, and the last mark is at the very end (last frame) of the recording, then editing fails at this last mark, and the newly created edited recording gets deleted. I suggest to change this to simply ignore any start mark that is at the very end of the recording. Second, if I have to edit a fistfull of recordings, I would expect that the edit commands are queued and processed one after the other, but it seems there is only one editing possible at one time: edit 115 250 Editing recording "115" [15.09.07 20:11 raid~Filme~Star Trek~Star Trek - Der erste Kontakt] edit 116 554 Editing process already active Maybe is is possible to implement a queuing for this? Thank you. pgpr5a5SOQXxT.pgp Description: PGP signature ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Straw poll: stable version 1.6.0 now?
On Sun, Feb 03, 2008 at 11:17:05AM +0100, Klaus Schmidinger wrote: >Should there be a stable version 1.6.0 now, based on what's in >version 1.5.14, but without DVB-S2 or even H.264 support? > > Yes or No? Yes. pgptdi5ZvSAJN.pgp Description: PGP signature ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Test Feed crashes vdr 1.6.0
Hello. For some days there i a new "Test Feed" channel being found automatic new channel scanner of vdr-1.6.0: [EMAIL PROTECTED]:/etc/vdr# tail -1 channels.conf Test Feed;Test Feed:10920:hC56:S19.2E:22000:0:0:0:0:0:1:1063:0 [EMAIL PROTECTED]:/etc/vdr# After this channel has been added to the channels.conf automatically, vdr doesn't get up any more after the next restart with the following syslog output at "-l 1": Jun 17 19:53:27 black vdr: [9340] ERROR: channel data results in invalid ID! Jun 17 19:53:27 black vdr: [9340] ERROR: error in /etc/vdr/channels.conf, line 1343 Is there any patch to prevent vdr from adding an invalid channel? Thank you. pgpkyiYtEzme3.pgp Description: PGP signature ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] no channel update for certain channels
On Tue Jan 27 11:03:39 CET 2009 Klaus Schmidinger wrote: > On 27.01.2009 11:01, Matthias Dahl wrote: > > On Tuesday 27 January 2009 10:37:24 Klaus Schmidinger wrote: > >> Have you tried contacting the broadcaster about this? > >> Such problems should be fixed at the root ;-) > > > > I agree. There is just one exception: it's done intentionally by > > the broadcaster to limit reception to certain boxes. :-} For > > those cases it would be nice to exclude those channels from the > > automatic update process. > > Those bastards... > > Can you give an example of such a channel? I am currently suffering from events like this: Jan 28 05:50:53 vdr vdr: [15232] changing pids of channel 84 from 2815+2815:2816=deu:0:32 to 2815+2815:2816=deu:0:0 Jan 28 05:50:54 vdr vdr: [15232] changing pids of channel 83 from 1535+1535:1536=deu:0:32 to 1535+1535:1536=deu:0:0 Jan 28 05:50:54 vdr vdr: [15232] changing pids of channel 82 from 1023+1023:1024=deu:0:32 to 1023+1023:1024=deu:0:0 Jan 28 05:50:54 vdr vdr: [15232] changing pids of channel 85 from 3071+3071:3072=deu:0:32 to 3071+3071:3072=deu:0:0 Jan 28 05:50:55 vdr vdr: [15232] changing pids of channel 81 from 1791+1791:1792=deu:0:32 to 1791+1791:1792=deu:0:0 Jan 28 05:50:55 vdr vdr: [15224] stopping recording due to modification of channel 83 Jan 28 05:52:45 vdr vdr: [15232] changing pids of channel 84 from 2815+2815:2816=deu:0:0 to 2815+2815:2816=deu:0:32 Jan 28 05:52:45 vdr vdr: [15232] changing pids of channel 83 from 1535+1535:1536=deu:0:0 to 1535+1535:1536=deu:0:32 Jan 28 05:52:45 vdr vdr: [15232] changing pids of channel 82 from 1023+1023:1024=deu:0:0 to 1023+1023:1024=deu:0:32 Jan 28 05:52:45 vdr vdr: [15232] changing pids of channel 85 from 3071+3071:3072=deu:0:0 to 3071+3071:3072=deu:0:32 Jan 28 05:52:45 vdr vdr: [15232] changing pids of channel 81 from 1791+1791:1792=deu:0:0 to 1791+1791:1792=deu:0:32 Jan 28 05:52:45 vdr vdr: [15232] changing pids of channel 75 from 2559+2559:2560=deu:0:0 to 2559+2559:2560=deu:0:32 Jan 28 05:52:45 vdr vdr: [15224] stopping recording due to modification of channel 83 Recording gets heavily fragmented and unviewable. I suggest that recordings shall not be stopped and restarted except when things are changed that are neccessary for the recording (which the TPID is not), and maybe there shall be even more rate limiting on PID updates for channels with active recordings on. Thank you. pgpeFDu3u3q5c.pgp Description: PGP signature ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] no channel update for certain channels
On Fri, Jan 30, 2009 at 05:09:24PM +0100, Klaus Schmidinger wrote: > On 28.01.2009 19:33, Patrick Rother wrote: > > I am currently suffering from events like this: > > > > Jan 28 05:50:53 vdr vdr: [15232] changing pids of channel 84 from > > 2815+2815:2816=deu:0:32 to 2815+2815:2816=deu:0:0 > > Jan 28 05:50:54 vdr vdr: [15232] changing pids of channel 83 from > > 1535+1535:1536=deu:0:32 to 1535+1535:1536=deu:0:0 > > Jan 28 05:50:54 vdr vdr: [15232] changing pids of channel 82 from > > 1023+1023:1024=deu:0:32 to 1023+1023:1024=deu:0:0 > > Jan 28 05:50:54 vdr vdr: [15232] changing pids of channel 85 from > > 3071+3071:3072=deu:0:32 to 3071+3071:3072=deu:0:0 > > Jan 28 05:50:55 vdr vdr: [15232] changing pids of channel 81 from > > 1791+1791:1792=deu:0:32 to 1791+1791:1792=deu:0:0 > > Jan 28 05:50:55 vdr vdr: [15224] stopping recording due to modification of > > channel 83 > > > > Jan 28 05:52:45 vdr vdr: [15232] changing pids of channel 84 from > > 2815+2815:2816=deu:0:0 to 2815+2815:2816=deu:0:32 > > Jan 28 05:52:45 vdr vdr: [15232] changing pids of channel 83 from > > 1535+1535:1536=deu:0:0 to 1535+1535:1536=deu:0:32 > > Jan 28 05:52:45 vdr vdr: [15232] changing pids of channel 82 from > > 1023+1023:1024=deu:0:0 to 1023+1023:1024=deu:0:32 > > Jan 28 05:52:45 vdr vdr: [15232] changing pids of channel 85 from > > 3071+3071:3072=deu:0:0 to 3071+3071:3072=deu:0:32 > > Jan 28 05:52:45 vdr vdr: [15232] changing pids of channel 81 from > > 1791+1791:1792=deu:0:0 to 1791+1791:1792=deu:0:32 > > Jan 28 05:52:45 vdr vdr: [15232] changing pids of channel 75 from > > 2559+2559:2560=deu:0:0 to 2559+2559:2560=deu:0:32 > > Jan 28 05:52:45 vdr vdr: [15224] stopping recording due to modification of > > channel 83 > > > > Recording gets heavily fragmented and unviewable. > > Can you post the channels.conf entry of a channel where this happens? These are 81 .. 85: BEATE-UHSE.TV,B-UHSE;PREMIERE:11758:hC34:S19.2E:27500:1791:1792=deu:32:1702,1722,1837,1833,1834,9C4,B00,D05:21:133:17:0 DISCOVERY CHANNEL,DISCOVERY;PREMIERE:11758:hC34:S19.2E:27500:1023:1024=deu:32:1702,1722,1837,1833,1834,9C4,B00,D05:14:133:17:0 DISCOVERY GESCHICHTE,GESCHICHTE;PREMIERE:11758:hC34:S19.2E:27500:1535:1536=deu:32:1702,1722,1837,1833,1834,9C4,B00,D05:13:133:17:0 ANIMAL PLANET,ANIMAL;PREMIERE:11758:hC34:S19.2E:27500:2815:2816=deu:32:1702,1722,1837,1833,1834,9C4,B00,D05:12:133:17:0 FOCUS GESUNDHEIT,FOCUS G;PREMIERE:11758:hC34:S19.2E:27500:3071:3072=deu:32:1702,1722,1837,1833,1834,9C4,B00,D05:15:133:17:0 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] no channel update for certain channels
On Sun, Feb 01, 2009 at 05:06:11PM +0100, Klaus Schmidinger wrote: > On 31.01.2009 07:47, Patrick Rother wrote: > > On Fri, Jan 30, 2009 at 05:09:24PM +0100, Klaus Schmidinger wrote: > >> On 28.01.2009 19:33, Patrick Rother wrote: > >>> I am currently suffering from events like this: > >>> > >>> Jan 28 05:50:53 vdr vdr: [15232] changing pids of channel 84 from > >>> 2815+2815:2816=deu:0:32 to 2815+2815:2816=deu:0:0 > >>> Jan 28 05:50:54 vdr vdr: [15232] changing pids of channel 83 from > >>> 1535+1535:1536=deu:0:32 to 1535+1535:1536=deu:0:0 > >>> Jan 28 05:50:54 vdr vdr: [15232] changing pids of channel 82 from > >>> 1023+1023:1024=deu:0:32 to 1023+1023:1024=deu:0:0 > >>> Jan 28 05:50:54 vdr vdr: [15232] changing pids of channel 85 from > >>> 3071+3071:3072=deu:0:32 to 3071+3071:3072=deu:0:0 > >>> Jan 28 05:50:55 vdr vdr: [15232] changing pids of channel 81 from > >>> 1791+1791:1792=deu:0:32 to 1791+1791:1792=deu:0:0 > >>> Jan 28 05:50:55 vdr vdr: [15224] stopping recording due to modification > >>> of channel 83 > >>> > >>> Jan 28 05:52:45 vdr vdr: [15232] changing pids of channel 84 from > >>> 2815+2815:2816=deu:0:0 to 2815+2815:2816=deu:0:32 > >>> Jan 28 05:52:45 vdr vdr: [15232] changing pids of channel 83 from > >>> 1535+1535:1536=deu:0:0 to 1535+1535:1536=deu:0:32 > >>> Jan 28 05:52:45 vdr vdr: [15232] changing pids of channel 82 from > >>> 1023+1023:1024=deu:0:0 to 1023+1023:1024=deu:0:32 > >>> Jan 28 05:52:45 vdr vdr: [15232] changing pids of channel 85 from > >>> 3071+3071:3072=deu:0:0 to 3071+3071:3072=deu:0:32 > >>> Jan 28 05:52:45 vdr vdr: [15232] changing pids of channel 81 from > >>> 1791+1791:1792=deu:0:0 to 1791+1791:1792=deu:0:32 > >>> Jan 28 05:52:45 vdr vdr: [15232] changing pids of channel 75 from > >>> 2559+2559:2560=deu:0:0 to 2559+2559:2560=deu:0:32 > >>> Jan 28 05:52:45 vdr vdr: [15224] stopping recording due to modification > >>> of channel 83 > >>> > >>> Recording gets heavily fragmented and unviewable. > >> Can you post the channels.conf entry of a channel where this happens? > > > > These are 81 .. 85: > > > > BEATE-UHSE.TV,B-UHSE;PREMIERE:11758:hC34:S19.2E:27500:1791:1792=deu:32:1702,1722,1837,1833,1834,9C4,B00,D05:21:133:17:0 > > DISCOVERY > > CHANNEL,DISCOVERY;PREMIERE:11758:hC34:S19.2E:27500:1023:1024=deu:32:1702,1722,1837,1833,1834,9C4,B00,D05:14:133:17:0 > > DISCOVERY > > GESCHICHTE,GESCHICHTE;PREMIERE:11758:hC34:S19.2E:27500:1535:1536=deu:32:1702,1722,1837,1833,1834,9C4,B00,D05:13:133:17:0 > > ANIMAL > > PLANET,ANIMAL;PREMIERE:11758:hC34:S19.2E:27500:2815:2816=deu:32:1702,1722,1837,1833,1834,9C4,B00,D05:12:133:17:0 > > FOCUS GESUNDHEIT,FOCUS > > G;PREMIERE:11758:hC34:S19.2E:27500:3071:3072=deu:32:1702,1722,1837,1833,1834,9C4,B00,D05:15:133:17:0 > > I can't see any permanently changing pids on that transponder. > When you say "Recording gets heavily fragmented and unviewable" > I would assume that the pids change every few minutes - but I haven't > seen that yet. > Does this happen only at certain times of day? > Or was it maybe a glitch on the provider side? It doesn't look like a glitch. If nobody else is seeing this, I have to assume that my CAM stuff is more unstable than I am aware of. Anyway I'd like to repeat my suggestion that recordings shall only be interupted when relevant changes have been made to the PIDs. Please include this to your todo list, maybe at the lower half. ;) Thank you. Jan 22 05:02:21 vdr vdr: [23430] changing pids of channel 53 from 225+225:226=deu:0:231 to 225+225:226=deu:0:0 Jan 22 05:02:34 vdr vdr: [23430] changing pids of channel 53 from 225+225:226=deu:0:0 to 225+225:226=deu:0:231 Jan 24 20:05:14 vdr vdr: [23823] changing pids of channel 83 from 1535+1535:1536=deu:0:32 to 1535+1535:1536=deu:0:0 Jan 24 20:05:14 vdr vdr: [23823] changing pids of channel 82 from 1023+1023:1024=deu:0:32 to 1023+1023:1024=deu:0:0 Jan 24 20:05:14 vdr vdr: [23823] changing pids of channel 85 from 3071+3071:3072=deu:0:32 to 3071+3071:3072=deu:0:0 Jan 24 20:05:15 vdr vdr: [23823] changing pids of channel 81 from 1791+1791:1792=deu:0:32 to 1791+1791:1792=deu:0:0 Jan 24 20:05:15 vdr vdr: [23823] changing pids of channel 75 from 2559+2559:2560=deu:0:32 to 2559+2559:2560=deu:0:0 Jan 24 20:05:16 vdr vdr: [23823] changing pids of channel 84 from 2815+2815:2816=deu:0:32 to 2815+2815:2816=deu:0:0 Jan 24 20:27:48 vdr vdr: [23820] changing pids of channel 83 from 1535+1535:1536=deu:0:0 to 1535+1535:1536=deu:0:32 Jan 24 20:27:49 v
[vdr] sparse DVB adapter numbers
Dear vdr fellows. For a reason not to go in details too much here, I would like to make vdr recognise sparse DVB adapter numbers. I have: r...@vdr:/dev/dvb# ls -l total 0 drwxr-xr-x 2 root root 200 Mar 19 11:59 adapter0/ drwxr-xr-x 2 root root 120 Mar 19 11:59 adapter1/ drwxr-xr-x 2 root root 120 Mar 19 11:59 adapter5/ drwxr-xr-x 2 root root 120 Mar 19 11:59 adapter6/ drwxr-xr-x 2 root root 120 Mar 19 11:59 adapter7/ r...@vdr:/dev/dvb# But vdr uses only the first two devices. Is there any easy possibility to patch the code accordingly? Thank you. pgpVNxuvVBhfv.pgp Description: PGP signature ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] sparse DVB adapter numbers
On Sun, Mar 22, 2009 at 02:21:07PM +0100, Klaus Schmidinger wrote:
> On 21.03.2009 14:17, Artur Skawina wrote:
> > Patrick Rother wrote:
> >> For a reason not to go in details too much here, I would like to make
> >> vdr recognise sparse DVB adapter numbers.
> >>
> >> I have:
> >>
> >> r...@vdr:/dev/dvb# ls -l
> >> total 0
> >> drwxr-xr-x 2 root root 200 Mar 19 11:59 adapter0/
> >> drwxr-xr-x 2 root root 120 Mar 19 11:59 adapter1/
> >> drwxr-xr-x 2 root root 120 Mar 19 11:59 adapter5/
> >> drwxr-xr-x 2 root root 120 Mar 19 11:59 adapter6/
> >> drwxr-xr-x 2 root root 120 Mar 19 11:59 adapter7/
> >> r...@vdr:/dev/dvb#
> >>
> >> But vdr uses only the first two devices.
> >>
> >> Is there any easy possibility to patch the code accordingly?
> >
> > ./vdr -D 0 -D 1 -D 5 -D 6 -D 7
>
> I'm afraid this won't work, because VDR stops scaning for DVB devices
> as soon as it hits a gap.
>
> You might want to try changing this function:
>
> bool cDvbDevice::Initialize(void)
> {
> int found = 0;
> int i;
> for (i = 0; i < MAXDVBDEVICES; i++) {
> if (UseDevice(NextCardIndex())) {
> if (Probe(*cDvbName(DEV_DVB_FRONTEND, i))) {
> new cDvbDevice(i);
> found++;
> }
> else
> NextCardIndex(1); // skips this one <=== changed line
> }
> else
> NextCardIndex(1); // skips this one
> }
> NextCardIndex(MAXDVBDEVICES - i); // skips the rest
> if (found > 0)
> isyslog("found %d video device%s", found, found > 1 ? "s" : "");
> else
> isyslog("no DVB device found");
> return found > 0;
> }
>
> Untested, don't know if it will actually work as expected.
I will test this and let you know.
Thank you!
pgpWKWwcEZ4QV.pgp
Description: PGP signature
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Can I disable pause live tv altogher?
On Fri, May 08, 2009 at 08:30:24PM +0300, Pasi Juppo wrote: > I'd also like to see option where live-tv pause can be enabled/disabled. I second this idea. I have a large recorder host, and satellite hosts for watching live TV and recordings (via NFS), but I usually don't want to record anything at the satellites. I.e. I'd prefer to have the instant-record and pause-live-tv keys disabled there. I could disable these remote control keys completety, but I do use the pause key while playing recordings, so this is not an option. So, a "don't record at this host" configuration option would be nice. Thank you. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Can I disable pause live tv altogher?
On Wed, May 13, 2009 at 11:08:56AM +0200, Nicolas Huillard wrote: > Patrick Rother a écrit : > > On Fri, May 08, 2009 at 08:30:24PM +0300, Pasi Juppo wrote: > >> I'd also like to see option where live-tv pause can be enabled/disabled. > > > > I second this idea. > > > > I have a large recorder host, and satellite hosts for watching live > > TV and recordings (via NFS), but I usually don't want to record > > anything at the satellites. > > I.e. I'd prefer to have the instant-record and pause-live-tv keys > > disabled there. > > > > I could disable these remote control keys completety, but I do use > > the pause key while playing recordings, so this is not an option. > > > > So, a "don't record at this host" configuration option would be nice. > > I think the good solution for this situation would be to forward the > recording request to the "large recorder host". For real, I have a watchdog script does this, i.e. look for timers and remove them, but this is an ugly workaround. As most pause key pressings are accidental, this is quite annoying. I'd prefer to have a switch to disable recording at all. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] sparse DVB adapter numbers
On Mon, Mar 23, 2009 at 03:39:43PM +0100, Patrick Rother wrote:
> On Sun, Mar 22, 2009 at 02:21:07PM +0100, Klaus Schmidinger wrote:
> > On 21.03.2009 14:17, Artur Skawina wrote:
> > > Patrick Rother wrote:
> > >> For a reason not to go in details too much here, I would like to make
> > >> vdr recognise sparse DVB adapter numbers.
> > >>
> > >> I have:
> > >>
> > >> r...@vdr:/dev/dvb# ls -l
> > >> total 0
> > >> drwxr-xr-x 2 root root 200 Mar 19 11:59 adapter0/
> > >> drwxr-xr-x 2 root root 120 Mar 19 11:59 adapter1/
> > >> drwxr-xr-x 2 root root 120 Mar 19 11:59 adapter5/
> > >> drwxr-xr-x 2 root root 120 Mar 19 11:59 adapter6/
> > >> drwxr-xr-x 2 root root 120 Mar 19 11:59 adapter7/
> > >> r...@vdr:/dev/dvb#
> > >>
> > >> But vdr uses only the first two devices.
> > >>
> > >> Is there any easy possibility to patch the code accordingly?
> > >
> > > ./vdr -D 0 -D 1 -D 5 -D 6 -D 7
> >
> > I'm afraid this won't work, because VDR stops scaning for DVB devices
> > as soon as it hits a gap.
> >
> > You might want to try changing this function:
> >
> > bool cDvbDevice::Initialize(void)
> > {
> > int found = 0;
> > int i;
> > for (i = 0; i < MAXDVBDEVICES; i++) {
> > if (UseDevice(NextCardIndex())) {
> > if (Probe(*cDvbName(DEV_DVB_FRONTEND, i))) {
> > new cDvbDevice(i);
> > found++;
> > }
> > else
> > NextCardIndex(1); // skips this one <=== changed line
> > }
> > else
> > NextCardIndex(1); // skips this one
> > }
> > NextCardIndex(MAXDVBDEVICES - i); // skips the rest
> > if (found > 0)
> > isyslog("found %d video device%s", found, found > 1 ? "s" : "");
> > else
> > isyslog("no DVB device found");
> > return found > 0;
> > }
> >
> > Untested, don't know if it will actually work as expected.
>
> I will test this and let you know.
>
> Thank you!
This seems not to work.
Does anybody have another idea?
Thank you.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] One recording per device only
Hello. I have a vdr host with 1 DVB-s FF card and 3 DVB-s USB devices and 3 DVB-t USB devices. When I have 2 concurrent DVB-s recordings at different transponders, these are done at different DVB-s USB devices and there is no problem, but if I have 2 concurrent recordings at the same transponder, I get lots of: Sep 24 16:27:39 vdr vdr: [20650] 2 cRepacker messages suppressed Sep 24 16:27:39 vdr vdr: [20650] cAudioRepacker(0xC1): skipped 572 bytes while syncing on next audio frame Sep 24 16:27:39 vdr vdr: [20650] 3 cRepacker messages suppressed Sep 24 16:27:39 vdr vdr: [20650] cAudioRepacker(0xC0): skipped 1148 bytes while syncing on next audio frame and scrambled data. As a first workaround / test setup I would like to limit vdr to do at most one recording per device and chose a new device even if a second recording is at the same transponder. Most suitably this shall apply one to specific devices or channels, if possible. How could this be achieved? Thank you. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
