When running pipewire on Debian PC where you use browser, music etc,
using JamesDSP to handle the sound, it makes for a better
music experience, with quality sound, same or better than previous ;l
https://flathub.org/apps/me.timschneeberger.jdsp4linux .
However the allow-list app # feature s
See https://wiki.debian.org/PipeWire
73
vk4tux
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Yes, what Hranfnkell said...
If we have been keeping up with our Linux journals and news. We would
realize that Pulse is out, pipewire is in. Announcement made over 18
months ago. Debian following the Enterprise has implemented pipewire
with that strange pulse bridge for backward compatibi
Thank you, but I dont think there is any code to change really. The bug is
not in wsjtx, it is in Qt vs pulseaudio. Just dont use the pulse audio
devices.
73 de TF3HR
On Tue, Nov 7, 2023 at 7:23 PM Daniel Uppström via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> Nice work, well done!
Nice work, well done!
Main developers, will you include this into the main branch?
73 Daniel SM6VFZ
On 11/5/23 19:38, Hrafnkell Eiriksson via wsjt-devel wrote:
The root cause of this all seems to be a bug in the interface between
pulseaudio (or the puseaudio interface for pipewire in Bookwork)
The root cause of this all seems to be a bug in the interface between
pulseaudio (or the puseaudio interface for pipewire in Bookwork) and Qt
audio device handling.
After suspending the SoundInput the audio thread is stuck spinning in a
loop somewhere in the qt multimedia plugin for pulse and/or th
And the reason for the 100% cpu load that prevents the audio out from
running seems to have something to do with the suspend() call on the
SoundInput. If I comment that out, nothing goes to high CPU load.
Just disabling monitoring through the GUI (main window) is enough to go to
100% cpu load on ws
Splitting the work done by the m_audioThread in widget/mainwindow.cpp into
two threads, m_audioInThread and m_audioOutThread also solves the problem
and is probably a better solution.
I've put the modulator and soundOutput on m_audioOutThread and the detector
and soundInput on the m_audioInThread.
I've been trying to figure out why I get no audio output on the Raspberry
Pi and have found out that it seems to be related to threading.
After liberal sprinkling of qDebug() in the code to see what was happening
and in what order things were called I figured out that the Modulator code
was never
n, Samsung Galaxy smartphone
Original message From: Hrafnkell Eiriksson via wsjt-devel
Date: 10/29/23 5:15 PM (GMT-05:00) To:
WSJT software development Cc: Hrafnkell
Eiriksson Subject: [wsjt-devel] No audio output on raspberry
pi HiI recently installed wstjx 2.6.1 on a RPi4 run
Hi
I recently installed wstjx 2.6.1 on a RPi4 running an up to date Bookworm
version of the Debian/RaspberryPI-OS. Wsjtx is installed from the
distribution repository.
I am unable to get it to output audio from wsjtx.
I've tried two different USB connected audio interfaces, a DigiRig mobile
and
11 matches
Mail list logo
