On 12.03.2012 23:01, Tony Houghton wrote:
...
I do have to restart VDR every few days
anyway, because it has a memory leak. Disabling eepg didn't fix that
IIRC, and the leak hides from valgrind.
Which version of VDR are you using?
Are you sure this is caused by the core VDR code, or could this
On Tue, 13 Mar 2012 09:55:06 +0100
Klaus Schmidinger klaus.schmidin...@tvdr.de wrote:
On 12.03.2012 23:01, Tony Houghton wrote:
...
I do have to restart VDR every few days
anyway, because it has a memory leak. Disabling eepg didn't fix that
IIRC, and the leak hides from valgrind.
Which
I've seen this a lot lately. due to tuning problems with my nova-t
500s, I've gotten frequent zero length recordings. Playing back these
either using the xine plugin, or xineliboutput, causes VDR to crash
and restart.
I'm using yavdr with only trivial modifications.
--
-Tor
On 13.03.2012 14:44, Tony Houghton wrote:
On Tue, 13 Mar 2012 09:55:06 +0100
Klaus Schmidingerklaus.schmidin...@tvdr.de wrote:
On 12.03.2012 23:01, Tony Houghton wrote:
...
I do have to restart VDR every few days
anyway, because it has a memory leak. Disabling eepg didn't fix that
IIRC, and
On Tue, Mar 13, 2012 at 8:08 AM, Torgeir Veimo torg...@netenviron.com wrote:
I've seen this a lot lately. due to tuning problems with my nova-t
500s, I've gotten frequent zero length recordings. Playing back these
either using the xine plugin, or xineliboutput, causes VDR to crash
and restart.
On Tue, 13 Mar 2012 16:11:44 +0100
Klaus Schmidinger klaus.schmidin...@tvdr.de wrote:
Can you give me an estimate of the rate at which memory is consumed?
Maybe you could have a shell running the command
top -b -d 600 | grep -w vdr
At the moment:
25956 vdr 20 0 520m 213m 5136 S
last I heard yavdr uses a bunch of patches but since I don't use it I don't
know that 100%.
Well that's always good and cheap to talk about things about any individual
heard about ... :-(
@Torgeir
Which version of yavdr do you use? Might it be possible to open a case on
vdr-portal.de in
Am 13.03.2012 17:52, schrieb Tony Houghton:
memory leak
I just met hepi, he also is a Doctor Who fan and is tuned to Astra2 as I am.
He complained about the bad status of EEPG, restarting his server every
three days or so due to a memory leak within that plugin.
As this is a 'must have' if you
On Tue, Mar 13, 2012 at 11:54 AM, Frank Neumann
v...@auktion.hostingkunde.de wrote:
last I heard yavdr uses a bunch of patches but since I don't use it I don't
know that 100%.
Well that's always good and cheap to talk about things about any individual
heard about ... :-(
There is nothing
Your claim that my comment is cheap is completely uncalled for.
Well, just needless, even you should realize that comments like this don't help
anybody.
That's what I read: Hey stupid I'm super cool and able to compile VDR by
myself, you're a nobody just able to use this bullshit yaVDR ...
I have a remote control that on pressing a single specific key it sends
two keys at once
80010051 00 KEY_3 VRC-1100
8001004c 00 KEY_5 VRC-1100
Can I use this key somehow in vdr´s remote.con (to assign a command in
the even that KEY_3 and KEY_5 are received at once)
On Tue, Mar 13, 2012 at 12:43 PM, Frank Neumann
v...@auktion.hostingkunde.de wrote:
That's what I read: Hey stupid I'm super cool and able to compile VDR by
myself, you're a nobody just able to use this bullshit yaVDR ...
Then you're a complete idiot because that is NOT what I said.
Grow up.
Got some hints at the vdr portal on how to get debug output. The
crashlog contains this stacktrace;
I presume it would be cause by one of the patches yavdr uses, since it
also happens with only the xine plugin enabled. This is yavdr 0.4,
with latest updates as of today.
Program terminated with
Hi Tor,
well honestly, I don't think it's one of the patches, it seems for me rather to
be again somehow vdr-plugin-extrecmenu.
The VDR version as of today has been tested since 2 month, to become part for
stable-vdr (first lucid, then natty) and nobody did realize this problem. But I
need to
On 14 March 2012 10:57, Frank Neumann v...@auktion.hostingkunde.de wrote:
Hi Tor,
well honestly, I don't think it's one of the patches, it seems for me rather
to be again somehow vdr-plugin-extrecmenu.
The VDR version as of today has been tested since 2 month, to become part for
This was driving me mad!
I have a NTSC TS-recording with 29.97002997 fps.
When I set cut marks via the VDR-OSD and cut the recording, this works fine.
But when I cut the same recording with the same cut marks with
`vdr --edit`, the cut points are offset by some seconds e.g. the beginning
of the
16 matches
Mail list logo
