Has anybody with working knowledge of LMCE and mythTV had a chance to look at this new API? Will it possibly make Myth more of a stable partner for MCE? Thom, I know you share my current disdain for Myth as far as stability. Could this new API allow us to see something of an improvement?

From what I gather from this API, we have 2 courses of action. 1) rewrite MythTV player to use the http calls with the new frontend API. or 2) create our own frontend and use the other API's which to me would be maybe more work but in the end a much better approch, since this could integrate into the new QOrbiter.

The backend of myth works just fine currently, it is the communication with the frontend that is flaky as hell. If this new API allows us manipulate myth within an orbiter screen of our design then this whole system becomes much more efficient and fluid.

posde, I understand where you are coming from. My point being that from what I could determine from looking at the code( and I could be very wrong) currently MythTV Player communicates through a socket with mythfrontend to watch, change channels etc. The mythfrontend client communication is fairly unstable. This new api would allow an lmce md to communicate directly with the mythbackend even if it is through the DCEROUTER. We could basically eliminate the mythtv frontend altogether in favor of an lmce frontend.

Thom from reading the API it looks like we would be able to eliminate the need for myth frontend all together and our MythTVPlayer would get the stream straight from the mythbackend. Under this approach we would need to handle the UI for the guide and programming etc. I'm curious how this is handled currently in VDR as it is my understanding that VDR is stricly a backend and LMCE handles the UI frontend.

VDR integration and MythTV integration are identical. Both are using dedicated players.

The advantage of the VDR integration is that the frontend gets out of its way, whereas the MythTV frontends jumps at you. The advantage of the MythTV integration is that you are able to select recordings from the videos part of LinuxMCE.

Posde my understanding of the MythTV .25 is that it allows the MythTV to get out of the way also. The big issue I see is the guide data and setting up recordings, how is this data presented to the orbiter for VDR, I would assume we could mimic that code.

For an example, look at the data grid generators in MythTV PlugIn, there are a few of them in there. These datagrids are generated, and sent over via the Datagrid Plugin to Orbiter when needed (when a DataGrid object is on a designobj)