slicerwizard
Member
So dsdauthor last posted here in February 2013 and the first sighting of DSD+ was Christmas 2013, therefore DSD+ drove off dsdauthor. You guys are hilarious.the original dsd author was gone (thanks to dsd plus)
So dsdauthor last posted here in February 2013 and the first sighting of DSD+ was Christmas 2013, therefore DSD+ drove off dsdauthor. You guys are hilarious.the original dsd author was gone (thanks to dsd plus)
So dsdauthor last posted here in February 2013 and the first sighting of DSD+ was Christmas 2013, therefore DSD+ drove off dsdauthor. You guys are hilarious.
* The “mbelib” developers created a D-STAR decoder
called “DSD” and published it, with “mbelib”, under the
BSD license.
* Another anonymous developer created a proprietary fork
called “DSD+” and declined to share his source code
with the original developers.
* The original developers know better now, and will put
their future work under GPL instead of BSD, but they
probably aren't going to do more work that helps DSD+.
* Mbelib has remained at release 1.0 for more than a year
* Recently, another closed-source DSD fork has
appeared called DSD Plus. [...] It greatly annoys me
that these improvements are locked out and
unavailable to people who want to make further
improvements. It annoys me even more that people
on the forums keep defending the choice of the
DSDPlus author to keep the software closed.
* I think the real pain for this developer of “mbelib”
was when he got a public “screw you” from what
was really his user community.
Yes, this absolutely is possible and just requires the correct setup in asound.conf. The advantage over trying to monitor your own stream via broadcastify is far less delay (it's instantaneous).
rx.py needs to output to "mout0" device
darkice.cfg needs to receive from "loop0" device
(code snipped)
Boatbod,
Will this allow me to monitor my stream through the HDMI port on a Raspberry Pi or would it need to be modified?
That was a quick reply! Thanks!The only modification would be to change hw:0,0 to whatever values are needed to select the HDMI port. Perhaps "hw:1,0"?
* Recently, another closed-source DSD fork has
appeared called DSD Plus. [...] It greatly annoys me
that these improvements are locked out and
unavailable to people who want to make further
improvements. It annoys me even more that people
on the forums keep defending the choice of the
DSDPlus author to keep the software closed.
So dsdauthor last posted here in February 2013 and the first sighting of DSD+ was Christmas 2013, therefore DSD+ drove off dsdauthor. You guys are hilarious.
What would be the easiest way to pipe the audio from a tinkerboard running dietpi to a local client?
I set up a local ices2 server and stream in to that to test darkice.Boatbod, thanks for info. I was able to get the audio out the 3.5mm after your advise. I am actually now going to feed into a Shoutcast2 Server from Darkice. Is there a way to test to make sure Darkice is receiving the stream or attempting to send it back out to the Shoutcast server. I am not sure if I am dealing with Darkice problems or Shoutcast through my provider.
Ive got op25 and darkice working fine for a single mono feed, but would like to seperate fire and law. Would it be possible to use this setup / darkice to use two instances of op25 (and dual rtls) to a single stereo feed?
By the way, how do you configure a single instance of darkice to split a stereo feed into two separate streams?