开云体育

I'm on 12.7.6, been running Flrig and Fldigi for years on this Mac, no problems. Try renaming the .fldigi folder in your home directory. Setup Fldigi again. Lonney K1LH

http://www.w1hkj.com/alpha/flrig/ Index of /alpha/flrigs * Parent Directory <http://www.w1hkj.com/alpha/> * darkscheme.UI.prefs <http://www.w1hkj.com/alpha/flrig/darkscheme.UI.prefs> *

Hey everyone. I'm looking for help to fix a problem with fldigi on my Mac computer (v 12.7.5). I downloaded fldigi and it worked for a day or 2, but now every time I try to open it, it closes almost

Hi. AFIK, it's an OS imposed restriction, of the use of "Microphone" like unknown (to the OS dev's) devices (aka any audio input device) as a privacy thing. Winders does much the same, but may be

No, sadly nothing new on this issue in this version. I’m running 4.2.05.24 on a M2 MacBook Air (Sequoia 15.0.1) and confirm the "FLDigi would like to access the microphone” issue IS still

Anything new on the "FLDigi would like to access the microphone" problem?

Ok, thanks

The comments / count reference is for the coder's convenience. ls src/rigs/other AOR5K.cxx???? PCR1000.cxx?? RAY152.cxx??? sunsdr2.cxx TMD710.cxx FLEX1500.cxx? PowerSDR.cxx? SmartSDR.cxx?

The latest OS that I build and test on is Sonoma 14.6.1. David

Hi again. Thanks for that info David. Checking off what you described... It was:- src/rigs/rigs.cxx:??? &rig_ICR71, ??? // 63 That escaped my radar.? (Of course, I've used "&rig_ICR9000"

Greetings, I am contemplating buying a iMac with M3. I’ve always used Easy Digi with my Toshiba Satelite with Win 7. Works great on BPSK31 that I operate 90% of my QSO’s. Is there an Easy Digi

Dave, I have been using FLdigi-4.2.05.24 successfully for several months now. I am going to have to upgrade my MacOS to the latest and greatest (Sequoia 15.0.1) in the near future. Have you done

Do a grep for R71 and you will find these line items that are critical to getting a new rig registered: src/Makefile.am:??? rigs/icom/ICR71.cxx \ src/Makefile.am:??? include/icom/ICR71.h

Hello again David (W1HKJ) OK. Following your last, I now have some code (copied from the IC-R71 files, changing ALL instances of "R71" to "R9000") that appears to build OK without errors. I don't

Thanks David. I was looking in the makefile.am file in the project's root director, not the src directory! Hence the confusion... Thanks again. 73. ??? Dave G0WBX. -- Created on and sent from

Yes, the CAT commands can be confusing. I was looking at byte 0 for the filter width, but byte 7 is correct. I changed the code to use names like your code and also fixed the vfo-b modes. I found

Thanks Steve.? Very confusing CAT commands. David

Dave, Look at src/Makefile.am # Sources that we build. It is OK to have headers here. flrig_SOURCES += \ ??????? rigs/rigbase.cxx \ ??????? rigs/rigs.cxx \ ???????

I tried your changes. It seems to revert to the incorrect operation before the changes I submitted. I don't see how your case statement can work for the modes. The only valid numbers in byte 6 are 0,

Hi again. Looking into this now.? But... These steps mentioned by Dave 'HKJ... How to add a new transceiver to flrig (A) ? Two new files will need to be added: ??? .