16
Users / Re: VDR has died...
« on: June 13, 2008, 12:01:57 pm »
Cheers, I will try this later and let you know if it works for me
News:
Rule #1 - Be Patient - Rule #2 - Don't ask when, if you don't contribute - Rule #3 - You have coding skills - LinuxMCE's small brother is available: http://www.agocontrol.com
LinuxMCE sponsor
open.home.automation
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
17
Users / Re: USB-UIRT Learning: I think it's sending multiple instances of each #?
« on: June 12, 2008, 05:23:44 pm »
I don't think its a fault of too many pronto code numbers. I had this fault with channel changing on my SKY box using the UIRT. Apparantly, its a problem with the ir transmitter itself and can be fixed to send single instances of your channel change codes by using a separate ir transmitter plugged into the UIRT's mini jack port.
There are previous threads on this forum relating to this. Have a scan for them.
There are previous threads on this forum relating to this. Have a scan for them.
18
Users / Re: VDR has died...
« on: June 12, 2008, 04:06:22 pm »
The only plugin I have installed is lcdproc for vdr (with your instructions niteman 
)
Did you just remove the plugin to get VDR woring again? Have you seen this problem after installing lcdproc plugin alone?
) Did you just remove the plugin to get VDR woring again? Have you seen this problem after installing lcdproc plugin alone?
19
Users / Re: VDR has died...
« on: June 11, 2008, 09:52:46 pm »
I did not get anything mentioning plutovdr in top.
However, if I enter
into konsole then I get this output:
has the port for vdr changed? If so how do I change it back? Also is there something wrong with xine config file?
However, if I enter
Code: [Select]
sudo plutovdrinto konsole then I get this output:
Code: [Select]
plutovdr 1.0.0~rc2-cvs-LMCE0710-8 (build with xine-lib 1.1.10, using xine-lib 1.1.7)
VDR server not given, searching ...
---------------------------------------------------------------
WARNING: MRL not given and server not found from local network.
Trying to connect to default port on local host.
---------------------------------------------------------------
[9460] [vdr-fe] Error: The name org.gnome.ScreenSaver was not provided by any .service files
[9460] [vdr-fe] (ERROR (gnome_screensaver.c,113): Resource temporarily unavailable)
[9460] [vdr-fe] Detected 2 CPUs
[9460] [vdr-fe] Multithreaded video decoding is not supported in xine-lib 1.1.7
configfile: error - tried to update non-num type 0 (key video.processing.ffmpeg_thread_count, value 2)
Press Esc to exit
params.c:OpenConfFile() - Unable to open configuration file "/home/linuxmce/.smb/smb.conf.append":
No such file or directory
added interface ip=192.168.0.4 bcast=192.168.0.255 nmask=255.255.255.0
Using netbios name DCEROUTER.
Using workgroup WORKGROUP.
[9460] [vdr-fe] fe_xine_open: xine_open("xvdr://127.0.0.1#nocache;demux:mpeg_block") failed
Error opening xvdr://127.0.0.1
[9460] [vdr-fe] Error: The name org.gnome.ScreenSaver was not provided by any .service files
[9460] [vdr-fe] (ERROR (gnome_screensaver.c,113): Resource temporarily unavailable)
linuxmce@dcerouter:~$ has the port for vdr changed? If so how do I change it back? Also is there something wrong with xine config file?
21
Users / Re: VDR has died...
« on: June 09, 2008, 11:24:49 pm »
Yes, I stopped VDR, and restarted after clearing the timers, then tried rebooting.
VDR must be doing something because I have a VFD display with the VDR-LCDProc plugin, and it is displaying up to date channel and EPG data.
I have tried using some of the channels.conf templates already in LMCE, just to check that its not my dvb-utils generated channels.conf causing trouble, but again I get channel data displayed on the VFD, but only a frozen flickr screen on my TV.
VDR must be doing something because I have a VFD display with the VDR-LCDProc plugin, and it is displaying up to date channel and EPG data.
I have tried using some of the channels.conf templates already in LMCE, just to check that its not my dvb-utils generated channels.conf causing trouble, but again I get channel data displayed on the VFD, but only a frozen flickr screen on my TV.
22
Users / Re: VDR has died...
« on: June 09, 2008, 05:18:55 pm »
Thanks for the replies all,
I cleared the timers with
and
Didn't return any errors, and included the lines
so my cards are there ok
Also got a tv stream with kaffine successfully.
Still I only get a frozen flickr screen when I press tv in the orbiter.
How do I get a picture through VDR in KDE (i.e. outside of LMCE)? I can test if VDR works. Or is there anyway to reset VDR? re-build from source?
Does LMCE have it's own timers file as well as VDR's?
I cleared the timers with
Code: [Select]
echo "" >/var/lib/vdr/timers.confand
Code: [Select]
tail /var/log/messageDidn't return any errors, and included the lines
Code: [Select]
Jun 9 15:59:03 dcerouter kernel: [ 750.129445] DVB: registering new adapter (cx88[0])
Jun 9 15:59:03 dcerouter kernel: [ 750.129450] DVB: registering frontend 0 (Conexant CX24116/CX24118)...so my cards are there ok
Also got a tv stream with kaffine successfully.
Still I only get a frozen flickr screen when I press tv in the orbiter.
How do I get a picture through VDR in KDE (i.e. outside of LMCE)? I can test if VDR works. Or is there anyway to reset VDR? re-build from source?
Does LMCE have it's own timers file as well as VDR's?
23
Users / VDR has died...
« on: June 07, 2008, 10:14:17 am »
I managed to get my final install of lmce Up how i wanted it, got a channels.conf for my dvb-t and s cards and told vdr to use th dvb-t conf for now in lmce admin to see how it went.
I chose tv from th lmce menu and got a picture.
However, the channels list was incomplete and not in the order of the channels.conf. No epg either!
Anyway, i tried pausing and rewinding live tv (which did work after a few seconds) and then turned my media centre off for the day.
Next day when i came back to it, booted up, clicked tv and the screen froze. So i entered kde and ran vdr from terminal. It failed saying it could not read timers. So i cleared the line in the vdr timers conf that appeared to relate to the program i paused the day before. Vdr then restarted in konsole without errors.
Returned to lmce, selected tv, and the screen still freezes.
Tried rebooting, and then cleared timers from vdradmin web interface. But still tv in lmce wont work.
The only thing i can think is that something is messed up with the recording timer in lmce. So firstly, how can i clear the recording timers in lmce?
I can't rule out that it may be a xine problem either, so secondly, how do i run vdr to display on xine in kde or from the konsole?
Many thanks in advance
I chose tv from th lmce menu and got a picture.
However, the channels list was incomplete and not in the order of the channels.conf. No epg either!
Anyway, i tried pausing and rewinding live tv (which did work after a few seconds) and then turned my media centre off for the day.
Next day when i came back to it, booted up, clicked tv and the screen froze. So i entered kde and ran vdr from terminal. It failed saying it could not read timers. So i cleared the line in the vdr timers conf that appeared to relate to the program i paused the day before. Vdr then restarted in konsole without errors.
Returned to lmce, selected tv, and the screen still freezes.
Tried rebooting, and then cleared timers from vdradmin web interface. But still tv in lmce wont work.
The only thing i can think is that something is messed up with the recording timer in lmce. So firstly, how can i clear the recording timers in lmce?
I can't rule out that it may be a xine problem either, so secondly, how do i run vdr to display on xine in kde or from the konsole?
Many thanks in advance
24
Developers / Re: Mame Installation Instructions
« on: June 05, 2008, 02:08:05 pm »
Thanks,
I added the option indicated in the sdlmame source readme.
I have added some of the roms from here http://mamedev.org/roms/ to my /home/public/data/games directory but their names dont appear in the LMCE games explorer. I have images for the games but the name on the right hand side reads "no matching rom"
Is this normal, or did my spidering not find a rom name list (it must have found the images!)
Apart from that, its all working pretty good on amd64! The games play well!
I added the option indicated in the sdlmame source readme.
I have added some of the roms from here http://mamedev.org/roms/ to my /home/public/data/games directory but their names dont appear in the LMCE games explorer. I have images for the games but the name on the right hand side reads "no matching rom"
Is this normal, or did my spidering not find a rom name list (it must have found the images!)
Apart from that, its all working pretty good on amd64! The games play well!
25
Users / Re: Random freezes. where do I start?
« on: May 31, 2008, 11:55:21 am »
A few users have had this problem with the asus M2N-SLI Deluxe motherboard and solved it with a BIOS update. Check the forum posts on freezes
26
Users / Re: VDR Plugins How-to?
« on: May 30, 2008, 07:01:17 pm »
Cheers nite_man, worked like a charm.
Adding the -fPIC option to the makefile results in an error as the deb adds a patch to change this (and fails if it has already changed).
I also removed the lcdproc dependancy from /debian/control before running dpkg... (don't know why it can't detect my lcd-proc!)
Anyway, thanks again
Adding the -fPIC option to the makefile results in an error as the deb adds a patch to change this (and fails if it has already changed).
I also removed the lcdproc dependancy from /debian/control before running dpkg... (don't know why it can't detect my lcd-proc!)
Anyway, thanks again
27
Developers / Re: Mame Installation Instructions
« on: May 30, 2008, 06:17:47 pm »
OK, I have got as far as making the Mame_Plugin without any problems. But how and what exactly do I need to change in the mame make file for x64??
Cheers
Cheers
28
Users / Re: Hauppauge Nova-HD-S2?
« on: May 30, 2008, 02:35:24 pm »
Well I have got the nova-hd-s2 working in vdr with the kewl driver, but only the S1 function.
I didn't try the alternate multi-pronto, but theres no need to get the S2 working yet as VDR 1.6.0 doesn't support it.
Anyways, I'll add a wiki page as soon as I get chance
I didn't try the alternate multi-pronto, but theres no need to get the S2 working yet as VDR 1.6.0 doesn't support it.
Anyways, I'll add a wiki page as soon as I get chance
29
Users / Re: VDR Plugins How-to?
« on: May 29, 2008, 11:44:40 pm »
Cheers,
I got as far as building the package, but it failed on a dependency - which I guess is lcdproc (even though I have lcdproc installed from source)
I guess it is lcdproc as I downloaded a pre-built lcdproc-plugin.deb from ubuntu and that too required installation of lcdproc. After installing the .deb successfully (and adding another lcdproc) I restarted vdr and had the message:
restarted vdr, and get the same message - lcdproc plugin left out!
Any ideas?
I got as far as building the package, but it failed on a dependency - which I guess is lcdproc (even though I have lcdproc installed from source)
I guess it is lcdproc as I downloaded a pre-built lcdproc-plugin.deb from ubuntu and that too required installation of lcdproc. After installing the .deb successfully (and adding another lcdproc) I restarted vdr and had the message:
Quote
WARNING: The following plugins have been left out due to possible binary incompatibility: lcdproc.I uninstalled the plugin and tried installing it following these instructions:
Quote
Download and untar somewhere appropriate version of VDR sources (1.4.7 in case of LinuxMCE)
Download the latest version of vdr-lcdproc plug-in
Untar it into <your_vdr_src_dir>/PLUGINS/src and make a symlink - ln -s lcdproc-0.0.10-jw2 lcdproc
Build plug-in: make plugins. Note, for AMD64 you should add option -fPIC to the CXXFLAGS into lcdproc Makefile. Otherwise you’ll get this error:
/usr/bin/ld: lcdproc.o: relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC
lcdproc.o: could not read symbols: Bad value
Copy <your_vdr_src_dir>/PLUGINS/lib/libvdr-lcdproc.so.1.4.5 to the /usr/lib/vdr/plugins
Add a new config file plugin.lcdproc.conf into /etc/vdr/plugins and put there following options:
-h 127.0.0.1
-p 13666
restarted vdr, and get the same message - lcdproc plugin left out!
Any ideas?