HDMI CEC and XBMC


96 posts   Page 4 of 4   1, 2, 3, 4
by dom » Fri Aug 17, 2012 5:43 pm
@welshbob
firmware pushed. rpi-update to get it.
Moderator
Moderator
Posts: 3861
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge
by Penetratore » Fri Aug 17, 2012 10:15 pm
dom wrote:@welshbob
firmware pushed. rpi-update to get it.


1. by firmware update- can i make it this way https://github.com/Hexxeh/rpi-update/
"wget http://goo.gl/1BOfJ -O /usr/bin/rpi-update && chmod +x /usr/bin/rpi-update"

and the new soft will have this config line in it?

2. CEC setting in the XBMC (open elec) has not effect on the statup behaviour

3. in the XBain rev 0.6 the CEC maped pilot keys is diffrent then in RaspBMC or open elec.THe "back" function is maped on the TV remote as key "Back" and not key "EXIT" like in the rest XBMC like distribution.
is there a easy way to put in the Openelece build a Xbain CEC settings?
Posts: 31
Joined: Thu Jul 26, 2012 8:33 pm
by eriksson25 » Fri Aug 24, 2012 9:49 pm
No longer using http to talk to XBMC (using UDP instead) meaning no need to remember to enable the built-in web server) and this also external key mapping making it easier to tailor.


Hi man, What do you mean by external key mapping?

I have a sony Bravia and everything is working perfect exept that I want to be able to pres "C" to do some settings and stuf. How could I mapp this to a unused button?

/KG
Posts: 1
Joined: Fri Aug 24, 2012 9:46 pm
by skabning » Fri Sep 07, 2012 8:50 am
I have an LG TV, and the remote works great with HDMI-CEC. However, none of the buttons register as the Context Menu, and I'm pretty sure that the button setup could be improved a bit if one were to have a rummage around. Does anyone have any idea if/how that's possible? I really like the idea of not having to have a second remote lying around!
Posts: 1
Joined: Fri Sep 07, 2012 8:49 am
by Sappher » Sun Sep 09, 2012 9:38 pm
I have Rasbian "wheezy" distro and XBMC installed with these instructions:

viewtopic.php?f=66&t=12455&p=133213&hilit=xbmc#p133213

I've been using XBMC Remote fow now, but it's pretty buggy. I have a CEC compatible TV (Philips, they call it EasyLink). I've enabled it from my TV.

Can anyone give my basic help on how to control XBMC with my TV remote? I'm a Linux noob (learning pretty fast though ;)), se be gentle.. What programs do I need? How do I get them? How do I set it up? Or is it even possible to use in Rasbian, do I need to install Rasbmc?
Posts: 4
Joined: Fri Aug 31, 2012 5:23 pm
by t-a-s » Fri Sep 14, 2012 7:30 pm
@Sappher If it's not working with your current set up your probably running a version from before libCEC was ported.

The latest builds of OpenELEC and Raspbmc both come with libCEC set up for the Pi and it works "out of the box", so an easy option to get CEC going is to install one of those. Alternatively to get it working on your current setup you could compile a new version of xbmc for RPi with libCEC, this will be the most difficult of the options but definitely worth learning.

The easiest option (to keep your current set up) is to use rpi-cecd (a hack that was written before libCEC was ported), this should just be a case of copying the binary to the Pi and running it.
Posts: 23
Joined: Sat Jun 09, 2012 5:36 pm
by Sappher » Fri Sep 14, 2012 9:30 pm
Thanks for the reply, I'll look into those over the weekend.
Posts: 4
Joined: Fri Aug 31, 2012 5:23 pm
by castalla » Sat Oct 06, 2012 4:11 am
I'm using Xbian 0.8. CEC works up to a point on my Samsung - cursor and Enter.

Does anyone know which button maps to Home?
Posts: 465
Joined: Thu Jul 19, 2012 3:46 pm
by numanoids » Sun Oct 07, 2012 11:39 pm
I've been playing with Raspbmc and Xbian's latest builds. Xbian is much snappier but the CEC mapping is missing the context menu which works fine on Raspbmc using my Samsung's Return button.

I've been looking through the logs and on Raspbmc it correctly identifies the button in the logs:

Code: Select all
20:04:41 T:1194325056   DEBUG: CecLogMessage - key pressed: return (Samsung) (91)


But on XBian it shows as an unknown button.

Is this somehting that can be manually configured and mapped or is it with the implementation of libcec?

THanks
Posts: 27
Joined: Wed Sep 26, 2012 11:14 am
by mcgyver83 » Fri Oct 12, 2012 9:18 am
BigEndian wrote:Thank you for the great work, it works like a charm with Raspbian and XBMC compiled from source. Now I am looking for a way to execute custom commands by pressing unused buttons. For example the "RED" Button for executing XBMC.

Background: I want to use Raspbian for a few more things than just XBMC so it would be nice to start it on demand via pressing a button on the remote control.

Is there any way to achieve that?


I'm also interested in this use...someone has suggestions?
Posts: 295
Joined: Fri Oct 05, 2012 11:49 am
by grabowski » Sat Nov 10, 2012 9:10 pm
rpi2000 wrote:Okay, one step further:

If I use another cable AND disconnect all other devices from HDMI ports (doesn't matter whether they are turned on or not) the TV finds a CEC device at least (called: "player").

But now: if I want to connect to this Anynet+ device it says. "device not connected. check and try again" Any ideas?


My problem is that CEC will work ONLY if I disconnect every other device from my Samsung TV. Any idea why my TV doesn't find XBMC when my satellite decoder is also connected to it?
Posts: 3
Joined: Fri Sep 28, 2012 6:08 pm
by castalla » Sat Nov 10, 2012 9:33 pm
As far as I've experienced cec - it's not worth the effort. I just use the flirc dongle - super easy to set up - and very flexible. Works a treat:

http://flirc.tv
Posts: 465
Joined: Thu Jul 19, 2012 3:46 pm
by grabowski » Sun Nov 11, 2012 9:14 am
castalla wrote:As far as I've experienced cec - it's not worth the effort. I just use the flirc dongle - super easy to set up - and very flexible. Works a treat:

http://flirc.tv


I must disagree here. Flirc consumes 1 USB port and it will work only if you have direct line of sight with your RPi. My RPi is in the attic and the biggest advantage of CEC is that I am able to control it through the TV's remote.

p.s.: my TV sits on a wall mount and the HDMI cable connecting it with the RPi is in the wall, so it's quite elegant :)
Posts: 3
Joined: Fri Sep 28, 2012 6:08 pm
by gaffer206 » Thu Dec 20, 2012 12:17 am
Sorry if this is answered elsewhere but I can't find it. I have a brand new pi with the latest raspbmc with libCEC 2.0.4. Its connected to a Yamaha AVR and a non-CEC monitor. I want to use the AVR remote to control XBMC. I think I need to change the connected HDMI device from 0 to 5 but I can't find anywhere in the XMBC menus or in /.xbmc/userdata/peripheral_data/rpi_2708_1001.xml to do it.

Is there any documentation for the contents of this file? I tried changing

<setting id="connected_device" value="255" />

But it got set back after restarting xbmc.

I can see my remote buttons being pressed in the log, but XBMC ignores them.

thanks

Julian
Posts: 1
Joined: Thu Dec 20, 2012 12:09 am
by migube » Fri Dec 28, 2012 10:07 pm
gaffer206 wrote:Sorry if this is answered elsewhere but I can't find it. I have a brand new pi with the latest raspbmc with libCEC 2.0.4. Its connected to a Yamaha AVR and a non-CEC monitor. I want to use the AVR remote to control XBMC. I think I need to change the connected HDMI device from 0 to 5 but I can't find anywhere in the XMBC menus or in /.xbmc/userdata/peripheral_data/rpi_2708_1001.xml to do it.

Is there any documentation for the contents of this file? I tried changing

<setting id="connected_device" value="255" />

But it got set back after restarting xbmc.

I can see my remote buttons being pressed in the log, but XBMC ignores them.

thanks

Julian


I have a philips 8440 and a direct connection works with CEC on the TV remote.
Connecting to the Yamaha RXV-667, neither the TV remote or Yamaha remote seems to send any CEC commands, though in debugging I see some initial messages exchanged with the AVR. (but just for audio?)

TV:
Code: Select all
21:55:06 T:2960450576   DEBUG: CecLogMessage - >> 0f:86:50:00
21:55:06 T:2960450576   DEBUG: CecLogMessage - >> TV (0) -> Broadcast (F): set stream path (86)
21:55:06 T:2960450576   DEBUG: CecLogMessage - >> TV (0) sets stream path to physical address 5000
21:55:06 T:2960450576   DEBUG: CecLogMessage - making Recorder 1 (1) the active source
21:55:06 T:2960450576   DEBUG: CecLogMessage - >> source activated: Recorder 1 (1)
21:55:06 T:2960450576   DEBUG: CecLogMessage - sending active source message for 'Recorder 1'
21:55:06 T:2960450576   DEBUG: CecLogMessage - << 10:04
21:55:06 T:2960450576   DEBUG: CecLogMessage - << Recorder 1 (1) -> broadcast (F): active source (5000)
21:55:06 T:2960450576   DEBUG: CecLogMessage - << 1f:82:50:00
21:55:06 T:2960450576   DEBUG: CecLogMessage - << Recorder 1 (1) -> TV (0): menu state 'activated'
21:55:06 T:2960450576   DEBUG: CecLogMessage - << 10:8e:00
21:55:06 T:2960450576   DEBUG: CecLogMessage - >> 01:8c
21:55:07 T:2960450576   DEBUG: CecLogMessage - >> TV (0) -> Recorder 1 (1): give device vendor id (8C)
21:55:07 T:2960450576   DEBUG: CecLogMessage - << Recorder 1 (1) -> TV (0): vendor id Philips (903e)
21:55:07 T:2960450576   DEBUG: CecLogMessage - << Recorder 1 (1) -> TV (0): vendor id feature abort
21:55:07 T:2960450576   DEBUG: CecLogMessage - << transmitting abort message
21:55:07 T:2960450576   DEBUG: CecLogMessage - << 10:00:8c:00
21:55:07 T:2960450576   DEBUG: CecLogMessage - >> 01:00:8e:00
21:55:07 T:2960450576   DEBUG: CecLogMessage - >> TV (0) -> Recorder 1 (1): feature abort ( 0)
21:55:12 T:2960450576   DEBUG: CecLogMessage - >> 01:44:04
21:55:12 T:2960450576   DEBUG: CecLogMessage - >> TV (0) -> Recorder 1 (1): user control pressed (44)
21:55:12 T:2960450576   DEBUG: CecLogMessage - key pressed: right (4)
21:55:12 T:2960450576   DEBUG: PushCecKeypress - received key a8 duration 0
21:55:12 T:2960450576   DEBUG: CecLogMessage - >> 01:8b:04


AVR:
Code: Select all
21:57:14 T:2960450576   DEBUG: CecLogMessage - >> 5f:84:00:00:05
21:57:14 T:2960450576   DEBUG: CecLogMessage - >> Audio (5) -> Broadcast (F): report physical address (84)
21:57:15 T:2960450576   DEBUG: CecLogMessage - >> 0f:87:00:90:3e
21:57:15 T:2960450576   DEBUG: CecLogMessage - >> TV (0) -> Broadcast (F): device vendor id (87)
21:57:15 T:2960450576   DEBUG: CecLogMessage - >> 5f:80:00:00:60:00
21:57:15 T:2960450576   DEBUG: CecLogMessage - >> Audio (5) -> Broadcast (F): routing change (80)
21:57:15 T:2960450576   DEBUG: CecLogMessage - >> 5f:87:00:a0:de
21:57:15 T:2960450576   DEBUG: CecLogMessage - >> Audio (5) -> Broadcast (F): device vendor id (87)
21:57:17 T:2960450576   DEBUG: CecLogMessage - >> 5f:72:01
21:57:17 T:2960450576   DEBUG: CecLogMessage - >> Audio (5) -> Broadcast (F): set system audio mode (72)
21:57:17 T:2960450576   DEBUG: CecLogMessage - >> Audio (5): system audio mode status changed from off to on


anyone using a Philips TV behind a Yamaha AVR?
On the AVR, the HDMI settings were set to ON (also tried OFF)
Putting TV in standby puts AVR in standby too, so they both seems to communicate...
tx
Posts: 28
Joined: Tue Jul 17, 2012 7:02 am
by migube » Fri Feb 15, 2013 8:21 pm
I managed to get it working by
1) using HDMI1 input on TV
2) HDMI 1 output on Yamaha
3) changing the HDMI cable .... (damn)

:)
Posts: 28
Joined: Tue Jul 17, 2012 7:02 am
by mocherz » Sat Mar 02, 2013 8:39 am
Ive got this weird problem where my tv recognizes the CEC setting on my rpi, although it thinks its on a different hdmi port than the one connected, if I switch the cable to the discovered port, everything works well untill I reboot, then the hdmi port broadcasting the CEC signal changes again. Would this have anything to do with my HDMI physical address? Any advice?
Posts: 5
Joined: Tue Aug 14, 2012 11:52 pm
by cranberry » Wed Apr 10, 2013 9:53 pm
I am not using XBMC, but I have problem with CEC. I have implemented own applicaiton to Rasbian wheezy. I can get Tx callbacks, but not Rx callbacks. My Samsung detects RaspPi as a CEC device and I can change OSD name (using vc_cec_set_osd_name function), which means that same name is in Samsung menu than I have defined in function call. It means that Samsung is receiving something.
Posts: 9
Joined: Wed Mar 13, 2013 4:37 pm
by oculos » Sat Apr 13, 2013 8:20 pm
rpi2000 wrote:
Okay, one step further:

If I use another cable AND disconnect all other devices from HDMI ports (doesn't matter whether they are turned on or not) the TV finds a CEC device at least (called: "player").

But now: if I want to connect to this Anynet+ device it says. "device not connected. check and try again" Any ideas?


Same issue here. If I disconnect the other HDMI (used by something other than the RPi), it works, and remain working even if I plug the other cable again (and stop if I switch to something else). If RPi is the only cable connected, it works all the time.

My TV is also a Samsung. I am wondering if this is rather a Samsung issue. I want to try a different cable on the other (non-RPi) device to see if it will make a difference. But it would be really nice to see this solved.
Posts: 2
Joined: Sat Apr 13, 2013 8:15 pm
by cranberry » Tue Apr 23, 2013 8:28 pm
Did you ever try to reboot (power cable) your Samsung? It helped to me, it solved the problem what I was investigating >1 month.
I will write very angry email to Samsung, I am very disappointed to their products!
Posts: 9
Joined: Wed Mar 13, 2013 4:37 pm
by oculos » Wed Apr 24, 2013 7:02 am
cranberry wrote:Did you ever try to reboot (power cable) your Samsung? It helped to me, it solved the problem what I was investigating >1 month.
I will write very angry email to Samsung, I am very disappointed to their products!


No, that's a good idea! I'll try that! :)
Posts: 2
Joined: Sat Apr 13, 2013 8:15 pm