Re: fldigi abort witnessed - Pi 4.2.05.24
On Sat, 11 Jan 2025 02:23:04 -0800 "Dave, G?WBX via groups.io" <g8kbvdave@...> wrote: Re:-
I would suggest that you provide feedback to the pipewire and
wireplumber developers OK Brian, I have signed up for gitlab, and have read access at least.
I'll wait a day and see if I gain access to comment/raise an issue.
(It seems they have been having a lot of spam posting issues.)
I thought Github was confusing enough, but gitlab takes the biscuit
in that respect! No doubt if one immerses oneself into it, the mists
clear, but for occasional users reporting issues, not helpful from
first impressions. I'll try and stick with it though.
I'll report back here on any progress with the issues I have found,
if they regard them as issues of course. I hope it works out, if you have any further problems you could try emailing Wim Taymans who works for Redhat and is the lead developer for pipewire. I don't have an email address to hand but it should be relatively easy to find. -- Brian G8SEZ
|
Re: Bug report/request - failure of various RsID/Lk operations fldigi V3 to V4
Bob,
Please download, install, and test fldigi-4.2.06.20
posted at
commit 62c2e6ca9566f04035a9c9bb5258348be369c3a4
Author: dave-w1hkj <w1hkj@...>
Date: Fri Jan 10 08:59:28 2025 -0600
RSID squelch
* correct RsID detection behavior
commit 33c741533ee618b10b405815abcbcccefbebc185
Author: dave-w1hkj <w1hkj@...>
Date: Thu Jan 2 18:41:09 2025 -0600
t
* reverted interleave depth to 25 ( 1 sec )
* reverted flush length to 20.
Those users testing THOR-25, please note that all testers should be on the same fldigi revision.
73, David
W1HKJ
On 1/10/25 01:23, Bob Cameron, VK2YQA
via groups.io wrote:
toggle quoted message
Show quoted text
Wonder if you would review this again Dave. Same behaviour in
4.2.06.19 (yeah I am slow...)
What I didn't make clear in my OP was with "Retain tx freq
lock" enabled, the operational expectation is that the RX freq
would shift to meet the RSID centre, but leave the TX frequency
where it is. If "Retain tx freq lock" is disabled I expect the
TX and RX to shift together. (which is what it does)
Note there us differing action too if the modem changes vs not.
Please try a few RSID's of the same modem, then try changing the
modem.
Cheers Bob
On 19/8/24 20:22, w1hkj wrote:
Bob,
This is on 4.2.05.25
The transmit stays locked at 7071.0 and the Rx is at 7071.3.
Dave
On 8/14/24 21:54, Bob Gypay wrote:
Crossposted? to both fldigi-devel and linuxham
Tested on v4.2.04.11 and 4.2.04.24 against 3.23.21 (By John
VK2ETA)
Using PSK250RC7, PSK500RC3, PSK125RC10 and PSK63RCx (ie not
all modems checked)
With "Retain tx freq lock" enabled in RsID configuration
plus Lk set, V4 no longer enables Lk operation nor splits
the wfall TX/RX for the PSK125RC &? PSK63RC modems. The
PSK250RC and PSK500RC modems act in the same way as 8PSKx
and OFDMx modems, shifting TX/RX together, ignoring the RsID
config setting and also not responding to Lk.
It might also be a good idea to force Lk operation when
setting this RsID config parameter and update the tooltip to
explain what is happening.
As it currently stands a mode such as PSK63RC5 is quite
troublesome to RsID tune as disabling TX lock can cause
TX/RX "walking" if any RIT is in play.
And since it is in the same "auto" tuning area it might be
a good idea to modify the AFC button tooltip to grey out on
unsupported modes. ie only single carrier PSK.
Cheers Bob VK2YQA
_______________________________________________
fldigi-devel mailing list
fldigi-devel@...
|
fldigi and flrig communicate
using the flrig xmlrpc server.? You can monitor the data
requests and responses using the trace tool:
The data streams will be added to the trace.txt file in
$HOME/.flrig (or the folder specified by --config-dir
<PATHNAME>).
That might give you a clue as to what is occuring.
David
On 1/11/25 04:42, Dave, G?WBX via
groups.io wrote:
toggle quoted message
Show quoted text
Thanks Dave (HKJ) that works OK.
However...? The first two invocations of the macro after creation,
failed to put the radio into TX.? Since then, it does!
Any insight about that?
Using Flrig as the radio interface.
73.
Dave G0WBX.
From: Dave, W1HKJ
Date: Fri, 10 Jan 2025 13:46:21 GMT
<PUSH>
<TXRSID:off>
<MODEM:NULL>
<CWID><TX><RX>
<@TXRSID:on>
<@POP>
You need to reset the TX RsID and modem restore using the @
predecedent to insure those occur after returning to the receive
mode.
Dave
--
Created on and sent from a Unix like PC running and using open source software:
|
Thanks Dave (HKJ) that works OK.
However...? The first two invocations of the macro after creation,
failed to put the radio into TX.? Since then, it does!
Any insight about that?
Using Flrig as the radio interface.
73.
Dave G0WBX.
From: Dave, W1HKJ
Date: Fri, 10 Jan 2025 13:46:21 GMT
<PUSH>
<TXRSID:off>
<MODEM:NULL>
<CWID><TX><RX>
<@TXRSID:on>
<@POP>
You need to reset the TX RsID and modem restore using the @
predecedent to insure those occur after returning to the receive
mode.
Dave
--
Created on and sent from a Unix like PC running and using open source software:
|
Update...
The Macro as specified earlier still at times fails to put the rig into Transmit.
(Seems more prevalent if you leave the system idle for a while.)
What tests would you like done?
73.
Dave G0WBX.
--
Created on and sent from a Unix like PC running and using open source software:
|
Re: fldigi abort witnessed - Pi 4.2.05.24
Re:-
I would suggest that you provide feedback to the pipewire and wireplumber developers
and
have lots of messages appearing and the main developers see them daily.
--
Brian G8SEZ
?
OK Brian, I have signed up for gitlab, and have read access at least.? I'll wait a day and see if I gain access to comment/raise an issue.
(It seems they have been having a lot of spam posting issues.)
?
I thought Github was confusing enough, but gitlab takes the biscuit in that respect!
No doubt if one immerses oneself into it, the mists clear, but for occasional users reporting issues, not helpful from first impressions.
I'll try and stick with it though.
?
I'll report back here on any progress with the issues I have found, if they regard them as issues of course.
?
73.
?
Dave G0WBX.
|
Re: [KM4ACK-Pi] Trouble installing VARA on RPi4
Adrian:
Many thanks for the reply ! Linux noob here, but studying. I think I have vb6run (I think SP6) and mfc42 already installed, but I will check.?
I do NOT have cabextract. I’ll also check the others. Now, with a 32 bit system, do I need wine64 or wine32 ?
I need to document all this, because if I actually do get this right, there are a lot of guys that want to know about it. I’ll keep notes. :)
73, Jamie
toggle quoted message
Show quoted text
On Jan 10, 2025, at 9:22?PM, Adrian Fewster, VK4TUX via groups.io <vk4tux@...> wrote:
?
I run some G4HFQ Yaesu VB6 software? (FTBCAT, FTBbasicMMO etc)
?under wine here; Had to do ;
winetricks
vb6run
winetricks
mfc42
also
sudo apt
install cabextract
sudo apt
install wine wine64 libwine fonts-wine
With good results
Its interesting with codeweavers 'Crossover' that I paid $ for,
that there is no apparent solution to run VB6 programs.
Their forum also ignored the question. wine/winetricks saved the
day.
vk4tux
On 11/1/25 12:46, James C. Hall, MD
WB4YDL via groups.io wrote:
OK, using Winetricks, I installed VB6, and a few missing
other files. I was still getting errors about missing or
misinstalled OCX files. I had to retrieve them at OCXme.com.
Finally, VARA FM materialized briefly … but shut down
quickly. A buzzkill. The error is something about advapi32.dll.
I tried a different version, but getting the same thing.
“Call from 7BDAACE8 to unimplemented function ADVAPI32.DLL.
PerfEnumerateCounterSet, aborting wine …” Then it calls for
debugger which didn’t run.
I’m close, just not there. Any help appreciated. Going to
copy this to linuxham group as well.
73, Jamie
WB4YDL
PS - while running Winetricks for missing files, this error
box came up
This may be the source of why the VARA install Pi App script
would just stall. I never got this box when I ran it - only with
Winetricks. Tried wineserver -k and -k9, but it never stopped
these boxes. But when I clicked OK, it woul take off and
continue to complete the requested fill.
Again, RPi4 with 32bit Bullseye.
On Jan 10, 2025, at 2:14?PM, James C.
Hall, MD WB4YDL <heartdoc@...> wrote:
?
Well, slowly I’m learning some of this Linux stuff ! HI I have
a couple SD cards that I go back and forth with. What I
decided to do was manually install Box86 and Wine thanks to a
great how-to article -
?
So, I installed VARA and VARA FM, but neither would run -
missing required DLL - a MS Visual Basic. So, I guess this
is where Winetricks comes in to save the day. Lots of
studying to do - but it is kinda fun and interesting.
I could never get the Pi Apps install routine for VARA to
work - it would just stall out in the middle of things. If
anyone can point me in the right direction on installing and
running Winetricks, I would appreciate it.
I may try that Pi Apps script again but on Ethernet
instead of WiFi. Something to try …
73, Jamie
WB4YDL
?Is there a time limit to install
something on a RPi or something ? I’ve been trying
to install VARA (using the Pi-Apps install) and I’ve
noticed that it will go so far in the installation
and just stop - I can wait an hour and it never
moves. The CPU slider on Conky will go down to idle
at 6-7%. I can restart the process and it may get a
little farther (since some things are now
installed), but it again stalls mid-stream. This is
a new Bullseye install with minimal 73Linux items
selected.
I installed VARA previously without issue a
couple years ago and didn’t have any issues thanks
to Jason’s tutorial.
WINE stalls about when installing fonts.
Any suggestions to try ?
73, Jamie
WB4YDL
|
Re: [KM4ACK-Pi] Trouble installing VARA on RPi4
OK, using Winetricks, I installed VB6, and a few missing other files. I was still getting errors about missing or misinstalled OCX files. I had to retrieve them at OCXme.com.
Finally, VARA FM materialized briefly … but shut down quickly. A buzzkill. The error is something about advapi32.dll. I tried a different version, but getting the same thing. “Call from 7BDAACE8 to unimplemented function ADVAPI32.DLL. PerfEnumerateCounterSet, aborting wine …” Then it calls for debugger which didn’t run.
I’m close, just not there. Any help appreciated. Going to copy this to linuxham group as well.
73, Jamie WB4YDL
PS - while running Winetricks for missing files, this error box came up
This may be the source of why the VARA install Pi App script would just stall. I never got this box when I ran it - only with Winetricks. Tried wineserver -k and -k9, but it never stopped these boxes. But when I clicked OK, it woul take off and continue to complete the requested fill.
Again, RPi4 with 32bit Bullseye.
toggle quoted message
Show quoted text
On Jan 10, 2025, at 2:14?PM, James C. Hall, MD WB4YDL <heartdoc@...> wrote:
? Well, slowly I’m learning some of this Linux stuff ! HI I have a couple SD cards that I go back and forth with. What I decided to do was manually install Box86 and Wine thanks to a great how-to article -
?
So, I installed VARA and VARA FM, but neither would run - missing required DLL - a MS Visual Basic. So, I guess this is where Winetricks comes in to save the day. Lots of studying to do - but it is kinda fun and interesting.
I could never get the Pi Apps install routine for VARA to work - it would just stall out in the middle of things. If anyone can point me in the right direction on installing and running Winetricks, I would appreciate it.
I may try that Pi Apps script again but on Ethernet instead of WiFi. Something to try …
73, Jamie WB4YDL
On Jan 6, 2025, at 9:51?PM, James C. Hall, MD <heartdoc@...> wrote:
?Is there a time limit to install something on a RPi or something ? I’ve been trying to install VARA (using the Pi-Apps install) and I’ve noticed that it will go so far in the installation and just stop - I can wait an hour and it never moves. The CPU slider on Conky will go down to idle at 6-7%. I can restart the process and it may get a little farther (since some things are now installed), but it again stalls mid-stream. This is a new Bullseye install with minimal 73Linux items selected.
I installed VARA previously without issue a couple years ago and didn’t have any issues thanks to Jason’s tutorial.
WINE stalls about when installing fonts.
Any suggestions to try ?
73, Jamie
WB4YDL
|
Re: fldigi abort witnessed - Pi 4.2.05.24
Thanks Brian.
?
I will follow that up.
?
73.
?
Dave G0WBX
?
|
Thanks Dave 'HKJ.
?
I'll try that when home tomorrow and let you know.
?
One thing that always frustrates me, is the lack of a context driven help system.? However, achieving that would not be a trivial undertaking.
?
I also fail to find the obvious in the help documentation, I just don't think in the way it is laid out.
?
(Same with general Web searching!? My Google foo is poor.)
?
73.
?
Dave G0WBX.
?
|
Re: Bug report/request - failure of various RsID/Lk operations fldigi V3 to V4
Bob,
I am investigating.
David
On 1/10/25 01:23, Bob Cameron, VK2YQA
via groups.io wrote:
toggle quoted message
Show quoted text
Wonder if you would review this again Dave. Same behaviour in
4.2.06.19 (yeah I am slow...)
What I didn't make clear in my OP was with "Retain tx freq
lock" enabled, the operational expectation is that the RX freq
would shift to meet the RSID centre, but leave the TX frequency
where it is. If "Retain tx freq lock" is disabled I expect the
TX and RX to shift together. (which is what it does)
Note there us differing action too if the modem changes vs not.
Please try a few RSID's of the same modem, then try changing the
modem.
Cheers Bob
On 19/8/24 20:22, w1hkj wrote:
Bob,
This is on 4.2.05.25
The transmit stays locked at 7071.0 and the Rx is at 7071.3.
Dave
On 8/14/24 21:54, Bob Gypay wrote:
Crossposted? to both fldigi-devel and linuxham
Tested on v4.2.04.11 and 4.2.04.24 against 3.23.21 (By John
VK2ETA)
Using PSK250RC7, PSK500RC3, PSK125RC10 and PSK63RCx (ie not
all modems checked)
With "Retain tx freq lock" enabled in RsID configuration
plus Lk set, V4 no longer enables Lk operation nor splits
the wfall TX/RX for the PSK125RC &? PSK63RC modems. The
PSK250RC and PSK500RC modems act in the same way as 8PSKx
and OFDMx modems, shifting TX/RX together, ignoring the RsID
config setting and also not responding to Lk.
It might also be a good idea to force Lk operation when
setting this RsID config parameter and update the tooltip to
explain what is happening.
As it currently stands a mode such as PSK63RC5 is quite
troublesome to RsID tune as disabling TX lock can cause
TX/RX "walking" if any RIT is in play.
And since it is in the same "auto" tuning area it might be
a good idea to modify the AFC button tooltip to grey out on
unsupported modes. ie only single carrier PSK.
Cheers Bob VK2YQA
_______________________________________________
fldigi-devel mailing list
fldigi-devel@...
|
Re: fldigi abort witnessed - Pi 4.2.05.24
On Fri, 10 Jan 2025 10:09:07 +0000 "Dave, G?WBX via groups.io" <g8kbvdave@...> wrote: Emulations are not always perfect of course, it takes only one "edge
case" and all bet's are off..
One thing I know Pipewire prevents, when using Pavucontrol, is
renaming of the devices.? Whatever instructions I follow (that has
always worked in the past) to make that facility available, it just
doesn't even attempt to allow renaming.
This is on LMDE 6, LMDE 5 worked perfectly in that respect.
I have tried WirePlumber, that seems to work (device renaming also,
within that application) and settings were remembered, but each time
it was started, the graphical layout was "re-arranged" differently
(at random, with items spread all over the UI and a tangle of
"wires"!) making it almost useless for most people.
Frankly, for serious usage where "stability of settings" is needed
between sessions, Pipewire still has some way to go.
Plus, detailed info about it is non existent to "varied and sketchy"
if you search online for help, indicating to me anyway, that it is
still someway off being suitable for prime-time distribution.
73.
Dave G0WBX.
Still, trying to figure out why I can only use one LMDE 6 PC as Root,
"my" user, it seems has lost the permissions needed to allow the
Cinnamon desktop to start!? (Something to do with permissions to
access ports 0x00 to 0x3f!)? None of the online solutions so far have
even come close to helping.?? That issue happened either during a
"proper and correct" shutdown, or a later (some days) cold boot. The
PC hardware is fine.
I would suggest that you provide feedback to the pipewire and wireplumber developers and have lots of messages appearing and the main developers see them daily. -- Brian G8SEZ
|
<PUSH>
<TXRSID:off>
<MODEM:NULL>
<CWID><TX><RX>
<@TXRSID:on>
<@POP>
You need to reset the TX RsID and modem restore using the @
predecedent to insure those occur after returning to the receive
mode.
Dave
On 1/10/25 06:47, Dave, G?WBX via
groups.io wrote:
toggle quoted message
Show quoted text
Hi.
I'm sure I had all this working in the past, but not now.......
Not helped by issues with my main PC preventing reliable access to
it.?? That is fully disconnected, cold and dead for now.
Fldigi 4.2.06 with Flrig 2.0.05 on LMDE 6 running on an 8 core
intel based machine, a Dell XPS laptop with 8G RAM, using external
USB connected sound device, and serial port DTR to key the radio,
a TS870s.
Using Fldigi/Flrig for "normal" working is fine, but attempting to
create a macro to send a CWID and "ONLY" a CWID, and I'm
failing...
I'm sure this has cropped up before in the list, but attempting to
create a macro to send a CWID and "ONLY" a CWID, regardless of the
prevailing mode that was being used I can't make work, after some
40 minutes faffing about, so hear I am.
This is the contents behind a freshly assigned "CW ID" Macro
button...
<TXRSID:off>
<PUSH>
<MODEM:CW>
<TX>
<CWID>
<RX>
<POP>
<TXRSID:on>
It fails miserably...
Firstly it doe not always put the rig into TX!? Sometimes it will
for a few attempts, then it'll not bother, but sends audio each
and every time.? (Debugging this with the rig on low power into a
load, while using the default audio device for the TX audio, so
hopefully no QRM being sent.)
It always sends a RSID (TXID button here is enabled by default,
and is not seen to be disabled while the macro runs.)? Then a
burst of Olivia 8/250 (the mode that is present before invoking
the macro) then does the CWID, and goes back to recieve.
The indicated mode does not change in the lower left display of
Fldigi either.
Each individual macro function works exactly as advertised, but
not it seems when combined into one file.? In this case.
What have I missed this time??? I.e.? How to force a macro to
execute sequentially, as it is shown in the editor.
I just want it to key the radio, send an unadulterated CWID
without any TXID or burst of whatever other digimode was being
used, then go back to RX restoring the mode that was in use before
the macro was invoked.
As earlier.? "Normal" Fldigi usage is fine.?? As are the usual
macros for calling answering sending info, logging and closing
QSO's etc.
Confused again and getting fed up with it.
73.
Dave G0WBX.
|
Hi. I'm sure I had all this working in the past, but not now....... Not helped by issues with my main PC preventing reliable access to it.?? That is fully disconnected, cold and dead for now. Fldigi 4.2.06 with Flrig 2.0.05 on LMDE 6 running on an 8 core intel based machine, a Dell XPS laptop with 8G RAM, using external USB connected sound device, and serial port DTR to key the radio, a TS870s. Using Fldigi/Flrig for "normal" working is fine, but attempting to create a macro to send a CWID and "ONLY" a CWID, and I'm failing... I'm sure this has cropped up before in the list, but attempting to create a macro to send a CWID and "ONLY" a CWID, regardless of the prevailing mode that was being used I can't make work, after some 40 minutes faffing about, so hear I am. This is the contents behind a freshly assigned "CW ID" Macro button... <TXRSID:off> <PUSH> <MODEM:CW> <TX> <CWID> <RX> <POP> <TXRSID:on> It fails miserably... Firstly it doe not always put the rig into TX!? Sometimes it will for a few attempts, then it'll not bother, but sends audio each and every time.? (Debugging this with the rig on low power into a load, while using the default audio device for the TX audio, so hopefully no QRM being sent.) It always sends a RSID (TXID button here is enabled by default, and is not seen to be disabled while the macro runs.)? Then a burst of Olivia 8/250 (the mode that is present before invoking the macro) then does the CWID, and goes back to recieve. The indicated mode does not change in the lower left display of Fldigi either. Each individual macro function works exactly as advertised, but not it seems when combined into one file.? In this case. What have I missed this time??? I.e.? How to force a macro to execute sequentially, as it is shown in the editor. I just want it to key the radio, send an unadulterated CWID without any TXID or burst of whatever other digimode was being used, then go back to RX restoring the mode that was in use before the macro was invoked. As earlier.? "Normal" Fldigi usage is fine.?? As are the usual macros for calling answering sending info, logging and closing QSO's etc. Confused again and getting fed up with it. 73. Dave G0WBX. -- Created on and sent from a Unix like PC running and using open source software:
|
Re: fldigi abort witnessed - Pi 4.2.05.24
From: Dave, W1HKJ
Date: Thu, 09 Jan 2025 13:48:52 GMT
Pipewire is designed to emulate the API calls made to Pulseaudio.
Emulations are not always perfect of course, it takes only one "edge case" and all bet's are off..
One thing I know Pipewire prevents, when using Pavucontrol, is renaming of the devices.? Whatever instructions I follow (that has always worked in the past) to make that facility available, it just doesn't even attempt to allow renaming.
This is on LMDE 6, LMDE 5 worked perfectly in that respect.
I have tried WirePlumber, that seems to work (device renaming also, within that application) and settings were remembered, but each time it was started, the graphical layout was "re-arranged" differently (at random, with items spread all over the UI and a tangle of "wires"!) making it almost useless for most people.
Frankly, for serious usage where "stability of settings" is needed between sessions, Pipewire still has some way to go.
Plus, detailed info about it is non existent to "varied and sketchy" if you search online for help, indicating to me anyway, that it is still someway off being suitable for prime-time distribution.
73.
Dave G0WBX.
Still, trying to figure out why I can only use one LMDE 6 PC as Root, "my" user, it seems has lost the permissions needed to allow the Cinnamon desktop to start!? (Something to do with permissions to access ports 0x00 to 0x3f!)? None of the online solutions so far have even come close to helping.?? That issue happened either during a "proper and correct" shutdown, or a later (some days) cold boot. The PC hardware is fine.
--
Created on and sent from a Unix like PC running and using open source software:
|
Re: Bug report/request - failure of various RsID/Lk operations fldigi V3 to V4
Wonder if you would review this again Dave. Same behaviour in
4.2.06.19 (yeah I am slow...)
What I didn't make clear in my OP was with "Retain tx freq lock"
enabled, the operational expectation is that the RX freq would
shift to meet the RSID centre, but leave the TX frequency where it
is. If "Retain tx freq lock" is disabled I expect the TX and RX to
shift together. (which is what it does)
Note there us differing action too if the modem changes vs not.
Please try a few RSID's of the same modem, then try changing the
modem.
Cheers Bob
On 19/8/24 20:22, w1hkj wrote:
toggle quoted message
Show quoted text
Bob,
This is on 4.2.05.25
The transmit stays locked at 7071.0 and the Rx is at 7071.3.
Dave
On 8/14/24 21:54, Bob Gypay wrote:
Crossposted? to both fldigi-devel and linuxham
Tested on v4.2.04.11 and 4.2.04.24 against 3.23.21 (By John
VK2ETA)
Using PSK250RC7, PSK500RC3, PSK125RC10 and PSK63RCx (ie not
all modems checked)
With "Retain tx freq lock" enabled in RsID configuration plus
Lk set, V4 no longer enables Lk operation nor splits the wfall
TX/RX for the PSK125RC &? PSK63RC modems. The PSK250RC and
PSK500RC modems act in the same way as 8PSKx and OFDMx modems,
shifting TX/RX together, ignoring the RsID config setting and
also not responding to Lk.
It might also be a good idea to force Lk operation when
setting this RsID config parameter and update the tooltip to
explain what is happening.
As it currently stands a mode such as PSK63RC5 is quite
troublesome to RsID tune as disabling TX lock can cause TX/RX
"walking" if any RIT is in play.
And since it is in the same "auto" tuning area it might be a
good idea to modify the AFC button tooltip to grey out on
unsupported modes. ie only single carrier PSK.
Cheers Bob VK2YQA
_______________________________________________
fldigi-devel mailing list
fldigi-devel@...
|
CTY-3502 Country Files - 10 January 2025
The Country (CTY) Files were updated on 10 January 2025:
For installation instructions, start at:
Hover your mouse over the word Contest in the menu, then select the
software you are using.
To install the file, follow the link to your software at the top of the page.
If you are interested in a bigger CTY.DAT for everyday logging, you can get
it here:
Note that the release notes (and Version Entity) for this larger file are
different than what is shown below. There is a separate link to them.
As a reminder, there is an RSS feed of the latest country file announcements:
Here are the release notes:
10 January 2025 (CTY-3502)
VER20250110, Version entity is Bulgaria, LZ
Added/changed Entities/Prefixes/Callsigns:
* EA7CA is Canary Islands, EA8
* TO8AN is St. Martin, FS
* GB2KW is Scotland, GM
* GB9KW is Wales, GW
* KC0RKB, KF5JC and WA6QDQ are all Hawaii, KH6
* AC1RU and KD9CVY are both Alaska, KL
* LU6DJ/D, LU6DM/D, LU8DCH/D, LU8EMD/D, LW5EVI/D and LW9EVV/D are all Argentina, LU
* LU1YY/V is Argentina, LU in ITU zone 16
* R8FF/P is in ITU zone 29, not ITU zone 30
* R8FF/P is in CQ zone 16, not CQ zone 17
* RA8CP/P is Asiatic Russia, UA9
* RC1BM/P is Asiatic Russia, UA9 in CQ zone 16
Removed Entities/Prefixes/Callsigns:
* EA3HSD/P in Spain, EA
* FO/NX1P in Marquesas Islands, FO/m
* W4ATD in United States, K
* K7DN, KN6EQR, KQ4UZD and N8XUL in Alaska, KL
* R8XF/P, R9JQ/6, RN3QOP/4 and UA9XL/P in European Russia, UA
* CF2I in Canada, VE
Though I am subscribed to this reflector so that I can make these
announcements, I do not see most messages posted to it. If you have
any comments or corrections to the country file, please contact me
directly.
73 - Jim AD1C
--
Jim Reisert AD1C, <jjreisert at alum.mit.edu>,
|
Re: fldigi abort witnessed - Pi 4.2.05.24
Same here on Fedora 39 and now 41. ?pavucontrol works fine
On Thu, 2025-01-09 at 14:15 -0600, Dave, W1HKJ via groups.io wrote:
toggle quoted message
Show quoted text
Thanks Brian.? Any reports from other distribution users?
David
On 1/9/25 13:07, Brian Morrison ,G8SEZ via groups.io wrote:
On Wed, 8 Jan 2025 18:15:05 -0600
"Dave, W1HKJ" <w1hkj@...> wrote:
Pipewire is supposed to emulate the API calls for pulseaudio.? I do
not think that pavucontrol is compatible with pipewire.
I've been using pipewire under Fedora for over 2 years now and
pavucontrol works perfectly with it here.
|
Re: fldigi abort witnessed - Pi 4.2.05.24
Thanks Brian.? Any reports
from other distribution users?
David
On 1/9/25 13:07, Brian Morrison ,G8SEZ
via groups.io wrote:
toggle quoted message
Show quoted text
On Wed, 8 Jan 2025 18:15:05 -0600
"Dave, W1HKJ" <w1hkj@...> wrote:
Pipewire is supposed to emulate the API calls for pulseaudio.? I do
not think that pavucontrol is compatible with pipewire.
I've been using pipewire under Fedora for over 2 years now and
pavucontrol works perfectly with it here.
|
Re: fldigi abort witnessed - Pi 4.2.05.24
On Wed, 8 Jan 2025 18:15:05 -0600 "Dave, W1HKJ" <w1hkj@...> wrote: Pipewire is supposed to emulate the API calls for pulseaudio.? I do
not think that pavucontrol is compatible with pipewire. I've been using pipewire under Fedora for over 2 years now and pavucontrol works perfectly with it here. -- Brian G8SEZ
|
Dave, W1HKJ