Controlling xine with lirc
I installed an HVR-1600 MCE-Kit as a TV capture card. Capture card works fine.
The kit comes with an MCE USB remote control and transceiver. The exact model is the black one (1069/335) as seen in the MythTV MCE_Remote page. This remote is considered a second generation USB device. I'm running 13.0 32-bit with a 2.6.30.5 kernel. As the current 0.8.5 stable version of lirc does not support the 2.6.30 kernel series, I built lirc cvs (0.8.6pre2). I created an rc.d script to automatically start the lirc daemon when booting. Using the irw command I confirmed each button is working. I found an lircd.conf.mceusb2 for the remote. As far as I can tell the remote works as expected. I'm running irexec as a daemon. Now I'm trying to control xine with lirc. I created an ~/.lircrc file. Here is a snippet: Code:
##########LAUNCHING BUTTONS####################### For testing and comparison purposes I have XBMC 9.04 installed in separate partitions. The remote control nicely manages the XBMC interface. I haven't yet figured out how that's done as I haven't found an lircrc config file anywhere. I appreciate any help. |
Hello Woodsman
I had the same problem with xine in slackware-13.0 i removed xine-ui with removepkg then i downloaded xine-ui-0.99.5.tar.gz from http://www.xine-project.org/releases and compiled it like this ./configure --enable-lirc then i did a make and a make install. after it was compiled my .lircrc file that was already made in my home directory worked right off the bat. I would have to guess that the slackware package of xine-ui that comes with slackware-13.0 isn't built with lirc enabled. But i cant confirm this considering im still in the very basic stages of learning linux. Here is the format of my lircrc file Code:
# fullscreen toggle then i added in my own values. Hope this helps in anyway. |
Quote:
I modified the stock build script. I rebuilt the package and updated the package. No change. :) I'll presume then that lirc is enabled by default. I ran xine with the --keymap option. That created an lircrc shell with a bunch of xxxxx options. I presume I have to manually replace the xxxxx with an actual button name that I derive from irw. I don't know the proper remote name to use. If I understand correctly I don't have to insert one because the default is all (*). I modified the lircrc file to no avail. :) Despite the moment of hope you provided, I still have no response from xine using the remote control. I must be missing something that is not obvious to me. :scratch: |
i ran irrecord for my lircd.conf and named my own keys.
as you can see from the above, my home key is KEY_HOME and so on. but i think as long as irw reports back the same keys pressed from your remote thats in your lircd.conf i think that portion of it is correct. can you post your lircd.conf for me too look at ? The reason i still think its xine-ui is because i didnt even touch my lircrc file at all once i removed xine-ui. literally right after xine-ui compiled form the link i provided everything worked. so that still leaves me to believe that the slackware xine-ui package is still at fault. If it was enabled by default then im curious why the exact lircrc file i have working now wont work with it. |
Quote:
Do you load irexec as a daemon? Quote:
Code:
# |
Moved to /Software as requested.
|
Try doing this
for remote = mceusb instead of xxxxxx and here you show . Code:
begin your lircd.conf shows Stop not stop so try changing it to this Code:
|
Sorry i missed your other question.
Yes i use irexec as a daemon also to start xine. i start it with screen irexec & then i close the window, if i dont use screen it wont work once the terminal window closes. |
Modifying your original script (case does matter):
Code:
##########LAUNCHING BUTTONS####################### Xine doesn't look for this file anywhere else. |
Quote:
without the period infront of it of course. it should work for every user account at that point. |
Quote:
Quote:
I start the lirc daemon when I boot. I created an rc.d script to easily start/stop/restart. In that script I also start/stop irexec. The irw command responds perfectly to every button I press. The fact that I can start xine with the remote control lets me know I have something correct. But nothing gets passed to xine. Is there a specific pecking order to all of this? I'm convinced I am missing something basic. |
try running this real quick,
irrecord bla.txt does it startup and ask you to press keys or exit? if its asking you to hit a bunch of keys on your remote then you can just not hit anything and it will quit. I might have an idea on whats going on. Let me know if it works for you as a user not as su. sorry this might be something not even related, but i use a usb transceiver myself. is yours usb also ? |
Quote:
Code:
irrecord - application for recording IR-codes for usage with lirc Perhaps the package was built incorrectly? Quote:
|
start lircd with
lircd /dev/lirc/0 i made a package of lirc with makepkg instead of the slackbuilds script. chmod 666 /dev/lirc/0 then try your remote again |
My rc.d script:
/usr/sbin/lircd -d /dev/lirc/0 I have a symlink at /dev/lirc0 pointing to /dev/lirc/0. Permissions are already 666, root:root. |
All times are GMT -5. The time now is 12:11 PM. |