<section id="apps">

    <title>Player application settings</title>

    <p>MIME types are categorized identifiers for file types. <var>Audio/mpeg</var> for
    <p>MIME types are abstract identifiers for media types. <var>Audio/mpeg</var> for
    example represents MP3 files, and <var>audio/ogg</var> means OGG Vorbis.  And the player
    setting dialog simply associates an audio type with a playback application:</p>

<table shade="rows" rules="rows cols">
  <thead>  <tr><td><p>Format</p></td>     <td><p>Application</p></td></tr> </thead>
    <tr><td><p><var>audio/mpeg</var></p></td>     <td><p><cmd>audacious</cmd></p></td></tr>
    <tr><td><p><var>audio/ogg</var></p></td>      <td><p><cmd>audacious</cmd></p></td></tr>

    somewhat slower because playback addresses are hidden away with extra
    page requests. Works reliably still. </p>
  </item>
  <item>
    <title><link href="http://listenlive.eu/">ListenLive.eu</link></title>
    <p>ListenLive is also an Europe-centric radio directory. </p>
  </item>
  <item>
    <title><link href="http://radiosure.com/">RadioSure</link></title>
    <p>Station database that's readily available as CSV list. </p>
  </item>
  <item>
    <title><link href="http://vtuner.com/">vTuner</link></title>
    <p>Categorized station list by a cross-platform streaming service provider. </p>
  </item>
  <item>
    <title><link href="http://reciva.com/">Reciva</link></title>
    <p>Reciva is an iPhone app, with a browsable station list. </p>
  </item>
  <item>
    <title><link href="http://punkcast.com/">PunkCast</link></title>
    <p>PunkCast is no longer maintained. It covered the NY music and tech
    scenes, but existing recordings are still accessible mostly (some are
    just weblinks howeever). This plugin is kept for nostalgic reasons;
    it was available with streamtuner1 as well. </p>
  </item>

    is made for. There are way better local music collection managers for
    Linux. It's just here for convenience, and displays files just as any
    other channel list. It has no specific file management features, and
    won't get any. </p>
  </item>
</terms>

<p>See also the list of
<link href="http://fossil.include-once.org/streamtuner2/wiki/plugins">available
plugins</link> in the project wiki.</p>

</page>

	
	<p>You can scan for available/new plugins there. And have them
	downloaded right away. New plugins are just downloaded, not
	implictly enabled. Reopen the config dialog to see them in the
	regular <key>📻 Channels</key> or <key>🔌 Feature</key> tabs, and
	then enable them.</p>
	
	<note><p>Updated plugins will not be automatically loaded if they've
	been active already. That requires either a restart. (Or disabling +
	saving once, then reenabling them.)</p></note>
	<note><p>Updated plugin versions won't be instantiated right away
	if they've been active already. That requires either a restart.
	Or disabling + saving once, then reenabling them.</p></note>
	
	<section id="configuration">
	<title>Configuration</title>
	<list>
	<item><p>Alternative download repositories may be configured. (Little
	practical value at the moment.)</p></item>
	<item><p>And you can let the plugin manager handle autoactivation

     	</item>
   	</list>
	</section>

	<section id="configuration">
	<title>User plugins</title>
	<p>Downloaded plugins are stored in <file>~/.config/streamtuner2/plugins</file>.
	To remove them, delete the individual *.py files there manually.</p>
	To remove them, delete the individual *.py files there manually. But
	keep the <file>__init__.py</file> stub.</p>
	<note style="bug"><p>Currently system-installed core plugins take
	precedence over downloaded updates.</p>
	<p>And you'll have to take care to eventually refresh/delete outdated user plugins,
	whenever you install a newer Streamtuner2 version.</p></note>
	</section>
	
	<section>