Ok, I'll check it out.

Downloading now, then will install right over the top of my existing 2.01
Tnx
73, N0AN

Hasan


On Fri, Jul 5, 2019 at 7:46 AM Black Michael <mdblac...@yahoo.com> wrote:

> This is version 2.0.1 with dropout debugging.
> If the decode light is not flashing then it sounds like you may have audio
> dropouts occurring.
> This version will show you when it fails with messages in the band
> activity window about "dropout".  You'll see a few messages on startup
> which is normal as the audio catches up.
>
>
> https://www.dropbox.com/s/isxwjybws1i8u6f/wsjtx-2.0.1-win32-dropouts.exe?dl=1
>
> de Mike W9MDB
>
>
> On Friday, July 5, 2019, 04:45:38 AM CDT, Hasan al-Basri <
> hbasri.schie...@gmail.com> wrote:
>
>
> Ok Mike, it decoded for > 24 hours but then stopped early this morning
> just before I got to the shack.
>
> Started 07/03/2019 @ 1723
> Stopped 07/05/2019 @ 0407 Both local
>
> These are the file saved dates. Again, I had to reboot a few minutes ago
> to get it to start saving files/decoding again.
>
> The rig was unattended from about 6 p.m. last  night until 4:19 a.m. when
> I came down to see if it was still decoding...I noticed it had stopped
> decoding 12 minutes b4 I got down here.
>
> Another symptom: When it stops decoding incoming signals, the Blue Decode
> light does NOT flash at the end of a sequence, ...even though the
> thermometer and the waterfall show sigs for the full sequence.
>
> Any other suggestions?
> 73, N0AN
> Hasan
>
>
> On Thu, Jul 4, 2019 at 5:35 AM Hasan al-Basri <hbasri.schie...@gmail.com>
> wrote:
>
> Ok, I'll check it out. Time is perfect and always is, I'm GPS locked to it.
>
> When I got down here this morning it was still decoding full fill of
> JTAlert. ...but it's only been 12 hours. (I did the remove driver, unplug
> it and let Win10 reinstall it at a reboot) . That's where I am now in my
> test.)
>
> Save none was checked, I just checked Save All, will provide if needed.
>
> Here's hoping...
>
> 73, N0AN
> Hasan
>
>
> On Wed, Jul 3, 2019 at 10:37 PM Black Michael <mdblac...@yahoo.com> wrote:
>
> We seem to be hearing problems with a few people on both 2.0.1 and
> 2.1.0-rc7.
> 2.0.1 has been out for a long time and if this was common I'd think we
> would have heard a lot more reports of the problem.
> Upgrading to 2.1.0-rc7 and back to 2.0.1 should (and I emphasize should)
> just revert completely back to 2.0.1 thought there is a bug with FT4 in
> that case.
>
> The common thread probably is Windows updates....or time is off.  Check
> http://time.is to ensure you're time is reported as "Exact".
>
> If you see waterfall activity but no decodes on of three things is likely
> happening.
>
> #1 Time is off
> #2 WAV files are not being recorded.  Ensure Save/All is checked and see
> if WAV files are showing up in the Save folder.  One user found using
> Remote Desktop that audio files weren't being saved.  TeamViewer worked
> though.
> #3 Audio corrupted.  If WAV files are showing up but not decoding and your
> time is correct then send in a few audio files so we can look at them.
>
> de Mike W9MDB
>
>
>
>
> On Wednesday, July 3, 2019, 10:27:56 PM CDT, Tod Farrell WE5TR <
> we5t...@gmail.com> wrote:
>
>
> Similar issue here on 2.0.1, win10, and flex6700 after a long operating
> session or even a long monitoring session. I.e. I’ll leave the shack
> powered up monitoring a band while I’m at work or elsewhere in the house.
>
> When I come back sometimes the waterfall is showing activity, dT is good,
> time.is is good, but no decodes.
> Other times it’s that clicking transit or tune causes no generated audio
> to the DAX  software which has a meter that shows me no incoming audio is
> present from WSJT-X.
>
> Typically corrected with a WSJT-X restart
>
> --
> 73
>
> Tod    WE5TR
> While mobile
>
> On Jul 3, 2019, at 16:52, Hasan al-Basri <hbasri.schie...@gmail.com>
> wrote:
>
> Hi Mike,
> No transmitting at all. RF Chokes all over the place. No issues running KW
> out on any band 6m through 80m. (if I have just rebooted the computer).
> Once it has run for several hours. it will stop decoding, whether I have
> transmitted or not, no matter qrp or qro. I monitor 24x7 , go days without
> tx'ing...it still goes deaf.
>
> IOW, it's not a USB RFI problem.
>
> All power settings for USB have been set to never sleep.
>
> I"m baffled, like I said, it acts like a memory leak and I don't think
> it's a coincidence that it showed up the very first time after installing
> and running RC7 64 bit.
>
> The problem NEVER showed up b4 RC7 64 bit was installed. I didn't change a
> thing in my setup or operating habits. Now I have to reboot every day or it
> just stops decoding, even having uninstalled RC7 64 bit and returned to
> 2.01 Gen Release.
>
> Audio level is perfect, waterfall shows signals...no decode.
> Reboot...decodes resume. No other program shows any symptoms like this at
> all on the same computer. WSJT-X is running on its own USB Sound Dongle for
> both RX and TX....and has been for over a year.
>
> Any further ideas are most welcome (TS-590sg, running from headphone jack
> for rx audio) Audio sounds perfect to the ear. Levels are right...
> Most peculiar!
>
> 73, N0AN
> Hasan
>
>
> On Wed, Jul 3, 2019 at 4:39 PM Black Michael via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
> Failing audio or rig connections are most always due to RFI or USB ports
> going to sleep.
> If RFI low power transmissions can be tested and if they work but high
> power does not then it's RFI.
> The USB ports going to sleep can be solved.
> https://www.windowscentral.com/how-prevent-windows-10-turning-usb-devices
>
> de Mike W9MDB
>
>
>
>
> On Wednesday, July 3, 2019, 04:31:39 PM CDT, rjai...@gmail.com <
> rjai...@gmail.com> wrote:
>
>
> I’ve seen this with other radios. Definitely not a flex only issue.
>
> Ria
> N2RJ
>
> On Wed, Jul 3, 2019 at 4:58 PM DX Jami via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
> Peter,
>
> Flex has its own set of unique problems and fixes.  Suggest you post your
> question on the Flex forum page.  Good luck.
>
>     Danny
>     AH6FX/W4
>
> On Wednesday, July 3, 2019, 3:11:48 PM EDT, Peter Putnam <pe...@ni6e.com>
> wrote:
>
>
> Greetings,
>
> I have been using WSJT-X quite successfully for several years during
> June VHF Contests. I experienced a failure of the WSJT program to accept
> received audio input after several hours of proper operation during the
> recent Field Day exercise.
>
> I'll provide a brief outline and reply with more detail, should it be
> needed.
>
> My computer is a Dell Optiplex 780 running Win 7 Pro SP1, 64-bit. The
> WSJT-X software version is 2.0.1 7ddcb7.
>
> My receiver is a Flex 6500. It passes data to a Flex-supplied "DAX"
> program that interfaces various applications that wish to receive the
> audio stream. WSJT accepts the stream and displays results on the Wide
> Graph and a small audio signal-strength window. Activity proceeded
> normally for the first three hours of Field Day, until both the Wide
> Graph and the audio signal-strength stopped showing any incoming audio.
>
> I can't offer any help on what might have caused the problem. It was
> abrupt and seemingly unrelated to any other system actions. I am unable
> to reproduce the problem.
>
> Several operators spent several hours speculating about what a solution
> might be. Program restarts and computer re-boots (time-tested favorite
> of generations) changed nothing. The only useful clue was that the DAX
> audio output stream was present and could be re-directed to Fldigi, but
> not to WSJT-X.
>
> I was able to restore operation for a brief period by stopping WSJT,
> renaming WSJT.ini and restarting WSJT. That fix lasted for a half hour.
> Repeating the procedure provided operation for the rest of Field Day.
>
> The two .ini files that were renamed are available for your inspection,
> along with the one that continued to function.
>
> Any suggestions you can offer to prevent a recurrence would be greatly
> appreciated.
>
> Regards,
> Peter
> NI6E
>
>
>
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> _______________________________________________
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
> _______________________________________________
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> _______________________________________________
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to