foo_upnp, UPnP/DLNA client and server (previously foo_upnp_mediaserver) Options

[bubbleguuum]

Download latest version of plugin 0.99.46 [BETA] [Changelog]
Documentation (work in progress)

Some use cases:

- Use the server to stream audio to a PS3, XBOX360 (using their interface), iPhone (PlugPlayer)
- Push audio from either your local foobar2000 Media Library or another UPnP Media Server to WMP12, an iPhone (PlugPlayer) or another foobar2000 instance on the network.
- Control foobar2000 playback from an iPhone, WMP12, or any other Control Point.
- Browse and play your Media Library and playlists remotely with an Internet connection
- Control a Linn Ds product including making playlists, switching sources, etc.

UPnP AV Media Server

• expose the foobar2000 Media Library, playlists and "what is currently playing"
• stream almost any audio format playable by foobar2000. That includes formats generally not supported by most standalone Media Servers, such as formats with CUE files, game music formats, audio files in archives, cd-audio, DTS, HDCD, ...
• stream album art
• powerful per device streaming options, to adapt audio format to the capabilities of the remote playing device. conversion to WAV or LPCM, transcoding to mp3, resampling, replaygain, bitdepth conversion, conversion to stereo, DSP chain,...
• customizable browse tree
• accessible from the Internet (only from foobar2000 or an iPhone/iTouch with PlugPlayer).
• works well when accessed from WMP12 (possibly also with WMP11, untested).

Media Server Browser (UPnP Browser)

• browse remote Media Servers for local playback or remote playback to an UPnP Renderer on the network
• browse and play music via the Internet from another foo_upnp Media Server, with optional transcoding to mp3 to save bandwidth
• retrieve album art

Control Point (UPnP Controller)

• control playback of UPnP Av Media Renderers (similar to Windows7 "Play to" feature)
• integration with the Media Server to serve locally managed audio
• specific support Linn Ds product: handle Playlist sources for on-device playlist management and other analog sources (volume control only)

UPnP AV Renderer

• allow foobar2000 playback be controllable by UPnP Control Points

How to enable logging to troubleshoot problems

Logging can be enabled in File->Preferences->Tools->UPnP->Server->Basic. Logging is mostly useful so I can troubleshoot issues when I don't have the hardware or can't reproduce the issue. If log to file is enabled, a log file called foo_upnp.log is generated in either your foobar install directory or in <Document and settins>/<login>/Application Data/foobar2000. This file is overwritten on each foobar2000 launch. You can also see logging in the foobar2000 console by enabling the relevant option. Log level can be changed. Usually the INFO level gives sufficient information but sometimes finer spammy levels are required to troubleshoot some issues.

This post has been edited by bubbleguuum: Apr 23 2013, 13:52

[Peter]

bubbleguuum, your metadb_display_field_provider use is critically flawed and probably breaks all mid-stream metadata processing for streams that your component isn't handling, please remove it or your component will be put on the list of problematic components. You're falling back to static track information cached in the metadb, which doesn't contain realtime playback information. If you try to hackfix this, you start feeding playback information to callers that don't want it, which is just as bad.

Rant: no matter how clearly documented the API is, people will just happily ignore what the documentation says anyway and then waste other people's time with "component A can't coexist with component B" problems.

[bubbleguuum]

bubbleguuum, your metadb_display_field_provider use is critically flawed and probably breaks all mid-stream metadata processing for streams that your component isn't handling, please remove it or your component will be put on the list of problematic components. You're falling back to static track information cached in the metadb, which doesn't contain realtime playback information. If you try to hackfix this, you start feeding playback information to callers that don't want it, which is just as bad.

Rant: no matter how clearly documented the API is, people will just happily ignore what the documentation says anyway and then waste other people's time with "component A can't coexist with component B" problems.

I had the feeling this was broken when I coded it to be honest. I posted a message about it in the development forum a few days ago that went unanswered.
I may be wrong but it looks like file_info cannot be written without being written to disk. In that case how should I proceed if metadb_display_field_provider is innapropriate? Oh yes I could present empty items in the playlist and info will be displayed when played, right ?

Rant: no matter how you ask for help in the development forum on some finer point of the SDK, sometimes you get no anwser. And the documentation does not explain all, far from it.

This post has been edited by bubbleguuum: Feb 21 2009, 02:24