>Why would you need 100GB of storage? That's a LOT. I've been running
>many a Linux host on 32GB of disk/ssd (or much less) for a very long
>time.
>
My base Debian system is around 16 GB plus a lot of stuff in /home, so yes I
think an embedded system without X and desktop environment could fit easily in
32 GB.
>transmissions. Regardless, don't archive in WAV... archive into MP3 or
>
>OGG and then rotate the files to off-site storage via the Internet. If
>
You could store audio as Codec2 (no transcoding) and save a lot of space.
I made a Codec2 repeater as well, but it uses my own (less optimized ) modems
for VHF and above only. Did not put into production yet, but I have some
transcoding into Opus to send the audio via VoIP also and link sites via
internet which would be a narrow bandwidth (200 kbps) modem using SDR devices
as well.
I'd be interested in David's LDPC to shave 2-3 dB off the current SNR, but have
no time currently to look into it. Can't wait to experiment with 3200 and new
2200 modes to be a rival to 5 kHz FM.
Best regards,
Adrian
>
>> 3) Be a General Purpose Linux box with all the development apps
>> and a remote GUI interface eg. Joe Taylor K1JT compiled and
>> tested the KVASD ARM binary on the BPi box here then made
>> available the ARM binary for WSJT and WSJT-X.
>
>Requiring GUIs on a Raspberry Pi increases the storage required but not
>
>by more than a few GB. It's your choice if you wish to do this on your
>
>remote repeater site.
>
>
>> So, I'd dearly like to run a Real Pi but without a High Speed Disk
>interface
>> on a real Pi, I have no reason to buy one. Yes, I have an original, a
>256Mb
>> one. SD cards broke (wore out) in days. That's why in about 2014 I
>went BPi
>> and have never looked back.
>
>Nothing you've mentioned above cannot be easily fulfilled with a USB
>attached disk/ssd. The Raspberry Pi line of SBCs have supported
>USB-based boot for some time (no longer requiring a microSD card) and
>the USB2 bus (while not super fast for today's standard) will easily
>meet your I/O performance needs.
>
>To your "wore out" issue, this can be a problem for systems that are
>abusing the the SD card (heavy writes all the time). This is easily
>mitigated using a mixture of tmpfs (RAM drives), better logrotation
>schedules, etc. You can see what I recommend here:
>
>http://www.trinityos.com/HAM/CentosDigitalModes/RPi/rpi2-setup.html
>
>
>> Keep smiling guys. I appreciate your thoughts.
>
>And yours too!
>
>
>> Current models with SATA on the SoC:
>>
>> Banana Pi M2 Ultra
>> Banana Pi M2 Berry
>
>Very nice hardware and I've considered upgrading but I've never been
>able to justify the high performance, lots of I/O possibilities, etc.
>I
>just really don't need it. The real differentiation is the community
>support. Raspbian (OS) and the Raspberry Pi (hardware) have excellent
>support, are constantly updated, improved, etc. The Rpi 3B+ still
>isn't
>using the fastest ARM processors, offer the best I/O possibilities,
>etc,
>but it was never intended to... mind you it does give you 4x ARM8 cores
>
>@ 1.4Ghz, 1GB of RAM, GE & 802.11AC wifi, and BT 4.2 for $35. That
>still staggers my mind.
>
>Anyway... up to you. Now back to the CODEC2 show!
>
>--David
>KI6ZHD
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Freetel-codec2 mailing list
Freetel-codec2@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freetel-codec2
