Reply to thread

Message: <blockquote data-quote="joboehl" data-source="post: 123922" data-attributes="member: 23490">Janjuul, everything is experimental at this point. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink    ;)" loading="lazy" data-shortname=";)" />STBs where not supported at the initial release, since the server did not supported plug-ins in the initial SVNs. It has support for that for a while now. Single-seat - One blaster/remote receiver. Multi-seat - On blaster at the server, one receiver in each client. At the client you can use whatever you whant as a remote. Being worked on. Not something that is not going to happen or not considered important. Just not ready. The first step was for the tvengine to embbed the subtitle in the stream. That's done. look for tourretes post's about that. He just released an update a cople of days ago. Actually, separating the engine from the presentation should bring even more stability. With the new arquitecture, if you are watching a DVD and recording a show, if the DVD player hangs there goes your recording. The same for plug-ins. An errand client plug-in will not affect the server, and vice-versa. Most of what is defined is in the wiki. The plug-in infrastructure is in the wiki for example. Just to make clear: the server plug-in interacts with the server, not the with the client. There is no communication from the client to the plug-in. It only communicates with the server. So, if you change a channel in the client, the server receives a request to change a channel. It then broadcast internally a message saying it's about to change a channel. Plug-ins can subscribe to the message and do whaetver they want: blast, send an e-mail, log the change so you audit what your kids are doing. But the plug-in interacts with the server, not the client. It's really simple actually.  Take a look at the wiki and the news frodo posts about the engine. Theres a lot of information about features and implementation. I think the new GUI is going to happen only after the engine. It needs a major revamp at the client side. About the other features, they should be posted at the feature requests forum. When a new release cycle begins, devs usually ask forum members witch fatures are most important. Thats how tvengine was born for example. And also, tvenginev3 and MP v0.3 are two different things. They evolve in separate. If you have a request/idea for MP appart from the TVEngine, go ahead and suggeest it. I know there is a lot of planning on improving the music part of MP. Interesting. I saw some of that information as part of the evolution of MCE extenders. It would be nice if those kind of devices could be programmable or worked with open standards (like rtsp). But if they for whatever reason look like MCE v1 extenders, it would be difficult to make anything work with them. But like I posted before, solutions like Hauppauge MVP already work with open protocols. Maybe they can work with MP in the future. And if they release new versions with more functionality (like a built in dvd player and things like that) it might become very interesting.</blockquote>

Verification