Page 54 of 55 FirstFirst ... 44452535455 LastLast
Results 531 to 540 of 544

  1. #531
    Forum Moderator PS3 News's Avatar
    Join Date
    Apr 2005

    Showtime Arabic PS3 Media Player by Haider Kiara is Now Available

    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

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

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


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

    Showtime Arabic PS3 Media Player by Haider Kiara is Now Available

    Showtime Arabic PS3 Media Player by Haider Kiara is Now Available

    More PlayStation 3 News...

  2. #532
    Contributor B0rm0t0s's Avatar
    Join Date
    Oct 2013
    wow, amazing

  3. #533
    Forum Moderator PS3 News's Avatar
    Join Date
    Apr 2005

    Quickstart to PS3 Plugin Development in Showtime by Facanferff

    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.


    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

    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:

    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 is a JSON ( encoded text file containing information about the plugin and its author. Example of a plugin.json file (from the Channel9 plugin):
            "type": "javascript",
            "id": "channel9",
            "file": "channel9.js",
            "showtimeVersion": "3.2",
            "version": "1.3",
          "category": "video",
         "homepage": "",
            "author": "Fábio Ferreira",
            "title": "Channel9",
            "icon": "logo.png",
            "synopsis": "Channel 9 – Videos from Microsoft",
            "description": "<p>Videos about the products from Microsoft.<p>"
    Now it’s time to learn more about each field and which ones are required for every plugin:
    type (REQUIRED): Type of plugin, currently only "javascript" is supported.
    id (REQUIRED): Unique identifier for a plugin. The IDs are assigned by the Showtime project. Any ID starting with the string "test" is reserved for development and can be used by plugin developers until a final ID has been assigned. The assigned IDs will be ASCII lowercase. To get an ID please mail andreas AT
    file (REQUIRED): Name of the file that contains the plugin script. Generally it’s a good idea to name it the same as the plugin ID.
    title (RECOMMENDED): Short title of the Plugin that is shown in home page, Plugin Central and some other places to identify the plugin. If omitted, the plugin ID (‘id’ field) will be used, but try to avoid this since it affects the user experience (plugins with lowercasing letters, etc.)
    showtimeVersion (RECOMMENDED): Minimum version required of Showtime for this plugin to work. If the current version of Showtime is less than this version the user won't be able to install the plugin but will be notified about what version of Showtime is required. The same goes if a plugin is updated and the new version requires a newer version of Showtime. Then the user will be refused to upgrade the plugin. If this field is omitted Showtime will assume the plugin works on all versions of Showtime.
    Note: If you install some plugin manually (e.g. moving the zip archive) and your Showtime version is lower than the specified in this field, the plugin will not show up.
    version (RECOMMENDED): Version of the plugin. If this does not match the current installed version of a user's plugin the user will be presented with the possibility to upgrade the plugin. If the field is omitted Showtime will set the version to "Unknown"
    category (RECOMMENDED): Category of the plugin. If the field is omitted Showtime will set the category to "Unknown". Following categories are known:
    "TV" - online TV
    "video" - streaming video
    "glwview" - UI extentions
    "subtitles" – subtitles
    Note: This quickstart is specific to “video” only.
    synopsis (RECOMMENDED): A short one line summary of the plugin or the service it accesses
    author (OPTIONAL): Plugin developer. Any UTF-8 characters is valid.
    homepage (RECOMMENDED): A URI with the location of the plugin homepage
    icon (OPTIONAL): Path to plugin icon. The path is relative to the plugin root directory. If no icon is available Showtime will use a placeholder image instead. Note: In general, use an icon as it helps user identify easily your plugin.
    description (OPTIONAL): Long rich-text formatted description of the plugin.
    Getting Started

    To run a plugin in a development environment, you may call from a terminal:
    build.linux/showtime -p testplugin
    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:
    mkdir testplugin
    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:
      "type": "javascript",
      "file": "testplugin.js",
      "id": "testplugin" 
    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 (

    So, let’s edit this file:
    (function(plugin) {
      showtime.print("Hello, Showtime " + showtime.currentVersionString);
    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.

    With this new knowledge let’s make it in use (edit it to match this code):
    (function(plugin) {
      // Add a URI route and a corresponding function to be invoked
      plugin.addURI("testplugin:hello", function(page) {
        showtime.print("I was called");
    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 and its a plugin for Web site

    I will not discuss the plugin.json of the plugin ( 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 (

    To make Showtime provide a link in home page to the plugin’s start page we need to create a service:
    var service = plugin.createService("Video Copilot", PREFIX + ":start", "video", true, plugin.path + "logo.png");
    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:
    plugin.addURI(PREFIX + ":start", startPage);
    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:
    page.appendItem(PREFIX + ':browse:' + escape('') + ':undefined', 'directory', { title: 'All Tutorials' });
    Here, page.appendItem will append a new item to the current page. Lets see the arguments:
    • 1st: PREFIX + ':browse:' + escape('') + ':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
    page.type = "directory";
    Means this page is a directory to browse content.
    page.contents = "items";
    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.
    page.loading = false;
    Tells Showtime that we don’t want anymore the loading symbol to be shown to user.

    Function getVideoList:
    var data = showtime.httpGet(url).toString();
    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):
    var videoParams = {
                title: video.title,
                sources: [{
                    url: video.url
    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).
    page.source = "videoparams:" + showtime.JSONEncode(videoParams);
    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.
    page.type = "video";
    This finally tells Showtime we have a video, so Showtime can handle everything to prepare video playback.
    function pageController:
    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:

    Publishing plugins

    You may check for all details about it.

    Bibliography (maintained by Andreas Oman (andoma), Fábio Ferreira (facanferff) and Leonid Protasov (lprot))


    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

    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.

    Quickstart to PS3 Plugin Development in Showtime by Facanferff

    Quickstart to PS3 Plugin Development in Showtime by Facanferff

    More PlayStation 3 News...

  4. #534
    Forum Moderator PS3 News's Avatar
    Join Date
    Apr 2005

    Showtime PS3 Media Player and MultiMAN PKG Updates Arrive

    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 04.03.582 [CEX].pkg / Showtime 04.03.582 [DEX].pkg / / / / 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:

    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)

    Showtime PS3 Media Player and MultiMAN PKG Updates Arrive

    More PlayStation 3 News...

  5. #535
    Forum Moderator PS3 News's Avatar
    Join Date
    Apr 2005

    Showtime PS3 Media Center Test Build v4.3.613 is Now Available

    Following up on the previous updates, today PlayStation 3 homebrew developer Andreas Oman updated the Showtime PS3 Media Player testing builds to v4.3.613 with the changes outlined below.

    Download: / /

    4.3.613 (Testing Build) Changelog:

    glw: Fix some nastyness related to how we resolve properties This fixes a long standing issue with image view in the UI, causing just the spinner to appear and no image to be shown
    hls: Fix issues when seeking past end of track when doing continous play
    osk: Replace ¤ with $
    Upgrade: Don't fail patch upgrade attempt if we can't open target file to get current hash
    Add Slovak translation
    Improve event routing

    Showtime PS3 Media Center Test Build v4.3.613 is Now Available

    More PlayStation 3 News...

  6. #536
    Forum Moderator PS3 News's Avatar
    Join Date
    Apr 2005

    Showtime PS3 Media Center v04.03.698 for MultiMAN is Released

    Following up on the previous revision, today PlayStation 3 homebrew developer Andreas Oman updated the Showtime PS3 Media Player testing builds to v04.03.698 followed by Showtime for multiMAN (both CEX and DEX) by deank with the changes outlined below.

    Download: / / / Showtime 04.03.698 [CEX].pkg (6.21 MB) / Showtime 04.03.698 [DEX].pkg (6.27 MB) / ShowTime v4.3.748 Cobra-ODE-V4.iso (13.7 MB) by Mussonero

    Showtime Media Center Changelogs


    Avoid some log messages from sqlite (we deal with them anyway)
    Call logfiles "showtime-#.log" instead of "showtime.log.#"
    h264: Skip the check converting h264 AVCC to annexb even when NAL unit len = 3.
    media: Fix lock-against-self when cycling subtitle/audio tracks …
    Make sure fa_parent() works on NTFS drives (ugly hack) …
    Update pl_PL, sp_SP, zh_CN language
    Make miner also translatable


    upnp: Add more URLs in device description
    settings/store: Fix lock inversion Fixes #1837
    ssdp: Remove unused code
    ssdp: If we fail to bind, retry later Fixes #1838
    Update translation files: Swedish, dk_DK, zh_CN
    Make system name configurable in Settings -> Network
    hls: Drop astray FA_DEBUG
    asyncio: Handle errors from poll() in a more resilient way poll() on ps3 can return error if there is a problem with one of the fd:s
    If settings storage can't use rename to overwrite, just log a debug message
    Improve ext subtitle load debug
    ASYNCIO: Add names to all file descriptor structs
    When ASYNCIO Poll error occurs, output more info in log
    subtitles: Fix some memory leaks when loading ext subs
    When user can rename discovered services, revert to original name if configured name is empty


    Upgrade librtmp - Fixes bug with DecodeTEA on BE systems. Fixes #1774
    upnp: One more fix. Fixes #1788
    upnp: Use URL to video file as canonical URL
    Rework how continous video playback build the video play list. Fixes #1819
    audio: Fix assert() in pulseaudio when skipping to next video track
    upnp: Fix issue causing names of UPNP services to be messed up
    ps3: Nag a bit more about donations if it's never turned on by the user
    HLS: More robust handling of corrupted segments
    RTMP: Set media source info. Fixes #1822
    hls: Avoid calling sub_scanner repeatedly if nothing will be scanned by it
    httpclient: Deal with "206 Partial Content" when we didn't ask for it.

    Here is the standalone version of Showtime 04.03.698 compiled by me with all the standard changes:

    Showtime for multiMAN is available as usual within mM/mmCM in the VIDEO column (press [Triangle] over "Start Showtime" and select "UPDATE").

    CEX/DEX standalone versions are also available for direct download (as .pkg) in the WEB column of multiMAN/mmCM.

    Showtime PS3 Media Center v04.03.698 for MultiMAN is Released

    More PlayStation 3 News...
    Attached Files Attached Files

  7. #537
    Junior Member tim132's Avatar
    Join Date
    Jan 2011
    I was wondering whether there's a way to add to collect metadata of my films?

  8. #538
    Registered User cuah's Avatar
    Join Date
    Jan 2014
    Getting error 404 when attempting to install plugins in showtime version 4.3.536. Seems like it cannot connect to internet. PS3 has internet connection and I can see browse on it fine. Any suggestions pls...

  9. #539
    Junior Member zazoon's Avatar
    Join Date
    Sep 2013

    Question Showtime problem

    I have Showtime problem with installing plugins ! Both standalone and multiman version don t work. I have reinstall - update / upgrade rogero 4.50 & multiman - still nothing. Update to Steven CEX-4.53 & newest multiman - still nothing.

    No plugin in apps ! I have deleted multiman and showtime and then update system bouth with rogero and Steven - and still nothing.

    I have tried and search for alternate plugin repository url. Did not find it ! This are versions of showtime i have tried and no go :

    Showtime 04.03.582 [CEX]
    Showtime 04.03.536 [CEX]
    Showtime 04.03.479 [CEX]

    Update all version to new one and still nothing !

    Any idea what to do ?

  10. #540
    Junior Member zazoon's Avatar
    Join Date
    Sep 2013
    Update: I have formatted ps2 system , put new mutliman 4.53 now i see all the plugins but i can it all them it say: http error 40.

    Any idea what to do next ?

    Internet connetion is ok , i have tried showtime version from multiman and no go , make an update to newest from multiman and still nothing.


Page 54 of 55 FirstFirst ... 44452535455 LastLast