f5vmr
commented
9 months ago You have copies and pasted a link that has delivered an excessive amount of information from my pages from that link, masking your query. Where you have installed Darkice, remove it, and source darkice from GitHub, it's more up to date. As far as assistance is concerned, I will be available after the holidays, look me up on qrz.com. I have a working system with darkice. Chris g4nab
On Mon, 25 Dec 2023, 16:01 robnoordt, @.***> wrote:
Ok, installed SVXlink on a raspberry pi, configure it as a simplex system and it works wel. at least, as far as I am now. But, I am still running into a few issues that I would like to resolve. But since my knowledge is limited, I will ask for the help of the specialists here. There are still two things that I can't get working properly. The first has to do with the identifiers that can be set as short and long in the configuration file.(/etc/svxlink/svxlink.conf) Then there is an identification in phone followed by this in CW. This is then broadcast on 2 meters. But now, when a QSO takes place on 2 meters, these identifications are always transmitted over the 2 meter QSO. And that is actually not desirable. I started looking for a setting that checks whether an incoming signal from the transeiver is active and if this is the case, it skips the identifications. But unfortunately I couldn't find it yet. I notice that a lot of explanations about SVXlink on the internet relate to repeaters and it works differently there than with simplex nodes. I hope you have the golden solution. It could be possible that the solution can be found in a .tcl file, but I don't dare to venture into that yet. The second problem that I have not yet been able to solve has to do with the stream via darkice and icecast. On the stream I only hear what comes from Echolink online. So the audio, the QSO of someone who has connected Echolink via smartphone or PC. And the identifications are also audibly broadcast via the stream. But, the signals that come from 2 meters, i.e. my transceiver, are not audible on the stream. I have checked my configuration several times with how G4NAB(Skip to content Mon. Dec 25th, 2023 16:57:06 Amateur Radio Station G4NAB
Amateur Radio
SVXLINK SVXLink and Darkice on Raspberry OS Bullseye lite and Svxlink 19.09.2 Avatar Byg4nab_ne63 DEC 2, 2023
Adding an audible output for Radio Listeners is the goal here, to provide added interest.
You should have at least installed SVXLink in the fashion described in the linked page here. Read and follow the directions explicitly. Do not use Bookworm yet as some of the repositories are not yet compatible.
DO NOT UNDER ANY CIRCUMSTANCES USE sudo apt install svxlink-server THE VERSION IS OUTDATED and will not contain SVXReflector.
You should have a USB Sound Card preferably the CM108 already described in these pages.
Time Allotment: Allow at least 60 Minutes at the very least.
Implementation for the DarkIce and Icecast2
Hopefully you shall have first tested and run your svxlink node.
If you want to stream the output for public consumption then this is what we shall do.
Installation of the Dummy Soundcard
In the terminal screen type the following command at the prompt.
sudo nano /etc/modules
Type the single line as follow
snd-aloop
Now type cntrl-o to save the new file and cntrl-x to exit the editor.
You can now load the module in your running system by typing sudo modprobe snd-aloop followed by enter.
Dummy Sound Card Configuration
At the other end of the Loopback, we will connect darkice as a streaming device. Type the following sudo nano /etc/asound.conf
Then type the following lines exactly as they are written.
pcm_slave.hw_Loopback_1_2 { pcm “hw:Loopback,1,2” format S16_LE channels 2 rate 48000 }
pcm.plug_Loopback_1_2 { type plug slave hw_Loopback_1_2 ttable { 0.0 = 1 0.1 = 1 } }
Ensure you have the correct syntax, and the correct number of curly braces. Save the file by typing cntrl-o and cntrl-x as before.
Create a new file by sudo nano /etc/modprobe.d/asound.conf
Type this one line.
options snd-aloop index=1 pcm_substreams=8
Save and close the file as before. Reboot the raspberry at this stage.
To verify the installation type sudo aplay -l
you should see the following:
List of PLAYBACK Hardware Devices card 0: Device [USB PnP Sound Device], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Loopback [Loopback], device 0: Loopback PCM [Loopback PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1 https://github.com/sm0svx/svxlink/issues/1: subdevice #1 https://github.com/sm0svx/svxlink/issues/1 Subdevice #2 https://github.com/sm0svx/svxlink/issues/2: subdevice #2 https://github.com/sm0svx/svxlink/issues/2 Subdevice #3 https://github.com/sm0svx/svxlink/issues/3: subdevice #3 https://github.com/sm0svx/svxlink/issues/3 Subdevice #4 https://github.com/sm0svx/svxlink/issues/4: subdevice #4 https://github.com/sm0svx/svxlink/issues/4 Subdevice #5 https://github.com/sm0svx/svxlink/issues/5: subdevice #5 https://github.com/sm0svx/svxlink/issues/5 Subdevice #6 https://github.com/sm0svx/svxlink/issues/6: subdevice #6 https://github.com/sm0svx/svxlink/issues/6 Subdevice #7 https://github.com/sm0svx/svxlink/issues/7: subdevice #7 https://github.com/sm0svx/svxlink/issues/7 card 1: Loopback [Loopback], device 1: Loopback PCM [Loopback PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1 https://github.com/sm0svx/svxlink/issues/1: subdevice #1 https://github.com/sm0svx/svxlink/issues/1 Subdevice #2 https://github.com/sm0svx/svxlink/issues/2: subdevice #2 https://github.com/sm0svx/svxlink/issues/2 Subdevice #3 https://github.com/sm0svx/svxlink/issues/3: subdevice #3 https://github.com/sm0svx/svxlink/issues/3 Subdevice #4 https://github.com/sm0svx/svxlink/issues/4: subdevice #4 https://github.com/sm0svx/svxlink/issues/4 Subdevice #5 https://github.com/sm0svx/svxlink/issues/5: subdevice #5 https://github.com/sm0svx/svxlink/issues/5 Subdevice #6 https://github.com/sm0svx/svxlink/issues/6: subdevice #6 https://github.com/sm0svx/svxlink/issues/6 Subdevice #7 https://github.com/sm0svx/svxlink/issues/7: subdevice #7 https://github.com/sm0svx/svxlink/issues/7
If you do not see this but some errors, then go back up to Dummy Sound Configuration, and remove the configuration, save the file, reboot and repeat the configuration once more.
Now, when you open the device ‘plug_Loopback_1_2’ in an application, the above will force the ‘Loopback,1,2’ to be configured with parameters that SvxLink likes, and the explicit wiring of only the left channel. The darkice config will then be like this:
[general]
duration = 0 # duration of encoding, in seconds. 0 means forever bufferSecs = 1 # size of internal slip buffer, in seconds reconnect = yes # reconnect to the server(s) if disconnected realtime = no # run the encoder with POSIX realtime priority rtprio = 3 # scheduling priority for the realtime threads this section describes the audio input that will be streamed
[input] device = plug_Loopback_1_2 # ALSA soundcard device for the audio input sampleRate = 22050 # sample rate in Hz. try 11025, 22050 or 44100 bitsPerSample = 16 # bits per sample. try 16 channel = 1 # channels. 1 = mono, 2 = stereo
Installing the apps Darkice and Icecast2
sudo apt install darkice icecast2
As you install icecast2, you will be presented with request for passwords and other parameters. Make notes as you proceed. You will need to configure darkice after reboot.
Directions are includes with both packages.
Darkice requires you to do the following before you can operate on it. sudo gunzip /usr/share/doc/darkice/examples/darkice.cfg.gz then sudo cp /usr/share/doc/darkice/examples/darkice.cfg /etc then sudo nano /etc/darkice.cfg to final configure the dummy sound card you have previously made above.
[general] duration = 0 bufferSecs = 5 reconnect = yes
[input] device = plughw:1,0 # You may need to change the numbers here for your setup sampleRate = 48000 bitsPerSample = 16 channel = 2
[icecast2-0] bitrateMode = cbr bitrate = 320 # Max bitrate for MP3 is 320 and best for binaural audio format = mp3 quality = 1.0 # Sets the quality of the stream 1.0 being highest server = your ip address # This is a free server or you can pay for one port = 8000 # Your port number from your icecast2 settings mountPoint = url:8000/stream # Omit the ‘/’ before ‘stream’ in Darkice “stream.mp3” for example password = source password here # Source password from icecast or private paid for server password name = your stream name # Name of account description = Live binaural stream for headphones # Stream description genre = Binaural 3D for headphones public = yes
Save the file.
sudo nano /etc/default/darkice and change “no” to “yes” and save and exit.
sudo nano /etc/default/icecast2 and add a new line ENABLE=true, save and exit.
Once you have configured IceCast – (sudo nano /etc/icecast2/icecast.xml), we can now…
sudo mkdir /etc/scripts
cd /etc/scripts
sudo nano darkice.sh, and type the following text exactly into it.
!bin/sh
sudo /usr/bin/darkice -c /etc/darkice.cfg
save and close the file.
sudo chmod +x darkice.sh
now
sudo nano /etc/rc.local
and insert the following line before the final line exit 0.
sleep 20
sudo sh /etc/scripts/darkice.sh
save the file.
Now we enable Icecast2 as follows.
sudo systemctl enable icecast2 && sudo systemctl start icecast2
Now we must reconfigure svxlink.conf to channel out to the Dummy Sound Card.
sudo nano /etc/svxlink/svxlink.conf
First of all we need to configure a transmitter channel.
[TxStream]
TYPE=Local AUDIO_DEV=alsa:hw:Loopback,0,2 AUDIO_CHANNEL=0 PTT_TYPE=NONE TIMEOUT=7200 TX_DELAY=0 PREEMPHASIS=0
Now to add it to a MultiTx
[MultiTx]
TYPE=Multi TRANSMITTERS=Tx1,TxStream
Now we change the Transmitter itself to reflect these changes.
[SimplexLogic]
Change TX=Tx1 to TX=MultiTx
And save the file.
Now finally we can reboot.
The stream will start after a short delay on boot up. In a browser type the ip address of the raspberry e.g. 192.168.1.195:8000
and click on the link presented.
http://svxportal-uk.ddns.net:8000
Post navigation Svxlink with DVSwitch Avatar By g4nab_ne63 RELATED POST DMRGENERAL RADIOSVXLINK Svxlink with DVSwitch NOV 9, 2023 G4NAB_NE63 SVXLINK Voice Sample Creation for SVXLink SEP 14, 2023 G4NAB_NE63 SVXLINK SVXLink Dashboard – in the making SEP 10, 2023 G4NAB_NE63 Leave a Reply Your email address will not be published. Required fields are marked *
Comment
Name *
Email *
Website
Save my name, email, and website in this browser for the next time I comment.
Search RECENT POSTS SVXLink and Darkice on Raspberry OS Bullseye lite and Svxlink 19.09.2 Svxlink with DVSwitch DMR and the Associated Repeater GB7HT in Northumberland. What is Amateur Radio? Some information for the Radio Listener RECENT COMMENTS ARCHIVES December 2023 November 2023 October 2023 September 2023 August 2023 CATEGORIES DMR Flight Simulator General Radio SVXLink Uncategorized META Log in Entries feed Comments feed WordPress.org YOU MISSED SVXLINK SVXLink and Darkice on Raspberry OS Bullseye lite and Svxlink 19.09.2 DECEMBER 2, 2023 G4NAB_NE63 DMRGENERAL RADIOSVXLINK Svxlink with DVSwitch NOVEMBER 9, 2023 G4NAB_NE63 DMRGENERAL RADIO DMR and the Associated Repeater GB7HT in Northumberland. OCTOBER 14, 2023 G4NAB_NE63 GENERAL RADIO What is Amateur Radio? OCTOBER 2, 2023 G4NAB_NE63 Amateur Radio Station G4NAB
Amateur Radio
Proudly powered by WordPress | Theme: Newsup by Themeansar.
Home G4NAB Microsoft Flight Simulator 2020) described this on his site but found no differences. Maybe I'm making a mistake somewhere or overlooking something. I hope you have suggestions that will also provide a solution to this. looking forward.
73's, PE1MEH
— Reply to this email directly, view it on GitHub https://github.com/sm0svx/svxlink/issues/654, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACAKA5CRPIQFNQIPFSULBZDYLGPNDAVCNFSM6AAAAABBCOSJYWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA2TKNZWGEYDSMY . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Ok, installed SVXlink on a raspberry pi, configure it as a simplex system and it works wel. at least, as far as I am now. But, I am still running into a few issues that I would like to resolve. But since my knowledge is limited, I will ask for the help of the specialists here. There are still two things that I can't get working properly. The first has to do with the identifiers that can be set as short and long in the configuration file.(/etc/svxlink/svxlink.conf) Then there is an identification in phone followed by this in CW. This is then broadcast on 2 meters. But now, when a QSO takes place on 2 meters, these identifications are always transmitted over the 2 meter QSO. And that is actually not desirable. I started looking for a setting that checks whether an incoming signal from the transeiver is active and if this is the case, it skips the identifications. But unfortunately I couldn't find it yet. I notice that a lot of explanations about SVXlink on the internet relate to repeaters and it works differently there than with simplex nodes. I hope you have the golden solution. It could be possible that the solution can be found in a .tcl file, but I don't dare to venture into that yet. The second problem that I have not yet been able to solve has to do with the stream via darkice and icecast. On the stream I only hear what comes from Echolink online. So the audio, the QSO of someone who has connected Echolink via smartphone or PC. And the identifications are also audibly broadcast via the stream. But, the signals that come from 2 meters, i.e. my transceiver, are not audible on the stream. I have checked my configuration several times with how G4NAB(Mon. Dec 25th, 2023 16:57:06 described this on his site but found no differences. Maybe I'm making a mistake somewhere or overlooking something. I hope you have suggestions that will also provide a solution to this. looking forward.
73's, PE1MEH