开云体育

Hello everyone! I have not been able to find an installation package for Fedora so I have decided to create and maintain the installer in Copr For those interested:

Hi Adrian, OK no problem Thanks for info 73 Waldek

Hi Waldek, Actually, please don't use that commit. It is very stupid and will not work, because it also tries to bind and listen to the remote IP address. I will write something that actually works

Hi Adrian, Yes Orange Pi Zero has not enough memory to run QRadioLink , maybe when we use Orange Pi Zero 3 with 2 or 4Gb RAM and OZPI Zero v3 has faster CPU it is possible run QradioLink but I use

I understand. It would be interesting to try to run qradiolink on the Orange Pi zero. There is an USB 2.0 port, the CPU seems powerful enough, the only possible problem could be the amount of memory.

Hi Adrian, Nothing, or rather the fact that I have my FM hotspot permanently running on Orange Pi Zero, which runs svxlink connected to FM POLND ( http://www.fm-poland.pl ), so I decided that since I

Hi Waldek, Obviously yes, you won't be able to use PTY squelch if running on separate machines. You can use CTCSS though. But just out of curiosity, what is preventing you from running svxlink on the

Hi Adrian, Ok thanks, it will be useful to use UDP svxlink across network not only on local computer But I see you are defined "SVXLINK SQL path" in "General Setting" so if I will be use UDP via

Hi Waldek, You're right, in the latest release it's only possible to use UDP audio from localhost. However, if it helps you, I've pushed a small temporary change for the UDP client here:

Hello Adrian, Sorry I haven't replied but I've been busy lately. Today I tried, but I understand that it is not possible to download audio via UDP from an address other than the local 127.0.0.1? I'm

Hi Waldek, So the svxlink connection feature was released in version 0.8.10, but I was not satisfied with the carrier drops at the start of the transmission caused by flowgraph underruns. That issue

The issue was not in svxlink (I think). It's more of a problem when using SQL_DET=VOX with UDP audio, because UDP datagrams stop arriving as soon as squelch is closed in qradiolink, and svxlink

Please note that the MUTE_TX_ON_RX option is used in part and must be specified in [SmplexLogic] This option is not used in the [GLOBAL] section See descriptions at

Yes but CARD_SAMPLE_RATE only supported sampling rates are: 16000 and 48000 it is not possible in this option select 8000 Hz Internally svxlink use 16 kHz (if I remember)

One other important thing I noticed: in the [GLOBAL] section there is this config option: MUTE_TX_ON_RX=0 What I see on my svxlink version is that if I enable this (which makes sense for a simplex

It's already possible, I tested this by setting: CARD_SAMPLE_RATE=16000 in the [GLOBAL] settings. As far as I can tell, svxlink can do either 16000 or 48000. qradiolink now has a dropdown for UDP

Hi Adrian, In svxlink, it would be useful to be able to, for example, select the sampling frequency for the UDP stream AUDIO_DEV=udp:<ip>:<port>,<sample_rate> where default sample rate is 16 kHz

Hi Waldek, I'm doing the direct UDP audio from svxlink to qradiolink. No USRP involved at the moment. I've solved it by adding a config option for UDP audio sample rate and resampling internally with

Hi Adrian, Note that UsrpLogic sends audio via UDP in 8 kHz USRP protocol and not 16 kHz , Because the standard in USRP used in DVSwitch/ Allstar Link is its own 8 khz audio and for this reason Adi

I figured it out eventually. I had a system instance of svxlink which was started by default (the init script is installed by apt). That was causing a conflict on the ALSA pulseaudio device. It works