Navi-X Showtime PS3 Media Player Plug-in Update v1.0 Out Now


88w ago - Following up on his previous update, this weekend PlayStation 3 homebrew developer facanferff has updated his Navi-X Showtime PS3 Media Player Plug-in to version 1.0 followed by v1.0.5 and v1.1.5 for Showtime PS3 Media Player with the changes below.

Download: Navi-X Showtime PS3 Media Player Plug-in Update v1.0 / Navi-X Showtime PS3 Media Player Plug-in Update v1.0.5 / Navi-X Showtime PS3 Media Player Plug-in Update v1.1.5

To quote: This update is a major release, it is the biggest update I ever released for a plugin for Showtime, and that being said is recommended that every user update to this new version.

Changelog v1.0.5:

  • Add: Allow user set the source for playlist search in settings
  • Add: New default source for playlist search (in TMDB View)
  • Add: Support for IMDB Lists
  • Add: Search for entries from Item Menu
  • Add: Stats system
  • Fix: IMDB's Parents Guide would not show up
  • Fix: Parser PLX would join the last two items of a playlist wrongly
  • Enhacement: Improve reporting system

Changelog v1.0:

General:

  • Add: Allow user to disable History Tracking
  • Add: Notifications for important things (such as reporting)
  • Fix: User would be logout after forced reload
  • Enhancement: Use notifications instead of messages that require user interaction

Playlists:

  • Add: Set number of elements in X axis (see note 1)
  • Add: Set number of elements in Y axis (see note 1)
  • Add: Allow user to hide information bar (see note 1)
  • Add: Store items in local Favorites playlist (see note 2)
  • Add: Playlists with IMDB/TMDB type redirect to TMDB view
  • Add: Support for subtitles in playlists
  • Fix: Entries with no title would fail to load page in PS3 platform
  • Fix: Titles with colors would be wrongly parsed
  • Enhancement: Set view in playlists upon entrance to avoid "screen transformation"

Processors:

  • Add: Report processors that don't work
  • Add: Display current status of processing (including countdown timer)
  • Add: Cache processors that have cacheable flag equal to 1
  • Add: Nested if statements
  • Fix: Subvariables in which the main class didn't exist would return error when trying to get it's result

Speed:

  • Enhancement: Improve plugin startup response time
  • Enhancement: Improve response time when browsing

TMDB:

  • Add: TMDB View (see note 2)
  • Add: Trailers
  • Add: Similar Movies
  • Add: Search in several networks for a movie
  • Add: Get Full Cast of a movie
  • Add: Get Full Crew of a movie
  • Add: Get movies in which a person appeared in the cast
  • Add: Use IMDB variable in PLX playlists to identify a movie
  • Add: Use TMDB variable in PLX playlists to identify a movie
  • Add: IMDB's Parents Guide

User Account:

  • Add: Save playlists IDs for user in local store
  • Enhancement: Use local History/Favorites playlist instead of online solution
  • Fix: When adding an item to a playlist that contained that item already, it would add again the item making it twice -> Remove the old one and add the fresh one
  • Fix: My Playlists

Note 1: These features are present in the Page Menu that can be accessed via Triangle (PS3) or F1 (PC).
Note 2: These features are present in the Item Menu that can be accessed via Square (PS3) or F3 (PC) after focusing the item to see the features relative to.

A quick look in the new views

As you might have seen in the changelog, this version features a new look for list view, it is possible due to a recent feature that lets plugins have their own view files (the way Showtime uses to show the GUI), it means this view is a custom view and not from Showtime's source code, it has been developed by myself using as model some mockups from opium2k and the guidance of andoma in terms of widgets available.

One other biggest new feature is the new exclusive TMDB View, it allows you get a list of persons in the cast/crew of the movie, a list of trailers that redirect to Youtube plugin, a list of movies in the collection, a list of similar movies, search for entries in one page provided as Search in Navi-X googlecode that you may use to get access to videos like Behind the Scenes and others of the movie, and finally access to IMDB's Parents Guide for the movie, perfect to help build up nice nights plans for all family.

Requirements

  • Showtime v3.99.448

Installation:

1. If you have one of the latest Showtime version (as required by the plugin) and installed previously the previous plugin it should be updated to the newest version once andoma updates the plugin repository with the new version.
2. Access the Plugin Central inside Showtime to install the plugin.
3. Put the zip archive available (linked above) in the directory /installedplugins/

Special thanks to (Alphabetically):

  • Andreas Oman (also known as andoma), for creating and maintaining the best alternative to XBMC
  • Opium2k, for creating mockups of both Array and TMDB views that ended being improved to the current state of them
  • Tyrant, for Beta Testing the plugin as the development happened and for giving ideas in what could be added/improved

FAQ

How can I log in to navixtreme.com?
In settings page of the plugin there should be an option that says "Login to navixtreme.com" click that. If you used before the previous version of the version and logged in and set to remember the credentials, this process will automatically use that information and adapt to the new authentication method otherwise you'll have to write your credentials. After doing this you never need to click this option again, just by starting Showtime with the plugin enabled will authenticate you.

Where can I find facanferff, andoma, opium and Tyrant?
In the channel #showtime on irc.efnet.net.

What happens to my automatic reports the plugin creates?
If you have the setting for it enabled, once you find a processor not working (generally giving a message starting with "Processor error: "), the plugin will call immediately a website hosted by the plugin's developer that might use the URL, processor and error to debug the problem and fix if it applies. If you want to get information on the current status of a report contact facanferff (via the channel mentioned in this FAQ) and provide your user id and the report id.

The user id is what identifies an installation, it consists of a mix of alphanumeric character followed by your nickname if you're authenticated there. You may see your user id at the folder /settings/jsstore/navi-x-tracking_settings and locate the line that starts by saying "user_id" and the value between double quotes in the right side of is your user id. But if you're authenticated then in the same file you should find a line for the variable "username", so your final user id will be the previous string you obtained plus 1 underscore plus your username, e.g. 1234567890_qwert

The report id is a string that identifies a report and is unique per report, to obtain that value access the navi-x-reports_ids in the same folder as before and locate the line that contains in left side _, the string attached to it is the report id.

If you want to contact the developer to get the status of the report and if you know that the report is for a processor that was reported only that time you may just provide your user id and processor name.

Which reports get a higher priority?
The reporting system sets automatically a priority checking the url and processor in the test bed, if in that test it has success then it is given High priority. If the test also gives an error but different than the one you obtained, it will be given a Medium priority, otherwise it is given Low priority.

I'm a developer and would like to know about those exclusive features of the plugin's API, where may I find those information?
Shortly after the release of this version, facanferff will release a tutorial explaining all of those exclusive features.

I would like to report or suggest about something not related directly to processors, where can I do it?
You should use the official Bug Tracker website for the plugin available (at lonelycoder.com/redmine/projects/navix) You don't need to provide your user id here.

Note: Reporting non working processors in this Web site will not give you a higher priority.

v1.1.5 Changelog:

After the release of Showtime Plugin TMDb v1.2.5, a new update to Showtime Plugin Navi-X is now available.

This version brings a new settings option that many users have been asking to set a new home page URL. This setting allows you to use your own PLX playlist or other PLX playlist without having problems with time-out that have been rather frequent with navixtreme.com

Changelog

  • Add: Setting option "Home Page URL" that allows user to change home page URL
  • Add: All items that are from navixtreme.com are labelled as so with "[NAVIXTREME]"

Thanks

  • andoma: for creating and maintaining Showtime
  • Tyrant: for Beta Testing my plugins

Special information

To allow a faster boot time of Showtime you may need to disable login in plugin's Settings.

Installation

Any Showtime v4.3.9 can find the update at Plugin Central.








Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!

Comments 543 Comments - Go to Forum Thread »

Quick Reply Quick Reply

PS3 News's Avatar
#533 - PS3 News - 18w ago
Following up on the previous updates, today PlayStation 3 homebrew developer Andreas Oman updated the Showtime PS3 Media Player testing builds alongside some MultiMAN PS3 PKG updates by deank with details below.

Download: showtime-gh-4.3.576-gb49e21c4.pkg / showtime-4.3.576-gb49e21c4.pkg / showtime-4.3.576-gb49e21c4.self / Showtime 04.03.582 [CEX].pkg / Showtime 04.03.582 [DEX].pkg / showtime-gh-4.2.pkg / showtime-4.2.pkg / showtime-4.2.self / Showtime-4.3.601-g7b1aca53.pkg.471.v4.3.601.pkg

v4.3.576 & Recent Changes

ps3: Fix bug in litecoin miner causing it to be a lot less efficient than it should be
ps3: Relax memory warning thresholds a bit. Now that we use TLSF it's much less of a problem
stos: sync() after critical writes to disk
Fix crash in UPNP code Fixes #1773
js: Add support for plugins to set cookies directly
ps3: Add a miner
Transfer Copyright to Lonelycoder AB
prop: Disable prop subscription stats
prop: Redeuce memory usage by reusing compile time strings during prop symlinking
prop: Correctly handle settings of a PROP_DIR to some other value
glw/view: Improve trace() function a bit
prop/core: We must use prop_ref_dec_locked() when prop_mutex is held Fixes #1797
ps3: Make it possible to edit discovered FAT and HDD sources from settings
ps3: Add NTFS support
httpclient: Fix broken cookie domain validation Fixes #1794
Add so called 'managed services'
Huge rework of prop tree symbolic links
Add missing title and contents for network discovered services
Add str_cleanup() helper
ps3: Add some mutex debug helpers
Update fr_FR.lang
Update it_IT.lang
glw: Fix problem when assigning 'args' attribute with a non-prop p Fixes #1776

From aldostools: Build 4.3.582 has two important changes since 4.3.576:

ps3: Fix bug causing NTFS drives not being able to be remounted
ps3: Show CPU and RSX temperature in sysinfo (Press L3 to view)

For more details: github.com/andoma/showtime/commits/master

From deank: I compiled showtime 4.3.582 for mM... It is available in the WEB column of multiMAN and also from the VIDEO column -> Update. Standalone versions are in the web column.

Update: v4.3.601 Testing Changelog:

subtitles/sub: Watch out for division by zero
glw: Fix minor memleak (one per glw session)
Fix play/pause issues
glw: Rework how we auto-rescale UI
audio: Fix invalid assert()
ftpserver: Add support for "OPTS UTF8 ON/OFF" and report is as a FEATure
Resolve prop for track in playqueue
audio: When flushing pipeline we must also flush resampler
builtin-osk: Add '@' character and close when user press back/exit button
Drop shoutcast support
httpserver: Send encoding as UTF-8 in various places
Fix 'use after free'
miner: Drop debug info
ps3: Fix bug causing NTFS drives not being able to be remounted.
ps3: Show CPU and RSX temperature in sysinfo (Press L3 to view)

More PlayStation 3 News...

PS3 News's Avatar
#532 - PS3 News - 20w ago
Following up on the previous update, today PlayStation 3 developer facanferff has made available a Quickstart to PS3 Plugin Development in Showtime with details below.

To quote: Since a long time ago, some users have requested me to write a tutorial so they could create their own Showtime plugins. This is an initial attempt to it, I hope you like. If I make some mistake, I'm sorry, I'm not a teacher.

Overview

Before we get our hands dirty, it’s important to explain some little things that might help you later in making your own plugins. Plugins for Showtime (also known as Apps) are exclusively written, at the moment, in Javascript. To bring plugins to life, Showtime uses a Javascript engine called Spidermonkey (as of now, Showtime uses Spidermonkey 1.8.0-rc1). To learn more about this engine, you may go to developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey.

If you ever did web development, you may wonder if the Javascript API that work in normal web browser might work here, well, the answer is no. Due to this, you will not find things like DOM or AJAX in your toolbox, but you may and should use the basic Javascript.

In this quickstart, I will assume the reader has good understanding of Javascript. If you don’t know it, you may check the several resources available online/offline. From these, I recommend check this: codecademy.com

The Showtime plugins’ job is to respond to browse and search requests and populate the internal data model with the actual information to be shown to the user via Showtime’s user interface(s).

Since there are different types of plugins, I will focus in this tutorial in only a type, plugins that browse content in the web and show it to user (e.g. Youtube plugin).

Structure of a plugin

Every plugin lives in a directory of their own. From the several files this directory may have, you need to have at least one file in the root of the plugin, plugin.json, which contains information about the plugin and the author. You may use sub-directories and custom names for other files in order to organize it better.

plugin.json

plugin.json is a JSON (json.org) encoded text file containing information about the plugin and its author. Example of a plugin.json file (from the Channel9 plugin):

Now it’s time to learn more about each field and which ones are required for every plugin:

Getting Started

To run a plugin in a development environment, you may call from a terminal:

The flag –p means that you want to load a plugin in development environment.

If you ran this already, you might get the following error: This will output something like: plugins [ERROR]: Unable to load development plugin: testplugin Unable to load testplugin/plugin.json -- File not found. This means or we don’t have a testplugin directory or we don’t have a plugin.json inside it. To create the directory do:

Now, to edit the plugin.json, open the file testplugin/plugin.json in any text editor that you like.
In there, let’s make our initial plugin.json:

With this, we specified that the plugin testplugin uses Javascript engine, has an ID ‘testplugin’ and the script is ‘testplugin.js’.

Whenever you want to reload the plugin you can use Shift+F5 in Showtime. This is helpful when you make changes to a plugin already in development environment inside Showtime, without the need of restarting Showtime. Even if the plugin gave an error, you may use this to try to reload it. When you reload it, all hooks and resources associated to the plugin are removed. This phenomenon happens also when a user removes a plugin from Showtime.

In case you are already in a page that belongs to the plugin itself, Showtime will reload the plugin and reload the page itself.

Now open your testplugin/testplugin.js in a text editor. Since we want to have a plugin that lives forever (so it can be called anytime) we need to have a scope where all local variables will live and also need to remember ‘this’ which is, when the script is invoked, a plugin object created by Showtime itself (showtimemediacenter.com/projects/showtime/wiki/JSAPI_plugin).

So, let’s edit this file:

Reload the plugin now with Shift+F5, if you look in the terminal windows from which you opened Showtime, you will find a line saying ‘Hello, Showtime XXX’ where XXX is your current Showtime version that was obtained via showtime.currentVersionString .

Routing an URI to the plugin

Since our plugin will respond to browse requests we need to have an URI associated to it. An URI is something like a URL you use to browse the Internet, but in this case it is used to browse in Showtime. Every plugin reservers URI space starting with the plugin’s ID specified in plugin.json. These URI routes registered by plugins have higher priority than URI routes that Showtime itself handles, so you can create an URI route like it is in a web browser (e.g. youtube.com)

With this new knowledge let’s make it in use (edit it to match this code):

Now, reload the plugin and if you type “testplugin:hello” in the search input field on Showtime’s home page, you will notice Showtime will open a new page with only a loading symbol, but in the terminal it will show the message provided to showtime.print.

A look in a real plugin

For this tutorial, I decided to use a real plugin made by me, which is called Videocopilot. The plugin source is located at github.com/facanferff/showtime-plugins/tree/master/videocopilot and its a plugin for Web site videocopilot.net.

I will not discuss the plugin.json of the plugin (https://github.com/facanferff/showti...ot/plugin.json) in this tutorial.
The lines of code or numbers of line are relative to version 0.9 (the most updated version at this moment).

Lets see then the plugin script (github.com/facanferff/showtime-plugins/blob/master/videocopilot/videocopilot.js).

To make Showtime provide a link in home page to the plugin’s start page we need to create a service:

Lets check each argument given to plugin.createService:

  • 1st: “Video Copilot” is the display name of the service
  • 2nd: PREFIX (which is a global variable specified as “videocopilot” + “:start” is the initial route of the service (the URI where is located the home page of the plugin)
  • 3rd: “video” tells Showtime this plugin provides video resources
  • 4th: true means the service should be enabled immediately, making it visible to user and
  • 5th: plugin.path (gives you the full path to the plugin’s root directory) + “logo.png” is the path to an image that identifies the plugin.

Since we registered the home page’s URI route, we need to specify what does that URI route:

Here, plugin.addURI registers a new URI route, in this case called “videocopilot:start” and startPage is the function to be called when this route is open by user request. The function provided to addURI should accept at least one argument, where the 1st one is a page object created by Showtime and used to manipulate the page.

function startPage:

Here, page.appendItem will append a new item to the current page. Lets see the arguments:

  • 1st: PREFIX + ':browse:' + escape('http://www.videocopilot.net/tutorials/') + ':undefined' , is the URI route that should be called when the user clicks this item
  • 2nd: type of item, from the several ones, the most used are: directory, used to specify this item will open a new page to browse contents; and video that specified this item will open a video resource
  • 3rd: metadata for the item, you may provide any information about this item as you want. The most used are: title, title of the item; icon, image to be shown associated to the item; description, a description of the item

Means this page is a directory to browse content.

Tells Showtime that the contents of this page are “items”, in most cases, you want to use this one, we will use it for this tutorial.

Tells Showtime that we don’t want anymore the loading symbol to be shown to user.

Function getVideoList:

Here, showtime.httpGet is a function you may call to do a GET request to a page (e.g. to obtains its source code) and .toString() is to convert its response to a Javascript String to manipulate.

plugin.addURI(PREFIX + ":video:simple: (.*)", function(page, link):

This is a Javascript object where we specify only the title of a video (displayed in video playback) and sources is an array where each object contains at least the url (e.g. the video’s url).

Here, page.source is the way to tell Showtime what we want to reproduce. Since we want to play a video we need to put always “videoparams:” before the parameters of video as specified before encoded in a JSON string.

This finally tells Showtime we have a video, so Showtime can handle everything to prepare video playback.

This function is used to add continuously items to a page. In the current version of the tutorial, I will not explain this, so whenever you want to show more items (e.g. of a second page) use page.appendItem and pass what you need.

This function adds a searcher to Showtime that can be used when a user searches for something (not a URI route) in search input field in Showtime’s home page. This function accepts 3 arguments:

  • 1st: title of the searcher, shown to user when searching something
  • 2nd: image of the search, also shown to user
  • 3rd: function that receives a page and query arguments (page is the same as specified before in the tutorial and query is a string containing what to search). This function is runs always whenever a user searches for something.

Note: In the function passed to plugin.addSearcher you need to specify somewhere the number of found entries via page.entries, otherwise Showtime will not show your searcher to user for that query.

I recommend you study carefully the code at: github.com/facanferff/showtime-plugins/blob/master/videocopilot/videocopilot.js

Publishing plugins

You may check showtimemediacenter.com/projects/showtime/wiki/SPMC for all details about it.

Bibliography

showtimemediacenter.com/projects/showtime/wiki/PluginDevelopment (maintained by Andreas Oman (andoma), Fábio Ferreira (facanferff) and Leonid Protasov (lprot))

Thanks

andoma: for creating Showtime

Final notes

I hope, you learned a little about plugin development in Showtime with this small tutorial. This tutorial is far away from being finished, I just wanted to give you an initial overview to the process of creating plugins for Showtime.

With a look in a real plugin, I believe you have now the fundamental tools to study better existing plugins and create new plugins. Whenever I can, I will try to update this tutorial to make it more complete and easier to understand.

For a reference of the functions Showtime provides I recommend you check showtimemediacenter.com/projects/showtime/wiki/JSAPIREF

And to conclude I leave here a screenshot of plugin TMDb so you can see the potential you can get from a plugin (below).

I hope you liked, facanferff.

More PlayStation 3 News...

B0rm0t0s's Avatar
#531 - B0rm0t0s - 27w ago
wow, amazing

PS3 News's Avatar
#530 - PS3 News - 27w ago
Following up on the previous updates and his Haider ENG2AR (Arabic) v1.03 PS3 CFW 4.46, this weekend PlayStation 3 developer Haider.Kiara has made available Showtime Arabic with details below.

Download: Showtime Arabic by haider.rar / Convert Sub arabic srt for ps3.rar

To quote: Hi all. Today I finished translation Showtime with some features

Features

  • added arabic language
  • support arabic subtitle (.srt)
  • added EarthLink TV (Only In Iraq)

Channels

  • Asian Series
  • Arabic Movies
  • EarthToon
  • Documentary
  • TV Shows Drama
  • TV Shows comedy
  • Sports (1,2,3,4,5,6,7,8,9,10)

Tutorial

How to convert .srt arabic to play on ps3 (you need use showtime above):





More PlayStation 3 News...

msteffes's Avatar
#529 - msteffes - 32w ago
I can play mkv file on my ps3 I have CEChH01 and also CECHK01, CECHL01 they all play them. I wish i coud get XBMC on the ps3 as a media player.













Affiliates - Contact Us - PS3 Downloads - Privacy Statement - Site Rules - Top - © 2014 PlayStation 3 News