[hpsdr] NVIDIA Jetson Nano SBC - YouTube video

[Scott Traurig]

> On Mon, Apr 29, 2019 at 12:21 PM Brian Lloyd <brian at lloyd.aero> wrote:
>
>>
>> We now have LinHPSDR. It supports protocols 1 and 2 of the HPSDR series
>> of radios concurrently. (Wow, already better than PowerSDR/Thetis in one
>> respect.) It appears to me to have a MUCH better potential for expansion
>> than does PowerSDR/Thetis. It is already logically more modular. It does
>> look like it is clearly moving in the direction you say you would like
>> to go (something more capable than PowerSDR/Thetis). The key is a
>> critical mass of people to use it and provide feedback to the builders
>> so that they have the motivation to keep developing.
>>
>
> - But that critical mass does not exist. When was the last time linHPSDR
> was updated?
>
> - Linux does not support all of the other software I want to use: DDUtil,
> JS8Call, N1MM, DXLabs, among others.
>
> - linHPSDR is missing features I now find important to my operations:
> leveler, pre and post EQ, CFC compressor, ALC adjustments, the new
> VOX/DEXP, N1MM "focusmaster", diversity (really beamforming), PureSignal,
> MIDI controller support--the list is too long to write. And for the CW
> folks, there is no high performance QSK. If we survey a mere dozen users
> this list will get VERY long.
>
> - Linux does not support my low latency ASIO sound hardware interface.
>
>
>> Scott, it is time. We have enough now to actually get on the air and do
>> nearly everything we want to do, without having to resort to running
>> Windows. It is time to repartition some disks.
>>
>
> I don't agree. Looking at only my list above, some of which are things I
> use every day and all are things I use frequently, and not even adding the
> other features and functions desired, and used daily, by the entire
> PowerSDR/Thetis demographic, linHPSDR is still many thousands of lines of
> code away from being ready to be the "daily driver" client software for
> most of the openHPSDR user community.
>
> Mind you, I'm not saying that linHPSDR development, or other alternative
> client development, should not occur. I'm only saying that it is not
> sufficiently mature or feature laden for me to be motivated to make the
> transition at this time. This is, of course, a chicken and egg type
> problem. If no one uses it where is the motivation for developers to
> continue? But right now the gap is too large for me to jump.
>
> I should add that I am very comfortable with Linux, have used Linux from
> time to time on various personal projects and certainly for a great many
> work projects, was an early and enthusiastic adopter of piHPSDR, built my
> own piHPSDR controller unit (a quite nice one if I may say so), and yet
> development stopped on piHPSDR. So now I am less enthusiastic, at least
> until I witness a some sort of significant rebirth in the Linux client
> domain.
>
> Finally, I am more than willing to pay money for good software. If that
> means the price of admission is Windows, I'll pay it. If somebody wants to
> write a kick-ass software environment for openHPSDR and wants to charge me
> two, three or even four hundred dollars for it, I'll happily pay for it if
> it is better than what I have now. I have too much invested in hardware to
> let it be shackled by mediocre software and firmware. Mind you, there is a
> lot to dislike about PowerSDR and Thetis from a developer point of view.
> But from a user perspective those clients still provide the most
> functionality by a wide margin.
>
> 73,
>
> Scott/w-u-2-o
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/attachments/20190429/66667915/attachment.html>