开云体育

That was too fast. No - it doesn't make it go away. Added: changing freq on radio and: progdefaults.maclogger_spot_rx 0 mclg_txhz = 7245000, maclogger_set_qsy: 7245000 progdefaults.maclogger_spot_rx 0

Tracked it down. Frequency was being changed in maclogger_set_qsy(). I had "Tune to Rx Spot" turned on and fldigi reacted on: [Radio Report:RxMHz:7.07968, TxMHz:7.07968, Band:40M, Mode:LSB, Power:100]

Yes. Flrig alone and: - flrig frequency display follows frequency changes made at radio - same for the other way - frequency changes made at flrig are applied to radio correctly - changes made via

Joel, any version of Linux is a good version of GNU/Linux, at least in someone's opinion. If your works is using RHEL, then Fedora has a lot in common. For the Broadcom drivers, you could also try

Thanks for the reply. I am a part of that group and have no issues communicating with the radio through the digirig using JS8Call or WSJT-X

make sure you are a member of "DIALOUT" group in Linuxkc Thanks Dan KC2STA <rjayg1979@...> wrote: -- Dan Ziolkowski KC2STA SKCC #4290T Ubuntu LINUX

I have a Yaesu FT-747GX that I am able to successfully use CAT control with through JS8Call and WSJT-X through a DigiRig mobile. I am trying to get it working with flrig, but am not having any luck. I

Hi. If you run Flrig alone, does Flrig "follow" what you do at the radio? If not, you need to find out why.? (Flrig settings, or Radio issue.) If it does, then something is wrong in how FlDigi,

Hello. I'm new to flrig/fldigi, so this is probably something obvious but wasn't able to track it down. fldigi 4.2.06 (also tried 4.2.06.05) on macbook pro m3 (macos sequoia), connected fo flrig

Thank you Gary.? Perhaps it is time for me to fultill the Apple Developer requirements. David

Dave, I took the liberty of using my Apple Developer ID to re-sign Fldigi-4.2.06.05.dmg, sending it through the Apple notarization tool and stapling the approval to the app. This should permit MacOS

Thanks Phil, Helpful background info, much appreciated! 73 de PC1K

I joined the ADIF community after the introduction of SUBMODE, version 3 I think. But from some of the discussion, I understand it was an attempt to get a handle on the growing proliferation of new

Dave, Other than the normal “malicious software” warning, having to go into System Settings and telling it to run anyway, and getting just a single “Fldigi wants to use your microphone”

Unfortunately just lost my Apple silicon mac last week. I know, because I started the discussion, my aim was to make logging more consistent. Before the change I have seen a FSKH105 QSO logged as

Same here on my M2 Mac mini. Dan

I had to go to System Settings > Privacy and Security > Security and tell it to open anyway it complained once again but once I gave it my fingerprint it opened. Only had to click once on mike use.

I need a few Mac users to test install this version of fldigi: http://www.w1hkj.com/alpha/fldigi/fldigi-4.2.06.05_SO.dmg on M1/2/4 systems. You may need to right click on the installed app icon in

I will look again at the code, but this change was forced upon us by the current ADIF specification. David

Sublime ?.? Thank you Lonnie.? I tried this on my M2 MacBook Air and it worked just as described.? The codesign will probably need to be repeated with each new fldigi install. David