Date   

locked Re: No sound after database update

HamApps Support (VK3AMA)
 

On 11/06/2021 12:38 pm, Charlie Hoffman wrote:
I can only guess that because I have the audio alerts turned off, I have not experienced any issues with the latest MS updates or with JTALERT.

The cause is an incompatibility between the package used to generate sounds and the new 5.0.7 NET runtime.
See https://hamapps.groups.io/g/Support/message/35526

de Laurie VK3AMA


locked Re: No sound after database update

AB8WD-Willie
 

To my knowledge at this time it only affects sound if it is off nothing to worry about.


locked Re: No sound after database update

Charlie Hoffman
 

I never had the issue because I do not use audio  alerts and have them turned off.
Everything is working fine and I have not had any closurers of the callsign window.
I'm on the air all day and make between 80 - 125 digital contacts per day without having any problems.

I can only guess that because I have the audio alerts turned off, I have not experienced any issues with the latest MS updates or with JTALERT.

If I turn on the SOUND alerts then I get the crackling noises and other problems.
I turned them back off, stopped JTA then restarted it and it's back to working normally.


locked Re: WSJT-X and JTAlert Interoperation

HamApps Support (VK3AMA)
 

On 11/06/2021 5:46 am, Joe Subich, W4TV wrote:
Sounds like you *failed to enable multicast UDP* in WSJTX.

See Help -> WSJTX UDP Setup in JT-Alert.

73,

   ... Joe, W4TV

Does DXLab support multicast UDP? I was under the impression that it did not.

de Laurie VK3AMA


locked Re: Announcement : NET 5.0.7 breaking JTAlert

Laurie, VK3AMA
 

On 11/06/2021 8:52 am, John P wrote:
Is this going to cause problems for Windows-7 users?

--
John P.
WA2FZW
NO.

de Laurie VK3AMA


locked Re: Announcement : NET 5.0.7 breaking JTAlert

John P
 

Is this going to cause problems for Windows-7 users?

--
John P.
WA2FZW


locked #Announcement : NET 5.0.7 breaking JTAlert - A progress report. #Announcement

HamApps Support (VK3AMA)
 

The source of the error causing sound to not work and the different 2.50.x windows, like the Callsigns window, to unexpectedly close and reopen has been identified.
  • The problem is within the NAudio package that JTAlert uses for audio output device selection and playback.

  • It only occurs with the most recent NET desktop runtime 5.0.7 that was forced upon us by recent Windows updates.

  • Downgrading the NET runtime to 5.0.6 resolves the issue.

  • Any application using NAudio will experience an access violation error when run against the 5.0.7 runtime. This is not limited to JTAlert.

The primary reason for using NAudio is that it allows selection of the sound output device. The inbuilt sound functions of C# WPF, in which JTAlert is coded, do not support sound device selection, all sounds are played on whichever device is set within Windows as the default.

At this time, I am coding a change to sound playback that does not use NAudio and will instead uses the default sound routines of C# WPF. This will mean the loss of sound device selection unfortunately. If or when NAudio is fixed or Microsoft reverse the 5.0.7 breaking change, I don't care which, I will return sound output device selection to JTAlert.

A new JTAlert release was due this week but I paused that release due to the current 5.0.7 situation. The new release will also have the sound playback fix. Hopefully in 2 or 3 days time as there are some significant enhancements coming to the Callsigns window and I need to finalize documentation for those first.

de Laurie VK3AMA


locked Re: No sound after database update

HamApps Support (VK3AMA)
 

On 11/06/2021 8:09 am, WU9D wrote:
Please be aware that I had to uninstall 5.0.7 and reinstall 5.0.5 (I don't have an install package for 5.0.6).

5.0.6 links were provided in the message titled "#Important #Announcement : Todays Windows update and broken JTAlert audio - THE FIX

de Laurie VK3AMA


locked Re: No sound after database update

WU9D <mike@...>
 

Please be aware that I had to uninstall 5.0.7 and reinstall 5.0.5 (I don't have an install package for 5.0.6).

Everything is humming along nicely now. The reinstall of JTAlert, although unnecessary, cleared out a lot of mistakes I made.


locked Re: No sound after database update

WU9D <mike@...>
 

Yes, there were some rather annoying updates this morning. I forgot to consider them, Laurie. I'll try to roll back.

Mike WU9D


locked Re: JTAlert 2.50.1 NO SOUND

Craig
 

Saw Postings on .NET 5.0.6  Rolled install back.  Thanks, C


locked JTAlert 2.50.1 NO SOUND

Craig
 

1 - No sound from any alerts, when live or testing
2 - Test Sound Card does not work, Testing speaker from Windows 10 Setting works fine....
3 - JTAlert program banner shows JTAlert 2.50.1 with (Updates) - cannot locate any updates required.

Need some guidance...

C


locked Re: No sound after database update

Laurie, VK3AMA
 



On 11/06/2021 6:52 am, WU9D wrote:

Sounds ceased or make crackling noises and the callsigns window opens and closes after database 2021.06.08 update.

 

I tried uninstalling, deleting remaining files, and registry purge but the result is the same, malfunctioning sound. All other Windows sounds performing normally, just JT Alert sounds are trashed.

 

Mike WU9D


The Database update is not the cause. It is the recent Windows update installing the NET 5.0.7 runtime is the cause. In your case that happened around the same time as your database update.

Rolling back the NET 5.0.7 runtime to 5..0.6 is the fix until Microsoft forces 5.0.7 again. See the recent forum messages, it has been discussed at length.

de Laurie VK3AMA


locked Re: WSJT-X and JTAlert Interoperation

John Snell
 

Multicast to 239.255.0.0 and/or localhost 127.0.0.1 no difference fir this problem.

Read the DXLabs note carefully. Spotcollector WSJTx on = JTAlert off.

Has nothing to do with the WSJTx or JTAlert config directly.

John Snell
http://SnellsNotebook.us

On Jun 10, 2021, at 1:46 PM, Joe Subich, W4TV <lists@subich.com> wrote:



No, this time the problem was that I was expecting too much interoperation and had blithely checked Spot Collector's WSJTX enable
box, blocking JTAlert.
Sounds like you *failed to enable multicast UDP* in WSJTX.

See Help -> WSJTX UDP Setup in JT-Alert.

73,

... Joe, W4TV


On 2021-06-10 3:07 PM, John Snell wrote:
Moving to a brand new WIN10 computer, I got DXLabs, WSJTx working, but kept having a problem getting JTAlert to communicate with WSJTx. Back and forth between two notebooks that previously had run without problem looking at config's all the way from WIN10 installed services to the check boxes in each app.
Finally found the piece of information I needed (which was NOT that I may have started the apps with differing privileges! => used Task Manager to add "Elevated" column and checked). No, this time the problem was that I was expecting too much interoperation and had blithely checked Spot Collector's WSJTX enable box, blocking JTAlert.
Here is the applicable note from DXLab's Getting Started page:
https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesDirect
Limitations
JT-Alert and SpotCollector cannot be simultaneously connected to the same instance of WSJT-X via the same UDP address and port; if you wish to use JT-Alert,
uncheck the Enable box in the WSJT-X panel on SpotCollector's Configuration window's Spot Sources tab
start JT-Alert.
SpotCollector will accept connections from up to 16 instances of WSJT-X
WSJT-X logs a single frequency for each QSO; it does not record both TX and RX frequencies.
The contest exchange information logged by WSJT-X is not yet documented; DXKeeper is unlikely to generate correct Cabrillo from QSOs logged by WSJT-X.
With SpotCollector connected to WSJT-X,
double-clicking a Spot Database Entry whose Mode field specifies FT8, JT65, JT65A, JT65B, JT65B2, JT65C, or JT65C will not change the mode in WSJT-X, or set the DX Callsign in WSJT-X.
double-clicking a Spot Database Entry for which no sub-band <https://www.dxlabsuite.com/dxlabwiki/SubbandDefinitions> is defined for the Entry's Mode within the Entry's band will result in no change of transceiver frequency or mode.
Hope this info finds the people who may need it in the future.
John Snell
jsnell6746@gmail.com
http://SnellsNotebook.us






locked No sound after database update

WU9D <mike@...>
 

Sounds ceased or make crackling noises and the callsigns window opens and closes after database 2021.06.08 update.

 

I tried uninstalling, deleting remaining files, and registry purge but the result is the same, malfunctioning sound. All other Windows sounds performing normally, just JT Alert sounds are trashed.

 

Mike WU9D


locked Re: Sound dead after latest Win 10 update today

Paul
 

Thanks, I was taking it literally, looking for PC along with Settings. Like I say, with these modern computers, I need to be led by the had with specifics. My experience with computers was back in the IBM 1403/sys360 days and imbedded military and NASA stuff programming in Ada. I retired from computers over 20 years ago and haven't kept up to speed.  

73, Paul


On Thursday, June 10, 2021, 03:38:07 PM EDT, Joe Subich, W4TV <lists@...> wrote:



> For those of us who are just users, where do I find this "PC Settings"
> to select. I'm sure it is obvious to many, but I can't find it.

Click on the Windows Icon at the left end of the Taskbar.  In the lower
left margin of the window that opens you should find a "gear" icon (2nd
from the bottom, just above the "power" icon).  Click that - it is PC
Settings (in fact if you hover the mouse over the "gear" it will expand
and say "Settings").

73,

    ... Joe, W4TV


On 2021-06-10 3:11 PM, Paul wrote:
>  In Windows 10 ... Select PC Settings -> Apps ... scroll down the
> list of installed applications until you find "Microsoft Windows
> Desktop Runtime - 5.0.7"
> For those of us who are just users, where do I find this "PC Settings" to select. I'm sure it is obvious to many, but I can't find it.

>







locked Re: WSJT-X and JTAlert Interoperation

Joe Subich, W4TV
 

No, this time the problem was that I was expecting too much interoperation and had blithely checked Spot Collector's WSJTX enable
box, blocking JTAlert.
Sounds like you *failed to enable multicast UDP* in WSJTX.

See Help -> WSJTX UDP Setup in JT-Alert.

73,

... Joe, W4TV


On 2021-06-10 3:07 PM, John Snell wrote:
Moving to a brand new WIN10 computer, I got DXLabs, WSJTx working, but kept having a problem getting JTAlert to communicate with WSJTx. Back and forth between two notebooks that previously had run without problem looking at config's all the way from WIN10 installed services to the check boxes in each app.
Finally found the piece of information I needed (which was NOT that I may have started the apps with differing privileges! => used Task Manager to add "Elevated" column and checked). No, this time the problem was that I was expecting too much interoperation and had blithely checked Spot Collector's WSJTX enable box, blocking JTAlert.
Here is the applicable note from DXLab's Getting Started page:
https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesDirect
Limitations
JT-Alert and SpotCollector cannot be simultaneously connected to the same instance of WSJT-X via the same UDP address and port; if you wish to use JT-Alert,
uncheck the Enable box in the WSJT-X panel on SpotCollector's Configuration window's Spot Sources tab
start JT-Alert.
SpotCollector will accept connections from up to 16 instances of WSJT-X
WSJT-X logs a single frequency for each QSO; it does not record both TX and RX frequencies.
The contest exchange information logged by WSJT-X is not yet documented; DXKeeper is unlikely to generate correct Cabrillo from QSOs logged by WSJT-X.
With SpotCollector connected to WSJT-X,
double-clicking a Spot Database Entry whose Mode field specifies FT8, JT65, JT65A, JT65B, JT65B2, JT65C, or JT65C will not change the mode in WSJT-X, or set the DX Callsign in WSJT-X.
double-clicking a Spot Database Entry for which no sub-band <https://www.dxlabsuite.com/dxlabwiki/SubbandDefinitions> is defined for the Entry's Mode within the Entry's band will result in no change of transceiver frequency or mode.
Hope this info finds the people who may need it in the future.
John Snell
jsnell6746@gmail.com
http://SnellsNotebook.us


locked Re: what appears in Windows Update today ?

Joe Subich, W4TV
 

No need to multi step by adding 7 days at a time, it will allow you to
hold updates in excess of a month.
True, but adding a week at a time is available from the primary
"Updates and Security" screen and does not require digging around
in the menu structure. The 35 day maximum deferral on the "Advanced
Options" screen is the same as five weeks (7 days at a time).

73,

... Joe, W4TV


On 2021-06-10 3:09 PM, Dave (NK7Z) wrote:
Hi Joe,
We appear to be talking about two different paths for holding updates...
The one I suggested does not force you to do the 7 more days thing... Here is a step by step:
0.  Left click the windows icon in the task bar.
1.  Open the settings dialog, by selecting the gear.
2.  Left click "Updates and Security"
3.  Left click "Advanced Options"
4.  There is a data above the word "Delivery Options", click the arrow.
5.  Select a date.  I selected July 15th.
No need to multi step by adding 7 days at a time, it will allow you to hold updates in excess of a month.
73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist, RFI
ARRL Asst. Director, NW Division, Technical Resources
On 6/10/21 7:42 AM, Joe Subich, W4TV wrote:


I go to my control panel and get into Windows Update Advanced
settings, and kill updates for a month or more.
For those using the Windows 10 menus/interface, it is "PC Settings ->
Update & Security" or "PC Settings -> Windows Update"

I think I just set it to not check until sometime in late July.  A
LOT longer than the 7 day thing...
Once one has "paused updates for 7 days", the option appears:
"pause updates for 7 *more* days".  By clicking that multiple
times one can delay updates for several weeks.

Unfortunately, I had to pause updates (did not want to do so since
that also appears to pause AV updates) as .NET 5.0.7 was forced on
my systems *again* this morning.

73,

    ... Joe, W4TV


On 2021-06-10 10:25 AM, Dave (NK7Z) wrote:
I go to my control panel and get into Windows Update Advanced settings, and kill updates for a month or more.  I think I just set it to not check until sometime in late July.  A LOT longer than the 7 day thing...

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist, RFI
ARRL Asst. Director, NW Division, Technical Resources

On 6/10/21 6:38 AM, Jim N6VH wrote:

On 6/10/2021 6:30 AM, Dwight Bosselman wrote:

After going back to 5.06 yesterday, this is what appears in Windows Update today. Persistent suckas they are!

73 Dwight NS9I
Dwight,

In case you haven't seen it, read my reply to Roger, AC6BW. That might be helpful. It is here:

https://hamapps.groups.io/g/Support/message/35486

73,

Jim N6VH


locked Re: what appears in Windows Update today ?

robert dorbecker
 

I installed 6.0 preview with no problems.
Bob N5DWW


locked Re: Sound dead after latest Win 10 update today

Joe Subich, W4TV
 

For those of us who are just users, where do I find this "PC Settings"
to select. I'm sure it is obvious to many, but I can't find it.
Click on the Windows Icon at the left end of the Taskbar. In the lower
left margin of the window that opens you should find a "gear" icon (2nd
from the bottom, just above the "power" icon). Click that - it is PC
Settings (in fact if you hover the mouse over the "gear" it will expand
and say "Settings").

73,

... Joe, W4TV


On 2021-06-10 3:11 PM, Paul wrote:
In Windows 10 ... Select PC Settings -> Apps ... scroll down the
list of installed applications until you find "Microsoft Windows
Desktop Runtime - 5.0.7"
For those of us who are just users, where do I find this "PC Settings" to select. I'm sure it is obvious to many, but I can't find it.

1621 - 1640 of 36897