[PROJECT] OpenHT

Did you install VMware Tools in the VM?


Yes, I did that early on, after initial install of the Ubuntu OS.
And the mouse works just fine with all other software I've used.
It's only PHT which has this particular problem (both standard PHT and OpenPHT).

Best regards: dlanor

I'm running it on 2 different ubuntu machines (HTPC and Notebook) without any mouse problems, so I think it has something to do with vmware. Could you please also install XBMC 12.3 to test the mouse functionality with your vmware installation ?

OpenPHT already has a modified "mouse.xml" file to fix the left-click issue but it seems like the ubuntu package still contains the old file, will fix that ...

I'm running it on 2 different ubuntu machines (HTPC and Notebook) without any mouse problems, so I think it has something to do with vmware.

I agree that this is a likely possibility. They obviously must mess around with the mouse drivers of Ubuntu, to achieve the sharing of the one mouse between host and guest systems.

Could you please also install XBMC 12.3 to test the mouse functionality with your vmware installation ?

I suppose I can do that. But I'm not sure where to find the proper install package.
Perhaps you can provide a link to a suitable XBMC package for Ubuntu 14.04.

OpenPHT already has a modified "mouse.xml" file to fix the left-click issue but it seems like the ubuntu package still contains the old file, will fix that ...

I see. But I probably won't be able to test that properly if the mouse problem is due to VMware device drivers. Though I suppose I could whip up a VM for VirtualBox instead...

In any case I won't have time for that tonight, as I'm rather busy testing other stuff (RasPlex related).
But I should be able to squeeze it in tomorrow.

Best regards: dlanor

@bkury:
I have now made the test you requested earlier, to verify that XBMC-Frodo 12.3 also has the same mouse problem as PHT and OpenPHT when used under Ubuntu 14.04 in the same VMware virtual machine as used in my earlier testing. I also noted another bug for this XBMC version, in that it was unable to terminate itself properly when using the “Quit” command. I later verified that this is a known bug reported by others too when using this XBMC version under Ubuntu 14.04.

In order to test whether the mouse issue has anything to do with the VMware tools or device drivers I have now also created a similar VM for use with the VirtualBox emulator. For this test I started by a basic install from the Ubuntu 14.04 distribution ISO (64bit version), after which I installed the VirtualBox guest additions (needed to get a useful screen resolution) using the command:
sudo apt-get install virtualbox-guest-dkms

I then used the Ubuntu software updater to fully update the system, after which I proceeded to test XBMC 12.3, installed by:
sudo apt-get install xbmc

After launching this XBMC application and enabling its mouse/touch input, I immediately noted exactly the same bug as previously seen under VMware, indicating that this is very likely an incompatibility between XBMC-Frodo and Ubuntu, inherited from XBMC by both PHT and OpenPHT. (I also saw the same termination bug as it had under VMware, so that too is a real bug, independent of emulator.)

After these tests I decided to see if the same bug remains in the latest XBMC/Kodi version, so I installed Kodi-Helix by:
sudo apt-get install python-software-properties pkg-config software-properties-common
sudo add-apt-repository ppa:team-xbmc/ppa
sudo apt-get update
sudo apt-get install kodi kodi-audioencoder-* kodi-pvr-*

These commands installed Kodi-Helix and also killed the old XBMC version (apparently Kodi took over its settings files).
Testing this Kodi version I noted that it had no trace of the bug that afflicted XBMC-Frodo. The mouse worked fine.
(Extensively tested both with normal XBMC mode+skin and with PlexBMC+Amber in Plex mode.)

After these tests I also installed PHT and OpenPHT in the same VirtualBox VM, and verified that the mouse bug remains for them (as expected), whereas Kodi restarted in new tests still has a well working mouse.

In my opinion these tests prove that the bug is due to an incompatibility between the mouse usage of XBMC-Frodo and Ubuntu 14.04, which bug has been inherited by PHT and OpenPHT since they both include XBMC-Frodo.

I’m not sure how/if I can install XBMC-Gotham for this kind of testing, to see if it too has the same bug.
The Ubuntu install methods I found only work for XBMC-Frodo and Kodi-Helix (without explicit request for any version).
So the mouse compatibility of Gotham remains undetermined.

But if you can replace the mouse-interface code of Frodo with corresponding code from Helix, in your OpenPHT sources for Ubuntu, you should be able to fix this mouse bug. I hope this can be done without introducing any lib incompatibilities or conflicting dependencies.

Best regards: dlanor

Subscribed!

@bkury:
I have now made the test you requested earlier, to verify that XBMC-Frodo 12.3 also has the same mouse problem as PHT and OpenPHT when used under Ubuntu 14.04 ...

Thanks for testing!
 

In my opinion these tests prove that the bug is due to an incompatibility between the mouse usage of XBMC-Frodo and Ubuntu 14.04, which bug has been inherited by PHT and OpenPHT since they both include XBMC-Frodo.

But it still only affects mouse usage when running within an VM Environment, on a physical ubuntu 14.04 machine the mouse is working fine.
 

But if you can replace the mouse-interface code of Frodo with corresponding code from Helix, in your OpenPHT sources for Ubuntu, you should be able to fix this mouse bug. I hope this can be done without introducing any lib incompatibilities or conflicting dependencies.

That's not something that can be done easily and would possibly introduce even more problems and unstable code. And then there is the question: Why spending time on this? This mouse issue only shows up within VM environments and I don't think many people actively use Frodo/PHT/OpenPHT in an VM enviroment ...

The correct but much harder way to fix this (and many other PHT issues) is updating the PHT core to KODI Gotham/Helix. I thought about this before I started the OpenPHT Project but I quickly realized that this would require working 40 hours/week (fulltime) for a couple of months.

But then again, there is always the (slight) possibility that someday PLEX will release a PHT version based on gotham/helix ...

But it still only affects mouse usage when running within an VM Environment, on a physical ubuntu 14.04 machine the mouse is working fine.

I'll take your word for it, but this may also be due to differing low level drivers.
VirtualBox and VMware obviously use different low level drivers in their emulations (else one would have sued the other), and yet both suffer exactly the same symptoms. This raises the possibility that it might affect yet other low-level drivers on different hardware from the Ubuntu PCs you use. (Similar to how the PHT video routines are incompatible with some Intel video device drivers. So it works fine on most systems but fails on some.)
 

That's not something that can be done easily and would possibly introduce even more problems and unstable code. And then there is the question: Why spending time on this? This mouse issue only shows up within VM environments and I don't think many people actively use Frodo/PHT/OpenPHT in an VM enviroment ...

I agree, and I didn't intend it as any urgent request, but just as a pointer to a possible solution, if/when you might see a practical way to implement it.
 

The correct but much harder way to fix this (and many other PHT issues) is updating the PHT core to KODI Gotham/Helix. I thought about this before I started the OpenPHT Project but I quickly realized that this would require working 40 hours/week (fulltime) for a couple of months.

But then again, there is always the (slight) possibility that someday PLEX will release a PHT version based on gotham/helix ...

That probably is inevitable in the long run, but it will probably be a very long time coming...

In any case, I obviously don't plan to use a VM for my real media player needs.
I've used it now mainly because it's my only way to test OpenPHT (until you make a Windows release).

Best regards: dlanor

Has anyone had a chance yet to test the DVD support? Also, are we talking about physical dvd's or just iso's?

Has anyone had a chance yet to test the DVD support? Also, are we talking about physical dvd's or just iso's?

Eventually OpenPHT should have the same ability as standard XBMC-Frodo when it comes to DVD playback, but the same limitation as any other Plex client when it comes to playback from Plex library sections. So OpenPHT should be able to play DVD discs or files when explicitly selected, but never as part of the Plex library. This is because the PMS server is unable to scan DVD ISOs properly.

NB: The custom PMS scanner addons that were once released to allow ISO scanning (after official ISO support was dropped) should NOT be used by anyone anymore, as they lack other abilities required by the updated PMS code using the scanners. I'm one of the people who did use it, with corrupted Plex database as a result. (Had to start over from scratch... :( )

I've just tested DVD playback in OpenPHT in an OSX Yosemite VM under VMware Workstation, and while it does playback one menu sequence, it's impossible to play the main videos of this disc, as the DVD menu navigation is not working at all. (So this would only work for menu-less DVDs with auto-starting playback.)

Mouse clicks in the DVD menu screen are ignored, which matches behaviour of XBMC/Kodi which allows only keyboard/DPad control of such menus. But OpenPHT does not allow that either, since it incorrectly opens the video playback OSD menu whenever any key is pressed, so that this OSD menu 'steals' keyboard/DPad focus away from the DVD menu handling routines. This needs to be changed so that the normal playback OSD menu is disabled while a DVD menu is open, even when it technically is a case of looped video playback. XBMC/Kodi handles this correctly, so it should not be very hard to fix.

Another bug is that the menu shown is the main menu for choice of feature playback or other options, meaning that the program has bypassed the initial language choice, probably in an attempt to skip an initial copyright warning text. But that is a fatal error when the same initial language choice also controls the language used in all subsequent DVD menus. For my test case the default language when bypassing the choice was French, which I've never studied formally and can barely 'decipher'. So this bug also needs to be fixed to make it work properly, like it does in XBMC/Kodi which plays the full content of the disc, skipping nothing.

Btw: I tested the XBMC/Kodi behaviour in both XBMC-Frodo and Kodi-Helix, so these aspects are not version dependent.

I've also tried to test DVD ISO file playback, but this is not working. After selecting an ISO file the player starts, but only shows the word "Buffering..." in a huge font across the screen, with a fixed percentage number beneath it, this apparently being some buffering percentage at which the program froze/failed. For my test case of a small single-layer DVD ISO file of 2.99 GiB, the frozen number was "53%". Fortunately it is only the player/buffer which is frozen. Other aspects of the program still work, and I can back out to main menu with 'Escape' key.

I get exactly the same result whether I launch the ISO file from the "Play File" command specific to the "Night" skin or with the "Videos" command accessible when allowing XBMC library entries in the home screen configuration of the "Night" skin. (Makes sense, as both browsers should launch files in the player identically.)

Attempting to play VIDEO_TS folders does not work at all, as these are not recognized as playable.
Browsing inside a VIDEO_TS folder to launch individual VOB files does allow them to be launched, but for those of any significant size (real show eps or movies), the result is the same as for ISO files. I just get that huge "Buffering..." message with a frozen percentage number beneath it. (This time it was "63%".)

Best regards: dlanor

Personally i dont see why anyone would care about mice. PHT was designed to be navigated with a remote or a keyboard imho. No need to waste time on mice. =P

My wife has a bunch of old shows and movies on dvd that she likes to watch often and Id love to only have a single interface for that. Looking forward to when this can be a reality. Keep up the great work!

Personally i dont see why anyone would care about mice. PHT was designed to be navigated with a remote or a keyboard imho. No need to waste time on mice. =P

This project is NOT just another branch of PHT intended to work exactly like PHT does.

This project is OpenPHT, intended to work better than official PHT, by restoring XBMC functionality that PHT lost.
And that includes functional use of a mouse.

You are of course entitled to your opinion that mice are a waste of time for this kind of application, an opinion obviously based on your own preferred method of using it. But there are lots of other people with different preferences, and I see no reason why the application should be limited to just one method of usage.

The current OSX version of OpenPHT does work fine with mouse control, and according to bkury it works equally well with a physical Ubuntu system. So apparently it's only the VM Ubuntu systems (both VMware and VBox) which suffer from the problems I reported earlier, and on that score I agree that it would be a waste of time to focus any development effort on that particular issue. But that does not modify my opinion about mouse being a useful interface for this application. It's just that the VM usage of it is too 'narrow' in scope to warrant development focus.

Edit:
I just realized that your post may have referred only to my most recent post, and the failure of a mouse to influence a DVD menu being played by OpenPHT. But that is an entirely different case. For that case I accept the limitation of using only keyboard to manipulate the DVD menu, but unfortunately that also fails with the current OpenPHT version, because of the OSD menu that steals input focus, so that the DVD menu handler never receives the keyboard input.

Best regards: dlanor

Chiming in to say I too look forward to the Windows client as well as Live TV functionality.

Setup OpenPHT today and really love the customisation and features and can't wait to experiment more to try and get Live TV through there too.

Only issue I have so far is that my Apple Remote has no effect on OpenPHT even though I have it setup correctly.  Regular PHT has no problems with the remote.  Is this a known bug? And does anyone know of a workaround or fix? I exclusively us the Apple Remote to control it so losing the Remote functionality would be a deal breaker for me.

Only issue I have so far is that my Apple Remote has no effect on OpenPHT even though I have it setup correctly.  Regular PHT has no problems with the remote.  Is this a known bug? And does anyone know of a workaround or fix? I exclusively us the Apple Remote to control it so losing the Remote functionality would be a deal breaker for me.

That's weird, I don't see a reason why the apple remote won't work but I will take a look. Does anybody else experience the same problem?

General Update:

I didn't have that much time to work on it but I'm still making some progress and I already fixed some issues. Unfortunately adding back addons support (python) for windows is much more annoying than I initially thought, so it will take me some more time to get it working. I will release an update as soon as I have a working windows client ...

always appreciate any update. I’m curious what kind of skin support your openPHT build will have. will we be able to use any of the current PHT skins or will they have to be modified in some way to support the added functionality?

always appreciate any update. I'm curious what kind of skin support your openPHT build will have. will we be able to use any of the current PHT skins or will they have to be modified in some way to support the added functionality?

Well, basically any plex compatible skin will also work with OpenPHT and because most custom PLEX skins are ported from XBMC they should already come with xml files to support most of the additional features like addon info, weather, ... 

But of course there are some small code changes necessary to support certain features, e.g. display additional menu entries like "Play DVD, Weather, Addons", so it really depends if a skin author is willing to add support for it.

Very exciting project!  Thanks for doing it.

Will there be an Openelec version of it in the future?

One of the most exciting things being worked on in Kodi for me is emulation.  Might be a year or two away from being merged into the main build, but it is still something I'm watching with excitement.  And your Open PHT project gives me hope that this exciting feature will make its way to Plex. 

Again, thanks!  Keep up the great work!

"One of the most exciting things being worked on in Kodi for me is emulation."

Sorry if this is a dumb question, but "emulation" of what?

Snes nes genesis etc :slight_smile: i think.

Will there be an Openelec version of it in the future?

If the demand is there, I don't see a reason why not.
 

One of the most exciting things being worked on in Kodi for me is emulation.  Might be a year or two away from being merged into the main build, but it is still something I'm watching with excitement.  And your Open PHT project gives me hope that this exciting feature will make its way to Plex.

It's not exactly a built-in solution but for now you could use/test the addon "ROM Collection Browser" to do that kind of stuff.