As your market grows im sure more and more harmony remote users will be grateful for this feature to be taken advantage of.
#Flirc harmony one not working software
One of the major reasons i purchased the flirc was due to the fact that it already had a logictech harmony profile as that was a major selling point for me as it would not only allow me to customize the buttons to my own likes (which the flirc software interface also does) but the fact that i can then utilize the services of harmony to control all of my devices by setting all the correct inputs based upon all devices involved within an activity with one button press of an activity function (which the flirc does not provide this functionality and not designed to do so) was the one thing that made me click "Add to Cart" button and in your forum now there are lots of posts of folks using a harmony remote and thus a big additional major selling point of the flirc as they like to keep this feature also. Now i myself have not played with Kodi yet so don't know the differences yet but there may be some. Since flirc itself has no control on how keys are mapped between different version of XBMC?Kodi, one thing for sure certain core keys will always or should remain the same. Changed mappings could be saved as new app profile in user profiles dir (given that there are Flirc provided profiles and user profiles kept separately).Īctually the best way may be by doing both.
There will be of course situations that some remotes can have more or less buttons or even different button names so the Flirc app itself would need to allow customization of function to button mappings (for example by displaying available functions and providing dropdown with button selection). Flirc app would need to allow selecting a remote profile and app profile pair (or even more pairs if capacity still allows to store multiple mappings). It could also provide default remote button name (from remote definitions). Application definitions would assign a name of function in the app to a key combination (could be in the same format as for record_api). Remote definitions would assign a set of names to hex hashes of IR signals each button creates (with an ability to assign multiple hashes to a single name for MCE/RC6 remotes and other similar) - one file per remote model. There could be two types of ini files: remote definition and application definition.
It would be even better if the profile definition could be in some easily editable format like ini, so the community can create new profiles by themselves. Profile definitions could be defined in some file format loadable by the Flirc software. I think it would be better to remove built-in profiles and ship Flirc with pre-programmed one for XBMC/Harmony setup (if this is main reason for the built-in profiles to exist in the first place). There are also other problems like for example differences in key shortcuts between software versions - like right now there are differences between XBMC and Kodi so it would require a new Harmony profile with at least some codes different from current one. I know that it allows a fast start if all someone wants is to control XBMC with Harmony (it only requires from the user to set up the Harmony remote with correct profile), but on the other hand it probably takes some space in the flash memory which could be used for some other functionality, given that the micro used in Flirc doesn't have it that much.
I've been wondering if having a built-in profiles in current form is really a good idea.
0 kommentar(er)
