¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
Date

Re: QTsoundmodem ptt and goio

 

¿ªÔÆÌåÓý

Yes, it should. You can select GPIO in the PTT setup. I haven't tried it for a while so would be interested to hear if it still works.

73,
John
?


On 09/01/2025 18:40, dtmenges@... via groups.io wrote:

I've run QTsoundmodem on a Pi 4 and a Signalink without problems. Does it support GPIO? I've not gotten it to work with a hat that I use with Direwolf. Thought I would ask before I spin my wheels too long.
?
Dave Menges


Re: Help with CTEXT Format and ASCII Codes

 

Hi Tom.?It seems to me that you are ending the CTEXT with four asterisks (****) instead of three (***). I have already made ascii art in CTEXT and it worked fine.


Em qui., 9 de jan. de 2025, 12:29, DO1ATM via <DO1ATM=[email protected]> escreveu:

After a streesfull week with a steep learning courve my LinBBQ is running and I even got ZORK and WORDL up and running.
Now, I thought it was time to meake it pretty and wanted to Add soem collor to the Propmpt, with now luck.
Colorcodes are not Working.
I tried '\033[32m? ?... (my TEXT) ...? ? \033[0m'
LinBPQ Start without Problem, but no collores are displayd via telnet in Bitvise nor AX25 in Putty, bot, bitvise an putte should be capeable of showing colors.
I also tried some kind of AscII ART in CTEXT between CTEXT: and ****
eg:
CTEXT:
____ _ _ ____ ____ ____ _
| _ \| | | | __ )| __ ) ___| | |__ _ _
| |_) | |_| | _ \| _ \___ \ | '_ \| | | |
| _ <| _ | |_) | |_) |__) | | |_) | |_| |
|_|_\_\_|_|_|____/|____/____/ |_.__/ \__, |
| _ \ / _ \/ | / \|_ _| \/ | |___/
| | | | | | | | / _ \ | | | |\/| |
| |_| | |_| | |/ ___ \| | | | | |
|____/ \___/|_/_/ \_\_| |_| |_|
****
Loock nicer in Terminal..
With the ASCII Art the Linbpq wouldent even Start.
By trying so it prompted, 'Translation Error'?
?
Is there any Trick to get this things Working?
?
Kind Regards and 73.
DO1ATM
Tom
?
?
?


QTsoundmodem ptt and goio

 

I've run QTsoundmodem on a Pi 4 and a Signalink without problems. Does it support GPIO? I've not gotten it to work with a hat that I use with Direwolf. Thought I would ask before I spin my wheels too long.
?
Dave Menges


Help with CTEXT Format and ASCII Codes

 

After a streesfull week with a steep learning courve my LinBBQ is running and I even got ZORK and WORDL up and running.
Now, I thought it was time to meake it pretty and wanted to Add soem collor to the Propmpt, with now luck.
Colorcodes are not Working.
I tried '\033[32m? ?... (my TEXT) ...? ? \033[0m'
LinBPQ Start without Problem, but no collores are displayd via telnet in Bitvise nor AX25 in Putty, bot, bitvise an putte should be capeable of showing colors.
I also tried some kind of AscII ART in CTEXT between CTEXT: and ****
eg:
CTEXT:
____ _ _ ____ ____ ____ _
| _ \| | | | __ )| __ ) ___| | |__ _ _
| |_) | |_| | _ \| _ \___ \ | '_ \| | | |
| _ <| _ | |_) | |_) |__) | | |_) | |_| |
|_|_\_\_|_|_|____/|____/____/ |_.__/ \__, |
| _ \ / _ \/ | / \|_ _| \/ | |___/
| | | | | | | | / _ \ | | | |\/| |
| |_| | |_| | |/ ___ \| | | | | |
|____/ \___/|_/_/ \_\_| |_| |_|
****
Loock nicer in Terminal..
With the ASCII Art the Linbpq wouldent even Start.
By trying so it prompted, 'Translation Error'?
?
Is there any Trick to get this things Working?
?
Kind Regards and 73.
DO1ATM
Tom
?
?
?


Re: BPQMail and RMS Forwarding

 

I received a few private messages about dropping the WW in addition to this thread.? This has solved the issue and it's no longer going to SMTP: (which I saw on one other occasion after changing some user options), or RMS:
?
Thank you!
?
Jay NT0Y


Re: BPQMail and RMS Forwarding

 

¿ªÔÆÌåÓý

You don't need the WW on the end, but it shouldn't cause the message being sent to Winlink, so it sounds like a bug. I'll look into it, but as Eric says removing the WW should stop it.

73,
John G8BPQ

On 08/01/2025 16:39, Eric H. Christensen via groups.io wrote:

The addresses shouldn't have .WW on the end. BPQ is thinking these messages should be routed through Winlink and is adding the RMS: part.? Remove .WW from your addresses and from the h-route of the BBSs.

73,
Eric WG3K
FM18rp
Packet: WG3K@WG3K.#SMD.MD.USA.NOAM
E-Mail: wg3k@...

Sent from Proton Mail Android



-------- Original Message --------
On 1/8/25 10:21, jason via groups.io wrote:
Happy new year to everyone!
?
New BPQ32 user here, latest version.? Running RMS, Chat, and Mail.
?
A group of hams and myself are attempting to set up forwarding between our individual nodes.?
?
Ham #1
?
Ham #2
?
When either one of us composes a message intended for forwarding, it ends up at the intended BBS i.e. Ham #1's message lands on Ham #2's board when addressed as above, however the TO address ends up prepended with "RMS:" instead of just landing on the board itself.? Is this intended behavior?? If we didn't want it to do this "RMS:" behavior, how would we stop it?? It makes it so that if you aren't a sysop on the target BBS, the message doesn't show up with a simple "ll".
?
Apologies if this has been addressed previously.? A search didn't yield anything from what I could see.? Also searched the docs.
?
Thanks ahead of time!
?
73
Jay NT0Y


Re: BPQMail and RMS Forwarding

 

The addresses shouldn't have .WW on the end. BPQ is thinking these messages should be routed through Winlink and is adding the RMS: part.? Remove .WW from your addresses and from the h-route of the BBSs.

73,
Eric WG3K
FM18rp
Packet: WG3K@WG3K.#SMD.MD.USA.NOAM
E-Mail: wg3k@...

Sent from Proton Mail Android



-------- Original Message --------
On 1/8/25 10:21, jason via groups.io wrote:
Happy new year to everyone!
?
New BPQ32 user here, latest version.? Running RMS, Chat, and Mail.
?
A group of hams and myself are attempting to set up forwarding between our individual nodes.?
?
Ham #1
NT0Y@NT0Y.#LAN.MI.USA.NOAM.WW
?
Ham #2
KD8MJJ@KD8MJJ.#SEMI.MI.USA.NOAM.WW
?
When either one of us composes a message intended for forwarding, it ends up at the intended BBS i.e. Ham #1's message lands on Ham #2's board when addressed as above, however the TO address ends up prepended with "RMS:" instead of just landing on the board itself.? Is this intended behavior?? If we didn't want it to do this "RMS:" behavior, how would we stop it?? It makes it so that if you aren't a sysop on the target BBS, the message doesn't show up with a simple "ll".
?
Apologies if this has been addressed previously.? A search didn't yield anything from what I could see.? Also searched the docs.
?
Thanks ahead of time!
?
73
Jay NT0Y


BPQMail and RMS Forwarding

 

Happy new year to everyone!
?
New BPQ32 user here, latest version.? Running RMS, Chat, and Mail.
?
A group of hams and myself are attempting to set up forwarding between our individual nodes.?
?
Ham #1
NT0Y@NT0Y.#LAN.MI.USA.NOAM.WW
?
Ham #2
KD8MJJ@KD8MJJ.#SEMI.MI.USA.NOAM.WW
?
When either one of us composes a message intended for forwarding, it ends up at the intended BBS i.e. Ham #1's message lands on Ham #2's board when addressed as above, however the TO address ends up prepended with "RMS:" instead of just landing on the board itself.? Is this intended behavior?? If we didn't want it to do this "RMS:" behavior, how would we stop it?? It makes it so that if you aren't a sysop on the target BBS, the message doesn't show up with a simple "ll".
?
Apologies if this has been addressed previously.? A search didn't yield anything from what I could see.? Also searched the docs.
?
Thanks ahead of time!
?
73
Jay NT0Y


Re: Hashtag Gremlin Strikes Again!

 

¿ªÔÆÌåÓý

Good eyes, Charles.
Typo

ww2bsa@...

There we go....

73 de Chris

-------- Original message --------
From: Charles Hargrove <n2nov@...>
Date: 1/7/25 8:42 PM (GMT-05:00)
Subject: Re: [bpq32] Hashtag Gremlin Strikes Again!

There should be a period and not a comma between fields.

On 1/7/2025 8:39 PM, Chris Lance WW2BSA wrote:
> My address is: ww2bsa@...,usa.noam

--
Charles J. Hargrove - N2NOV
NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord.

NYC-ARECS/RACES Nets 441.100/136.5 PL
ARnewsline Broadcast Mon. @ 8:00PM
NYC-ARECS Weekly Net Mon. @ 8:30PM
http://www.nyc-arecs.org

NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM
on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32

"Information is the oxygen of the modern age. It seeps through the walls
topped
by barbed wire, it wafts across the electrified borders." - Ronald Reagan

"The more corrupt the state, the more it legislates." - Tacitus

"Molann an obair an fear" - Irish Saying
(The work praises the man.)

"No matter how big and powerful government gets, and the many services it
provides, it can never take the place of volunteers." - Ronald Reagan







Re: Hashtag Gremlin Strikes Again!

 

There should be a period and not a comma between fields.

On 1/7/2025 8:39 PM, Chris Lance WW2BSA wrote:
My address is: ww2bsa@...,usa.noam
--
Charles J. Hargrove - N2NOV
NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord.

NYC-ARECS/RACES Nets 441.100/136.5 PL
ARnewsline Broadcast Mon. @ 8:00PM
NYC-ARECS Weekly Net Mon. @ 8:30PM


NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM
on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32

"Information is the oxygen of the modern age. It seeps through the walls topped
by barbed wire, it wafts across the electrified borders." - Ronald Reagan

"The more corrupt the state, the more it legislates." - Tacitus

"Molann an obair an fear" - Irish Saying
(The work praises the man.)

"No matter how big and powerful government gets, and the many services it
provides, it can never take the place of volunteers." - Ronald Reagan


Hashtag Gremlin Strikes Again!

 

Although I posted to SYSOPS in the US, I thought I'd mention it here n Groups.io
?
It seems someone has altered my white page address. It is NOT ww2bsa@ww2bsa.#nj.usa.noam
?
My address is: ww2bsa@...,usa.noam
?
Thank you for your attention to this.
73 de Chris ww2bsa


Re: Limit on NNTP message size Re Claws?

 

Not sure if this helps but for more info:

n9seo@debian:~$ ls -lah bpq/Mail/m_030725.mes 
-rw-r--r-- 1 n9seo n9seo 73K Jan  6 17:07 bpq/Mail/m_030725.mes


Limit on NNTP message size Re Claws?

 

Hi is there some limitation on the max size of a NNTP pull from BPQ with claws?

A recent bull sent to BBS@WW with bbs list is ~ 70K. When I try to view it in claws, I get the following on BPQ-6.0.24.54 w/ claws 4.3.0 (64 bit Arch Linux AUR package).

  This message can't be displayed.
  This is probably due to a network error.

  Use 'Network Log' in the Tools menu for more information.
2025-01-07 10:42:36] NNTP> GROUP BBS.WW 
[2025-01-07 10:42:36] NNTP< 211 2 30725 30728 BBS.WW 
[2025-01-07 10:42:38] NNTP> ARTICLE 30728 
[2025-01-07 10:42:38] NNTP< [data - 8192 bytes]
[2025-01-07 10:42:38] NNTP< [data - 6288 bytes]
[2025-01-07 10:42:38] NNTP< [data - 8192 bytes]
[2025-01-07 10:42:38] NNTP< [data - 8192 bytes]
[2025-01-07 10:42:38] NNTP< [data - 8192 bytes]
[2025-01-07 10:42:38] NNTP< [data - 4384 bytes]
[2025-01-07 10:42:38] NNTP< [data - 7240 bytes]
[2025-01-07 10:42:38] NNTP< [data - 1448 bytes]
[2025-01-07 10:43:38] NNTP> DATE 
[2025-01-07 10:43:39] NNTP< [data - 8192 bytes]
** NNTP connection to 192.168.X.X:119 has been disconnected.

So it appears to time out. I tried to crank up the socket timeout in Claws to 120 or 180 but it stalls out at the same byte count and throws the same error messaging.


Re: New bpq32 install connection refused

 

Correction ion previous post:
?
For the line:
sudo setcap "CAP_NET_ADMIN=ep CAP_NET_RAW=ep CAP_NET_BIND_SERVICE=ep" pi
"pi" here should instead be the name of the executable. (probably pilinbpq or linbpq)


Re: New bpq32 install connection refused

 

A few things:
?
You stated you are using Direwolf, but your config is setup for a serial "PITNC".
For direwolf, you should be using the Network KISS options to connect your BPQ node to DireWolf.
?
Your port one for DireWolf for 2M should look more like this if DireWolf is running on the same system:
Replace the PORTNUM as needed, IP if running on another device, Port if KISS Listen on direwolf, and beacon call
PORT
   PORTNUM=1
   ID=144.930 MHz 1200 bps
   TYPE=ASYNC
   SPEED=19200
   PROTOCOL=KISS
   IPADDR=127.0.0.1
   TCPPORT=8001
   RESPTIME=1500
   MHEARD=Y
   BCALL=KN4MKB-7
   MINQUAL=100
   KISSOPTIONS=NOPARAMS
   CHANNEL=A
   FULLDUP=0
   NOKEEPALIVES=1
ENDPORT
?
Your DireWolf Config for 2M should look something like this after your Audio/PTT config:
MODEM 1200
RETRY 5
FRACK 3
MAXFRAME 7
EMAXFRAME 30
PACLEN 128
DWAIT 0
TXDELAY 25
TXTAIL 15
MAXV22 3
?
With that out of the way, you probably need to enter the following command to allow non root users to use all ports (replace 'pi' with your pi username is different):
sudo setcap "CAP_NET_ADMIN=ep CAP_NET_RAW=ep CAP_NET_BIND_SERVICE=ep" pi
?
And gove the executable the right permissions:
sudo chmod +x linbpq
?
I'm not familiar with the Ham stack you are running.
It may have a firewall installed you aren't aware of.
?
Try the following commands to open the ports as the root user:
sudo su
iptables -A INPUT -p tcp --dport PORTNUMBER -j ACCEPT
ufw allow PORTNUMBER
?
If the pi is in the same network as the connecting device, your router and it's forwarded ports have nothing to do with it.
NAT/ Port Forwarding is a routing/firewall function to direct traffic from one network to the port of a device on another.
If your devices are on the same network (255.255.255.0/24), then the NAT is bypassed anyways as it doesn't need to happen.
?
Not to knock the people who build them, but a lot of those autoinstall config builders and install scripts put a lot of "stuff" into the config files they generate.
Things change over time, and everyone setup is different, and it just usually doesn't go well with BPQ for the config portion. If you are ever to change anything in the future, you will need to understand the config anyways.
?
"I tried browser connection to http://127.0.0.1:8010 and Telnet to 127.0.0.1 8010.? Both of these result in 'connection refused' messages."
So if you you doing this from the Pi itself it may be fine.
But if you are connecting from elsewhere, like in your previous post, you need to use the LAN address of your Pi instead of 127.0.0.1.
You can use "ip a" in a terminal to see it.
?
I recommend you just remove the LinBPQ installation, purge any systemd entries, and start from scratch.?
?
I've written a detailed guide to build your own configuration you can find here:
?
Follow along the above link, and also open:
?
That way you can build your config file, follow along and check Johns Documentation to make sure you don't need to tweak something, or add something.
Being a SysOP, I think it pays to build your own. That way you really understand what each of the lines mean and what they do.
?


Re: ARDOPCF and QtSoundModem?

 

Hi Niels,

Thanks for the feedback. I have spent the better part of the last two days reviewing group threads and anything else I could find that might help. I pretty much get the same results you show below with versions?1.0.4.1.1, 1.0.4.1.2, and 1.0.4.1.3 no matter how I tweak values within dsnoop and dmix.

I even tried compiling with different hard coded values as suggested in one of the threads by Peter LaRue and while I have little experience coding for soundcard audio I think the following results from a test with hard coded values suggests that the inability to utilize dsnoop / dmix within .asoundrc is at least in part still an issue with ardopcf and not entirely an alsa problem as some suggest.

WARNING: Inconsistent ALSA playback configuration: 1000000 * 12000 != 12000 * 1000000.
WARNING: The -A option was specified.? So, ALSA misconfiguration will be ignored.? This option is ONLY intended for testing/debuging.? It IS NOT INTENDED FOR NORMAL USE.

Very curious that ardopcf determines 1000000 * 12000 != 12000 * 1000000 ???

Between that error / bug and what seems like little interest in pursuing the issue based on Peter's comments at the bottom of the discussion at I am inclined to pass on ardopcf at least until it is a little further along in development. Running ARDOP_Win.exe via wine on linux works far better on the x86 and x64 systems here than does ardopcf and it plays nice with dsnoop and dmix as long as the wine registry is updated properly.

73 de Rich WA3WLH


Re: ARDOPCF and QtSoundModem?

 

¿ªÔÆÌåÓý

Hi Rich, same problem here...

What I have...

.asoundrc

pcm.snd_card {
??????? type hw
??????? card 0
??????? device 0
}

ctl.snd_card {
??????? type hw
??????? card 0
??????? device 0
}

pcm.dmixer {
??? type dmix
??? ipc_key 1024
??? ipc_perm 0666?????? # Other users can also use dmix at the same time
??? slave.pcm "snd_card"
??? slave {
??????? period_time 0
??????? period_size 1024
??????? buffer_size 4096
??????? channels 2
??? }
??? bindings {
??????? 0 0
??????? 1 1
??? }
}

# The dsnoop plugin, which allows you to record multiple programs at the same time.
pcm.dsnooper {
??? type dsnoop
??? ipc_key 2048
??? ipc_perm 0666
??? slave.pcm "snd_card"
??? slave
??? {
??????? period_time 0
??????? period_size 1024
??????? buffer_size 4096
??????? channels 2
??? }
??? bindings {
??????? 0 0
??????? 1 1
??? }
}

pcm.ardopin {type rate slave {pcm "plug:dsnooper" rate 48000}}
pcm.ardopout {type rate slave {pcm "plug:dmixer" rate 48000}}

pcm.asymwine {
??????? type asym
??????? playback.pcm "ardopout"
??????? capture.pcm "ardopin"
}

# make a default plug for it
pcm.!default {
??????? type plug
??????? slave.pcm "asymwine"
}

# define a plug for /dev/dsp
pcm.dsp {
??????? type plug
??????? slave.pcm "asymwine"
}

I can run QtSoundModem just fine with plug:dsnooper and plug:dmixer or plug:ardopin and plug:ardopout.

Opening Playback Device plug:ardopout Rate 12000
Real Device plug:ardopout
Play using 2 channels
Playback Buffer Size 1024
Opening Capture Device plug:ardopin Rate 12000
Real Device plug:ardopin
Record channel count set to 2
Capture using 2 channels
InitSound :ardopin :ardopout
Input peaks = -3905, 5005
Input peaks = -5162, 7286
Input peaks = -5755, 5354
Input peaks = -4943, 6005
Input peaks = -4785, 7166

Opening Playback Device plug:dmixer Rate 12000
Real Device plug:dmixer
Play using 2 channels
Playback Buffer Size 1024
Opening Capture Device plug:dsnooper Rate 12000
Real Device plug:dsnooper
Record channel count set to 2
Capture using 2 channels
InitSound plug:dsnooper plug:dmixer
Input peaks = -4187, 5763
Input peaks = -4433, 5210
Input peaks = -5048, 5448
Input peaks = -32768, 32767
Input peaks = -4869, 6892


But ardopcf can`t set the sample rate.... (fist shutdown QtSoundModem)

d9q@linux:~/ardop$ ./ardopcf-412 8515 plug:ardopin plug:ardopout -A -G 8514
ardopcf Version 1.0.4.1.2 ()
Copyright (c) 2014-2024 Rick Muething, John Wiseman, Peter LaRue
See for licence details including
? information about authors of external libraries used and their licenses.
ARDOPC listening on port 8515
Capture Devices

Card 0, ID `PCH', name `HDA Intel PCH'
? Device hw:0,0 ID `ALC3234 Analog', name `ALC3234 Analog', 1 subdevices (1 available)
??? 2 channels,? sampling rate 44100..192000 Hz
? Device hw:0,2 ID `ALC3234 Alt Analog', name `ALC3234 Alt Analog', 1 subdevices (1 available)
??? 2 channels,? sampling rate 44100..192000 Hz

Playback Devices

Card 0, ID `PCH', name `HDA Intel PCH'
? Device hw:0,0 ID `ALC3234 Analog', name `ALC3234 Analog', 1 subdevices (1 available)
??? 2 channels,? sampling rate 44100..48000 Hz
? Device hw:0,3 ID `HDMI 0', name `HDMI 0', 1 subdevices (1 available)
??? 2..8 channels, sampling rate 32000..192000 Hz
? Device hw:0,7 ID `HDMI 1', name `HDMI 1', 1 subdevices (1 available)
??? 2..8 channels, sampling rate 32000..192000 Hz
? Device hw:0,8 ID `HDMI 2', name `HDMI 2', 1 subdevices (1 available)
??? 2..8 channels, sampling rate 32000..192000 Hz

Using Both Channels of soundcard for RX
Using Both Channels of soundcard for TX
Opening Playback Device plug:ardopout Rate 12000
WARNING: Inconsistent ALSA playback configuration: 21333 * 12000 != 256 * 1000000.
This will result in a playblack sample rate of 12000.187503 instead of 12000.
This is an error of about -15.625244ppm.? Per the Ardop spec +/-100ppm should work well and +/-1000 ppm should work with some performance degredation.


WARNING: The -A option was specified.? So, ALSA misconfiguration will be accepted and ignored.? This option is primarily intended for testing/debuging.? However, it may also be useful if ardopcf will not run without it.? In this case, please report this problem to the ardop users group at ardop.groups.io or by creating an issue at .


Opening Capture Device plug:ardopin Rate 12000
cannot set capture sample rate (Invalid argument)
Error in InitSound().? Stopping ardop.

I'm running an older version of Ardopc that does work.

73 Niels PD9Q



Op 2-1-2025 om 23:18 schreef Rich Sahlender via groups.io:

Hi John et al,

Although I've had no issues for several years using your ardopc both x86 and x64 I finally got around to testing with ardopcf for no good reason other than to busy myself for a few hours given the claim of many bug fixes... which led me to this thread from back in July.

I am so far only able to make ardopcf work by dedicating the ALSA audio device. Everything else I try including completely replacing the .asoundrc here with dmix, dsnoop, and plug entries as in your example all fail complaining about something called the playback "period size". I even tried specifying multiple combinations of periods, period_time, buffer_time, period_size, and buffer_size in the .asoundrc to no avail.

So before getting into any details I should mention I have no inclination to change what works and your ardopc / ardopc64 work fine here with no problem sharing the audio device via dsnoop and dmix. I am posting this mostly to ask if you or others in the group have been able to make ardopcf share the audio device on x86 / x64 systems (I think the initial thread was for rPi's which I do not use here) and more importantly if the claim of many bugs being fixed in ardopcf make it worthwhile to switch from ardopc(64) assuming it can be made to share audio. Otherwise not experiencing any "bugs" in ardopc(64) here I may as well just leave things alone.

There are FWIW some limited details below.

73 de Rich WA3WLH

Here is an example of how I use your ardopc64 and share the audio without issue using my .asoundrc:

./ardopc64 8515 IC7700_asym IC7700_asym
ardopc Version 1.0.4.1mBPQ-Debug5
-SNIP-
Using Both Channels of soundcard for RX
Using Both Channels of soundcard for TX
Opening Playback Device IC7700_asym Rate 12000
Opening Capture Device IC7700_asym Rate 12000
ardopc listening on port 8515

Yet using ardopcf with the same .asoundrc fails:

./ardopcf_amd64_Linux_64 8515 IC7700_asym IC7700_asym
ardopcf Version 1.0.4.1.3 ()
- SNIP-
Using Both Channels of soundcard for RX
Using Both Channels of soundcard for TX
Opening Playback Device IC7700_asym Rate 12000
cannot set playback period size (Invalid argument)
Error in InitSound().? Stopping ardop.

And finally here is an example of trying ardopcf using a .asoundrc the includes only what is in your example and edited to change from hw card 2 to 1:

./ardopcf_amd64_Linux_64 8515 snoop02 mix02
ardopcf Version 1.0.4.1.3 ()
-SNIP-
Using Both Channels of soundcard for RX
Using Both Channels of soundcard for TX
Opening Playback Device mix02 Rate 12000
cannot set playback period size (Invalid argument)
Error in InitSound().? Stopping ardop.








Re: ARDOPCF and QtSoundModem?

 

You need to add the -A parameter to the ardopcf command line. Even with this I can't get the latest version to work and am currently using ardop-1.0.4.1.2. The error message is different (if I remember correctly is to to with sample rate).

Even with the older version another ham couldn't get it to work, and had use my binary.? I run on a 64 bit Pi.

I've had a look at the source changes between ardop-1.0.4.1.2 and the latest but haven't so far found what has changed. When I have a bit more time I'll investigate further.

73,
John

On 02/01/2025 22:18, Rich Sahlender via groups.io wrote:
Hi John et al,

Although I've had no issues for several years using your ardopc both x86 and x64 I finally got around to testing with ardopcf for no good reason other than to busy myself for a few hours given the claim of many bug fixes... which led me to this thread from back in July.

I am so far only able to make ardopcf work by dedicating the ALSA audio device. Everything else I try including completely replacing the .asoundrc here with dmix, dsnoop, and plug entries as in your example all fail complaining about something called the playback "period size". I even tried specifying multiple combinations of periods, period_time, buffer_time, period_size, and buffer_size in the .asoundrc to no avail.

So before getting into any details I should mention I have no inclination to change what works and your ardopc / ardopc64 work fine here with no problem sharing the audio device via dsnoop and dmix. I am posting this mostly to ask if you or others in the group have been able to make ardopcf share the audio device on x86 / x64 systems (I think the initial thread was for rPi's which I do not use here) and more importantly if the claim of many bugs being fixed in ardopcf make it worthwhile to switch from ardopc(64) assuming it can be made to share audio. Otherwise not experiencing any "bugs" in ardopc(64) here I may as well just leave things alone.

There are FWIW some limited details below.

73 de Rich WA3WLH

Here is an example of how I use your ardopc64 and share the audio without issue using my .asoundrc:

./ardopc64 8515 IC7700_asym IC7700_asym
ardopc Version 1.0.4.1mBPQ-Debug5
-SNIP-
Using Both Channels of soundcard for RX
Using Both Channels of soundcard for TX
Opening Playback Device IC7700_asym Rate 12000
Opening Capture Device IC7700_asym Rate 12000
ardopc listening on port 8515

Yet using ardopcf with the same .asoundrc fails:

./ardopcf_amd64_Linux_64 8515 IC7700_asym IC7700_asym
ardopcf Version 1.0.4.1.3 ()
- SNIP-
Using Both Channels of soundcard for RX
Using Both Channels of soundcard for TX
Opening Playback Device IC7700_asym Rate 12000
cannot set playback period size (Invalid argument)
Error in InitSound().? Stopping ardop.

And finally here is an example of trying ardopcf using a .asoundrc the includes only what is in your example and edited to change from hw card 2 to 1:

./ardopcf_amd64_Linux_64 8515 snoop02 mix02
ardopcf Version 1.0.4.1.3 ()
-SNIP-
Using Both Channels of soundcard for RX
Using Both Channels of soundcard for TX
Opening Playback Device mix02 Rate 12000
cannot set playback period size (Invalid argument)
Error in InitSound().? Stopping ardop.





Re: ARDOPCF and QtSoundModem?

 

Hi John et al,

Although I've had no issues for several years using your ardopc both x86 and x64 I finally got around to testing with ardopcf for no good reason other than to busy myself for a few hours given the claim of many bug fixes... which led me to this thread from back in July.

I am so far only able to make ardopcf work by dedicating the ALSA audio device. Everything else I try including completely replacing the .asoundrc here with dmix, dsnoop, and plug entries as in your example all fail complaining about something called the playback "period size". I even tried specifying multiple combinations of periods, period_time, buffer_time, period_size, and buffer_size in the .asoundrc to no avail.

So before getting into any details I should mention I have no inclination to change what works and your ardopc / ardopc64 work fine here with no problem sharing the audio device via dsnoop and dmix. I am posting this mostly to ask if you or others in the group have been able to make ardopcf share the audio device on x86 / x64 systems (I think the initial thread was for rPi's which I do not use here) and more importantly if the claim of many bugs being fixed in ardopcf make it worthwhile to switch from ardopc(64) assuming it can be made to share audio. Otherwise not experiencing any "bugs" in ardopc(64) here I may as well just leave things alone.

There are FWIW some limited details below.

73 de Rich WA3WLH

Here is an example of how I use your ardopc64 and share the audio without issue using my .asoundrc:

./ardopc64 8515 IC7700_asym IC7700_asym
ardopc Version 1.0.4.1mBPQ-Debug5
-SNIP-
Using Both Channels of soundcard for RX
Using Both Channels of soundcard for TX
Opening Playback Device IC7700_asym Rate 12000
Opening Capture Device IC7700_asym Rate 12000
ardopc listening on port 8515

Yet using ardopcf with the same .asoundrc fails:

./ardopcf_amd64_Linux_64 8515 IC7700_asym IC7700_asym
ardopcf Version 1.0.4.1.3 ()
- SNIP-
Using Both Channels of soundcard for RX
Using Both Channels of soundcard for TX
Opening Playback Device IC7700_asym Rate 12000
cannot set playback period size (Invalid argument)
Error in InitSound().? Stopping ardop.

And finally here is an example of trying ardopcf using a .asoundrc the includes only what is in your example and edited to change from hw card 2 to 1:

./ardopcf_amd64_Linux_64 8515 snoop02 mix02
ardopcf Version 1.0.4.1.3 ()
-SNIP-
Using Both Channels of soundcard for RX
Using Both Channels of soundcard for TX
Opening Playback Device mix02 Rate 12000
cannot set playback period size (Invalid argument)
Error in InitSound().? Stopping ardop.


Re: Happy New Year!

 

Best wishes all BPQ nodes and users and leaders!?
It¡¯s been great for me a past AEA packet radio ampr operator. I look forward to the new beginning you Chris and all the East Coast sysops and our lone Woolf k5 in Wisconsin.? The future looks promising. Congratulations and?
? ? ?¡°No regrets ¡°!

N9pno Iowa
George Kirn had contact with this data.


On Tue, Dec 31, 2024 at 7:21?PM Chris Lance WW2BSA via <Ww2bsa=[email protected]> wrote:

Happy New Year to all!
73 de Chris
ww2bsa