开云体育

I was listening to the start of the Qnet Array pre-net just now. I had a short QSO with someone and then was just listening for the net to start when I started hearing short beeps coming for the laptop. I tried to mouse-click on the unlink tab and nothing happened. I had to close it down by closing down the terminal box. Is there a timer that needs to be adjusted to prevent this from happening again. Cal N9KO

I've uploaded a new release (200508) today with many changes: Since the very beginning IRC clients have maintained both an "inner" and "outer" Follow-Me cache for routing. The inner cache was maintained the IRCDDB thread and the outer cache was maintained by the gateway. This is redundant and very inefficient. DigitalVoice, qdv, now uses a single cache to manage Follow-Me data. The location of the configuration directory has been moved from $(HOME)/.config/qdv to $(HOME)/etc. After doing a "make install" the binary will be installed in $(HOME)/bin. If this directory is not in your search path, you can start it from your home directory by typing "bin/qdv" or from any directory by typing "~/bin/qdv". You can add $(HOME)/bin to your search path by modifying you $(HOME)/.bashrc file. Look for the "export PATH" line. Incoming audio quality has been significantly improved by applying the same "healing" technology I developed for QnetGateway. This will repair many situations with incoming voice streams where packets are lost or arrive out of order. It is now possible to maintain a link while you are routing. I don't recommend this, but it is possible. If you just enable linking, URCall will be fixed on "CQCQCQ". If you enable both linking and routing, be sure URCall is properly set before keying up! Use "CQCQCQ" to send your voice-stream to the linked reflector. Anything else will be sent on a route. A web-based dashboard is now included. This is very similar to the dashboard I've already developed for QnetGateway. It uses the php mini-server. This web server is not suitable for the world-wide-web an should only be used on a local network. To install it, type "sudo make installdash", then surf to "http://localhost", or "http://<hostname>.local (where <hostname> is the name of the system qdv is running on), or "http://127.0.0.1" using a browser on the system that qdv and the mini-server is running on. Finally, there is an About dialog box. You may need to click the "X" twice to make it go away. Tom N7TAE

Hi.. Are there any future plans to support non NW Ambe Boards as I have 2 that come up as Serial but the Program wont detect them. Thanks Rob. mw1coe

First off, thank you very much for all your hard work. I recently install qdv on a clean Buster image on a Raspberry Pi 4. I followed your instructions as listed in git to the letter (hence the clean image as I didn't want pulseaudio messing with my settings in various things running on other images). Everything installed and built correctly according to the terminal output. When I run 'bin/qdv,' the gui starts and I get this terminal output: ----------------------------- pi@raspberrypi:~ $ bin/qdv read 62 indicies from /home/pi/.config/qdv/announce/index.dat Host map contains: 622 XLX_Hosts.txt 506 DExtraHosts.txt 456 DCS_Hosts.txt 474 DPlus_Hosts.txt 0 MyHosts.txt Initialized AMBE3000R version V120.E100.XXXX.C106.G514 --------------------------------- If I click on 'Settings' the button in the gui goes grey, and nothing else happens at all. The gui is completely frozen. To stop the program, I have to go back to terminal and issue ctrl+c. The full output in the terminal changes to this: --------------------------------- pi@raspberrypi:~ $ bin/qdv read 62 indicies from /home/pi/.config/qdv/announce/index.dat Host map contains: 622 XLX_Hosts.txt 506 DExtraHosts.txt 456 DCS_Hosts.txt 474 DPlus_Hosts.txt 0 MyHosts.txt Initialized AMBE3000R version V120.E100.XXXX.C106.G514 Initialized AMBE3000R version V120.E100.XXXX.C106.G514 ---------------------------------- Any ideas on what could be happening?

John Hays posted an issue on the qdv github, listing several problem, the most serious was that audio wasn't working on Raspbian. After investigating, I found out that qdv not only depends on alsa (asound), it also depends on pulseaudio. On my Ubuntu development system (a System76 Kudu), pulseaudio is installed by default. This is not the case with the Raspberry Pi. So now the README.md file has a short section on how to install pulseaudio on Raspbian. Buster, the latest version of Raspbian, is a prefect platform for qdv. The full version is very friendly and easy to configure, with a GUI interface to all critical Raspberry Pi configuration parameters. There's no need to use sudo raspi-config anymore! The Raspberry Pi 3 or 4 has plenty of horsepower to easily run qdv. And the four USB ports are prefect, one each for a wired mouse and keyboard, a USB-headset and the Northwest Digital ThumbDV(tm). BTW, I still consider qdv to be in alpha release. I have observed some infrequent problems where qdv has to be restarted. Tom N7TAE

First of all, let me start by saying: Stream audio programming on Linux is challenging! I am still learning a lot about ALSA and PulseAudio and how they interact. The good new is that... You now are not forced to use the default PulseAudio devices for qdv! After much research I finally have audio card selection working with qdv. The key was seeing a few lines of source code from ALSA's aplay/arecord (specifically the -L output) and other examples I found on the web. The trouble is "aplay -L" will potentially report many devices that either aren't actually there, or are incompatible with qdv, but I did find that, at least so far, the plughw type devices seem to always work, and as near as I can tell, all cards have a plughw I/F. So in addition to "default", you can now select any plughw device on your system. There is a separate selection for input (microphone) and output (speakers) in the Settings Dialog.

I keep gettng a "Not in Cache" message. I tried Dstar1 and Dstar2. The install looks like it went OK. Using Ubuntu 18.04 LTS on a 64bit Dell D830 with 4 GB RAM. 22:00:37: findRoutes = [22:00:37: ] 22:00:37: Repeater callsign: [N9KO-A] 22:00:37: connecting to rr.openquad.net at 9007 22:00:37: Waiting for rr.openquad.net connection status of 2 22:00:37: rr.openquad.net status=0 22:00:42: rr.openquad.net status=0 22:00:47: rr.openquad.net status=0 22:00:52: IRC server is using IPV4 22:00:52: QnetGateway...entering processing loop 22:00:52: get_irc_data thread[0] started 22:00:59: Finding Routes for... WELCOME_TO_QUADNET 22:01:07: id=84e1 start RPTR flag0=00 ur=DSTAR2 r1=N9KO A r2=N9KO G my=N9KO /QDV 22:01:07: could not find a repeater for user DSTAR2 22:01:07: User [DSTAR2 ] not in local cache, try again 22:01:13: id=84e1 END RPTR NOT_IN_CACHE