Hi Dave,

?

Perhaps the UI setting shown in the message linked below will allow you to revert it. On mine, the default was “gtk +”

?

?

—

Graeme

How do I revert back to the light theme for FLDIGI. It's set as a silver style scheme at the moment.

I have looked in some earlier posts about theme's but can't find a way back to the original theme.

Any help would be appreciated.

--

Hi David,

?

Thank you for fixing the waterfall colour palette issue. It’s working fine for me now.

?

—

Graeme

--

I was working on my FLDIGI with my ICOM 7300. Tx is working great but I am getting strange characters on the RX screen. Looks similar to Japanese.

I must have something set wrong?

Any help would be appreciated.

--

Thank you Dave! The new delayed QSY macro tag works perfectly with my G106!

?

73! de HA3MGA Gabor

I want to thank all of you for input. All of your suggestions were very helpful. After my company leaves this weekend, I'm going to review all of your suggestions and play with my Fldigi settings. I'll let you know how things work out. I appreciate your time and committment to helping me. Thank you.?

?

Darryl

Thank you for your input.?

?

Darryl

Thank you for your input. I'm going to revise my settings.

?

Darryl

Thank you for your input.

?

Darryl

Darryl,

If you consider how digital decoding works, it's a logical consequence, that below a certain amount of SNR (Signal/Noise Ratio), things become completely unreadable - and thus gibberish. Since the computer only reproduces but doesn't 'understand' what it puts on the screen, both cases may and will occur, especially with fading signals on shortwave.


- - - - - -


Take a classic MFSK16 mode, for example, as used on W1AW for their QST bulletins on SW. Simply put, after synching onto the (last found) tone transition time, the decoder only checks, in any pre-defined (fixed length) time slot, which of the 16 tones (used in this mode by design) has the highest amplitude, and considers this one the 'correct' (and supposedly transmitted) tone. Its number is then fed into the FEC and text decoding logic for the text output. As you can imagine, at any audio and SNR level, there will *always* be one of the 16 tones that has the highest amplitude, even if pure noise is received. Thus, unless the decoding logic itself shuts itself down to 'idle' in case of too many consecutive errors, the result will be gibberish put out into the RX window. Usually the decoding logic is designed for high(est) sensitivity, and therefore will continue evaluating, even if the result does not meet the mode's FEC requirements during a certain time.

In modes like MFSK, keeping the idle tone active (uninterrupted) while transmitting, even in text (typing) pauses, usually avoids random characters on the RX side, provided the signal (SNR) is high enough for proper decoding in the first place. If, on the other hand, there are signal gaps, even fractional second pauses entirely without a transmitted signal, as is the case between text blocks and image transmissions in Kim KD9XB's Shortwave Radiograms, you'll usually see a certain amount of gibberish until the TX signal (and RX synch) is restored, when the next text block or image header starts.

The best general workaround on the receiving side, as stated in this discussion thread before, is to activate the Squelch button (bottom right) and then slowly increase the green slider next to it upward in transmission pauses until you shut off (most of) the unwanted characters. Obviously, this is a manual process and exaggerating the Squelch level will turn FLdigi more insensitive against weak or borderline signals, which might otherwise, at least in part, have been decoded. So it's up to you...


- - - - - -


Whenever hams are polite (and knowledgeable) enough to activate TxID (the standardized RSID mode tag), and you do the same on the RX side by activating RxID (both buttons are top right in the FLdigi window), you can setup FLdigi to notify you about the start of a new message (signal). The notifier is user-configurable, and if you add a few empty lines before and after an easily visible RSID tag text, the result may look like this (an example from Shortwave Radiogram, as received this week):


- - - - - -


Shortwave Radiogram now changes to MFSK64 ...



k hcy*Rf0itií


----------------------------------------------------
RSID: <<2024-10-17T23:38Z MFSK-64 @ 1499>>
----------------------------------------------------

?sLRr s n? iwc







This is Shortwave Radiogram in MFSK64

Please send your reception report to radiogram@...


- - - - - -


You see, there still is a bit of gibberish received and logged in signal pauses, but a new transmission (or mode switch) is now clearly visible in your RX text window!

I attach my 'notify.prefs' as stored in 'C:\Users\ < U S E R N A M E > \fldigi.files', which should give you the RSID tag layout shown above, should you be inclined to try it out (be sure to close FLdigi if you copy this file into your folder - and backup your existing file before, in case you wish to return to the previous settings). The leading and trailing empty lines are defined in 'notify.prefs' by the NewLine token backslash-n (\n = 1 new line, \n\n = 1 new and empty line etc.), and you can easily adapt this to your needs in any text editor. The tiny preview in the 'Notifications' Dialog may not correctly show such extra lines etc., but they will be visible in the RX window. Most user-configurable settings are available under Menu - Configure - Notifications, others under Menu - Configure - Config Dialog - IDs [+] RsID, and 2 attached (commented) screenshots show some of the settings to choose from.

Note: in FLdigi, RSID can be (de)activated *per mode*, which may not be very intuitive, but is certainly way better than no choice at all. In the attached screenshot 'FLdigi_Configuration.png', you'll see a Button 'Rx modes' and another Button 'Transmit modes'. They are entirely independent, but only activating the RSID function for all 'your' modes in both TX and RX will make these useful features available.


- - - - - -


On the other hand, when people don't use RSID and we can only resort to the Squelch option described above, I dearly miss a simple feature in FLdigi, which would be adding an (ideally user configurable) marker and/or newline(s), whenever Squelch opens again. That would then, instead of simply appending new text *within* the current line (so far without any indication that there was a transition or new message), place a new message *below* the previous one. I don't really understand why nobody has implemented such a helpful function, which, code wise, should be easy enough to realize, I assume. Especially when there are random characters between closed Squelch periods from time to time, such a simple visualizaton would certainly help sort the wheat from the chaff in the RX text. But sadly, so far, this is just a suggestion, not a feature.


Good luck and enjoy FLdigi, it's really a great piece of free software, thanks to Dave's generous work he puts into ever improving it...


Vy 73 SWL Tobias
.-.-.

You can turn on SQL, but at the risk of losing text from modes with forward error correction.

Good Afternoon Follow FLdigi users,

?

I have followed the FLdigi setup procedures and watched many videos. However, I can not find any information on how to stop the gibberish text on the screen. What do I do in the setup to stop the Gibberish text?

?

?