Date   
Fldigi Off Line Message

Richard Small
 

I have had the "Fldigi off line" message when i shut down Fldigi but today I got it in a session while receiving a picture in MFSK128. What ever was going on killed Flamp and caused the loss of the incoming partial message. In the past this message was a nuisance and of no value to me. Today it was detrimental to the receipt of a message. Fldigi was operating and continued to operate as did Flamp after restarting. Flmsg ver 4.1.11, but message has been around for a long time.

The start of Flamp is fragile. Using Autostart in Fldigi it often crashes on start. Restarting from Autostart Test will usually keep it up.

Dick, WB6DIK

Re: fldigi 4.1.10

Dave, KI7VLV
 

Understood. Thank you. Sure! Please add me to the list. ki7vlv@... 73, D

Re: flamp closes when using the file ... audio capture RX save dialog

Dave
 

Strange behavior on Windows 7.  The same dialog correctly discovers the wav and mp3 files when opened from either the <AUDIO:...> macro tag creation, or when setting up the configuration items for audio alarms.

Dave

On 4/3/20 7:16 PM, Dave wrote:

Easy ones first.

The files are visible on Linux, so this is a Windows interface issue.  I can confirm that the mp3 and wav files are not visible until "All files" are selected.

For now, list this as a "known bug" with a work-around.  I'll refrain from advising to move to a Linux OS.

David


On 4/3/20 6:46 PM, John Rabold wrote:


On a slightly-related note, when using "File|Audio|Playback" with the dialog box filter at "Waveform Audio Format (*.mp3;*.wav)", any *.wav files in the specified folder are invisible. They become visible only with the filter set at "All Files (*.*)".

John / KS6M

Re: flamp closes when using the file ... audio capture RX save dialog

Dave
 

Easy ones first.

The files are visible on Linux, so this is a Windows interface issue.  I can confirm that the mp3 and wav files are not visible until "All files" are selected.

For now, list this as a "known bug" with a work-around.  I'll refrain from advising to move to a Linux OS.

David


On 4/3/20 6:46 PM, John Rabold wrote:


On a slightly-related note, when using "File|Audio|Playback" with the dialog box filter at "Waveform Audio Format (*.mp3;*.wav)", any *.wav files in the specified folder are invisible. They become visible only with the filter set at "All Files (*.*)".

John / KS6M

Re: flamp closes when using the file ... audio capture RX save dialog

Dave
 

John,

Thank you for your comprehensive report.

David, W1HKJ

On 4/3/20 6:46 PM, John Rabold wrote:
I am confirming this behavior under certain specific circumstances, and I agree that it has been around for a while. I am using fldigi 4.1.11, flmsg 4.0.14, and flamp 2.2.05 on Windows 10. When launching "File|Audio|RX capture" OR "File|Audio|Playback" in fldigi, and the dialog box opens to specify the capture or playback file, with flmsg and flamp running, flamp will crash with the "fldigi off line" error message. Further, though flmsg does not display an error message at that point, it does not close cleanly; it is "not responding" for a few seconds. However, this happens on my system ONLY with flmsg executing. If flmsg is NOT executing, flamp continues to run and there is no error message. If flmsg is not launched or if it is closed manually before invoking "File|Audio|RX capture" OR "File|Audio|Playback" in fldigi, flamp remains executing and there is no error message.

Once capture or playback has begun, flmsg can be safely launched without causing flamp to crash.

In case this behavior is related to the settings at Misc|NBEMS interface (I have not tested this), my settings are: NBEMS data file interface checked, Open message folder NOT checked, Transfer direct to executing flmsg NOT checked, Open with flmsg checked, Open in browser checked, and the correct full path to the flmsg executable specified in the text box: C:\Program Files (x86)\flmsg-4.0.14\flmsg.exe

On a slightly-related note, when using "File|Audio|Playback" with the dialog box filter at "Waveform Audio Format (*.mp3;*.wav)", any *.wav files in the specified folder are invisible. They become visible only with the filter set at "All Files (*.*)".

John / KS6M

Re: flamp closes when using the file ... audio capture RX save dialog

John Rabold
 

I am confirming this behavior under certain specific circumstances, and I agree that it has been around for a while. I am using fldigi 4.1.11, flmsg 4.0.14, and flamp 2.2.05 on Windows 10. When launching "File|Audio|RX capture" OR "File|Audio|Playback" in fldigi, and the dialog box opens to specify the capture or playback file, with flmsg and flamp running, flamp will crash with the "fldigi off line" error message. Further, though flmsg does not display an error message at that point, it does not close cleanly; it is "not responding" for a few seconds. However, this happens on my system ONLY with flmsg executing. If flmsg is NOT executing, flamp continues to run and there is no error message. If flmsg is not launched or if it is closed manually before invoking "File|Audio|RX capture" OR "File|Audio|Playback" in fldigi, flamp remains executing and there is no error message.

Once capture or playback has begun, flmsg can be safely launched without causing flamp to crash.

In case this behavior is related to the settings at Misc|NBEMS interface (I have not tested this), my settings are: NBEMS data file interface checked, Open message folder NOT checked, Transfer direct to executing flmsg NOT checked, Open with flmsg checked, Open in browser checked, and the correct full path to the flmsg executable specified in the text box: C:\Program Files (x86)\flmsg-4.0.14\flmsg.exe

On a slightly-related note, when using "File|Audio|Playback" with the dialog box filter at "Waveform Audio Format (*.mp3;*.wav)", any *.wav files in the specified folder are invisible. They become visible only with the filter set at "All Files (*.*)".

John / KS6M

Re: WEFAX reception in FLDIGI losing phasing alignment sync often

Dave
 

Have you discussed the problem with the seller of the VB-Audio Virtual Cable ?  What are the specifications for that software?

Try saving the incoming audio to a wav file (off-line from fldigi) and then playing back that wav file using fldigi's wav file playback mechanism.  You might also be able to anayze the wav file to see if it contains any obvious missing audio segments.

Have you tried simultaneously receiving that WEFAX signal using a h/w receiver or transceiver with fldigi.  Perhaps on a separate computer.  Your SDR implementation seems to have a number of "black boxes" over which you have little control.

Dave

On 4/3/20 5:43 PM, roger.tobin@... wrote:

I have an issue that seems common to all the versions of FLDIGI I’ve kept up with over the past couple of years.

 

When I am receiving a WEFAX from a station like NMC (Pt. Reyes CA), the image will lose the alignment whenever there is other activity on my computer.  If I walk away from the system for an extended period of time, the received images tend to be aligned, even if they are a bit noisy.

 

If the signal is strong (rarely), this can still happen, but perhaps not as often (I don’t have any definite proof of this).

 

I’m using VB-Audio Virtual Cable to pipe the sound from SDRuno, which is being fed by my RSP1-A.  I’m on a Windows machine running the latest builds of W10 from the fast ring.  I have SDRuno set to run at high process priority.

My CPU is an i5-7200U @2.50GHz, and I have 12GB RAM

 

All that I can figure is that something is getting swapped in and the piped signal is being delayed by a very small amount that is then throwing off the logic in FLDIGI.

 

Is there a solution like some switch in FLDIGI that would fix the issue, or do I have to consider using a dedicated machine to avoid the problem?  Is there a better virtual cable program that might fix this?

 

Any thoughts or advice would be welcome!

 

Thanks,

Roger

 

Roger Tobin

Roger.tobin@...

N1EYZ

 

WEFAX reception in FLDIGI losing phasing alignment sync often

roger.tobin@...
 

I have an issue that seems common to all the versions of FLDIGI I’ve kept up with over the past couple of years.

 

When I am receiving a WEFAX from a station like NMC (Pt. Reyes CA), the image will lose the alignment whenever there is other activity on my computer.  If I walk away from the system for an extended period of time, the received images tend to be aligned, even if they are a bit noisy.

 

If the signal is strong (rarely), this can still happen, but perhaps not as often (I don’t have any definite proof of this).

 

I’m using VB-Audio Virtual Cable to pipe the sound from SDRuno, which is being fed by my RSP1-A.  I’m on a Windows machine running the latest builds of W10 from the fast ring.  I have SDRuno set to run at high process priority.

My CPU is an i5-7200U @2.50GHz, and I have 12GB RAM

 

All that I can figure is that something is getting swapped in and the piped signal is being delayed by a very small amount that is then throwing off the logic in FLDIGI.

 

Is there a solution like some switch in FLDIGI that would fix the issue, or do I have to consider using a dedicated machine to avoid the problem?  Is there a better virtual cable program that might fix this?

 

Any thoughts or advice would be welcome!

 

Thanks,

Roger

 

Roger Tobin

Roger.tobin@...

N1EYZ

 

Re: fldigi 4.1.10

Dave
 

All MFSK pic modes remain in TX at the conclusion of the pic transmission.  Use a macro to send an image if you want to conclude with a return to RX

Both flmsg and flamp transmission include the callsign as a part of the transmission.  FCC requirement for identification is satisfied by the embedded data, so a CWID is only needed if you like to hear the ID.

Development test releases (alpha) are nearly always posted at http://www.w1hkj.com/alpha/fldigi/, unless for a private test to assist a user debug a specific issue.  Would you like to be added to the list of fldigi testers?

Dave

On 4/3/20 3:11 AM, Dave, KI7VLV wrote:

Good day again!

(1) Again, this is a low priority. Just built .11.02. CW ID button is definitely there, as you know. Though it will not trigger/sound the CW callsign when using flmsg, nor flamp.

(2) When using MFSK 128 for pictures, the mode continues to sound after image is complete. One has to manually click T/R to unkey. I can't recall if this is a known issue. (2a) In this mode, manually clicking T/R to unkey also does NOT trigger CW ID as it DID so in .08. (3) My group and I were looking for a pipeline of alpha fixes. Is this or your sourceforge page the best place to look for what's on deck in subsequent alpha builds?

Thank you again, Dave KI7VLV

Re: fldigi 4.1.10

Dave, KI7VLV
 

Good day again!

(1) Again, this is a low priority. Just built .11.02. CW ID button is definitely there, as you know. Though it will not trigger/sound the CW callsign when using flmsg, nor flamp.

(2) When using MFSK 128 for pictures, the mode continues to sound after image is complete. One has to manually click T/R to unkey. I can't recall if this is a known issue. (2a) In this mode, manually clicking T/R to unkey also does NOT trigger CW ID as it DID so in .08. (3) My group and I were looking for a pipeline of alpha fixes. Is this or your sourceforge page the best place to look for what's on deck in subsequent alpha builds?

Thank you again, Dave KI7VLV

flamp closes when using the file ... audio capture RX save dialog

we1u.david@...
 

When I try to save "Capture RX" audio file in fldigi; flamp opens a dialog box with the message "fldigi off line" and a "close" button.

I started to notice this with fldigi-4.1.01 and flamp 2.2.0x something

running fldigi from terminal show the following error
 

(fldigi:16184): Gtk-WARNING **: 17:17:03.821: Unable to locate theme engine in module_path: "adwaita",
 
(fldigi:16184): GLib-GIO-CRITICAL **: 17:17:03.946: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
I: [17:17:27] misc/arq_io.cxx : 697 : test_arq_clients
    socket 58 timed out, error 32, send: Broken pipe
I: [17:17:27] network/socket.cxx : 688 : close
 

Re: fldigi 4.1.10

Dave
 

XYL won't let me out carousing ;-).

Dave

On 4/1/20 9:01 PM, K4IVE wrote:
You and the team have been quite the busy beavers lately!
 
Thanks Dave,
 
Kevin
K4IVE
 
 
Sent: Wednesday, April 01, 2020 at 8:46 PM
From: "Dave" <w1hkj@...>
To: nbems@groups.io
Subject: Re: [nbems] fldigi 4.1.10

The alpha source has it fixed.

On 4/1/20 8:26 PM, Dave, KI7VLV wrote:

Heh. Roger that. I was gonna state that it wasn't worth the cycles exerted. I like the feature in case my toddlers pull me away from station during our weekly practice drills. My peers know my message is sent and I legally signed off. :-) I'll find the code file and fiddle with it soon.
Thanks again! Dave KI7VLV

Re: fldigi 4.1.10

K4IVE
 

You and the team have been quite the busy beavers lately!
 
Thanks Dave,
 
Kevin
K4IVE

 
 
Sent: Wednesday, April 01, 2020 at 8:46 PM
From: "Dave" <w1hkj@...>
To: nbems@groups.io
Subject: Re: [nbems] fldigi 4.1.10

The alpha source has it fixed.

On 4/1/20 8:26 PM, Dave, KI7VLV wrote:

Heh. Roger that. I was gonna state that it wasn't worth the cycles exerted. I like the feature in case my toddlers pull me away from station during our weekly practice drills. My peers know my message is sent and I legally signed off. :-) I'll find the code file and fiddle with it soon.
Thanks again! Dave KI7VLV

Re: fldigi 4.1.10

Dave
 

The alpha source has it fixed.

On 4/1/20 8:26 PM, Dave, KI7VLV wrote:

Heh. Roger that. I was gonna state that it wasn't worth the cycles exerted. I like the feature in case my toddlers pull me away from station during our weekly practice drills. My peers know my message is sent and I legally signed off. :-) I'll find the code file and fiddle with it soon.
Thanks again! Dave KI7VLV

Re: fldigi 4.1.10

Dave, KI7VLV
 

Heh. Roger that. I was gonna state that it wasn't worth the cycles exerted. I like the feature in case my toddlers pull me away from station during our weekly practice drills. My peers know my message is sent and I legally signed off. :-) I'll find the code file and fiddle with it soon.
Thanks again! Dave KI7VLV

Re: fldigi 4.1.10

Dave
 

Build this version: http://www.w1hkj.com/alpha/fldigi/

You might be the one in ten thousand looking for that button :-X.

Dave

On 4/1/20 7:19 PM, Dave, KI7VLV wrote:

Thank you again.

The "hidden" cw id button persists. Heh.

I performed a make install so it would use all my config. And a "fresh" from scratch as well. Just in case. I may not know what I'm doing. :-)

Pls see attached.

73, Dave KI7VLV

Re: fldigi 4.1.10

Dave, KI7VLV
 

Thank you again.

The "hidden" cw id button persists. Heh.

I performed a make install so it would use all my config. And a "fresh" from scratch as well. Just in case. I may not know what I'm doing. :-)

Pls see attached.

73, Dave KI7VLV

fldigi 4.1.11 posted

Dave
 

At http://www.w1hkj.com/files/fldigi/

and at Source Forge.

Please remove 4.1.10 from your system and install 4.1.11.  Sorry for the inconvenience.  This was definitely a programmer error :'(.

73, David, W1HKJ


Wed Apr 1 2020 - Version 4.1.11

  *** Bug fix release ***

  cwio_morse
    * segmentation fault fix
      - change cwio_morse to *cwio_morse

  AWOL CW id button
    * Fixed "hidden" state of CW ID button

  MacOS
    * update build.m4 for Xcode 11

  Macros
   * Restore execution code for <TUNE
   * Retain delayed execution code for <!TUNE
   * Create new macro <@TUNE
   * All three versions allow tune interval to be spec'd
     in fractional seconds, i.e. 2.5, 5.1 10.0 15
   * <TUNE:nn.nn> used alone returns to receive
   * <TUNE:nn.nn> followed by text remains in transmit
     to complete the transmission.
   * Examples:
     . <TUNE:10.0>
     . <TUNE:5>
       <TX>tune test <!TUNE:1.5> de w1hkj k
       <RX>
       <@TUNE:2.5>
   * Remove text size restriction on CPS test report.

  RigCat config
    * restore missing control labels

  CW 5 wpm
    * 5 wpm farnsworth speed demands larger OUTBUFSIZE
      - increase output buffer to 65536

  audio alert
    * fix seg fault
      - test for existence of audio_alert instance

  analysis mode
    * changes to data file output - submitted by John Gibbons, N8OBJ

  flrig auto off
    * add ability to shutdown flrig/xcvr during fldigi shutdown

  maclogger
    * correct interpretation of UDP frequency string
    * update transceiver frequency based on UDP frequency

  mkappbundle
    * modify 'version' to include patch level

  nanoIO
    * Correct TTY interface code

  start/stop transitions
    * add code to soften the start/stop transitions for all modems

  CW DTR-RTS
    * generate CW on selected DTR/RTS signal line
    * CW DTR/RTS signals generated concurrent with AF counterparts and
      within a separate thread.

  Olivia 2 tones
    * correct trailing edge cutoff of postamble tones

  Xmlrpc Xcvr
    * enable QSY when Xmlrpc client xcvr is connected

  mp3
    * simplify mp3 conversions
      - test for file access using fopen
      - use linear sample rate converter

  contestia cr
    * correct suppression of <CR> display

  serial port
    * insure that DTR and RTS are always disabled when closing port

  Check Version
    * correct version check logic

fldigi 4.1.10

Dave
 

Depending on your OS and your processor you may experience a start up crash on 4.1.10.  I have identified the cause and am preparing version 4.1.11 for distribution.  It should be posted in less than 2 hours.  Thanks for your patience.

 73, David, W1HKJ


fldigi 4.1.01 i386 dmg for OS-X

Dave
 

Will not run due to a segmentation fault:11.  I am investigating.  In the meantime I've removed the i366 dmg from the download sites.  The x86_64 dmg is OK.

David