@Massaguana said:
Are the skin’s still updated via oPHT? because it looks like this feature don´t work…
Default OpenPHT Skin, Black Edition, and Aeon Nox are all updated in-app. It is working but we’ve had some reports of inconsistency with the skin updater, which is being looked into. Try rebooting a couple times as the skin update version check will happen on the boot up.
Current Skin Versions available are:
Aeon Nox 5.2.3
OpenPHT 1.7.1
Plex - Black Edition 16.11.24
@benjaminwolf said:
Default OpenPHT Skin, Black Edition, and Aeon Nox are all updated in-app. It is working but we’ve had some reports of inconsistency with the skin updater, which is being looked into. Try rebooting a couple times as the skin update version check will happen on the boot up.Current Skin Versions available are:
Aeon Nox 5.2.3
OpenPHT 1.7.1
Plex - Black Edition 16.11.24
I use the black edition and it did not auto update. I manually updated as the old version was not displaying settings or recently added properly after the update to 1.7.1.
Also keep up the good work on OpenPHT. Having PlexPass means I can try the new PMP but I find OpenPHT to be easier to use and much better layout (who thinks 2 rows of tv/movies/music is acceptable on a TV - big enough my neighbours could probably read the covers).
@benjaminwolf said:
@vago34 said:
I would be extremely grateful if a .tar file of the embedded version could be made available. You’ve provided me with these in the past [forums.plex.tv/discussion/216102/dual-boot-with-chrome-os-and-openpht-on-hp-chromebox#latest]) , and this way is the only way I have to be able to upgrade.Which version did you end up using? The generic or the Nvidia legacy?
I used the generic. Thank you so much!!
@vago34 said:
@benjaminwolf said:
@vago34 said:
I would be extremely grateful if a .tar file of the embedded version could be made available. You’ve provided me with these in the past [forums.plex.tv/discussion/216102/dual-boot-with-chrome-os-and-openpht-on-hp-chromebox#latest]) , and this way is the only way I have to be able to upgrade.Which version did you end up using? The generic or the Nvidia legacy?
I used the generic. Thank you so much!!
You’re welcome, I think? Did you get the 1.7.1 TAR file you needed or do you still need it?
I had problems with Black skin updating. I followed the advice above to reboot a couple of times and it did indeed update to the latest version. Brilliant!
I apologize if this has been addressed already but with version 1.7.1, I can no longer use custom keymaps using Eventghost.
I have the buttons “O” for on screen menu, “S” for subtitle toggle, “T” for audio track toggle mapped to my Rosewill remote. These functions have worked beautifully with my eventghost script that i’ve run for years and through many versions of PlexHT and now OpenPHT, but with this latest version, they no longer work.
If I push the button mapped for “O”, it seems like each command is recognized twice or something, because the menu will pop up and quickly disappear. Same thing with “S” and “T”.
@SN6941 said:
I apologize if this has been addressed already but with version 1.7.1, I can no longer use custom keymaps using Eventghost.I have the buttons “O” for on screen menu, “S” for subtitle toggle, “T” for audio track toggle mapped to my Rosewill remote. These functions have worked beautifully with my eventghost script that i’ve run for years and through many versions of PlexHT and now OpenPHT, but with this latest version, they no longer work.
If I push the button mapped for “O”, it seems like each command is recognized twice or something, because the menu will pop up and quickly disappear. Same thing with “S” and “T”.
So if I understand this software correctly, you’re running on a Windows box? And EventGhost intercepts the IR command on the windows box, then maps the signal to a corresponding keyboard command?
@SN6941 said:
I apologize if this has been addressed already but with version 1.7.1, I can no longer use custom keymaps using Eventghost.
OpenPHT v1.7+ is now using port 9777 instead of port 9778 for remote/events. I don’t know your exact setup but make sure that your eventghost config and scripts are using the correct “new” port.
I’m using OpenPHT on Windows, and when I start up the application the PIN box for the users don’t line up correctly like they did before. This is an issue with both the OpenPHT 1.7.1 and the Plex Black Edition 16.11.24 skin.
Thanks a lot for the brilliant work. Just a short question, any chance of implementing Kodis subtitle engine. Everything else works great with OpenPHT (I’m on Windows) and Plex now but the subtitle matching is utterly useless. I use the subzero addon as a compliment to the normal Plex one and end up with 4 subtitles witch more often than not is all wrong.
@Vuzrak said:
I’m using OpenPHT on Windows, and when I start up the application the PIN box for the users don’t line up correctly like they did before. This is an issue with both the OpenPHT 1.7.1 and the Plex Black Edition 16.11.24 skin.
This is a known phenomenon. It has no impact on functionality, so I hesitate to call it an ‘issue’, but it’s been reported.
@Ceril said:
Thanks a lot for the brilliant work. Just a short question, any chance of implementing Kodis subtitle engine. Everything else works great with OpenPHT (I’m on Windows) and Plex now but the subtitle matching is utterly useless. I use the subzero addon as a compliment to the normal Plex one and end up with 4 subtitles witch more often than not is all wrong.
You can always post a feature request on the github site. The team may or may not implement it in the future.
@samplex said:
Is the eMMC Module for Odroid C2 now supported?
I just booted my Odroid C2 from the emmc, so it appears so. 
@benjaminwolf said:
@vago34 said:
@benjaminwolf said:
@vago34 said:
I would be extremely grateful if a .tar file of the embedded version could be made available. You’ve provided me with these in the past [forums.plex.tv/discussion/216102/dual-boot-with-chrome-os-and-openpht-on-hp-chromebox#latest]) , and this way is the only way I have to be able to upgrade.Which version did you end up using? The generic or the Nvidia legacy?
I used the generic. Thank you so much!!
You’re welcome, I think? Did you get the 1.7.1 TAR file you needed or do you still need it?
Nope I still need it. I was just thanking you in advance
@benjaminwolf said:
@SN6941 said:
I apologize if this has been addressed already but with version 1.7.1, I can no longer use custom keymaps using Eventghost.I have the buttons “O” for on screen menu, “S” for subtitle toggle, “T” for audio track toggle mapped to my Rosewill remote. These functions have worked beautifully with my eventghost script that i’ve run for years and through many versions of PlexHT and now OpenPHT, but with this latest version, they no longer work.
If I push the button mapped for “O”, it seems like each command is recognized twice or something, because the menu will pop up and quickly disappear. Same thing with “S” and “T”.
So if I understand this software correctly, you’re running on a Windows box? And EventGhost intercepts the IR command on the windows box, then maps the signal to a corresponding keyboard command?
yes, I am running it on an Intel NUC with Windows 7
@bkury said:
@SN6941 said:
I apologize if this has been addressed already but with version 1.7.1, I can no longer use custom keymaps using Eventghost.
OpenPHT v1.7+ is now using port 9777 instead of port 9778 for remote/events. I don’t know your exact setup but make sure that your eventghost config and scripts are using the correct “new” port.
Do you know exactly where in eventghost I need to make this port setting change? Would you like me to post my script?
@greekislandlover said:
I had problems with Black skin updating. I followed the advice above to reboot a couple of times and it did indeed update to the latest version. Brilliant!
I am also having trouble with Black Edition updating. It shows v.16.06.13. I restarted OpenPHT many times and also rebooted my server a few times, but had no luck. Is there a way to trigger a skin update manually? Thanks!
@SN6941 said:
@benjaminwolf said:
@SN6941 said:
I apologize if this has been addressed already but with version 1.7.1, I can no longer use custom keymaps using Eventghost.I have the buttons “O” for on screen menu, “S” for subtitle toggle, “T” for audio track toggle mapped to my Rosewill remote. These functions have worked beautifully with my eventghost script that i’ve run for years and through many versions of PlexHT and now OpenPHT, but with this latest version, they no longer work.
If I push the button mapped for “O”, it seems like each command is recognized twice or something, because the menu will pop up and quickly disappear. Same thing with “S” and “T”.
So if I understand this software correctly, you’re running on a Windows box? And EventGhost intercepts the IR command on the windows box, then maps the signal to a corresponding keyboard command?
yes, I am running it on an Intel NUC with Windows 7
Check your debug log to see if EventGhost is sending them twice. You may want to replicate the issue with debug on and upload your OpenPHT logs here so we can look at it.
@SN6941 said:
@bkury said:
@SN6941 said:
I apologize if this has been addressed already but with version 1.7.1, I can no longer use custom keymaps using Eventghost.
OpenPHT v1.7+ is now using port 9777 instead of port 9778 for remote/events. I don’t know your exact setup but make sure that your eventghost config and scripts are using the correct “new” port.Do you know exactly where in eventghost I need to make this port setting change? Would you like me to post my script?
This would only apply if you were sending commands via the builtin event listening server and not just sending a virtual keystroke on the same machine running OpenPHT.
@“Christopher Rung” said:
@greekislandlover said:
I had problems with Black skin updating. I followed the advice above to reboot a couple of times and it did indeed update to the latest version. Brilliant!I am also having trouble with Black Edition updating. It shows v.16.06.13. I restarted OpenPHT many times and also rebooted my server a few times, but had no luck. Is there a way to trigger a skin update manually? Thanks!
As a temporary measure, try turning on: SYSTEM SETTINGS > NETWORK > ADVANCED NETWORK SETTINGS > Wait for network before starting OpenPHT
If that doesn’t work, you could try manual installation. You’ll need to check the relevant skin sub-forum for availability outside the auto-updater.
Thank you, @benjaminwolf!
I opened OpenPHT and got a notification about a theme auto-update. The new theme was activated by switching to the “Black Edition (Updated)” theme, which then replaced the old Black Edition.
