<<a href="http://opensoundcontrol.org/introduction-osc">http://opensoundcontrol.org/introduction-osc</a>><br><br>It's also worth noting that many of the issues that have come up in this discussion have been addressed at some length in connection with XMPP.<br>
<br>Just to make note of it, I am continuing work in deadly earnest on the system originally discussed in the FSM paper, although there have been a few detours along the way.<br><br>Contrary to some of the discussion here, I've been persuaded that it's not the API that matters, it's the namespace and service discovery protocol, and that there are perfectly usable models for these in both OSC and XMPP.<br>
<br>Similarly, many if not most of the issues involved in IF and baseband data transport have been worked over at length in connection with both CoreAudio (Mac OS X) and PulseAudio. These systems are very similar under the hood. It's hard to see how they could be improved on.<br>
<br>73<br>Frank<br>AB2KT<br><br><div class="gmail_quote">On Tue, Dec 1, 2009 at 7:05 AM, Jeremy McDermond <span dir="ltr"><<a href="mailto:mcdermj@xenotropic.com">mcdermj@xenotropic.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">***** High Performance Software Defined Radio Discussion List *****<br>
<br></div><div class="im">
On Dec 1, 2009, at 5:26 AM, John Melton wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The client server interface is fairly simple. It uses a TCP connection<br>
for commands but uses UDP for the I/Q samples and any returned audio.<br>
</blockquote>
<br></div>
Maybe this is way too complex to implement for what we want, but I've been thinking about the problem of a "HPSDR Server" a bit, and it seems to me what we're implementing is a essentially a streaming media server with I/Q data. It makes a certain amount of sense to me to use existing protocols on the wire, so it might make some sense to consider RTSP/RTP for transporting control and data in this case. We can come up with some sort of URL format in the RTSP port to specify receiver and frequency, and we can use RTSP to set up RTP streams on UDP ports for the clients to pick up. A frame format can be defined or stolen in RTP for the I/Q data we need as well. We can probably use some of the work of others in the forms of RTSP/RTP libraries. The advantages of this are that RTP is designed to transport time-sensitive media like this that requires a low amount of jitter. We're not too different than streaming video or audio in that regard. Additionally, RTSP and RTP are well understood, and will flow past many firewalls without any problem.<br>
<br>
Again, a fairly ambitious idea, and maybe not a "1.0 feature" but something to think about at least.<div class="im"><br>
<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Regards,<br>
<br>
John g0orx/n6lyt<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
HPSDR Discussion List<br>
To post msg: <a href="mailto:hpsdr@openhpsdr.org" target="_blank">hpsdr@openhpsdr.org</a><br>
Subscription help: <a href="http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org" target="_blank">http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org</a><br>
HPSDR web page: <a href="http://openhpsdr.org" target="_blank">http://openhpsdr.org</a><br>
Archives: <a href="http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/" target="_blank">http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/</a><br>
<br>
</blockquote>
<br></div><font color="#888888">
--<br>
Jeremy McDermond (NH6Z)<br>
Xenotropic Systems<br>
<a href="mailto:mcdermj@xenotropic.com" target="_blank">mcdermj@xenotropic.com</a></font><div><div></div><div class="h5"><br>
<br>
<br>
<br>
_______________________________________________<br>
HPSDR Discussion List<br>
To post msg: <a href="mailto:hpsdr@openhpsdr.org" target="_blank">hpsdr@openhpsdr.org</a><br>
Subscription help: <a href="http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org" target="_blank">http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org</a><br>
HPSDR web page: <a href="http://openhpsdr.org" target="_blank">http://openhpsdr.org</a><br>
Archives: <a href="http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/" target="_blank">http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>The dose makes the poison. -- Paracelsus<br><br>Please note new phone numbers:<br>mobile: (908) 442-8863<br>work: (908) 428-4916<br>