开云体育

Phil. If your system reliably uses the same "device path" to reach the codec chips, then you can use that to steer things in the right direction with a couple of udev rules. I'm (currently, but that

ok, well two rigs the same is different, no one mentions two rigs until now :-) Re audio dev names, same problem on macOS with Icom and the integrated USB audio, they appear with the same generic

Have fun, indeed. The same is true for USB Audio Codecs. Although my two Icom radios have serial numbers implanted in the USB Serial chips, their audio codecs are indistinguishable from USB point of

Lonney, the issue is only a problem when one has multiple same make of USB<>Serial products showing the exact same information to the PC when enumerated. The exception being FTDI based devices (and it

I reverted to hamlib 4.6 and successfully built fldigi 4.2.06.19. It works with my Yaesu FT-890. I switched Hamlib back to version 4.7~git and fldigi 4.2.06.19 still works with my Yaesu FT-890. This

I compiled 4.2.06.17 with hamlib 4.6, which did not work, but it now works with hamlib 4.7. It is apparent that he "fixed" fldigi 4.2.06.18 for hamlib 4.6. Since the rig_caps variable is the source of

The Country (CTY) Files were updated on 02 January 2025: https://www.country-files.com/cty-3501-02-january-2025/ For installation instructions, start at: https://www.country-files.com/ Hover your

Hi Steve It actually broke my fldigi/hamlib alpha builds. ie 4.2.06.18 and 19 now fails with Hamlib 4.7~git 2024-12-29T16:43:39Z SHA=028d75 64-bit (and later) rigcontrol/hamlib.cxx: In function

Hamlib has recently reverted the change that broke fldigi hamlib control build with this comment: Change rig_list_foreach back to using const argument -- was breaking many C++ application builds I

http://www.w1hkj.com/alpha/fldigi * fldigi-4.2.06.19.dmg <http://www.w1hkj.com/alpha/fldigi/fldigi-4.2.06.19.dmg> * fldigi-4.2.06.19.tar.gz <http://www.w1hkj.com/alpha/fldigi/fldigi-4.2.06.19.tar.gz>

I'll read more into it later, I've never ever had a problem? using the sym links in /dev/serial/by-id , they always work, they always point to the right device on my Debian 12(ish) systems and Icom

Hello, I purchased a new MacMiniv M4. Now I am having the issue on my Mac when starting fldigi that I am always bothered by a pop-up message asking for Microphone access. How to overcome it? In the

Happy New Year to you too Sir. Let's all hope 2025 is less troublesome than 2024 was! 73. Dave G0WBX. -- Created on and sent from a Unix like PC running and using open source software:

Hi Lonney. Yes, those links work too, but the problem is, not that one or other style of link works or not, is that the default links/symlinks created by the OS, can change whenever it is kicked into

Initial test looks good.? XMIT transmits.? Cancel stops transmitting with the correct message.? Remove removes.? Thank you sir, great suggestion! I am running FLDIGI version 4.2.06.? Should I

2.2.14 installed and running.? Will advise.

Yea, that version was released in error and has a few issues, grab 2.2.14. http://www.w1hkj.com/files/flamp/ Robert

2.2.13 This is on a RPi, 4B, Bookworm.? Everything else in FLAMP seems to work as expected.

Richard, What version are you using? Robert

"does not XMIT" means that the transmitter is not keyed, the transmit timer left of "Spot" in the upper right does not come on, the T/R button in the lower right does not change to red, no signal in