Archive > MythTV Plugin Users

Using mythtv & lirc and choosing main GUI on MD ?

(1/3) > >>

archived:
Hi,

I'm running mythtv and I tried to use lirc remote and it works - it's Ati Remote Wonder and it works out of the box - it only lacks better configuration file for ATI remote.
- where can I find lirc remote configuration file to change ?
- would Pluto system mind if I add other mythtv plugins (like mythnews, mythvideo, mythmusic, ....) ?
- how is mythfrontend exactly started and from where ?

I'm also thinking a lot about what would be best GUI for MD. Existing Orbiters are great and intuitive GUI (specially for touchscreens or mouse), but will probably be hard to adopt for navigation with ordinary Remotes.

On the other side there are GUIs that are great to use with remotes but lack touchscreen or mouse support (Freevo, Mythtv, ....).

I know, that there are a lot of stuff to be done with Pluto so I just think, why not use mythfrontend as GUI on MD - it could be best combination for now...

We could still control it from Orbiters and ordinary remotes and get other functionalities too (mythnews, maybe mythphone, etc....).

Mythtv could be "plutonized" with custom skin and that would be IMHO quite good solution...

I wonder what are plans for MD GUI and what would be best solution in current situation... I'm little spoiled by using mythfrontend for a longer period of time....

Is there any possibility to put MD Orbiter in mythtfrontend mode from lirc remote ?

Does perhaps Xine player in Pluto support lirc ? Can Xine player be started with messages - like MessageSend ... file_to_play ?

What are plans for lirc integration and navigation on MD Orbiters ?

Thanks in advance,

regards,

Rob.

archived:
Hi,

no one there to give answers  :shock:  ?

Well I dig a little bit further. My Ati Remote Wonder also works on MD Orbiter GUI (but more as mouse moving and 2 button click device). If I get in mythtv it also works - but now with arrow buttons and OK as enter....

Now I tried to give proper configuration file (lircrc) to mythtv to use other buttons too - I copied file to /root/.mythtv/lircrc but no progress - remote still works on 5 buttons....

Is myhtv using it's native lirc capability? How and where does Pluto use lirc ?  Where are configuration files for remotes stored (lircrc) ?

I guess adding lirc support to Xine will make navigation with remotes on MD possible - anyone working on that ?

Thanks in advance,

regards,

Rob.

archived:
Hi Rob,

Come on, you post your first message at 5:00pm, and then at 10:00 you write "no one there to give answers"...  :)  Our guys may be programmers, but some of them do try to leave the office every once in a while... <lol>

It sounds like your Ati Remote is just simulating a mouse.  I've used them before, and that's how they work.  That's not a very convenient way to navigate either (too slow).

The way the Orbiter's OSD display works with a regular IR remote is like this:  From the main menu, punch the same number combination on the I/R remote to trigger scenarios like you would on the mobile phone.  "1" brings up all the lighting scenarios (numbered, like on the phone), "2" activates the second one.  "2" brings up the media menu, "2" starts TV.  That's the fastest way to do it, since it's just 2 keystrokes, and is faster than most remotes, particularly for common tasks where you remember the keystrokes (ie 22 = tv in every room).  The other thing you can do is use the i/r remotes up/down/left/right button to highlight the buttons.  It's not a mouse where you're moving a pointer--down moves the highlighter down.  This is the same way Myth and nearly all other set top boxes work (like your cable box).

Once you select the media scenario you want, like 'TV', you no longer even have a menu.  Just use the remote like normal "play", "rewind", "fast forward", "skip up/down", etc.

All the code in Pluto is in place to do this, and it works and we've tested it.  The LIRC configuration is stored in the database "choose advanced, device templates, peripherals, remote controls, LIRC".  You'll see all the LIRC remotes, and the device data has the config file.  The device driver LIRC_DCE writes out a standard LIRC configuration file and runs lirc like normal.  So, to lirc, there should be no difference--we didn't modify it.

For some reason lirc isn't working, and we don't know why.  It does work for others, so it's not an inherint bug in lirc.  But we've posted messages to the lirc forums and have not gotten any responses.  Radu is working on debugging the lirc issue.

As soon as lirc is working, try using pluto with the i/r remote.  You could try using Myth front-end.  However, it seems like a huge amount of work.    The OrbiterGen app would need to be re-written to output whatever Myth needs.  And the Myth front-end won't be able to handle DCE messages.  So it would need to be rewritten.  Plus, a new floorplan module would need to be written for Myth.  Myth's internal datagrids are likely different than ours--that would need to be rewritten.

As far as the other Myth plug-ins, give them a try.  We don't do anything at all that should break/interfere with Myth.  When you hit 'watch tv', all it does is spawn '/usr/bin/mythfrontend' in a window and make that window top-most.  We didn't change a thing, so you can do anything with Myth.

BTW, re LIRC support to Xine...  We already did that.  As soon as we get lirc working, that will work too.

archived:
Oh, Rob, by the way....  If you ever want to look at this stuff (like LIRC) or have some insight on how to make it work, just send Radu an IM.  We have several test systems that our guys work on, and he can just open a port so you can ssh into one and see what we're doing.

archived:

--- Quote from: "aaron.b" ---Hi Rob,

Come on, you post your first message at 5:00pm, and then at 10:00 you write "no one there to give answers"...  :)  Our guys may be programmers, but some of them do try to leave the office every once in a while... <lol>
--- End quote ---


Hi, thanks for response. Well my first posting is dated at 16 of May - or am I missing something  :)


--- Quote from: "aaron.b" ---It sounds like your Ati Remote is just simulating a mouse.  I've used them before, and that's how they work.  That's not a very convenient way to navigate either (too slow).

The way the Orbiter's OSD display works with a regular IR remote is like this:  From the main menu, punch the same number combination on the I/R remote to trigger scenarios like you would on the mobile phone.  "1" brings up all the lighting scenarios (numbered, like on the phone), "2" activates the second one.  "2" brings up the media menu, "2" starts TV.  That's the fastest way to do it, since it's just 2 keystrokes, and is faster than most remotes, particularly for common tasks where you remember the keystrokes (ie 22 = tv in every room).  The other thing you can do is use the i/r remotes up/down/left/right button to highlight the buttons.  It's not a mouse where you're moving a pointer--down moves the highlighter down.  This is the same way Myth and nearly all other set top boxes work (like your cable box).

Once you select the media scenario you want, like 'TV', you no longer even have a menu.  Just use the remote like normal "play", "rewind", "fast forward", "skip up/down", etc.

All the code in Pluto is in place to do this, and it works and we've tested it.  The LIRC configuration is stored in the database "choose advanced, device templates, peripherals, remote controls, LIRC".  You'll see all the LIRC remotes, and the device data has the config file.  The device driver LIRC_DCE writes out a standard LIRC configuration file and runs lirc like normal.  So, to lirc, there should be no difference--we didn't modify it.

For some reason lirc isn't working, and we don't know why.  It does work for others, so it's not an inherint bug in lirc.  But we've posted messages to the lirc forums and have not gotten any responses.  Radu is working on debugging the lirc issue.

As soon as lirc is working, try using pluto with the i/r remote.  You could try using Myth front-end.  However, it seems like a huge amount of work.    The OrbiterGen app would need to be re-written to output whatever Myth needs.  And the Myth front-end won't be able to handle DCE messages.  So it would need to be rewritten.  Plus, a new floorplan module would need to be written for Myth.  Myth's internal datagrids are likely different than ours--that would need to be rewritten.

As far as the other Myth plug-ins, give them a try.  We don't do anything at all that should break/interfere with Myth.  When you hit 'watch tv', all it does is spawn '/usr/bin/mythfrontend' in a window and make that window top-most.  We didn't change a thing, so you can do anything with Myth.

BTW, re LIRC support to Xine...  We already did that.  As soon as we get lirc working, that will work too.
--- End quote ---


Thanks for all info... Well I agree on mythtv. I see it more as temporary complement to pluto GUI - right now you can easily read weather forecast, RSS news and other stuff that will probably come to pluto later...

Navigation on MD you described seems nice and useful - hardly wait to use it...

I'm already in contact with Radu - and i'm helping in some way. From now and then I just try to put some problems also on forums - in the spirit of open source world - so other guys can contribute also....

When I get in mythtv arrow and OK buttons  work - so I guess this comes from real lirc daemon - not simulating mouse....

I still don't get one thing: my remote works as mouse - lirc_atiusb module is in place - so that means that lirc is smiulating it? Is this Pluto's lirc doing that job or does it come from some Debian default installation ?
If we start from here, it means that lirc is working - but ....

I hope we will solve this soon....

Regards,

Rob.

Navigation

[0] Message Index

[#] Next page

Sitemap 
Go to full version