Re: [vdr] Defunct screensaver processes under Xine
On Mon, Apr 14, 2008 at 7:51 PM, Todd Luliak <[EMAIL PROTECTED]> wrote: > > > I'd be happy if the screensaver never ran again, as it's of no use here > whatsoever. > Where do I begin looking to curb the creation of these zombies? > Do you need to run gnome at all? Its quite processor intensive if all you are doing is using it to watch TV. See the other recent thread on starting VDR/xine at boot time using startx / replacing the session manager and those problems with gnome screensaver won't be apparent. Also, there is a later version (patch) of CoreAVC for xine that I released on the list which will apply to the hg version of xine (with a bit of tweaking with more recent versions). The updated version will support channels at resolutions different to 1920x1080i (there are quite a few of them). HTH ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Multiple decryption with TechniCrypt CW CAM
Klaus Schmidinger wrote:
Does the log really end at that point?
If there is no "Ca Pmt Reply" then the CAM doesn't reply to
the query.
That is, no reply in this point.
Because I got second confirmation from TechniSat Support about multiple
decryption possibility, I made small test changes in ci.c file (ci.diff).
After that multiple decryption works! I know, this is not right solution, but
now it proved that CAM works in principle. Why it doesn't reply to query at vdr
startup, i don't know, but later it does (log.txt).
Any ideas for an elegant solution?
Arthur
--- ci.c.orig 2008-04-15 14:55:59.0 +0300
+++ ci.c2008-04-15 14:58:41.0 +0300
@@ -771,6 +771,7 @@
}
dbgprotocol("\n");
}
+ state = 6; //AK
break;
default: esyslog("ERROR: CAM %d: conditional access support: unknown
tag %06X", Tc()->CamSlot()->SlotNumber(), Tag);
}
@@ -789,6 +790,7 @@
else if (state == 3 && timer.TimedOut()) {
dsyslog("CAM %d: doesn't reply to QUERY - only a single channel can be
decrypted", Tc()->CamSlot()->SlotNumber());
state = 4; // normal operation
+ repliesToQuery = true; //AK
}
}
@@ -1888,7 +1890,7 @@
}
}
-#define QUERY_REPLY_WAIT 100 // ms to wait between checks for a reply
+#define QUERY_REPLY_WAIT 300 // ms to wait between checks for a reply //AK
bool cCamSlot::CanDecrypt(const cChannel *Channel)
{
[EMAIL PROTECTED]:~# runvdr
Slot 1: reset...ok.
Slot 1: module present
Slot 1: module ready
Slot 1: creating connection 0/1
-
MakePrimaryDevice: 1
=
SetVideoFormat: 0
SetVolumeDevice: 200
Slot 1: create connection 0/1
1: --> 00 01 82 01 01
1: <-- 00 01 83 01 01 80 02 01 00
. . . . . . . . .
Slot 1: connection created 0/1
Slot 1: receive data 0/1
1: --> 00 01 81 01 01
1: <-- 00 01 A0 07 01 91 04 00 01 00 41 80 02 01 00
. . . . . . . . . . A . . . .
Slot 1: open session 00010041
Slot 1: new Resource Manager (session id 1)
1: --> 00 01 A0 0A 01 92 07 00 00 01 00 41 00 01
Slot 1: ==> Profile Enq (1)
1: --> 00 01 A0 09 01 90 02 00 01 9F 80 10 00
Slot 1: receive data 0/1
1: --> 00 01 81 01 01
1: <-- 00 01 A0 09 01 90 02 00 01 9F 80 11 00 80 02 01 00
. . . . . . . . . . . . . . . . .
Slot 1: <== Profile (1)
Slot 1: ==> Profile Change (1)
1: --> 00 01 A0 09 01 90 02 00 01 9F 80 12 00
Slot 1: receive data 0/1
1: --> 00 01 81 01 01
1: <-- 00 01 A0 09 01 90 02 00 01 9F 80 10 00 80 02 01 00
. . . . . . . . . . . . . . . . .
Slot 1: <== Profile Enquiry (1)
Slot 1: ==> Profile (1)
1: --> 00 01 A0 1D 01 90 02 00 01 9F 80 11 14 00 01 00 41 00 02 00 41 00
03 00 41 00 24 00 41 00 40 00 41
Slot 1: receive data 0/1
1: --> 00 01 81 01 01
1: <-- 00 01 A0 07 01 91 04 00 02 00 41 80 02 01 00
. . . . . . . . . . A . . . .
Slot 1: open session 00020041
Slot 1: new Application Information (session id 2)
1: --> 00 01 A0 0A 01 92 07 00 00 02 00 41 00 02
Slot 1: ==> Application Info Enq (2)
1: --> 00 01 A0 09 01 90 02 00 02 9F 80 20 00
Slot 1: receive data 0/1
1: --> 00 01 81 01 01
1: <-- 00 01 A0 1E 01 90 02 00 02 9F 80 21 15 01 00 00 03 3D 0F 54 53 44
20 43 72 79 70 74 20 43 6F 6E 61 78 80 02 01 00
. . . . . . . . . . . ! . . . . . = . T S D
C r y p t C o n a x . . . .
Slot 1: <== Application Info (2)
Slot 1: receive data 0/1
1: --> 00 01 81 01 01
1: <-- 00 01 A0 07 01 91 04 00 03 00 41 80 02 01 00
. . . . . . . . . . A . . . .
Slot 1: open session 00030041
Slot 1: new Conditional Access Support (session id 3)
1: --> 00 01 A0 0A 01 92 07 00 00 03 00 41 00 03
Slot 1: ==> Ca Info Enq (3)
1: --> 00 01 A0 09 01 90 02 00 03 9F 80 30 00
Slot 1: receive data 0/1
1: --> 00 01 81 01 01
1: <-- 00 01 A0 0B 01 90 02 00 03 9F 80 31 02 0B 00 80 02 01 00
. . . . . . . . . . . 1 . . . . . . .
Slot 1: <== Ca Info (3) 0B00
Slot 1: ==> Ca Pmt (3) 3 3
1: --> 00 01 A0 10 01 90 02 00 03 9F 80 32 07 03 00 00 01 00 01 03
Slot 1: ==> Ca Pmt (3) 4 1
1: --> 00 01 A0 1A 01 90 02 00 03 9F 80 32 11 04 04 42 01 00 01 01 02 08
C0 00 00 04 08 C1 00 00
SetAudioChannelDevice: 0
SetDigitalAudioDevice: 0
SetAudioChannelDevice: 0
SetVolumeDevice: 200
SetPlayMode: 1
frame: (0, 0)-(-1, -1), zoom: (1,00, 1,00)
SetPlayMode: 0
Slot 1: ==> Ca Pmt (3) 5 1
1: --> 00 01 A0 16 01 90 02 00 03 9F 80 32 0D 05 04 42 01 00 07 01 09 04
0B 00 E3 EC
Slot 1: ==> Ca Pmt (3) 4 1
1: --> 00 01 A0 20 01 90 02 00 03 9F 80 32 17 04 04 42 01 00 07 01 09 04
0B 00 E3 EC 02 08 C0 00 00 04 08 C1 00 00
SetAudioChannelDevice: 0
SetDigitalAudioDevice: 0
SetAudioChannelDevice: 0
SetPlayMode: 1
video: synced early
vdr-xine: Clien
Re: [vdr] xineliboutput audio lip sync problems
Well it looks like I'm the only Gentoo user here that is experiencing this problem. I noticed a bit more on when it occurs. I've current changed my vdr process to run at -19 priority to see if it makes any difference. Livetv is some how now correct. But I still experience problems with recordings where cutting/editing occured. So I changed to vdr-softdevice, and I'm experience the same problem. LiveTV is acceptable but still experience audio/video sync problems after the replay has reached a edit/cut mark. (This is a recording that was processed) Any ideas? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Defunct screensaver processes under Xine
>Do you need to run gnome at all? Its quite processor intensive if all >you are doing is using it to watch TV. See the other recent thread on >starting VDR/xine at boot time using startx / replacing the session >manager and those problems with gnome screensaver won't be apparent. > >Also, there is a later version (patch) of CoreAVC for xine that I >released on the list which will apply to the hg version of xine (with >a bit of tweaking with more recent versions). The updated version will >support channels at resolutions different to 1920x1080i (there are >quite a few of them). > >HTH No, I don't "need" Gnome and am looking into alternatives per your suggestion. I hate the idea of having to run a display manager at all, but the picture looks too good to back out now. ;) On the other note, I've been trying with a current HG of xine-lib: changeset: 10295:c22d7a4b5854 tag: tip parent: 10282:6948d6d0a31e parent: 10294:dcabf02a88e6 user:Darren Salt <[EMAIL PROTECTED]> date:Tue Apr 15 01:06:51 2008 +0100 summary: Merge from 1.1. and applied the patch "xine-lib-1.2hg-coreavc.diff" with fuzz, then ./autogen.sh --disable-dxr3; make only to end up with : make[6]: *** [i386/dsputil_mmx.o] Error 1 make[6]: Leaving directory `/usr/local/src/xine-lib-1.2/contrib/ffmpeg/libavcodec' make[5]: *** [ffmpeg/libavcodec/libavcodec.a] Error 2 make[5]: Leaving directory `/usr/local/src/xine-lib-1.2/contrib' make[4]: *** [../../../contrib/ffmpeg/libavcodec/libavcodec.a] Error 2 make[4]: Leaving directory `/usr/local/src/xine-lib-1.2/src/combined/ffmpeg' make[3]: *** [all] Error 2 make[3]: Leaving directory `/usr/local/src/xine-lib-1.2/src/combined/ffmpeg' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/xine-lib-1.2/src/combined' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/xine-lib-1.2/src' make: *** [all-recursive] Error 1 So I've been trying to work my way around that to no avail. Your thoughts there would be MORE than welcome! Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput audio lip sync problems
On Tuesday 15 April 2008, Theunis Potgieter wrote: > Well it looks like I'm the only Gentoo user here that is experiencing this > problem. > > I noticed a bit more on when it occurs. I've current changed my vdr process > to run at -19 priority to see if it makes any difference. Livetv is some how > now correct. But I still experience problems with recordings where > cutting/editing occured. > > So I changed to vdr-softdevice, and I'm experience the same problem. LiveTV > is acceptable but still experience audio/video sync problems after the > replay has reached a edit/cut mark. (This is a recording that was processed) > > Any ideas? Not yet. Regarding you mentioned softdevice, can you tell us which ffmpeg svn release do you use (output of command ffplay [~ first 8 lines] gives a good hint)? At cut marks there are bigger pts jumps. Can you prepare a short recording which includes about 45 seconds before and after of your above mentioned recording for download? Link to download location should be send in private mail. Stefan Lucke ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Multiple decryption with TechniCrypt CW CAM
On 04/15/08 14:33, Arthur Konovalov wrote: > Klaus Schmidinger wrote: >> Does the log really end at that point? >> >> If there is no "Ca Pmt Reply" then the CAM doesn't reply to >> the query. > > That is, no reply in this point. > Because I got second confirmation from TechniSat Support about multiple > decryption possibility, I made small test changes in ci.c file (ci.diff). > > After that multiple decryption works! I know, this is not right > solution, but now it proved that CAM works in principle. Why it doesn't > reply to query at vdr startup, i don't know, but later it does (log.txt). > > Any ideas for an elegant solution? Can you narrow down which of these three changes is actually necessary to make it work? I would assume that state = 4; // normal operation + repliesToQuery = true; //AK } by itself should do the trick. Please revert all your changes and do just #define QUERY_REPLY_TIMEOUT 5000 // ms to wait for a reply to a query (change 2000 to 5000 in this line). If this doesn't help, try #define QUERY_WAIT_TIME 3000 // ms to wait before sending a query as well (and check whether any one of these changes helps by itself). Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Multiple decryption with TechniCrypt CW CAM
Klaus Schmidinger wrote:
> Can you narrow down which of these three changes is actually necessary
> to make it work?
I can repeat tests tomorrow, but I recall that this (it was first change):
>state = 4; // normal operation
> + repliesToQuery = true; //AK
>}
and this (next change, because first doesn't help and I saw replays to
query: Slot 1: <== Ca Pmt Reply (3) 1144 01 82 2210=82 2211=82):
dbgprotocol("\n");
}
+ state = 6; //AK
break;
was necessary in this case.
> #define QUERY_REPLY_TIMEOUT 5000 // ms to wait for a reply to a query
> (change 2000 to 5000 in this line). If this doesn't help, try
Previously tried with 6000, negative.
> #define QUERY_WAIT_TIME 3000 // ms to wait before sending a query
Will try tomorrow.
Arthur
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Defunct screensaver processes under Xine
On Tue, Apr 15, 2008 at 3:57 PM, Todd Luliak <[EMAIL PROTECTED]> wrote: > No, I don't "need" Gnome and am looking into alternatives per your > suggestion. I hate the idea of having to run a display manager at all, but > the picture looks too good to back out now. ;) > You don't need a display manager - you can run VDR with a suitable plugin at fullscreen right on top of X11. > and applied the patch "xine-lib-1.2hg-coreavc.diff" with fuzz, > then ./autogen.sh --disable-dxr3; make > only to end up with : > [cut] > So I've been trying to work my way around that to no avail. Your thoughts > there would be MORE than welcome! > Hmmm there isn't an actual compilation error in your paste, you might have to provide some more lines from above it. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Defunct screensaver processes under Xine
>...provide some more lines from above it. It looks like it bombs right about here: (hope it's enough...) in: make -C ffmpeg/libavcodec libavcodec.a ... In file included from i386/dsputil_mmx.c:30: i386/mmx.h:24:2: warning: #warning Everything in this header is deprecated, use plain asm()! New code using this header will be rejected. i386/h264dsp_mmx.c: In function `put_h264_qpel4_h_lowpass_3dnow': i386/h264dsp_mmx.c:1881: error: can't find a register in class `GENERAL_REGS' while reloading `asm' make[6]: *** [i386/dsputil_mmx.o] Error 1 make[6]: Leaving directory `/usr/local/src/xine-lib-1.2/contrib/ffmpeg/libavcodec' make[5]: *** [ffmpeg/libavcodec/libavcodec.a] Error 2 make[5]: Leaving directory `/usr/local/src/xine-lib-1.2/contrib' make[4]: *** [../../../contrib/ffmpeg/libavcodec/libavcodec.a] Error 2 make[4]: Leaving directory `/usr/local/src/xine-lib-1.2/src/combined/ffmpeg' make[3]: *** [all] Error 2 make[3]: Leaving directory `/usr/local/src/xine-lib-1.2/src/combined/ffmpeg' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/xine-lib-1.2/src/combined' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/xine-lib-1.2/src' make: *** [all-recursive] Error 1 display mangler ->gone<- Mm... better. A pair of CPUs say thanks ! Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Rotor patches
There are 2 patches for the Rotor plugin: vdr-1.5.5-rotor.diff Rotor-0.1.4-vdr1.5.10.diff They patch different areas. Are they both needed for vdr-1.6? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Rotor patches
Hy. No, just Rotor-0.1.4-vdr1.5.10.diff. Lucian. Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
