That begs the question: why doesn’t WSJT-X store its temporary WAV files in RAM instead of on disk? I appreciate some systems are RAM-constrained so I guess it might need to be a config option.
73 Gary ZL2iFB From: Bill Barrett <[email protected]> Sent: 12 February 2019 11:43 To: Black Michael <[email protected]>; WSJT software development <[email protected]> Subject: Re: [wsjt-devel] Audio dropout patch Hi Mike- I am running win7 Pro and W.D. is off. The Production Version does not save any files. I run a small RAM Disk for the wav file directory since running 8 instances to take load off the disk. Thanks anyway for the suggestions. 73; Bill W2PKY On Mon, Feb 11, 2019 at 5:19 PM Black Michael via wsjt-devel <[email protected] <mailto:[email protected]> > wrote: Windows 10 has Defender by default. You need to exclude the WSJT-X directory where the supports files and save directory are located. Mike On Monday, February 11, 2019, 4:16:36 PM CST, Bill Barrett <[email protected] <mailto:[email protected]> > wrote: Hi Mike- I do not run any Virus scans. I didn't see any catchup messages beyond the start of the program. Thanks for the debugging version. Bill W2PKY On Mon, Feb 11, 2019 at 4:46 PM Black Michael via wsjt-devel <[email protected] <mailto:[email protected]> > wrote: That patch has (i.e. should have) no effect on wav files being saved at all. I would suspect something else is wrong is you have wav files being saved an None is checked. Have you excluded your WSJT-X directory from your virus scanner? de Mike W9MDB On Monday, February 11, 2019, 3:42:46 PM CST, Bill Barrett <[email protected] <mailto:[email protected]> > wrote: Hi Mike- Tried your patch version, seems to be saving many wave files even though the save none option is checked. Bill W2PKY On Mon, Feb 11, 2019 at 12:01 PM Black Michael via wsjt-devel <[email protected] <mailto:[email protected]> > wrote: This patch shows audio catchups and dropouts and is otherwise quiet so I do believe this is worthwhile to add to WSJT-X and the documentation...most everybody should see several "catchup" messages when WSJT-X starts as the audio buffer is drained. After that those with stable audio will see no more messages. Those who have audio problems may see more "catchup" messages which are harmless or "dropout" messages which indicates a problem that needs fixing. <https://www.dropbox.com/s/ji82h5ldfir5g8f/wsjtx-2.0.0-win32-test33.exe?dl=1> https://www.dropbox.com/s/ji82h5ldfir5g8f/wsjtx-2.0.0-win32-test33.exe?dl=1 We've found several solutions which I'm documenting now and that I'll make available soon. de Mike W9MDB _______________________________________________ wsjt-devel mailing list [email protected] <mailto:[email protected]> https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list [email protected] <mailto:[email protected]> https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list [email protected] <mailto:[email protected]> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
