$ ./build_linux.sh
would run I had to run this$ git clone https://github.com/drowe67/freedv-gui.git
>>> an email to digita...@googlegroups.com
>>> <mailto:digitalvoice+unsub...@googlegroups.com>.
Hi Peter.
Yes. In my case, I downloaded a zip of the Git repository, and unzipped that into a folder. I've had some bad experiences with Git in the past, and don't trust it any more (way too easy to damage a repo' in error) though I know others who rave about it.
What Linux OS are you using, on what hardware? I'm running Mint 19.2 64 bit, on Dell or HP hardware. An 8 core Dell XPS laptop and 4 core Small Format HP desktop, both Intel based, 6 and 8G RAM respectively.
The laptop is dual boot, Linux by default, Win7 if some radio
programming is needed, that can't be done with CHIRP. (DMR
usually.) The HP is Linux only.
The Dell XPS laptop only has the single internal single sound system, while the HP machine has multiple internal sound ports (front headset port, rear line-in/line-out, HDMI/DVI and so on) + the two external devices that are attached to two radios, the SDR dongles, and a USB headset.)
I find ALSA is a pain to use in that environment, as before the instances move about each boot. But I have used ALSA's scripting interface in the past on another machine, so that a mobile DireWolf based APRS dual band station/gateway would start-up correctly, but that was over 3 years ago, and a different flavour of Linux (Linux Lite, still Debian based, on an Acer One netbook!)
In essence, that was as much a dedicated system as any, and I'm sure I could do the same with FreeDV on a dedicated box, but in this case I would like it to co-exist (though not always running at the same time) with other audio interface software I use, that is ludicrously easy using Pulse and Pavu, but a right royal restricting pain in the butt if I have to use ALSA.
Unless, anyone knows how to get ALSA to share RX devices with multiple applications at the same time. (That Pulse permit's and handles without question.)
I have looked into installing the JACK system, but it seems there are issues on Debian based systems, where Pulse is pre-installed.
~ ~ ~
Lastly. "Playing" in single card RX only mode, works. Playing
back the test wav files, work, with the exception of Horus mode.
Before UDP was enable, FreeDV just quit if you tried to start
that.
With UDP enabled, when you try to play the Horus test file from the website, it fill's the screen with "Many" copies of the file chooser dialogue. Needing FreeDV killing off via the command line in another workspace! However if left to it's own devices, it eventually crashes and burns anyway. (I don't know any HAB users of Horus in the UK or EU, so is probably a non-problem, most use DlFldigi with custom RTTY settings, or LORA systems.)
~ ~ ~
PTT? Never had a problem. There again, I grew up with RS232 and am fully aware of all it's little foibles.
73.
Dave G8KBV.
You received this message because you are subscribed to a topic in the Google Groups "digitalvoice" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/digitalvoice/TUTSQXqKNx8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to digitalvoice...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/digitalvoice/cfe2324f-8755-491f-a62c-8513b1c5f937%40googlegroups.com.
Now, the next problem. I ran pasuspender /usr/local/bin/freedv and now the audio config shows the
Jim W6JVE
Hi.
Indeed, I've been doing the same, but with QSSTV taking audio from the Goonhilly WebSDR, using PA to route the "RX Audio" from the "monitor" of the "default output device", that was being used as the input source for QSSTV.
(This running a fully up-to-date Mint 19.2, 64 bit, with the Cinnamon desktop.)
I've done exactly the same (sometime simultaneously) with Fldigi
too.. Not only with the QO100 WebSDR, but with other HF SDR's on
the web. Just "tune in" and watch the appropriate decoder, no
need to keep launching and killing decoder app's.
Sadly, with FreeDV, this sort of trick doesn't seem to be an option, not at the moment without even more physical sound devices and patch cables!.
73.
Dave G0WBX.
--
You received this message because you are subscribed to a topic in the Google Groups "digitalvoice" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/digitalvoice/TUTSQXqKNx8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to digitalvoice...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/digitalvoice/CD6A54F7-9052-4B8B-819C-19BEB0C0E181%40gmail.com.
You received this message because you are subscribed to the Google Groups "digitalvoice" group.
To unsubscribe from this group and stop receiving emails from it, send an email to digitalvoice...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/digitalvoice/9173881b-d253-41f4-96be-aca7d8c4740en%40googlegroups.com.
Hi.
I don't know how they do it, but many Ham applications seem to use ALSA for their sound I/O, but in a way that routes through Pulse, then probably back to ALSA. I don't truly know.
But I and others regularly use more than one sound card
application simultaniously under Linux, without
issues.
Here we have Audacity and Fldigi, both configured to use Pulse via ALSA, and sharing the same stream (I have an old iMic device used for my HF radio) without any issues at all.
Each is also using a different sample rate, as far as they are concerned. Audacity using it's default 44100 rate, fldigi it's default 8000 sample rate.
I have in the past had Fldigi, WSJTx, QSSTV and Audacity, all
running at the same time, "listening" to the same source. And
also able to be easily flipped to another source ("Input Device"
say the VHF radio) without bringing the world crashing down, or
disturbing the application that just had it's audio stream
re-sourced.
It all works seamlessly. And has done for some years, allowing
one to change levels as seen by the different applications,
without affecting the others.

The above is a screen scrape from this Mint 19.3 64 bit system,
running on 10 year old 4 core Intel I5 based hardware, with 8G
RAM.
Sadly, it is currently impossible to do this with FreeDV if you
have any instance of PavuControl running, FreeDV gets utterly
messed up in it's audio device selection, eventually crashing and
burning, and also de-stabilising other programs as a result.
We have to ask, Why? (At least two of those in the above list, are also QT based applications, so what do they do different? They are open source too, but that level of programming is way above my grey cell ability to understand.)
As before, I'm willing to test, but the last install of a binary I tried, was floored by undocumented and unresolvable dependency issues. (Other .deb file distributed applications, manage to detect and fix any needed dependencies, "automagically".)
I tried a build from source on another Mint 19.3 machine, but
also found dependency issues there that I was unable to resolve,
resulting in a lack of enthusiasm about it all. How many other
potential users/testers etc have been put off by that? To this
day, the last successful build of FreeDV, was V4.1 Dev. That went
100% to plan as described in the documentation at the time.
I'm actually considering removing and flushing FreeDV from the systems here. As on HF the noise level is such that it can't reliably decode anything but the strongest stations anyway (that of course would be perfect copy under analogue SSB.)
Not that I've ever seen/heard any FreeDV signals other than on
80m on Sunday Mornings for the RSGB news. The QSO finder page
always seems unused when I look...
Coupled with the issue that currently it is impossible to do anything else "sound card digi-mode" wise, with the computer if FreeDV is running.
I would like to experiment with it on VHF/UHF, but until the crazy restriction on the use of the sound subsystem when it is running is resolved, I can't.
When the weather warms up, and we can get out and about again, I
hope to get out portable (or at least vehicle portable) to get
away from the urban RFI Smog, just to see what it can do in a
quiet location. Assuming I can find such a spot!
73.
Dave G8KBV (G0WBX is also me. Well, the licence fee's are zero,
so why not...)
--
You received this message because you are subscribed to the Google Groups "digitalvoice" group.
To unsubscribe from this group and stop receiving emails from it, send an email to digitalvoice...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/digitalvoice/6b629f25-a163-c67a-f214-f30f2831f52b%40googlemail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/digitalvoice/42170494-4a2f-4bdc-ac73-c798e1a53156n%40googlegroups.com.


Hello Mooneer. (And listeners.)
Coming back to this...
I've removed the old 1.4_dev files. AFAIKT, it was all built in the source tree, and run from there...
But, trying your .deb's again, it is all a bit of a disaster.
So far, all I've got to install is LPCNet 0.2.0 from lpcnet_0.2.0_amd64.deb
in your dropbox.
That the file codec2_0.9.2_amd64.deb (also in your dropbox) said it needs.
But even after LPCNet is successfully installed, the codec2 .deb still fails saying :-
Error: Dependency is not satisfiable: LPCNet (>= 0.2.0)
PLEASE PLEASE (sorry) Test such things as .deb files on a
"Clean" system (even in a VM) that you have never done any
development work with to make sure the result is as desired,
before making them available to others for testing.
If you're using Virtual Box, it is easy to have a "clean" master
VM, that you can (A) clone when needed for testing, not needing to
go through the usual install every time. And (B) keep up to date
from the distro repo's while keeping it "user application" clean.
Or, create .deb files that can identify and fetch their own
dependency needs, as many other software authors manage to do it
seems. Heck, even the OS updates using the same underlying
system, manages to find what's needed "automagically" when
something like the kernel is updated.
Currently, I now have no FreeDV system here at all.
Oh, and why does the codec2 .deb "readme" give instructions to build it from source? AFIK the .deb file(s) should be installing executable's, or is that not the case?
If not, it needs documenting in plain sight.
Sorry if I sound spiky, I've just wasted another two hours on this ending up with a headache, also resulting in no FreeDV at all, not that I could use it much on the low bands anyway.
Regards.
Dave G8KBV
Ha-ha… you wasted 2 hours, I wasted about 2 months and never got it to work properly..
--
You received this message because you are subscribed to the Google Groups "digitalvoice" group.
To unsubscribe from this group and stop receiving emails from it, send an email to digitalvoice...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/digitalvoice/5eab5e2c-ba37-1ca9-34b7-124ecff6fc15%40googlemail.com.
--
You received this message because you are subscribed to the Google Groups "digitalvoice" group.
To unsubscribe from this group and stop receiving emails from it, send an email to digitalvoice...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/digitalvoice/5eab5e2c-ba37-1ca9-34b7-124ecff6fc15%40googlemail.com.