❌

Normal view

There are new articles available, click to refresh the page.
Before yesterdayMain stream

Share Soundcard between Direwolf and VARA on Linux

By: KN4MKB
30 May 2024 at 23:00

I wish I could make this one simple, but we are getting into complex territory. Please read the instructions and follow along carefully. This is not something I recommend doing without knowing your way around Linux, and so the basics are not covered(it would be too long). this should let you share the same soundcard between direwolf and other apps like VARA, and FLDigi as well. I ran into this when I wanted to have VARA and Dire wolf share a soundcard for my BPQ32 node on Linux. By default, Dire wolf takes complete control of the sound card interface, as well as VARA when ran within wine. There are several tweaks and changes needed to make this work, so buckle in. In this guide, I’ve used this post to install VARA within wine on Debian 12. I’ve used this post to install dire wolf.

Splitting the Interface

First, we need to grab your sound cards device name. Enter cat /proc/asound/cards to get a list of sound cards, pay attention to the β€œDevice” or β€œDevice_1” relating to your radios digital audio interface card. I my case, I needed both (one was used for 2m, the other for HF). Note the name somewhere, paying attention to the case as well.

Now, we need to open the β€œasound” configuration file (or make a new one if it doesn’t exist), and enter some information. First, check if one exists for your current user with : cat ~/.asound. If you get file does not exist, that’s fine. If you instead see file info, enter rm ~/.asound to get rid of it. The reason we did that was because the user configuration file overrides the global (which is the one we will now create/edit).

Enter sudo nano /etc/asound.conf to create/edit the existing global configuration. If your file is empty, awesome. If it contains content, remove everything.

What we will do now, is name our new split soundcard interface. In the following example, I’ve taken the soundcard listed as β€œDevice” from above, and now named it β€œdigirig” in this new interface, and split it into β€œdigirig-rx” for the receive(audio in), and β€œdigirig-tx” for the transmit (audio out)

We will now paste the following template:

Take care to replace the word β€œDevice” with the name you found above (probably the same), and if you would like to rename the interface to something other than β€œdigirig” like I have here, replace all instances of it with something lowercase and simple you will remember.

pcm_slave.digirig {
   pcm {
      type hw
      card Device
   }
   period_time 0
   buffer_size 8192
}

pcm.digirig-dmix {
   type dmix
   ipc_key 2023041901
   slave "digirig"
   bindings.0 0
}

pcm.digirig-dsnoop {
   type dsnoop
   ipc_key 2023041902
   slave "digirig"
   bindings.0 0
}

pcm.digirig-rx {
   type plug
   slave.pcm "digirig-dsnoop"
   hint.description "digirig RX audio plug"
}

pcm.digirig-tx {
   type plug
   slave.pcm "digirig-dmix"
   hint.description "digirig TX audio plug"
}

If you have 2 sound card interfaces, such as I do, you will just paste the above twice, one after the other. You will need to rename all instances of β€œdigirig” (or whatever you called the first one) to something else (to refer to the second card). You will also need to replace β€œDevice” once more with the name of the second sound card (probably β€œDevice_1”).

Great, save that file. Issue the following command to have the changes take effect.

sudo alsa force-reload

If you get command not found, you’re better off rebooting before continuing.

Now, we will now make sure we’ve done this part right. Open up your direrwolf configuration file (probably nano ~/direwolf.conf) and find the β€œADEVICE” line and remove it.

Replace it with the following. (Obviously replacing β€œdigirig” if you’ve renamed it in the asound file we made/edited above.

ADEVICE  digirighf-rx digirighf-tx

Save the file, and restart Dire wolf. Dire wolf should start fine, and your audio device should be working as it did before. If not, stop here, somethings wrong.

Getting VARA to use the Split interface

Now that dire wolf is using our split interface, we now need to get VARA on board, which is a little more involved.

First, we need to get your wine prefix to be configured using ALSA. If using VARA in the default prefix, this could be as simple as running β€œwinetricks sound=alsaβ€œ. Give it a try, as it won’t hurt either way. Otherwise, you will run the following command, replacing β€œ.wine32” with the wine prefix you’ve made for VARA.

 env WINEARCH="win32" env WINEPREFIX="/home/aspect/.win32" winecfg

Another way you can try to achieve this is by running β€œwinetricks” within desktop mode, selecting the prefix where VARA is installed, choosing β€œChange Settings”, finding β€œsound=alsa” and pressing β€œOk”

vara wineprefix config
setting vara to alsa in wine

Next we need to set some registry keys on the Wine prefix to identify our split interfaces. Similar to the above, we will enter the following command to open the registry editor for the VARA prefix:

env WINEARCH="win32" env WINEPREFIX="/home/aspect/.win32" regedit

You can also reach the Registry editor using the β€œwinetricks” command, selecting the prefix, and opening the regedit from there.

You will navigate to the following key and leave it it open:

HKCU->Software->Wine->Drivers->winealsa.drv

set input and output devices for alsa in a wine prefix

Just as in the above screenshot, you will right click the empty space, and select new -> multi-string value.

Create one key called β€œALSAInputDevices” and another called β€œALSAOutputDevices”. In each of them, for the value, make a list of the relative -rx or -tx devices we made before in the asound file. (If you only have 1 sound card interface to use, you only need the one here). (-rx being in the Input devices, and -tx being in the Output.)

set the digirig as an option for vara to use in wine

Save, and close it all out.

Starting VARA

Now start VARA as you normally do in WINE. In the soundcard settings, now chose the interface we specified in the registry relating to the one we created in the asound configuration file.

vara running on debian 12

Direwolf and VARA should now be able to share the sound interface this way!

The post Share Soundcard between Direwolf and VARA on Linux appeared first on TheModernHam.

April Showers at Marsh Creek State Park

By: WB3GCK
18 May 2024 at 20:16

Lately, most weekends have been rainy around here. The forecast for tomorrow is much better than the rain today. Unfortunately, family obligations gave me no choice than to activate today.

I headed over to Marsh Creek State Park (US-1380, KFF-1380) early this morning, to avoid heavier rain later in the day. Despite the lousy weather, there were a lot of cars in the parking lot.Β 

A rainy morning on Marsh Creek Reservoir
A rainy morning on Marsh Creek Reservoir

The rig today was my usual Penntek TR-35 (5 watts, CW) and my 12-foot loaded whip. As is my usual practice, I started on 40M. The band predictions forecasted poor daytime conditions on 40M, but that wasn’t my experience. Although some of the signal reports I received were lower than usual, I logged my first 10 contacts in about 13 minutes. My first contact was in Georgia, so that’s not too bad for 40M. The 30M band also seemed to be in decent shape.Β 

When I moved up to 20M, I found some annoying broadband noise across the band. I’ve never encountered that here before, so I was wondering if there was a hybrid vehicle or something in the parking lot. I skipped 20M and moved up to 17M. The band was nearly devoid of activity, and 15 minutes of CQing failed to produce a single contact. While I was CQing, though, I passed the time by watching a large heron wading by. I went back to 40M to finish up.

This Heron was walking through the shallows looking for breakfast
This Heron was walking through the shallows looking for breakfast

My final tally was 32 contacts, three of which were park-to-park. I didn’t have any DX contacts this morning, but there were some highlights:

  • I had park-to-park contacts with KD8IE on two bands.
  • I worked my friend Frank N3FLL. I talked to Frank on a local repeater on my way to the park and gave him a heads-up. He found me on 40M.
  • I worked Al N3KAE on 40M. Al is the Regional Coordinator who uploads my WWFF logs for me. It was great to add him to the log.
Ready for the rain, with my patented coil protector (aka grocery store plastic bag) and some pipe insulation to seal the window opening
Ready for the rain, with my patented coil protector (aka grocery store plastic bag) and some pipe insulation to seal the window opening

My setup withstood the rain pretty well this morning. I used a piece of pipe insulation on the passenger side window, where I fed the coax through. The fit could have been better, but it kept the rain out. Once again, I used a plastic bag to protect my homebrew coil. When I took the antenna down, I used a chamois cloth to dry the whip as I collapsed it. That worked pretty well.Β 

Pipe insulation sealing the window where the coax enters. The fit wasn't great, but it was good enough.
Pipe insulation sealing the window where the coax enters. The fit wasn’t great, but it was good enough.

Hopefully, we’ll have a rain-free weekend one of these days.

73, Craig WB3GCK

❌
❌