<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
********************************<br>
Well said Steve!!<br>
I'm very happy with the current mRX PS GUI and very happy with the
performance.<br>
I've been enjoying the ride since those articles in RadCom; the
HPSDR has been THE radio in my shack since January 2009.<br>
Many, many thanks again to all the gang mentioned & perhaps a
few others.<br>
Mind you, it would be interesting to get some software running on
Linux/Ubuntu, perhaps cuSDR with a few "apt-get" statements?<br>
73, Hans VK5YX.<br>
********************************<br>
<br>
<div class="moz-cite-prefix">On 26/10/16 14:34, Steve Ireland wrote:<br>
</div>
<blockquote cite="mid:5A2AE99E1F524AF3A1B722870DD60BF7@StevesHPpcPC"
type="cite">
<pre wrap="">***** High Performance Software Defined Radio Discussion List *****
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<div dir="ltr">
<div style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR:
#000000">
<div>G’day </div>
<div> </div>
<div>It has been interesting to follow the discussion in
regard to the development of software for the various pieces
of hardware produced through HPSDR and the commercial
extension of this by Apache Labs.</div>
<div> </div>
<div>As a scientific journalist and ‘Igor’ to my great friend
Phil Harman VK6APH/VK6PH’s ‘Dr Frankenstein’ in his
explanation of basic SDR principles in the RSGB’s RadCom
magazine and their extension into HPSDR development, there
are a couple of basic ideas/principles that Phil works by
which I think recounting here would be timely.</div>
<div> </div>
<div><em>1. The development of open PowerSDR and the
associated software/hardware is a hobby for all of us
principally concerned in it</em></div>
<div> </div>
<div>CuSDR is a fantastic piece of software development. Part
of this is it has a wonderful GUI, but it is a fully
integrated piece of software that Hermann DL3HVH kindly
developed in his spare time until he developed a very
debilitating and life-changing medical condition that meant
he could no longer continue its development. </div>
<div> </div>
<div>People should accept the development of CuSDR has
stopped. It seems to me the only way this situation could
possibly change is if a suitably skilled programmer is
prepared to step forward and approach Hermann to see if he
would consider handing over a copy of his code for future
open source development.</div>
<div> </div>
<div>I hope I’m wrong, but don’t see anyone rushing forward to
offer Hermann their services.</div>
<div> </div>
<div><em>2. If no-one volunteers to carry out a particular
part of a development and then sees it through, it ain’t
going to happen </em></div>
<div><em></em> </div>
<div>The development of Open PowerSDR has been done by a a
small group of very dedicated enthusiasts who give their
time freely (literally) – take a bow Bill Tracey, KD5TFD,
Doug Wigley, W5WC and Dr Warren Pratt, NR0V. Similarly, the
hardware development has kindly done by a similar small
group of very dedicated volunteers, of which Kjell LA2NI is
one.</div>
<div> </div>
<div>The software works well but everyone is a volunteer, with
their own interests and abilities, which means that software
development doesn’t necessarily proceed in a logical or
straightforward manner. If there had been someone who had
volunteered to re-do the GUI side and had the knowledge,
ability and time to complete this, it would have happened!
No volunteer who could do this means no change in the GUI. </div>
<div> </div>
<div align="left">On a final note, for me, there is one thing
that has - and will always - limit the development of
software defined amateur radio – there are simply not enough
people who are interested in writing software for it, have
the necessary skills do it and are prepared to volunteer
their services to do it.</div>
<div align="left"> </div>
<div align="left">However, thankfully there are a few who are
– but we shouldn’t expect miracles from them, or that they
devotedly do exactly what we want them to do. </div>
<div> </div>
<div>Vy 73</div>
<div> </div>
<div>Steve, VK6VZ/G3ZZD </div>
<div> </div>
</div>
</div>
<br>
<table style="border-top: 1px solid #D3D4DE;">
<tbody>
<tr>
<td style="width: 55px; padding-top: 13px;"><a
moz-do-not-send="true"
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient"
target="_blank"><img moz-do-not-send="true"
src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-tick-v1.gif"
style="width: 46px; height: 29px;" height="29"
width="46"></a></td>
<td style="width: 470px; padding-top: 12px; color: #41424e;
font-size: 13px; font-family: Arial, Helvetica,
sans-serif; line-height: 18px;">Virus-free. <a
moz-do-not-send="true"
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient"
target="_blank" style="color: #4453ea;">www.avast.com</a>
</td>
</tr>
</tbody>
</table>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
HPSDR Discussion List
To post msg: <a class="moz-txt-link-abbreviated" href="mailto:hpsdr@openhpsdr.org">hpsdr@openhpsdr.org</a>
Subscription help: <a class="moz-txt-link-freetext" href="http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org">http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org</a>
HPSDR web page: <a class="moz-txt-link-freetext" href="http://openhpsdr.org">http://openhpsdr.org</a>
Archives: <a class="moz-txt-link-freetext" href="http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/">http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/</a></pre>
</blockquote>
<br>
</body>
</html>