PS3 Media Server

by **otmanix** » Sun Sep 27, 2009 3:47 pm

Question

Is there a list of supported media renderers (streaming clients) for PS3 Media Server?

Answer:

An overview of the supported renderers can be found on the About page. The full list of supported renderers (and families of renderers) can be found in the renderers directory of your PMS installation.

To add or update support for a particular renderer, see here.

by **otmanix** » Sat Oct 31, 2009 3:53 pm

Troubleshooting - PMS - manual setup of Windows firewall
Error: PS3 can't be found by PMS because Windows firewall is blocking connections.

Solution: PMS needs incoming port 5001 tcp/udp to run properly. Instead of that one can also set up an firewall exeception for Java program javaw.exe (JRE/JDK) and wrapper.exe if PMS is running as a service. Windows firewall settings can be changed by GUI or command line. It would take lots of screenshots so I prefer to give you a list of commands to set up Windows firewall.

Windows 7 and Vista firewall settings

You have to start command line as Administrator.

Open required ports (incoming port 5001 tcp/udp):

Code: Select all: C:\>netsh advfirewall firewall add rule name="allow PMS - UDP" dir=in protocol=udp localport=5001 security=notrequired action=allow OK. C:\>netsh advfirewall firewall add rule name="allow PMS - TCP" dir=in protocol=tcp localport=5001 security=notrequired action=allow OK.

Let's look if the result is as expected:

Code: Select all: C:\>netsh advfirewall firewall show rule name="allow PMS - TCP" Regelname: allow PMS - TCP ---------------------------------------------------------------------- Aktiviert: Ja Richtung: Eingehend Profile: Domäne,Privat,Öffentlich Gruppierung: Lokales IP: Beliebig Remote-IP: Beliebig Protokoll: TCP Lokaler Port: 5001 Remoteport: Beliebig Edgeausnahme: Nein Aktion: Zulassen OK. C:\>netsh advfirewall firewall show rule name="allow PMS - UDP" Regelname: allow PMS - UDP ---------------------------------------------------------------------- Aktiviert: Ja Richtung: Eingehend Profile: Domäne,Privat,Öffentlich Gruppierung: Lokales IP: Beliebig Remote-IP: Beliebig Protokoll: UDP Lokaler Port: 5001 Remoteport: Beliebig Edgeausnahme: Nein Aktion: Zulassen OK.

If you have installed PMS as a service you have to allow wrapper.exe (path depends on 32/64bit):

Code: Select all: C:\>netsh advfirewall firewall add rule name="allow PMS service" dir=in program="C:\Program Files (x86)\PS3 Media Server\win32\service\wrapper.exe" security=notrequired action=allow

Let's look if the result is as expected:

Code: Select all: C:\>netsh advfirewall firewall show rule name="allow PMS service" Regelname: allow PMS service ---------------------------------------------------------------------- Aktiviert: Ja Richtung: Eingehend Profile: Domäne,Privat,Öffentlich Gruppierung: Lokales IP: Beliebig Remote-IP: Beliebig Protokoll: Beliebig Edgeausnahme: Nein Aktion: Zulassen OK.

If you're not satisfied with the result delete the firewall rule:

Code: Select all: C:\>netsh advfirewall firewall delete rule name="allow PMS service" 1 Regel(n) wurde(n) gelöscht. OK.

Instead of opening ports you can also allow javaw.exe from JDK/JRE (path depends on 32/64bit and version of Java)

Code: Select all: netsh advfirewall firewall add rule name="allow PMS - JDK" dir=in program="C:\program files\java\jdk1.6.0_16\bin\javaw.exe" security=notrequired action=allow

or

Code: Select all: netsh advfirewall firewall add rule name="allow PMS - JRE" dir=in program="C:\Program Files (x86)\Java\jre6\bin" security=notrequired action=allow

You may also want to disable firewall completely:

Code: Select all: netsh advfirewall set currentprofile state off

Syntax of netsh command has change in Windows 7:
How to use the "netsh advfirewall firewall" context instead of the "netsh firewall" context to control Windows Firewall behavior: http://support.microsoft.com/kb/947709

Windows XP firewall settings

Open required ports (incoming port 5001 tcp/udp):

Code: Select all: netsh firewall add portopening protocol=TCP port=5001 name=”allow PMS - TCP” mode=ENABLE scope=SUBNET netsh firewall add portopening protocol=UDP port=5001 name=”allow PMS - UDP” mode=ENABLE scope=SUBNET

If you have installed PMS as a service you have to allow wrapper.exe:

Code: Select all: netsh firewall set allowedprogram "C:\Program Files\PS3 Media Server\win32\service\wrapper.exe" allow_PMS_service ENABLE

Instead of opening ports you can also allow javaw.exe from JDK/JRE (path depends version of Java)

Code: Select all: netsh firewall set allowedprogram "C:\Program Files\Java\jre6\bin" allow_PMS_JRE ENABLE

You may also want to disable firewall completely:

Code: Select all: netsh firewall set opmode mode=disable

I didn't have the opportunity to test it on Windows XP. Please write a note if there syntax errors or sth like that...

by **meskibob** » Sat Jan 02, 2010 6:39 pm

Troubleshooting - PS3 - Connectivity
Error: PMS doesn't show up on the PS3 until PMS is restarted or until PMS sends an alive notice (approximately every three minutes). PMS also doesn't respond to the PS3's "Search for Media Servers" request.

Solution: Something in your setup is not allowing PMS to accept/reply to the PS3's M-Search request when the PS3 boots up (or when you do the Search for Media Servers, or when it comes back from a game or internet browsing). Make sure that the software firewall on the server is set up to allow incoming requests from the PS3 (e.g. add the PS3's IP to "Trusted IP" list), and that your router is allowing Multicast traffic.

by **meskibob** » Sat Jun 19, 2010 1:52 am

Q: Where are the PMS config, log, database files etc. located?

A: The actual locations are listed in the first lines of output on the Traces tab in the GUI and the debug.log.
Most files are, by default, in the application working directory (usually the application install directory - OSX see * below), but there are a couple external locations as well:

Profile Directory
Windows

%PROGRAMDATA%\PMS (Vista, 7)
%APPDATA%\PMS (XP)
Note that the ProgramData and AppData folders are hidden. Open Windows Explorer and either paste the above path into the address bar or show hidden folders to browse it.

Linux &c.

~/.config/PMS

OSX

~/Library/Application Support/PMS
Note that in OSX Lion the users "Library" folder is invisible. Use the "Go to Folder" command (CMD + SHIFT + G in Finder) and paste the path to browse it.

Temp Directory

Directory configured in PMS.conf as

Code: Select all

temp_directory=

if exists and writable; or
System temp directory\ps3mediaserver

Log files

(Linux only) /var/log/ps3mediaserver/%USERNAME%/ if writable by PS3MS's user or group; or
Profile folder (see above) if writable; or
Temp folder (see above).

You can set custom log location by placing copy of logback.xml (and logback.headless.xml for console mode) in profile folder (see above) and editing them. Be careful, editing logback.xml or logback.headless.xml in application folder is useless because they are overridden during application update.

Specific default locations:

The "PMS.conf" and "WEB.conf" files are located in the Profile directory listed above.
The .bat/.sh files are located in the application working directory.
Renderer config files, plugins, and database files are located in subdirectories of the application working directory.

Resetting PMS back to default:

To reset the program settings, delete the PMS.conf file
To reset the list of web streams, replace the WEB.conf file with the default WEB.conf located at https://github.com/ps3mediaserver/ps3me ... s/WEB.conf
To reset a renderer, replace the specific renderer's conf file with the default conf located at https://github.com/ps3mediaserver/ps3me ... /renderers
To reset the .bat or .sh files, replace the file with the default file located at https://github.com/ps3mediaserver/ps3me ... -resources

* Note: The Application Working Directory on OSX is at

/Applications/PS3 Media Server.app/Contents/Resources/Java
Note that in OSX the "PS3 Media Server.app" folder is invisible. Use the "Go to Folder" command (CMD + SHIFT + G in Finder) and paste the path to browse

by **meskibob** » Fri Aug 13, 2010 8:50 pm

Problem: I cannot see PMS from my DLNA client!

Solution: This can be caused by a variety of factors, but the potential causes can be broken up into two groups: "Before UDP Broadcast" and "After UDP Broadcast".
The line in the trace or debug.log that separates these two groups (this signifies the UDP broadcast) is:

Code: Select all: The server should now appear on your renderer

Note1: for the suggestions below, Windows, Apple and several OEM manufacturers install and enable default protection programs (e.g. Windows Defender or Peer Guardian).
Make sure that the settings for ALL antivirus, firewall, malware and protection programs are checked.

Note2: direct connections are a special case, check the additional details at the bottom of this post.

-------------------------------------------------------------------------------------------------------------------------

Before UDP Broadcast
These can typically be spotted through errors or notes in the trace or debug.log before the line above.

PMS cannot bind to the IP-address or port on the network interface:
Some other program is already using that port ("Address already in use").

Check with "netstat -a" through the command line, and change the port in the PMS settings if needed
If you are using a Mac with EyeTV, some background processes from EyeTV's EyeConnect software may be causing the in-use error. To solve it, quit all processes and launch PMS first, and then EyeTV.

A software firewall is blocking javaw.exe (and wrapper.exe if running as a Windows service) from binding to the port

Open the firewall settings and make sure the .exe's are allowed or the specific port is open

You forced the wrong IP address in the PMS settings

Clear the setting or force the correct IP address (the IP address of the server)
Note: you should only have to the force IP if you've assigned multiple IPs to a single NIC

You opened multiple instances of PMS or a javaw.exe process got hung up:

Close all open instances of PMS and then kill any* remaining javaw.exe processes. Alternatively, restart your computer to get rid of unwanted processes.
Note: You may have other programs using javaw.exe, so exercise due diligence in killing the tasks.

PMS is bound to the wrong network interface:
You have multiple NICs enabled, and PMS automatically selected a NIC different than the one desired (e.g. on Mac OS X the program Parallels creates a virtual network interface "vnic1", or on Windows it somehow selected the "localhost" adapter).

Force the correct network interface under "Network settings".

You forced the wrong network interface under "Network settings".

Either force the correct network interface or clear the setting.

You do not have the proper access or permissions for the PMS install folder:
You need to make sure there are full read/write permissions on the PMS install folder

Check the base filesystem permissions
On Windows Vista/7, reinstall with "Run as Administrator" on the installer
Check if any filesystem protection programs are blocking access (some antivirus/malware programs have this feature)

PMS is taking time to register a component or setting:
This isn't really an "error", in that large collections of files (eg a large iTunes database) can take some time for PMS to go through. You need to either

Wait for PMS to do its thing, after which it should properly broadcast and show up on your device, or
Disable the engine/setting

After UDP Broadcast
At this point everything should be fine within PMS, so you need to look externally.

Your software firewall or other software is blocking the traffic between PMS and your device:

A software firewall is somehow blocking the connection apart from the specific items listed above (e.g. blocking inbound local connections).
- Add the device's IP to your firewall's "Trusted List" or allow all local traffic.
- Temporarily disable all firewalls to confirm, and then check your firewall's help documentation.
If you are using Hamachi VPN, try disabling its drivers or uninstalling the software.
If you are using Avast Anti-virus, check the expert settings for a module called Auto Sandbox. Make sure that "javaw.exe" is excluded from the Auto Sandbox.

Your router is blocking the traffic:

Your router may just need to be rebooted. This is probably not the issue if you've never been able to connect PMS to your client device.
Check the router's firewall to see if the traffic is being blocked. For some routers it helps to disable the SPI Firewall.
If using a wireless connection, check if Wireless Isolation is enabled on your router, and if so disable it.
Check your router's settings to see if there are any settings to toggle for UDP traffic or multicast/IGMP traffic (e.g. IGMP Proxy on Verizon FIOS routers [source 1, source 2]).
Notes:
1. Most UPnP settings on routers are to allow the devices on the LAN to dynamically configure the port forwarding and other router settings with minimal user interaction. This shouldn't need to be enabled for the actual UPnP/DLNA traffic in the LAN, and in some cases it actually causes issues when enabled on bad routers.
2. Port forwarding isn't required for standard use of PMS. It is only needed if you're trying to stream web-content.
3. Some routers are crap and either a) don't have the proper settings or b) just mishandle traffic regardless of the settings. This can even vary within the same router for wired vs wireless traffic.
4. You can to try updating your router's firmware to workaround these issues (source)
See if a different DLNA program (WMP, TVersity, Wild, etc) works using the same router/settings.
If you've checked everything else, give the forum or Google a search and see if other people are having UPnP/DLNA issues with the same router.

The host file on your Linux box needs to be corrected:

Add the server's FQDN to the server's host file (/etc/hosts).
- How to determine your current hostname/domainname.

Windows is set to a Public network location instead of Home:

Choose a network location (Windows 7 and Server 2008)
Choose a network location (Vista)

Your server and device are on different subnets:

Per the DLNA protocol (which uses UDP broadcast packets), the server and device must be on the same subnet. The easiest way to check is if you can ping the device from the server (a successful ping typically means same subnet, at least for home networks). This issue should only really happen if you have multiple routers or managed switches in your network (in which case you'll need to bridge your routers together). If you only have a single router/switch, then you incorrectly set a manual IP address on at least one of your devices leading to a subnet mismatch.

Your server or device is configured to use an invalid IP address:

Some IP addresses are reserved (eg x.x.x.255) and should not be used by any device on the LAN. You should only see this issue if you are manually assigning IP addresses at some point (on the device, at router level, etc).

Your device is not set up to access any DLNA servers:

On the PS3, make sure that "Settings > Network Settings > Media Server Connection" is enabled.
See your device's manual.

Note: this only covers PMS showing up on your device, nothing regarding playback or file browsing.

-------------------------------------------------------------------------------------------------------------------------

In addition, you can run into issues (both Before and After UDP Broadcast) when trying to use a direct connection (no router or switch, just the computer with PMS and the device)
Examples:

PMS can't bind to the IP/Port because both devices need to be turned on for the connection to exist (before PMS is started)
You didn't use a crossover cable (only needed if BOTH devices are NOT gigabit)
You have a mismatch in the IP settings
The device has two (or more) NICs and is using the wrong one (eg PS3 still using the wifi NIC)

This thread/post covers almost everything needed to correctly set up a direct connection.

by **chocolateboy** » Sun Sep 26, 2010 7:05 pm

Question: There are multiple versions of PMS available. Which version should I use?

Two versions are available:

Release:

The official release version of PMS is 1.90.1. This is recommended for most users.

Development:

If you have an issue with PMS, please use the latest snapshot build to check if it has already been fixed. Snapshot builds are also recommended if you're interested in experimenting with an upcoming feature or just enjoy living on the bleeding edge. Testing these builds helps us to improve the official releases and gives us feedback on what works and what still needs fixing or improving.

Unofficial:

In addition to the official releases, there is also an unofficial build of PMS:

The pms-mlx ("media library extension") build offers a completely rewritten media library with a range of new and frequently-requested features. It is currently in alpha, and has some features that are incomplete, and others that may be subject to change, but it is scheduled to be merged into the official build once it has been thoroughly tested, so downloading it and offering feedback is encouraged.

Site
Wiki
Source Code
Discussion

by **chocolateboy** » Wed Sep 29, 2010 3:29 pm

Question: How do I get web video feeds/streams to work?

Answer:

Use the PMSEncoder plugin (make sure you're using the latest version of PMS). See the relevant sections of the documentation for installation instructions, tips and troubleshooting help.

If the Web folder doesn't appear on your renderer, see here. For help with particular feeds/streams/sites, see here.

To discuss or report issues with PMSEncoder, post in this thread (please follow the instructions for reporting an issue if you want a reply).

by **chocolateboy** » Sat Oct 16, 2010 11:08 pm

Problem: PMS doesn't reflect newly added/removed/renamed files/folders

Solution:

To refresh a directory listing, navigate back out of the folder then back into it. New folders will appear at the bottom of the folder list (e.g. after the #--TRANSCODE--# folder, if enabled), and new files will appear at the bottom of the file list. Removed files and folders won't be listed.

Added files/folders will be sorted correctly when PMS is restarted.

Note: these instructions apply to the PS3 and may not apply to other renderers.

by **meskibob** » Wed Oct 20, 2010 5:23 pm

Problem: Some MKV files are returning "Data corrupted" or other playback errors while other MKV files work fine.

Potential Solution:The compression header was enabled by the file creator (issue with a setting in the newer MKVToolnix program set).
http://www.ps3mediaserver.org/forum/viewtop ... 163#p38163

by **chocolateboy** » Sat Oct 23, 2010 7:34 pm

Problem: I have a problem with PMS. Do I need to upgrade anything?

Solution:

If PMS works for you, carry on using whatever version of PMS/Java you like.

If it doesn't work, please make sure you're using the the latest version of Java and the latest snapshot build of PMS before reporting issues.

PS3 Media Server

PS3 Media Server Tutorial/FAQ

Re: PS3 Media Server for dummies / tutorial howto documenta

Re: PS3 Media Server for dummies / tutorial howto documentation

Re: PS3 Media Server for dummies / tutorial howto documenta

Re: PS3 Media Server for dummies / tutorial howto documenta

Re: PS3 Media Server for dummies / tutorial howto documenta

Re: PS3 Media Server for dummies

Re: PS3 Media Server for dummies

Re: PS3 Media Server for dummies

Re: PS3 Media Server for dummies

Re: PS3 Media Server for dummies

Who is online