{"id":162,"date":"2007-01-22T08:24:00","date_gmt":"2007-01-22T16:24:00","guid":{"rendered":"http:\/\/www.mccambridge.org\/blog\/2007\/01\/howto-mythtv-snes-joystick-control\/"},"modified":"2022-09-11T00:40:44","modified_gmt":"2022-09-11T00:40:44","slug":"howto-mythtv-snes-joystick-control","status":"publish","type":"post","link":"http:\/\/www.mccambridge.org\/blog\/2007\/01\/howto-mythtv-snes-joystick-control\/","title":{"rendered":"Howto: Mythtv SNES Joystick Control"},"content":{"rendered":"

Update:<\/strong> Why oh why can’t Blogger preview my post in the *actual* stylesheet of my blog? I seem to remember WordPress doing this… if so, I must switch. ASAP.<\/p>\n

I’m back down in Madison, and in the midst of unpacking all my junk after moving down here from home. One thing that Nate & I set up right away is my HTPC, an Ubuntu<\/a>-based MythTV<\/a> box. Unfortunately, I noticed over winter break that my homemade serial-port IR receiver has given up the ghost, so I can no longer control MythTV from my universal remote. I’ve ordered the parts for a USB IR receiver<\/a>, but as I mentioned earlier, my soldering iron has also<\/em> given up the ghost…<\/p>\n

So, what to do in the interim? Well, there is a keyboard attached to the Myth box, but it doesn’t reach the couch. Enter the SNES controller and MythTV joystick control. Here’s how I got it to work:<\/p>\n

Goal<\/h3>\n\n
Control MythTV from an SNES controller (or any other gamepad)<\/li>\n<\/ul>\n
Required Software \/ Hardware<\/h3>\n
\n
MythTV (I believe any version since 0.17 will work)<\/li>\n
SNES controller connected via parallel port adapter and the gamecon driver (see Documentation\/input\/joystick-parport.txt in the Linux source tree)<\/li>\n
jstest<\/code> (Optional, available on Ubuntu in the “joystick” package)<\/em><\/li>\n<\/ul>\nDetermining joystick layout<\/h3>\nThe first step in writing a MythTV joystick configuration is to determine the exact layout of your joystick, as Linux sees it. Specifically, we need to know what axes (and axis values) and buttons correspond to the controls on the joystick.<\/p>\nIf you’re using an SNES controller with the gamecon<\/code> driver, I’ve done the legwork, and you can skip to the next section<\/a> below, using my example configuration. (Obviously you should test it and make sure it works.)<\/p>\n To determine the layout of your own joystick, you can use the optional jstest<\/code> program mentioned above. You can install it on Ubuntu from the joystick<\/code> package (you will need the universe repository enabled):<\/p>\n $ sudo apt-get install joystick<\/code><\/p>\n Run jstest<\/code> and record the axis numbers and values, as well as button numbers, that correspond to all the controls you wish to use on your joystick. jstest<\/code> requires a parameter of the joystick device to open. For example, I run jstest<\/code> like this for my first SNES controller:<\/p>\n $ jstest \/dev\/input\/js0<\/code><\/p>\n jstest<\/code> produces output for my SNES controller like this:<\/p>\n Driver version is 2.1.0.<\/p>\n Joystick (SNES pad) has 2 axes (X, Y)<\/p>\n and 8 buttons (BtnX, BtnY, BtnTL, BtnTR, BtnTR2, BtnSelect, BtnThumbL, BtnThumbR).<\/p>\n Testing ... (interrupt to exit)<\/p>\n Axes: 0: 0 1: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off<\/code><\/p>\n This tells me that the joystick as seen by Linux has two axes and 7 buttons. Pressing them in sequence changes the output, such as this output when I hold the directional pad to the left and press the “A” button:<\/p>\n Testing ... (interrupt to exit)<\/p>\n Axes: 0:-32767 1: 0 Buttons: 0:on 1:off 2:off 3:off 4:off 5:off 6:off 7:off<\/code><\/p>\n This tells you that the D-pad “left” direction corresponds to value -32767 on Axis 0, and that the “A” button corresponds to button 0.<\/p>\n Compiling a full list for your joystick would give you a mapping like this one for the SNES controllers & gamecon driver:<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nSNES Button<\/th>\n Linux joystick mapping<\/th>\n<\/tr>\n D-Pad Up<\/td>\n Axis 1: -32767<\/td>\n<\/tr>\n D-Pad Right<\/td>\n Axis 0: 32767<\/td>\n<\/tr>\n D-Pad Down<\/td>\n Axis 1: 32767<\/td>\n<\/tr>\n D-Pad Left<\/td>\n Axis 0: -32767<\/td>\n<\/tr>\n A<\/td>\n Button 0<\/td>\n<\/tr>\n B<\/td>\n Button 1<\/td>\n<\/tr>\n X<\/td>\n Button 2<\/td>\n<\/tr>\n Y<\/td>\n Button 3<\/td>\n<\/tr>\n L<\/td>\n Button 4<\/td>\n<\/tr>\n R<\/td>\n Button 5<\/td>\n<\/tr>\n Select<\/td>\n Button 6<\/td>\n<\/tr>\n Start<\/td>\n Button 7<\/td>\n<\/tr>\n<\/table>\n<\/a><\/p>\n Writing the MythTV Joystickmenurc<\/code>Configuration File<\/h3>\nNow that you have the logical layout of your joystick in hand, it’s time to configure MythTV itself. This is done by means of the joystickmenurc<\/code> configuration file, located at ~\/.mythtv\/joystickmenurc<\/code> for the user that mythfrontend is launched under. This file will instruct MythTV as to which joystick device it should open, and then provides a mapping from the joystick layout to the keyboard strokes for MythTV.<\/p>\n joystickmenurc<\/code> Format<\/h4>\nAs described in the formatting section<\/a> of the Joystick Control page on the MythTV Wiki, the format for the joystickmenurc<\/code> is as follows:<\/p>\n \ndevicename <devname><\/code><\/dt>\n Specify the name of the joystick device to use, (e.g. \/dev\/input\/js0)<\/dd>\n button <num> <keystring><\/code>\n<\/dt>\n Send keystring<\/code> when button num<\/code> is released\n<\/dd>\n chord <cnum> <bnum> <keystring><\/code>\n<\/dt>\n If button cnum<\/code> is down, and button bnum<\/code> is released, send keystring<\/code>\n<\/dd>\n axis <num> <from> <to> <keystring><\/code>\n<\/dt>\nIf axis num<\/code> goes into the range of from<\/code>–to<\/code> send keystring<\/code>\n<\/dd>\n<\/dl>\nExample joystickmenurc<\/code> for SNES controller<\/h4>\nI think the formatting is best explained by an example. Below is the actual ~\/.mythtv\/joystickmenurc<\/code> file I use on my system, with commenting explaining exactly what is intended and how it works. If you use an SNES controller attached via the gamecon<\/code> driver to \/dev\/input\/js0<\/code>, this configuration should work for you as-is. Simply drop it in your ~\/.mythtv<\/code> directory and relaunch mythfrontend<\/code>. For everyone else, feel free to use this as a template, or see the Joystick Control<\/a> page on the MythTV Wiki for an example of an Xbox configuration file.<\/p>\n \n# ~\/.mythtv\/joystickmenurc\n# Joystick menu config file\n#\n# Created 1\/21\/2007 by Colin McCambridge\n# based on instructions at http:\/\/www.mythtv.org\/wiki\/index.php\/Joystick_Control\n#\n# This joystick menu configuration controls MythTV with an SNES\n# gamepad connected via parallel port and the gamecon driver.\n#\n# Controls:\n# SNES Pad Keypresses Joystick Device\n# -------- ---------- ---------------\n# UP\/DOWN axis Up, Down Axis 1: U -32767 D 32767\n# LEFT\/RIGHT axis Left, Right Axis 0: L -32767 R 32767\n# B Enter Button 1\n# Y Esc Button 3\n# A P (Play\/Pause) Button 0\n# X S (Guide) Button 2\n# Start M (Menu) Button 7\n# Select I (Info) Button 6\n# Left Top Page Up (REW) Button 4\n# Right Top Page Down (FF) Button 5\n#\n\n###########################################################\n#\n# SNES Gamepad Device\n#\n###########################################################\n\ndevicename \/dev\/input\/js0\n\n###########################################################\n#\n# D-Pad\n#\n###########################################################\n\n#Up\n axis 1 -32767 -1 Up\n#Down\n axis 1 1 32767 Down\n#Left\n axis 0 -32767 -1 Left\n#Right\n axis 0 1 32767 Right\n\n###########################################################\n#\n# Buttons\n#\n###########################################################\n\n#A ==> Play\/Pause\n button 0 P\n#B ==> Enter\n button 1 Enter\n#X ==> Guide (S)\n button 2 S\n#Y ==> Exit (Esc)\n button 3 Escape\n\n#Start ==> Menu (M)\n button 7 M\n#Select ==> Info (I)\n button 6 I\n\n#Left Top ==> Rewind (PgUp)\n button 4 PgUp\n#Right Top ==> F.Fwd (PgDown)\n button 5 PgDown\n<\/pre>\n<\/blockquote>\nFinal Notes<\/h3>\nFor making your own joystickmenurc<\/code> file, you may find the MythTV Default Keybindings<\/a>, or the more abbreviated Remote Control Buttons<\/a> list handy references as to the control operations you can define.<\/p>\n For an exact list of valid key names to use (e.g. “Escape”) refer to the Qt documentation for the Qt.Key enum<\/code><\/a>. This document lists key names in the form: “Qt::Key_Escape<\/code>“, use only the name following the underscore.<\/p>\n Note:<\/strong> there is an undocumented discrepancy regarding the keys Page Up and Page Down. While the Qt.Key<\/code> enum lists them as PageUp<\/code> and PageDown<\/code>, they can actually only be specified as either \"PgUp\"<\/code> and \"PgDown\"<\/code>, or \"Page Up\"<\/code> and \"Page Down\"<\/code> respectively. See messages 3 and 4 of this email thread<\/a> for reference, or view the relevant Qt source file (especially the keyname[]<\/code> array at line 89, and method decodeString<\/code> at line 388): qkeysequence.cpp<\/code><\/a><\/p>\n","protected":false},"excerpt":{"rendered":" Update: Why oh why can’t Blogger preview my post in the *actual* stylesheet of my blog? I seem to remember WordPress doing this… if so, I must switch. ASAP. I’m back down in Madison, and in the midst of unpacking all my junk after moving down here from home. One thing that Nate & I […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[7,12,21,24],"tags":[],"_links":{"self":[{"href":"http:\/\/www.mccambridge.org\/blog\/wp-json\/wp\/v2\/posts\/162"}],"collection":[{"href":"http:\/\/www.mccambridge.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.mccambridge.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.mccambridge.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.mccambridge.org\/blog\/wp-json\/wp\/v2\/comments?post=162"}],"version-history":[{"count":1,"href":"http:\/\/www.mccambridge.org\/blog\/wp-json\/wp\/v2\/posts\/162\/revisions"}],"predecessor-version":[{"id":1733,"href":"http:\/\/www.mccambridge.org\/blog\/wp-json\/wp\/v2\/posts\/162\/revisions\/1733"}],"wp:attachment":[{"href":"http:\/\/www.mccambridge.org\/blog\/wp-json\/wp\/v2\/media?parent=162"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.mccambridge.org\/blog\/wp-json\/wp\/v2\/categories?post=162"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.mccambridge.org\/blog\/wp-json\/wp\/v2\/tags?post=162"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

SNES Button<\/th>\n	Linux joystick mapping<\/th>\n<\/tr>\n
D-Pad Up<\/td>\n	Axis 1: -32767<\/td>\n<\/tr>\n
D-Pad Right<\/td>\n	Axis 0: 32767<\/td>\n<\/tr>\n
D-Pad Down<\/td>\n	Axis 1: 32767<\/td>\n<\/tr>\n
D-Pad Left<\/td>\n	Axis 0: -32767<\/td>\n<\/tr>\n
A<\/td>\n	Button 0<\/td>\n<\/tr>\n
B<\/td>\n	Button 1<\/td>\n<\/tr>\n
X<\/td>\n	Button 2<\/td>\n<\/tr>\n
Y<\/td>\n	Button 3<\/td>\n<\/tr>\n
L<\/td>\n	Button 4<\/td>\n<\/tr>\n
R<\/td>\n	Button 5<\/td>\n<\/tr>\n
Select<\/td>\n	Button 6<\/td>\n<\/tr>\n
Start<\/td>\n	Button 7<\/td>\n<\/tr>\n<\/table>\n <\/a><\/p>\n Writing the MythTV `Joystickmenurc<\/code>Configuration File<\/h3>\nNow that you have the logical layout of your joystick in hand, it’s time to configure MythTV itself. This is done by means of the joystickmenurc<\/code> configuration file, located at ~\/.mythtv\/joystickmenurc<\/code> for the user that mythfrontend is launched under. This file will instruct MythTV as to which joystick device it should open, and then provides a mapping from the joystick layout to the keyboard strokes for MythTV.<\/p>\n` `joystickmenurc<\/code> Format<\/h4>\n`As described in the formatting section<\/a> of the Joystick Control page on the MythTV Wiki, the format for the joystickmenurc<\/code> is as follows:<\/p>\n \ndevicename <devname><\/code><\/dt>\n Specify the name of the joystick device to use, (e.g. \/dev\/input\/js0)<\/dd>\n button <num> <keystring><\/code>\n<\/dt>\n Send keystring<\/code> when button num<\/code> is released\n<\/dd>\n chord <cnum> <bnum> <keystring><\/code>\n<\/dt>\n If button cnum<\/code> is down, and button bnum<\/code> is released, send keystring<\/code>\n<\/dd>\n axis <num> <from> <to> <keystring><\/code>\n<\/dt>\nIf axis num<\/code> goes into the range of from<\/code>–to<\/code> send keystring<\/code>\n<\/dd>\n<\/dl>\nExample joystickmenurc<\/code> for SNES controller<\/h4>\nI think the formatting is best explained by an example. Below is the actual ~\/.mythtv\/joystickmenurc<\/code> file I use on my system, with commenting explaining exactly what is intended and how it works. If you use an SNES controller attached via the gamecon<\/code> driver to \/dev\/input\/js0<\/code>, this configuration should work for you as-is. Simply drop it in your ~\/.mythtv<\/code> directory and relaunch mythfrontend<\/code>. For everyone else, feel free to use this as a template, or see the Joystick Control<\/a> page on the MythTV Wiki for an example of an Xbox configuration file.<\/p>\n \n# ~\/.mythtv\/joystickmenurc\n# Joystick menu config file\n#\n# Created 1\/21\/2007 by Colin McCambridge\n# based on instructions at http:\/\/www.mythtv.org\/wiki\/index.php\/Joystick_Control\n#\n# This joystick menu configuration controls MythTV with an SNES\n# gamepad connected via parallel port and the gamecon driver.\n#\n# Controls:\n# SNES Pad Keypresses Joystick Device\n# -------- ---------- ---------------\n# UP\/DOWN axis Up, Down Axis 1: U -32767 D 32767\n# LEFT\/RIGHT axis Left, Right Axis 0: L -32767 R 32767\n# B Enter Button 1\n# Y Esc Button 3\n# A P (Play\/Pause) Button 0\n# X S (Guide) Button 2\n# Start M (Menu) Button 7\n# Select I (Info) Button 6\n# Left Top Page Up (REW) Button 4\n# Right Top Page Down (FF) Button 5\n#\n\n###########################################################\n#\n# SNES Gamepad Device\n#\n###########################################################\n\ndevicename \/dev\/input\/js0\n\n###########################################################\n#\n# D-Pad\n#\n###########################################################\n\n#Up\n axis 1 -32767 -1 Up\n#Down\n axis 1 1 32767 Down\n#Left\n axis 0 -32767 -1 Left\n#Right\n axis 0 1 32767 Right\n\n###########################################################\n#\n# Buttons\n#\n###########################################################\n\n#A ==> Play\/Pause\n button 0 P\n#B ==> Enter\n button 1 Enter\n#X ==> Guide (S)\n button 2 S\n#Y ==> Exit (Esc)\n button 3 Escape\n\n#Start ==> Menu (M)\n button 7 M\n#Select ==> Info (I)\n button 6 I\n\n#Left Top ==> Rewind (PgUp)\n button 4 PgUp\n#Right Top ==> F.Fwd (PgDown)\n button 5 PgDown\n<\/pre>\n<\/blockquote>\nFinal Notes<\/h3>\nFor making your own joystickmenurc<\/code> file, you may find the MythTV Default Keybindings<\/a>, or the more abbreviated Remote Control Buttons<\/a> list handy references as to the control operations you can define.<\/p>\n For an exact list of valid key names to use (e.g. “Escape”) refer to the Qt documentation for the Qt.Key enum<\/code><\/a>. This document lists key names in the form: “Qt::Key_Escape<\/code>“, use only the name following the underscore.<\/p>\n Note:<\/strong> there is an undocumented discrepancy regarding the keys Page Up and Page Down. While the Qt.Key<\/code> enum lists them as PageUp<\/code> and PageDown<\/code>, they can actually only be specified as either \"PgUp\"<\/code> and \"PgDown\"<\/code>, or \"Page Up\"<\/code> and \"Page Down\"<\/code> respectively. See messages 3 and 4 of this email thread<\/a> for reference, or view the relevant Qt source file (especially the keyname[]<\/code> array at line 89, and method decodeString<\/code> at line 388): qkeysequence.cpp<\/code><\/a><\/p>\n","protected":false},"excerpt":{"rendered":" Update: Why oh why can’t Blogger preview my post in the actual stylesheet of my blog? I seem to remember WordPress doing this… if so, I must switch. ASAP. I’m back down in Madison, and in the midst of unpacking all my junk after moving down here from home. One thing that Nate & I […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[7,12,21,24],"tags":[],"_links":{"self":[{"href":"http:\/\/www.mccambridge.org\/blog\/wp-json\/wp\/v2\/posts\/162"}],"collection":[{"href":"http:\/\/www.mccambridge.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.mccambridge.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.mccambridge.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.mccambridge.org\/blog\/wp-json\/wp\/v2\/comments?post=162"}],"version-history":[{"count":1,"href":"http:\/\/www.mccambridge.org\/blog\/wp-json\/wp\/v2\/posts\/162\/revisions"}],"predecessor-version":[{"id":1733,"href":"http:\/\/www.mccambridge.org\/blog\/wp-json\/wp\/v2\/posts\/162\/revisions\/1733"}],"wp:attachment":[{"href":"http:\/\/www.mccambridge.org\/blog\/wp-json\/wp\/v2\/media?parent=162"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.mccambridge.org\/blog\/wp-json\/wp\/v2\/categories?post=162"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.mccambridge.org\/blog\/wp-json\/wp\/v2\/tags?post=162"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}