Hi Martin,
In order to localize the issue could you try this test:
in the call input field press F6 (your callsign) twice with no delay between
the presses.
Do you hear the half space between the callsigns or do they run together?
73,
Zoli
On Tue, Dec 24, 2024 at 02:31:57AM +0100, Martin Krat
It doesn't change anything if I'll use version from apt, or from git. I'll try
to contact with developers.
Thanks
Br
Marcin
Wysłano z bezpiecznej poczty e-mail Proton Mail.
--- Original Message ---
niedziela, 28 sierpnia 2022 21:45, Csahok Zoltan napisał(a):
> Check your libcw6 ve
Check your libcw6 version. There was a fix in 3.5.1 for something similar.
(see also http://unixcw.sourceforge.net/news.html )
73, Zoli
On Sun, Aug 28, 2022 at 07:19:04PM +, Marcin SP6MI wrote:
> It was Slackware, it doesn't have by default option to install tlf, it has to
> be compiled and
It was Slackware, it doesn't have by default option to install tlf, it has to
be compiled and installed manually.
No during test in ubuntu, I've found that cwdaemon starts extending dah signals
and ends transmission with setting carrier. It's strange, not sure if it's
causes by interface driver
It could also be that your distro's (older) TLF was started instead
of the one you compiled due to PATH issues.
73,
Zoli
On Sun, Aug 28, 2022 at 07:02:33PM +, Marcin SP6MI wrote:
> Hi,
> I was running in from subfolder in my $HOME, and tlf was built from latest
> git version. Ok, I'll invest
Hi,
I was running in from subfolder in my $HOME, and tlf was built from latest git
version. Ok, I'll investigate this, now I'm testing on latest Ubuntu, and looks
that this problems doesn't occur.
Thanks for tip.
All the best,
Br
Marcin SP6MI
Wysłano z bezpiecznej poczty e-mail Proton Mail.
Hi Marcin,
Thanks for reporting this issue.
I assume that you were running TLF from a directory that was not
writeable by your user (e.g. / or /usr/bin).
Could you check if this issue goes away when starting TLF
from a writeable directory? You could test writetability
by executing
touch .paras
b
