[hpsdr] PowerSDR, cuSDR and new GUI for HPSDR.

[H.A.Meijer]

Hi,


In my opinion, a nice "bling bling GUI" is  "nice", but not much more 
then just "nice", more important are the basic (W)DSP RX/TX high performance

we have now for some time.

Filter shapes, noise-blanker, noise reductions, low latency and best of 
all, adaptive predisposition for TX. etc. etc. etc.

I can live with a "dated GUI"  and hope that the developers keeps 
spending there time on these "basic-performance" and not on

some "bling bling GUI nonsense".


sorry,  just had to express my feelings.....


73'

Bert PA2XHF



Op 22-10-2016 om 7:16 schreef Hans Remeeus:
> ***** High Performance Software Defined Radio Discussion List *****
>
>>
>> I see your point and I have missed you at the last meetings in 
>> Fr.hafen! It was a real loss for the HPSDR project that you had to 
>> stop your work on cuSDR.
>>
>> What I meant with my comment about PSDR was that as the main GUI is 
>> kept in Thetis and if it is to be continued then many modifications 
>> have to be done to get it more easy to use.
>>
>> But there is no doubt about that a completely new GUI is needed! And 
>> in my opinion, cuSDR is the best I have seen so far. I remember the 
>> first time I tested it with Hermes and it worked perfect at the first 
>> attempt! And you said that I was the first that even tested it with 
>> Hermes! So I really hope that you are going to be able to continue 
>> the work on it.
>>
>>  I decided to move this discussion to OpenHPSDR forum. I feel that 
>> the discussion on the other forum easily runs out of control!
>>
>> 73, Kjell
>>
>>
>>
>> På Thu, 20 Oct 2016 07:53:59 +0200, skrev Hermann hvh.net at gmail.com 
>> [apache-labs] <apache-labs at yahoogroups.com>:
>>
>>     I totally disagree here.
>>
>>
>>     There are not only some modifications needed here Kjell, sorry.
>>     The complexity of the Software has reached a stage, where the
>>     lack of a well-defined and well maintained software architecture
>>     is crucial.
>>     I have tried to show this up at various occasions and with my
>>     cuSDR. This effort was well acknowledged by some, but that was
>>     all. Unfortunately after my Burn-Out three years ago I had to
>>     stop the development, left with a stroke in my left eye. It was
>>     impossible to continue my day job (embedded software
>>     architectures for multicore ECUs in automotive) AND doing 3 to 4
>>     hours software development for cuSDR daily.
>>
>>     I have seen these problems in many professional environments,
>>     where neglecting the amount of work and costs for a thorough
>>     software development ended in a desaster.
>>
>>
>>     73, Hermann DL3HVH
>>
>>
>>
>>
>> _______________________________________________
>> HPSDR Discussion List
>> To post msg:hpsdr at openhpsdr.org
>> Subscription help:http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
>> HPSDR web page:http://openhpsdr.org
>> Archives:http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/
>
>
>
> _______________________________________________
> HPSDR Discussion List
> To post msg: hpsdr at openhpsdr.org
> Subscription help: http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
> HPSDR web page: http://openhpsdr.org
> Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/attachments/20161022/46f5984e/attachment.htm>