1. 28 Jan, 2020 1 commit
  2. 15 Jan, 2020 1 commit
    • Moritz Grimm's avatar
      Remove half-baked support for "passthrough encoders" · 83d1d17b
      Moritz Grimm authored
      The correct way is to just not configure an encoder for a stream, which
      is what the documentation already states. Encoder sections now require
      a program name to be set or the configuration will not load.
      Fixes a segfault in ezstream.c, as reported by Tom McCallum via Github.
  3. 23 Jan, 2018 1 commit
  4. 18 Nov, 2017 1 commit
    • Moritz Grimm's avatar
      Change config format to (eventually) support concurrent streams to many servers · ed9e84f3
      Moritz Grimm authored
      Everything ties together in stream configurations, of which there can be many
      For the time being, every stream configuration but the "default" is ignored.
      Every stream/server/encoder/decoder configuration now has the name "default"
      by default, so that configuring names is only needed to resolve ambiguities.
      Decoder configurations are now also constrained in this manner for consistency,
      meaning they are no longer uniquely identified by a number of file extensions
      but also a name.
  5. 22 May, 2015 1 commit
  6. 21 May, 2015 1 commit
  7. 20 May, 2015 1 commit
  8. 15 May, 2015 1 commit
  9. 05 May, 2015 1 commit
    • Moritz Grimm's avatar
      Refactor configuration (work in progress) · 43e48648
      Moritz Grimm authored
      * Move -m and -n command line options into the config file
      * Restructure configuration file:
        - Group into "server", "stream", "media", "metadata", "decoders", and
        - Untangle decoder and encoder:
          o Decoders match on file extensions and convert to a canonical "internal"
          o Encoders create one of the supported stream formats, potentially using
            different parameters (like bitrate)
        - Consistently specify stream format
        - Enable reencoding by selecting an encoder
      * Architecturally separate configuration file storage from parsing
        - Allows for different configuration back-ends in the future, like
          YAML, SQL, REST API, ...
      * Support roll-back in case of error on (re)load
      * Anticipate HTTPS support