News:

Latest versions:
Server plugin: 0.5.1
MVP dongle: 0.5.2
Raspberry Pi client: 0.5.2
Windows client: 0.5.2-1

Main Menu
Menu

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.

Show posts Menu

Messages - domaju

#1
This is to let you know that the solution also worked for me. Just a few hints which might be helpful for others:

(1) I had to remove the substring "REMOTE_" in the variable names as intruced by yotom. Otherwise I still got the error message which he was mentioning.
(2) For some reasons, in my installation, irexec was looking to /etc/lirc/lirc/lircrc instead of /etc/lirc/lircrc. I just copied the lircrc into a newly created subdirectory (I first missed that but I came across a helpful error message when I run irexec manually  :D)
(3) Last but not least: irexec has to run while using vompclient. I put "irexec -d" into the rc.local. I could imagine that the configuration should have done that for me. But in my case, it did not.

Much better than at the beginning: even the color buttons work. Also, when pressing a key constantly, there is auto repeat now.

MANY THANKS
#2
Thanks for the explanation! I think I have to give it up with my remote.

However: Before actually switching to LIRC: Another option might be to buy exactly the same hardware which you are using. Which Microsoft MCE remote control and IR receiver were you using?

Markus

#3
Hi again,

here comes the result of my efforts:

> -login as root and retry; perhaps it is a permissions problem?
This made no difference

>check the /sys directory structure (again as root)
The /sys/class/rc directory  is missing (class and other subdirectories of class exist)

>-what does ir-keytable (without arguments) report?
Exactly the same as with "-t"

>-unplug and replug your remote, and look with dmesg and/or /var/log/syslog what the kernel is reporting

Jan 25 15:49:34 raspberrypi kernel: [21664.448880] usb 1-1.2: USB disconnect, device number 4
Jan 25 15:49:38 raspberrypi kernel: [21668.271897] usb 1-1.2: new low-speed USB device number 6 using dwc_otg
Jan 25 15:49:38 raspberrypi kernel: [21668.429383] usb 1-1.2: New USB device found, idVendor=05a4, idProduct=9881
Jan 25 15:49:38 raspberrypi kernel: [21668.429422] usb 1-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jan 25 15:49:38 raspberrypi kernel: [21668.462338] input: HID 05a4:9881 as /devices/platform/bcm2708_usb/usb1/1-1/1-1.2/1-1.2:1.0/input/input4
Jan 25 15:49:38 raspberrypi kernel: [21668.475287] hid-generic 0003:05A4:9881.0005: input,hidraw0: USB HID v1.10 Keyboard [HID 05a4:9881] on usb-bcm2708_usb-1.2/input0
Jan 25 15:49:38 raspberrypi kernel: [21668.588528] input: HID 05a4:9881 as /devices/platform/bcm2708_usb/usb1/1-1/1-1.2/1-1.2:1.1/input/input5
Jan 25 15:49:38 raspberrypi kernel: [21668.589514] hid-generic 0003:05A4:9881.0006: input,hidraw1: USB HID v1.10 Mouse [HID 05a4:9881] on usb-bcm2708_usb-1.2/input1

> load the mceusb module by hand with modprobe.
Done using "sudo modprobe mceusb". I hope that was the right way of doing it.

Now, the error message when entering "ir-keytable" or "it-keytable -t" changed:
Couldn't find any node at /sys/class/rc/rc*.
Indeedd, /sys/class/rc now exists but has no entries

>what does lsusb report?

Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 007: ID 05a4:9881 Ortek Technology, Inc.
Bus 001 Device 005: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard

Just to state it again: In general, the remote is working with the vompclient, meaning that somehow, somewhere it was recognized.

Markus

#4
As a newbie, I had the following starting point:

- I installed the vompclient using the instructions http://www.loggytronic.com/vomp-pi.php
- During the (second) installation, I had the USB IR sensor of my HAMA MCE plugged in (I first missed that and the remote was not working at all)
- The hama remote worked out of the box so far.

In order to be more flexible with the key mapping, I thought following the instructions of dingo35 is a good idea. After installing ir-keytable with "apt-get install ir-keytable", I run "ir-keytable -t". This is the result:

/sys/class/rc/: No such file or directory

What do I miss?

Markus



#5
Thank you, Marten: I was able to start from scratch after removing the file as described by you (I was looking for some file of the client - that was my fault).

I won't touch the video output anymore. With HDMI everythings works great!

Markus
#6
Hello experts!

I managed to run vomp on my new raspberry. At present, for testing it, is connected as follows:
- via the HDMI output and a HDMI -> DVI cable to a TFT display
- via the Video output to an old flat screen TV with low resolution
- via the stereo jack to some cheap active loud speaker.

Using the Vompclient configuration menu I was able to show the TV image on the TFT display. However with my following two efforts I failed:
(a) I tried to switch the picture via the vomp configuration to the video output -> I was not able to see a picture on the TV (the display changed somehow for a moment -  but no picture at the end)
(b) I tried to stick with the hdmi output but to redirect the audio to the loud speaker using the VOMP configuration menu -> now both video outputs turn black after starting the vompclient

Unfortunately, I could not recover from (b) as I cannot access the vompclient configuration menu anymore for changing it.

My questions are:
- Is there a way to reset the "vompclient configuration" to its initial state so I can start checking again?
- Did I anything stupid which is the obvious reason why I failed with (a) and (b)

Amendment: I attached the present vompclient logfile, maybe it is helpful?  Sorry for the two copies, one of them is for better reading with a Windows editor - apart from that they are the same.

Best wishes
Markus
#7

.. with the standalone filters as suggested by you it works perfectly! Many thanks!!!

Markus

PS: I just ordered a Rasperry Pi for the next challenge.

#8
Vomp For Windows / No picture with Windows Client
January 12, 2014, 15:34:23
I am running the latest version of the Windows client (0.4.0-1) on my Windows 7, 64 bit. It starts well, connects to the server. I can access all channels and menus but I never managed to see live TV or a recording.

I also tried to download some decoders as I read that this has been an issue in the past.  In the video filter menu and the H264 filter menu I now find: ffdshow, LAV and Microsoft DTV-DVD  (see attached picture) - None of them is working for me.

I guess I missed something stupid?

Markus