Even with 1.3.37 I recognize often log messages like this:
Oct 15 20:53:11 linvdr user.debug vdr[3007]: recording thread started
(pid=3007, tid=62476)
Oct 15 20:53:11 linvdr user.debug vdr[3008]: TS buffer on device 1 thread
started (pid=3008, tid=63501)
Oct 15 20:53:18 linvdr user.debug vdr[3004]: buffer usage: 70% (tid=58376)
Oct 15 20:53:18 linvdr user.debug vdr[3004]: buffer usage: 60% (tid=58376)
Oct 15 20:53:18 linvdr user.debug vdr[3004]: buffer usage: 70% (tid=58376)
Oct 15 20:53:18 …
[View More]linvdr user.debug vdr[3004]: buffer usage: 60% (tid=58376)
Oct 15 20:53:18 linvdr user.debug vdr[3004]: buffer usage: 70% (tid=58376)
Oct 15 20:53:18 linvdr user.debug vdr[3004]: buffer usage: 60% (tid=58376)
Oct 15 20:53:18 linvdr user.debug vdr[3004]: buffer usage: 70% (tid=58376)
Oct 15 20:53:18 linvdr user.debug vdr[3004]: buffer usage: 60% (tid=58376)
Oct 15 20:53:18 linvdr user.debug vdr[3004]: buffer usage: 70% (tid=58376)
Oct 15 20:53:18 linvdr user.debug vdr[3004]: buffer usage: 60% (tid=58376)
Oct 15 20:53:18 linvdr user.debug vdr[3004]: buffer usage: 70% (tid=58376)
Oct 15 20:53:18 linvdr user.debug vdr[3004]: buffer usage: 60% (tid=58376)
Oct 15 20:53:18 linvdr user.debug vdr[3004]: buffer usage: 70% (tid=58376)
Oct 15 20:53:19 linvdr user.debug vdr[3004]: buffer usage: 80% (tid=58376)
Oct 15 20:53:20 linvdr user.debug vdr[3004]: buffer usage: 90% (tid=58376)
Oct 15 20:53:20 linvdr user.debug vdr[3003]: clearing transfer buffer to
avoid overflows
Oct 15 20:53:20 linvdr user.debug vdr[3004]: buffer usage: 0% (tid=58376)
It happens with different kernel versions and firmware versions,but it
started some months ago. Yesterday it happend when I recorded a movie from
Pro7 (budget card) while watching another channel from the FF-card.
It is much better since using Live AC3, but the problem still exists. Some
guys on vdrportal have the same problem. Any idea what the reason could be?
I even tried kernel 2.4 and the old driver, and it did not solve the
problem!
It seems to occur especially when the mpeg bitrate goes high (above 5
Mbit/s). DMA for the hard disc is on!
I am using gcc 2.95 and when compiling vdr, the following message appears:
tools.o: In function `cUnbufferedFile::Close(void)':
/usr/src/vdr-1.3.36/tools.c:885: warning: posix_fadvise is not implemented
and will always fail
Could there be a connection to the problem? I always thought it would only
effect that the old file cache behaviour is used.
[View Less]
Hi,
since my current living room machine is really too loud :-( I think
about separating things and building a Xine plugin client based on a
CN400 chipset (Via Epia SP8000 or Commell LV-667D/T Mini-ITX boards). I
believe MPEG4 acceleration doesn't work yet with the Unichrome Pro, or
does it (and there aren't any real HDTV broadcasts in DE yet, anyway,
but just to invest in the right technology)? I want to use DVI out to
my HDTV capable LCD TV. Any positive or negative experience to share? Dies
…
[View More]XvmC work with the CN400 as it does with the CLE266?
--
Kiss me twice. I'm schizophrenic.
[View Less]
This is probably an odd request but still!
Has anyone had a go at creating a plugin which provides a dummy DVB device?
This may sound like a pointless idea but bear with me. I've just been setting
up a slave vdr system for occasional use. With this, I'm nfs mounting
the /video directory from my main vdr system, and its main use is for
watching recordings whilst I'm upstairs on a TV with a nice interface, remote
control, etc.
At the moment, I am using streamdev so that I don't get lots of …
[View More]"Channel not
available" and "No DVB device" error messages popping up every few minutes!
It would be much simpler to create a plugin which provides a dummy DVB device
but I don't want to reinvent the wheel if someone else has already done this!
Not looked into this very deeply yet but would I need to create a fake DVB
stream to send to vdr from the plugin or would it still keep on giving me the
"Channel not available" messages?
Cheers,
Laz
[View Less]
this happens if the MENUTIMEOUT makes the OSD menu
disappear while a message is displayed.
Or if the driver/firmware is faulty and generates a timeout.
That is how I found it, but I can also reproduce it without
the driver timing out.
maybe the access to cSkinDisplay::Current is not
thread safe? What happens if it is deleted while
executing SetMessage?
vdr@mm:~/src$ diff -up skins.prev skins.c
--- skins.prev 2005-06-30 10:17:20.000000000 +0200
+++ skins.c 2005-06-30 10:17:10.000000000 …
[View More]+0200
@@ -191,7 +191,8 @@ eKeys cSkins::Message(eMessageType Type,
cStatus::MsgOsdClear();
}
else {
- cSkinDisplay::Current()->SetMessage(Type, NULL);
+ if (cSkinDisplay::Current())
+ cSkinDisplay::Current()->SetMessage(Type, NULL);
cStatus::MsgOsdStatusMessage(NULL);
}
}
Breakpoint 1, ~cSkinDisplay (this=0x9ef49c8) at skins.c:28
28 isyslog("~cSkinDisplay");
(gdb) bt
#0 ~cSkinDisplay (this=0x9ef49c8) at skins.c:28
#1 0x080ffceb in ~cSkinDisplayMenu (this=0x9ef49c8) at skinsttng.c:349
#2 0x080fb254 in ~cSkinClassicDisplayMenu (this=0x9ef49c8) at skinclassic.c:203
#3 0x080ddd2a in ~cOsdMenu (this=0x9ef75e8) at osdbase.c:97
#4 0x080d6d4c in ~cMenuMain (this=0x9ef75e8) at menu.c:124
#5 0x081235b5 in main (argc=14, argv=0xbfb8f9f4) at vdr.c:800
(gdb) c
Continuing.
cannot read /Musik//Deutsch/Reinhard_Mey/immer_weiter/12.Selig_sind_die_Verrückten.flac: No such file or directory
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 147463 (LWP 23498)]
0x080fec04 in cSkinClassicDisplayMessage::SetMessage (this=0x9ef4608, Type=mtInfo,
Text=0xbe9ff734 "cannot read /Musik//Deutsch/Reinhard_Mey/immer_weiter/12.Selig_sind_die_Verrückten.flac: No such file or directory")
at skinclassic.c:639
639 osd->DrawText(0, 0, Text, Theme.Color(clrMessageStatusFg + 2 * Type), Theme.Color(clrMessageStatusBg + 2 * Type), font, Setup.OSDWidth, 0, taCenter);
--
Wolfgang
[View Less]
VDR developer version 1.3.37 is now available at
ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.3.37.tar.bz2
A 'diff' against the previous version is available at
ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.3.36-37.diff
The changes since version 1.3.36:
- Added compiler options "-fPIC -g" to all plugins (thanks to Rolf Ahrenberg).
- Fixed initializing the day index when editing the weekday parameter of a
repeating timer (thanks to Marco Schlüßler).
- No longer removing superfluous …
[View More]hyphens in EPG data - would become too
language dependent to handle all kinds of exceptions.
- Modified switching to Dolby Digital audio in live mode, if the driver
and firmware can handle live DD without the need of a Transfer Mode (thanks
to Werner Fink). Live DD mode requires a full featured DVB card and a
LinuxDVB driver with firmware version 0x2622 or higher. Older versions will
use Transfer Mode just like before.
- Implemented handling of the "CA PMT Reply" for CAMs (thanks to Marco
Schlüßler for figuring out some obscure length bytes in the CA PMT Reply
data of AlphaCrypt CAMs).
- Some preparations for being able to record several encrypted channels from
the same transponder at the same time (or record and view different encrypted
channels), provided the CAM in use can handle this. This is work in progress
and isn't actively used, yet.
- Fixed SetProgress() in the 'skincurses' plugin in case Total is 0 (reported
by Stefan Huelswitt).
- Added a copy constructor to cString and fixed its assignment operator
(thanks to Holger Brunn).
- The new function Skins.QueueMessage() can be called from a background thread
to queue a message for display. See VDR/skins.h for details.
- The SVDRP command MESG uses the new message queueing facility, so MESG
commands may now be executed at any time, and the message will be displayed
(no more "pending message").
Have fun!
Klaus
[View Less]
Hello,
there is a new version of the pvrinput plugin available:
http://home.arcor.de/andreas.regel/files/pvrinput/vdr-pvrinput-0.0.9.tgz
I officially only support ivtv driver 0.4.0 with this version of the
plugin. Never or older versions could make problems, especially using
VBI teletext. I really recommend version 0.4.0 when using teletext
because the teletext errors (errorneous lines) seem to be gone.
Changes since 0.0.8:
- adapted setting of VBI mode to new API used in driver version 0.…
[View More]4.0.
- removed dynamic setting of VBI embedded mode as this doesn't work when
the video device is opened.
Andreas
[View Less]
This is just an example. Not really a big issue since I don't really use
vdr EPG, but strange anyway.
It's now 9:55, on Rai3
(RAI3;RAI:11766:vC23:S13.0E:27500:514:652=ita:578:0:3403:318:5200:0) the
current progtam is "Maratona di Firenze".
The channel info tells me
7:45 E' domenica papa'
8:45 Screensaver
OTOH the program guide (menu-1) tells me
7:45 E' domenica papa'
9:15 Maratona di Firenze
12:00 Tg3 -RaiSport notizie
....
Why the information in the channel info is different from the
…
[View More]information in the program guide? And why both show a program that
already ended as the current one?
As an added twist "lste" shows "Maratona di Firenze" as the first one.
The epg data has been loaded through SVDRP (using mhwepg), but that
shouldn't make a difference, should it?
The strange thing is that this only seems to apply to rai channels,
mediaset ones (canale 5, italia 1, that also get their data with mhwepg)
show the current program (maybe because these channel don't broadcast
epg data while the rai ones do?).
Bye
--
- Yo también quiero una Europa libre de Patentes de Software -
- I want a Software Patents Free Europe too! And you? -
---------------------------------------------------------------
EuropeSwPatentFree - http://EuropeSwPatentFree.hispalinux.es
[View Less]
I don't think this is currently possible but there are occasions when it would
be handy to have a 'single frame advance' button from 'pause mode' when
playing back a video.
With multi-speed mode enabled, it is possible to step forward at a speed of
about a frame every second, or so, but it would be handy to be able to pause
a video and then step forward frame-by-frame on a keypress. On some 'normal'
video recorders, pressing pause will pause, as expected, and then pressing it
again will …
[View More]step forward a frame. Pressing play is needed to start replay once
again.
Would this be easy to implement?
Cheers,
Laz
[View Less]
Hello list,
I'm wondering what should happen when assigning a cString to another where
both have pointers to the same buffer? As of version 1.3.36, we first free
it and duplicate it afterwards.
That surely isn't intended, but how to deal with this?
1) Leave them pointing to the same buffer after operator=
2) Don't free the buffer, but duplicate it (that happens in vdr<1.3.36)
Do you see good arguments for 1)? I only have one for 2), as you (I) expect
to receive a new copy of cString's …
[View More]buffer you assinged from. And this
cString's destructor will take care about freeing memory of the original
buffer.
Thanks for your comments,
Holger
(who feels ashamed to start a discussion about a one-line-patch :-)
[View Less]
Hi,
i have updated my Linux from Ubuntu hoary to breezy. After this update
noad is not setting any marks now.
I tried to recompile it, but no success so far. The version is 0.6.0.
Has anyone this problem too?
Bye
Matthias