I've merged Dushmaniac with my repository so it should now be up to date with xbmc mainline. I've also added support for updating the records and timer s in the add-on when the backend announces changes to these. I'm not sure it will fix the issue mronkko and Jimmer is seeing.
deadite66: I will see if there are anything I can do to lower the cpu utilization. however the atom processor it not exactly the most powerfull cpu around but at least the power utilization doesn't increase with higher load.
fiveisalive: Dteirney's plugin uses the mythxml data interface to get information about the recordings and program guide. The interface doesn't support scheduling of recordings. The MythXML interface has been replaced with a new API in the current development version of MythTV (ver. 0.25). The new API will support scheduling of recordings etc and I plan to support it instead of libcmyth when 0.25 is released.
The libcmyth library takes care of the communication with the mythtv backend though the MythProtocol and the MySQL server. This expose the majority of the mythtv features (including the scheduling of recordings). I'm not sure how active the development of libcmyth are at mvpmc (last update was 11 months ago and in its current form MythTV 0.24 is not supported). The libcmyth library is also used by the xbmc virtual filesystem in mainline. For more information about the status of libcmyth please see https://github.com/xbmc/xbmc/pull/386
. I plan to push the changes I made to libcmyth to mainline when the code is more mature.
dubstar_04: Thanks for the video. I will add it to the first post. I would be happy to also add your tutorial to the post if you send it to me.
mronkko: I've looked though the log and it looks like xbmc jumps to the end of the video when the stepforward command is recieved. Does the same happen when you use the fast forward button on the GUI? I will try to add some more debug info into the code that should produce a more informative log.