Newer source available from package origin. (host go-agent-stagingbot-7)

• Files Changed
• Browse Source

Newer source available from package origin. (host go-agent-stagingbot-2)

• Files Changed
• Browse Source

Newer source available from package origin. (host go-agent-monitor-4)

• Files Changed
• Browse Source

- Update version to 3.3.1
  * Fix a bug in the MQTT documentation and add sanity checking for the port
    chosen -- thanks to David Crook.
  * Fix a bug that caused manual format and rate settings to be ignored --
    thanks to Jörg Krause.
  * Add missing support for format settings S24_LE, S24_BE, S32_LE and S32_BE.
  * Fix a bug that caused dither to be too loud.
  * Fix error message for invalid 
  * Automatic Format and Speed Selection for alsa devices. Using the alsa back
    end, when you specify the output device, Shairport Sync will now, by
    default, select the best output format and speed. For instance, if your
    output device is capable of 32-bit operation, it will be selected. In some
    situations, this will give a noticeable improvement in sound quality – see
    the discussion of audio improvements below. The greatest bit depth will
    always be selected, and the lowest speed that is a multiple of 44,100.
  * Audio Transient Reduction: A Disable Standby feature to eliminate certain
    faint-but-annoying audible pops and clicks has been added for alsa devices.
    The setting prevents an output device entering standby mode and thus
    minimises standby/busy transitions, which can sometimes be heard. It is
    pretty impressive, especially combined with fixes to the dithering code
    described below. If you can enable 24- or 32-bit audio output to your output
    device, you can get even better results. This feature is available in the
    ALSA back end (standard in Linux) when it is driving output devices that can
    provide precision delay information, i.e. most hardware output devices and
    possibly some virtual devices.
  * New active/inactive program hooks. Basically, these are "deglitched"
    replacements for play start/play end program hooks. When a play session
    starts, the system goes active. When the play session ends, the system
    remains active for a period determined by the active_state_timeout setting,
    10 seconds by default. If another play session starts before the period

• Files Changed
• Browse Source

branch from 15.1

• Files Changed
• Browse Source

Automatic request from openSUSE:Factory by UpdateCrawler

• Files Changed
• Browse Source

Automatic request from openSUSE:Factory by UpdateCrawler

• Files Changed
• Browse Source

Automatic request from openSUSE:Factory by F-C-C Submitter. Please review this change and decline it if Leap do not need it.

• Browse Source