A proxy won't be needed with the next DNAS release because the password value can be manipulated (as was done with the 2.2.x releases to allow for the 2.x-style user field to be provided from 1.x sources) to include the sid parameter, thus allowing multiple 1.x source clients to connect like 2.x source clients can do.

So there is no need to have additional ports opened (just the default 2 - though going all 2.x means you only need one port opened) or proxies in the way / messing with things and other than some possible config / UI tweaks in clients, there generally should be no real changes needed in any of the 1.x source clients (Liquidsoap included) to be able to feed multiple streams to the next DNAS release whatever the SC protocol version being used. It just comes down to providing the password in the correct format needed.

On 01/01/2015 17:51, John Plsek wrote:
Just a heads up, it all works now, including metadata. If there's any interest shown, I'll include better documentation.

Over at shoutcast/winamp/radionomy they keep saying that DNAS2 supports DNAS1 streams, even multiple streams to the one DNAS2 server. However, you have to open up two ports for each stream - which totally defeats the benefits of DNAS2, and is not going to be an option for hosted DNAS2.

On 21 December 2014 at 21:21, John Plsek <[email protected] <mailto:[email protected]>> wrote:

    I've written a simple proxy that sits between a Shoutcast v1 (or
    ICY) source client and Shoutcast DNAS v2 (Ultravox 2.1). As far as
    I know there's no (easy) way to stream more than one ICY stream TO
    DNAS v2, so, because ocaml makes my eyes bleed, I decided to write
    a proxy which is more or less universal - i.e. not liquidsoap
    specific, but I did write it because liquidsoap has no support of
    Ultravox 2.1 protocol.

    It's well tested with two streams, not sure how well it goes with
    more sources, if you use it and something breaks, you can keep
    both pieces :p

    Fairly easy to use, once it's running (you need nodejs) you simply
    point your source to the host/port of the proxy, and set the
    stream password to

    :host:port:SID:UID:pass:

    the : can be anything (as long as they're all the one character)
    .. e.g. ~host~port~SID~UID~pass~ and must be the first AND last
    characters of the password. This defines the
    host/port/streamid/userid/password of the DNAS v2 server

    Currently metadata is accepted through the standard DNAS v1
    method, however, for some reason it is being rejected by DNAS v2 -
    I'm hoping to get some clarification on the format of the metadata
    that Ultravox 2.1 will accept, but shoutcast forums make glaciers
    look like avalanches

    https://github.com/jaromanda/dnas-proxy - the DNAS code is partly
    based on some code I found on github, I will give proper credit
    when I track it down again!!




------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now.http://goparallel.sourceforge.net


_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users

------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users

Reply via email to