|
Re: Fldigi and Win11 audio tricks
FYI, I see that you posted this is possibly a hardware issue because the problem also occurs under Win10, but I wanted to add a note for Win11 users. Win11 does not handle audio the same way as Win10. It is *not* sufficient simply to configure the audio devices in the fldigi app and expect it to work correctly.? There are application-specific audio settings in the Windows 11 sound settings control panel that must be set properly. In Win10 all you have to do is select the sound devices inside fldigi (or js8call, wsjt-x, etc.) and off you go. That does *not* work in Windows 11.? I've detailed the settings approach that I had to use to get fldigi working correctly in Win11 in another thread, so my main point here is that you can't just post a screen shot of the fldigi audio config and expect that to mean anything for Windows 11. Windows 11 itself may be rerouting the audio elsewhere, regardless of what setting you make in the fldigi audio config panel. 73 de AE4ON On Sun, Nov 10, 2024, 2:20?PM Kenneth G. Gordon via <kgordon2006=[email protected]> wrote: OK. I have just now confirmed that our problem here is NOT in Win11. It occurs in Win10 |
|
Re: Fldigi and Win11 audio - DO NOT buy Acer
I just got out the glass to see the other one <grin>. Thanks for the new image.
toggle quoted message
Show quoted text
~R~ On 2024-11-10 19:35:, Kenneth G. Gordon via groups.io wrote:
On 10 Nov 2024 at 18:35, Rich NE1EE via groups.io wrote: |
|
Re: Fldigi and Win11 audio - DO NOT buy Acer
¿ªÔÆÌåÓýOn 10 Nov 2024 at 18:35, Rich NE1EE via groups.io wrote:
> Thanks for pinning that down (stunning construction flaw), and then
> telling us in clear detail. I hope that Costco is notified. Can you
> give us the model of the Acer, or is 'Acer Aspire 3' sufficient? We
> have a local Costco, and I want to let folks know, because we have an
> active group of digi hams. ~R~
>
> On 2024-11-10 18:29:, Kenneth G. Gordon via groups.io wrote:
> >I have determined that pins 2 and 3, or Data+ and Data- are reversed
> >in the two USB ports of this new Acer Aspire 3 laptop. It was bought
> >at Costco.
Here is a photo with higher resolution.
-- Ken Gordon W7EKB |
|
Re: Fldigi and Win11 audio - DO NOT buy Acer
¿ªÔÆÌåÓýOn 10 Nov 2024 at 18:35, Rich NE1EE via groups.io wrote:
> Thanks for pinning that down (stunning construction flaw), and then
> telling us in clear detail. I hope that Costco is notified. Can you
> give us the model of the Acer, or is 'Acer Aspire 3' sufficient? We
> have a local Costco, and I want to let folks know, because we have an
> active group of digi hams. ~R~
>
> On 2024-11-10 18:29:, Kenneth G. Gordon via groups.io wrote:
> >I have determined that pins 2 and 3, or Data+ and Data- are reversed
> >in the two USB ports of this new Acer Aspire 3 laptop. It was bought
> >at Costco.
Here you go, Rich.
-- Ken Gordon W7EKB |
|
Re: Fldigi and Win11 audio - DO NOT buy Acer
On 10/11/2024 23:29, Kenneth G. Gordon via groups.io wrote:
I have determined that pins 2 and 3, or Data+ and Data- are reversed in the two USB ports of It's been a few years since I worked on USB and then only upto USB 2.0 before USB 3 and USB-C came on the scene. Usually Data+ and Data- are used for differential working but non differential values were used for indicating what data-rate was supported by the device (i.e. B end). So maybe it was only tested with USB-C devices and not with legacy USB 1.1 and 2.0 devices. I would reckon that most serial interface cards are USB 2.0. 73 Phil GM3ZZA
|
|
Re: Fldigi and Win11 audio - DO NOT buy Acer
Thanks for pinning that down (stunning construction flaw), and then telling us in clear detail. I hope that Costco is notified. Can you give us the model of the Acer, or is 'Acer Aspire 3' sufficient? We have a local Costco, and I want to let folks know, because we have an active group of digi hams.
toggle quoted message
Show quoted text
~R~ On 2024-11-10 18:29:, Kenneth G. Gordon via groups.io wrote:
I have determined that pins 2 and 3, or Data+ and Data- are reversed in the two USB ports of |
|
Re: M4 Mac Mini Error w/Fldigi ("fldigi-4.2.06" would like to access the microphone.)
I can say that this is also the case with newer releases of W10 and W11. Settings > Privacy > Mic|Camera is a new setting. I leave it turned off, and turn it on when I want to do fldigi or something specific w a mic or camera. So I guess you need to say yes to the question, or find a place in the OS to turn it on. In Windows, we can select different apps that have permission to use these items.
toggle quoted message
Show quoted text
fldigi won't work in Windows unless it finds the port audio drivers, and it won't find them unless the mic is enabled and fldigi has permission to use the mic...which it needs as audio stream from the radio. fldigi used to crash when it couldna find the audio devices, but now it pops a dialog that says it can't find it, and keeps running. The config needs to change (mic permission, etc) and fldigi restarted. It won't work unless restarted. I did see your post, so I see that you have been addressing mic issues. Not an Apple guy, so no clues here, sorry to say. ~R~ On 2024-11-10 15:29:, Lonnie Craven via groups.io wrote:
I have checked, unchecked, and checked the microphone access, but the program still crashes. |
|
M4 Mac Mini Error w/Fldigi ("fldigi-4.2.06" would like to access the microphone.)
I have used Fldigi successfully for several years with a 2018 Mac mini. I recently upgraded to a M4 Mac Mini. Since then, I have not been able to get Fldigi to work with my new Mac Mini. ? I first used Homebrew to install the latest version of Fldigi. That didn't work. ? Then, I downloaded Fldigi from the main website. That also didn't work. ? Here's what happens when I attempt to open the program: Fldigi will open for 2 or 3 seconds, close, and then the attached message will be displayed. ? I have checked, unchecked, and checked the microphone access, but the program still crashes. ? So, what steps am I missing? Thanks for your suggestions. ? Lonnie Craven (K4KZ) |
|
Re: Fldigi and Win11 audio tricks
GA, Ken...busy here, so a few quick notes
On 2024-11-10 12:10:, Kenneth G. Gordon via groups.io wrote: I'll try once more to explain it: the audio signal from the radio's receiver, through the digital interface and the computer's USB port is being directed to the computer's MIC inputCorrect. instead of to the computer's speakers and to Fldigi's on-screen waterfall display where it should appear.This means ~to me~ that fldigi's input port is ~not~ connected to the USB mic input. This is why I have the habit of loosely following the PDF guidelines...by naming the proper USB ports at the driver level, I am less likely to get them wrong in fldigi. I'll send pics later. And the signal from Flidigi which is meant to be directed from the computer through the USB port and the digital interface to the radio transmiter's MIC jack is, instead being output to the computer's speakers and never appears at the transmitter at all, where it is supposed to be.If I saw that here, I'd immediately check the fldigi port config to verify that its TX is going to the correct driver (CODEC). So you are on the right track when you say that you might post images later...so will I. As we talk in the room where we are working, Fldigi's waterfall is displaying audio signals which vary with our voices.Makes sense. It means that fldigi is configured to send its output to the system speakers...possibly identified as some specific device, such as Realtek speaker. Cheers, ~R~ NE1EE |
|
Re: Fldigi and Win11 audio tricks
¿ªÔÆÌåÓýNo. I have it configured as you show it. I'll post photos asap. At this point, I am strongly suspecting an error in the laptop, perhaps within the audio system driver. More later. Ken W7EKB Sent via the Samsung Galaxy S21 5G, an AT&T 5G smartphone -------- Original message -------- From: "K1APJ via groups.io" <K1APJ@...> Date: 11/10/24 09:36 (GMT-08:00) Subject: Re: [winfldigi] Fldigi and Win11 audio tricks It sounds like you have FLDigi configured to use the laptop's speaker and microphone channels, rather than the Signalink USB.
?
Here is a snip of my FLDigi soundcard configuration. Yours should be similar. Note that it uses the speaker and mic OF THE USB AUDIO DEVICE, not the Realtek soundcard in the computer. If the USB soundcard driver does not appear, you may have a missing driver.
?
-- Ken Gordon W7EKB |
|
Re: Fldigi and Win11 audio tricks
It sounds like you have FLDigi configured to use the laptop's speaker and microphone channels, rather than the Signalink USB.
?
Here is a snip of my FLDigi soundcard configuration. Yours should be similar. Note that it uses the speaker and mic OF THE USB AUDIO DEVICE, not the Realtek soundcard in the computer. If the USB soundcard driver does not appear, you may have a missing driver.
?
|
¿ªÔÆÌåÓýBill,
The enable switch is in the menu Logbook->Connect to Server.
The port fldigi tries to connect to is 8421.
There is also and interface to broadcast a UDP datagram
containing an ADIF record - this can be goot from
Configure->Logging->Cloud-UDP. There's also specific
configuration for MacLogger and N3FJP loggers.
Phil.
On 10/11/2024 15:36, Philip Rose via
groups.io wrote:
|
¿ªÔÆÌåÓý
Hi Bill,
Fldigi uses a TCP datagram to communicate with the logging software. The payload is an XMLRPC response and request. My logging software supports the following requests calls:
Log.list_methods - lists the supported methods
Log.add_record - Adds the ADIF data sent as a new record.
Log.get_record - Returns the ADIF record that matches certain fields (call, band, mode)
Log.update_record - merges the current record with the supplied record.
Log.check_dup - returns true, false or possible for the supplied ADIF record.
I can't remember where I got the specifications of these from apart from may be reverse engineering the Fldigi logging interface to fllog. I don't have an instance of fldigi on this machine otherwise I could look to see where the fields you need to enter in
its config. There is a menu item to enable connection to the log server (which is what my logging app behaves as). I had a brief scan through the fldigi and fllog manuals but couldn't see anything.
Hope this helps a bit.
Phil GM3ZZA
From: [email protected] <[email protected]> on behalf of Bill - W1WRH via groups.io <w1wrh@...>
Sent: 10 November 2024 2:24 AM To: [email protected] <[email protected]> Subject: [winfldigi] callsign lookup in logging program #fldigi #Log4om ?
I am trying to find the link from Fldigi to logging programs that allows them to look up previous calls when a callsign is entered in Fldigi to start a QSO.? When used with DX Keeper as soon as you enter a callsign in Fldigi, DX Keeper and DxView look
up the callsign.? When used with N3FJP the same process happens.? I am trying to duplicate this lookup with Log4OMv2 but I cannot find what is sending the data to the other programs.?
?
Does anyone have any idea where I can look, or how to do this set up?
?
Thanks in advance for any ideas.
73
Bill
w1wrh
|
|
Re: Fldigi and Win11 audio tricks
GM, Ken,
I understand the frustration...I'll resp0nd inline, and hope that quoting makes it clear... On 2024-11-09 20:53:, Kenneth G. Gordon via groups.io wrote: If one looks at the levels displayed in the MIC output display in say the audio mixer,"MIC output display" I want to be sure we are on the same page here...MIC output display means the output from the ~driver~ to Windows apps, not output to an external device, such as digirig. mic is an input. I avoid this discussion in my mind by labeling devices as recommended in the attached. one sees the levels being output by the receiver through Fldigi.Not quite, IIUC. The mic input is the audio signal that has not reached fldigi yet. You should be able to kill fldigi, tune the radio to a signal, and see a response on the Windows mic meter. From there, if fldigi is configured to use this input, the audio stream will reach fldigi. fldigi doesna reroute received audio streams anywhere that I know of. There is no such display in the SPEAKER level control reading where it should be.That makes sense. The only way for the spkr meter to respond to mic inputs is to have it configured that way. Please see the attached. In principle, these docs work ~in general~ for any radio and sound card IF, such as SignaLink or digirig. Note in particular, "In Playback and Recording, the digirig should NOT be a Default or Default Comm Device. Only fldigi will be using it." Of course, if you want to hear the RX audio, then configure the driver to send audio to the speakers. fldigi will be able to ~also~ receive the audio stream. It's just sent to 2 places: fldigi, because fldigi is configured to use that mic device; and the system speakers, because the driver is configured that way. The docs attached assume that you ~don't~ want to listen to all that digital audio, so the mic and speaker devices attached to the sound card you are using, such as digirig or SL, are NOT a Default or Default Comm Device. I adjust the audio to the radio speaker or an external speaker when I am using any of my radios except HTs. That way, I can confirm received signals, yet turn down the volume so I am not annoyed by the noise. Can't do that w HTs., but there are many visual indications of both RX audio (on radio and laptop), and the fldigi SIG display. Ordinarily, in Win10, one can see audio from the radio receiver being displayed in theONLY if the system is configured that way. Instead, in Win11 we are seeing the audio output by theThis is exactly where it should be. Radio ~output~ is a mic or line level ~input~ to the computer. As I said, in this case, I fixed the issue by installing and activating a new seat of Win10 Pro 64 bit.You have been very clear with your posts, but I admit that it leaves me puzzled about how you normally config your system in W10. As you see in the attached docs, the Sound dialog is pictured. What is not pictured, but is described in the text, is further configuration, noted by comments such as "Listen: Unselect Listen to this device." All I can say otherwise is that I am a regular user of fldigi, have been for many years, and use a variety of Windows. I use fldigi with W11, following both the recommendations of the attachments AND accounting for the peculiarities of W11, which, IMO, make life more difficult, but still follow the same rules. Kind regards, Rich |
Daniel (AE4ON)
Rich NE1EE
Philip Rose
Lonnie Craven
