Hello,
is there something "special" to do in order to get lcdproc working on my
G15 lcd keyboard ?
Or maybe another LCD plugin ?
I got a really suspicious Illegal instruction when compiling with
gcc-4.3alpha of today so I tried with gcc-4.2.2 with same result.
With gcc-4.2.2 I used : -g -march=k8 -pipe
And with 4.3alpha : -g -O3 -march=core2 -DPIC -pipe -Wall
If I start vdr with -Plcdproc I get on the LCD :
"Welcome to V D R
Video Disk Recorder
Version : 1.5.12"
Then :
" Mute
`black …
[View More]bar"
" Some epg info"
And then vdr quit with :
"Illegal instruction"
OK, then some gdb :
gdb ./vdr
GNU gdb 6.7.1
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu"...
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run -u greg -c /etc/vdr -l 3 -P'xine -r' -Plcdproc
Starting program: /usr/src/vdr-1.5.12/vdr -u greg -c /etc/vdr -l 3 -P'xine -r' -Plcdproc
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff1c1fd000
-------------------------
MakePrimaryDevice: 1
=========================
SetVideoFormat: 1
SetVolumeDevice: 255
frame: (0, 0)-(-1, -1), zoom: (1.00, 1.00)
SetVideoWindow: 0, 0, 720, 576, 720, 576
SetVolumeDevice: 255
SetAudioChannelDevice: 0
frame: (0, 0)-(-1, -1), zoom: (1.00, 1.00)
SetPlayMode: 1
[New LWP 27864]
[New LWP 27871]
Program received signal SIGILL, Illegal instruction.
[Switching to LWP 27871]
0x00002ad88fc4c0e3 in cLcd::GetTimeDateStat (this=0x82c840, string=0x44006b70 "", OutStateData=0x44006760)
at lcd.c:586
586 if ( offset || !( ShowStates && ((t%LcdSetup.FullCycle) >= LcdSetup.TimeCycle) )) {
Current language: auto; currently c++
(gdb) bt
#0 0x00002ad88fc4c0e3 in cLcd::GetTimeDateStat (this=0x82c840, string=0x44006b70 "", OutStateData=0x44006760)
at lcd.c:586
#1 0x00002ad88fc4e4d1 in cLcd::Action (this=0x82c840) at lcd.c:846
#2 0x00000000004e9ab4 in cThread::StartThread (Thread=0x82c840) at thread.c:244
#3 0x0000003e99006067 in ?? () from /lib/libpthread.so.0
#4 0x0000003e984c5c7d in clone () from /lib/libc.so.6
Some difference with gcc-3.4.6 :
Program received signal SIGSEGV, Segmentation fault.
[Switching to LWP 9495]
cLcd::GetTimeDateStat (this=0x863840,
string=0x44006c90 "success\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\n"..., OutStateData=0x44006c70) at lcd.c:588
588 snprintf(string,wid+1,"<%s %02d.%02d %02d:%02d:%02d>",
Current language: auto; currently c++
(gdb) bt
#0 cLcd::GetTimeDateStat (this=0x863840,
string=0x44006c90 "success\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\nsuccess\n"..., OutStateData=0x44006c70) at lcd.c:588
#1 0x00002abce618f3af in cLcd::Action (this=0x863840) at lcd.c:846
#2 0x00000000005052a1 in cThread::StartThread (Thread=0x863840) at thread.c:244
#3 0x0000003e99006067 in ?? () from /lib/libpthread.so.0
#4 0x0000003e984c5c7d in clone () from /lib/libc.so.6
VDR 1.5.12 source :
ftp.cadsoft.de:/pub/people/kls/vdr/Developer/vdr-1.5.12.tar.bz2
graphlcd plugin : http://home.pages.at/linux/dvb.html
So it seems clear the plugin don't care about memory usage...
Did someone know how to fix it ?
--
Grégoire FAVRE http://gregoire.favre.googlepages.comhttp://www.gnupg.orghttp://picasaweb.google.com/Gregoire.Favre
[View Less]
Hi,
I am novice in VDR programming. I tried writing a plugin for getting
EPG data from the Internet and using it. Now a prototype is up and
running.
To debug, extend and maintain the plugin I could use some more
information. I wish I could get my hands on some documentation on the
VDR classes (what they do...) and EPG ( for eg. how/when to set
eventID, TableID ).
I have with me doxygen generated documentation. But I still do not
have something on par with cEvent::FixEpgBugs() kind of …
[View More]comments.
Any help would be welcomed.
Thanks in advance,
Sundararaj
[View Less]
Hi,
here's a new plugin especially for VDRs not running 24/7. It allows you
to execute tasks in the context of VDR and trigger wakeups for this.
Features:
- optional wakeup of VDR to execute a job (no dummy timers needed anymore)
- prevent a shutdown while a job is still executed
- optional announcements of job start/finish via OSD
- start external jobs via SVDRP in the context of VDR
- display current and previous job output
Requirements:
- vdr >= 1.5.1 or
- vdr-1.4.5 with the backport …
[View More]of the new shutdown handler
(http://www.udo-richter.de/vdr/patches.html#shutdown)
Project homepage and screenshots:
http://winni.vdr-developer.org/scheduler
Download:
http://winni.vdr-developer.org/scheduler/downloads/vdr-scheduler-0.1.0.tgz
Have fun!
Christian
[View Less]
Hello,
lign 105 of dvbsubtitle.c is :
bool Decode8BppCodeString(const uchar *Data, int &Index, int&y, int y);
shouldn't that be :
bool Decode8BppCodeString(const uchar *Data, int &Index, int&x, int y);
Or better all 3 advanced declarations ligns :
bool Decode2BppCodeString(const uchar *, int &, int&, int);
bool Decode4BppCodeString(const uchar *, int &, int&, int);
bool Decode8BppCodeString(const uchar *, int &, int&, int);
At least with gcc 4.3alpha …
[View More]of today I can't compil vdr-1.5.1x with this.
--
Grégoire FAVRE http://gregoire.favre.googlepages.comhttp://www.gnupg.orghttp://picasaweb.google.com/Gregoire.Favre
[View Less]
Greets. If you have more then one dvb device and each is plugged into
a diseqc switch, how would you define a diseqc.conf for each of them?
I've checked VDR's documentation and saw no reference to this unless
I've somehow missed the info. If VDR doesn't currently support
different diseqc.conf's per each dvb adapter, I guess this could be a
formal request to add support for this. Maybe just doing something
like this:
# Format: device satellite slof polarization lof command
where device is …
[View More]used for this purpose? Not sure the best way to
identify the devices since they can be pci, pci-e, usb, etc.
Any thoughts?
Thanks fellas!
[View Less]
Hello,
I know 720p, 1080p/i resolution are getting common which is fine.
>From the next feature thread I see there is some interest in H.264
channels :-)
I don't like the hardware decoder solution : Intel core duo 2 are really
cheap now and don't use that much power...
I built my VDR PC (in fact my only PC...) with such a solution (and a
fanless nvidia gfx card) and I find it perfectly suited for HD.
The most important part from my point of view was the case :
http://techgage.com/article/…
[View More]antec_p182_performance_mid-tower/
So that I don't have noise from the PC...
I think almost any PC with core duo 2 CPU are enough for perfect H.264
decoding...
I don't really like closed hardware solution neither...
--
Grégoire FAVRE http://gregoire.favre.googlepages.comhttp://www.gnupg.orghttp://picasaweb.google.com/Gregoire.Favre
[View Less]
> Besides, I don't think
> that many users are still using some ancient pc with a slow cpu
> like Klaus has.
I've been using a IBM Netstation, 266mhz, 128 mb ram with a FF dvb-s and a aver 771 dvb-t. It worked FLAWLESSY ! I could record 2 streams and play a third one, the OSD was slow but recording were ok. (At the time I used ~1 Ghz AMD and Intel chip and chipsets that were not able to handle the load !!!!)
Now it has hardware and software problems... I will solve as soon as I …
[View More]have time...
Aver 771 doesn't work anymore, don't know why, it doesn't lock any signal. Also in a Windows PC. I just bought an USB stick, I'm looking for a PCI-USB2 adapter.
I upgraded the ram to 256 and then upgraded from suse 9 to 10.3.... that is a bloated S.o. that takes forever to do anything....
Francesco
[View Less]
Hi,
I'm having heavy artifacts with the new vdr-1.5.11 in finnish DVB
channels. The picture freezes now very often compared to previous VDR
version (I reported about the same rare problem in vdr-1.5.10) and it
seems that the problem is the new SUBTITLE_PACKS size. I reverted it
back to 2048 and haven't noticed the problem after that.
During the freeze VDR's transfer buffer gets full and VDR is clearing
transfer buffer to avoid overflows. This happens only on channels with
DVB subtitling.…
[View More]
I'm using 4MB FF card as a primary device, if that makes any difference.
BR,
--
rofa
[View Less]