Date   

locked Re: How to reduce volume of "ding" sound when a QSO is saved?

HamApps Support (VK3AMA)
 

On 11/11/2019 3:43 am, Uwe wrote:
Is there any way to control / reduce volume of the "ding" sound played when a QSO is logged?. My system is Win 10 64 bit. Tried already to reduce JTAlert's volume slider at Windows' volume sound mixer, but that seems to have an impact only on volume of all other JTAlert sounds (but not on the "ding" sound). And within JTAlert program I didn't find any volume control for that. Would also be enough if I there is a way to disable the "ding" entirely.

73 de Uwe, DG2YCB
That sound is controlled by Windows itself and cannot be adjusted within JTAlert. It is the default "Asterisk" sound set within your Windows Sound theme. The volume for this sound and all Windows sounds is controlled by the "Master Volume" you have set for Windows. This is not new and has been present within JTAlert for many years and only applies to information popup notices like the logging confirmation.

de Laurie VK3AMA


locked Re: How to give B4 highest Alert priority?

HamApps Support (VK3AMA)
 

On 11/11/2019 4:42 am, Uwe wrote:
Today I started JTAlert with logging into Standard ADIF File enabled. (That adif file contains all my QSOs including information about DXCC, CQ zone, ITU zone, State, and QSL.) Works well so far.

But: Now B4 is no longer highest alert priority. Means when I am getting an alarm about "New Zone", work a station within that zone, QSO is logged and the station is calling CQ again, I am now getting again the alert "New Zone". Before I enabled logging into an adif file, in such a case the callsign came as B4 and no alert was played again for the same station on the same band.

How can I get this behaviour back while adif logging enabled?

I understand that as long the zone is not yet confirmed another callsign within this zone will be alerted. But the same callsign at the same band? Makes no sense for me. Generated dupes..

73 de Uwe, DG2YCB
There is no priority adjustment available for the B4 because it is not a true alert, but an indicator.

If you not getting the B4 shown for all newly logged Callsigns, the likely cause is you have the "Play alert when decoded callsign worked B4" option checked for the Alert that is being generated.

de Laurie VK3AMA



locked Re: Ver 2.15 Fatal Error on startup

HamApps Support (VK3AMA)
 

On 10/11/2019 11:11 pm, Mario Pedreschi GM3MZX via Groups.Io wrote:
Hi,
Been using JTAlert for years without any problems but after installing V 2.15.0 I get an error warning on startup as follows.

FATAL ERROR
There has been an error opening the SQLite database : DXCC
Function:_dxcc-init()
Program will now exit.

Uninstalled V2.15.0 and reinstalled V2.14.5 and all works fine again, would appreciate some help.

73 De Mario  GM3MZX

Mario,

That error is thrown by JTAlert when it is unable to open the cty.dat.sqlite file.
The file is located at C:\ProgramData\HamApps\Databases\cty.dat.sqlite

I suspect that whatever the cause of the error, it was resolved by the reinstall of JTAlert. You should be good to load the latest version, give it a try and let me know if the problem persists.

de Laurie VK3AMA


locked New JTAlert 2.15.2 is available - Audio delay Fix. #Announcement #NewRelease

HamApps Support (VK3AMA)
 

The Latest JTAlert version 2.15.2 is now available @ https://hamapps.com/JTAlert/

The Release Notes...
2.15.2 (10-NOV-2019)

  Fixes:

    - Some users experiencing delays in alert sounds playing (5, 10, 30 seconds).
       The delays were common among Flex/DAX users. The cause is unknown and was
       resolved by changing the sound library used (first introduced in 2.15.1)

de Laurie VK3AMA


locked Re: New JTAlert 2.15.1

Barry <boat.anchor@...>
 

SRI TYPO

On Sun, Nov 10, 2019 at 09:52 AM, Barry wrote:
Laurie
I have reverted to 2.14.5 for a couple days and will try 2.15.2 again in the new week.
TVM
Barry

On Sat, Nov 9, 2019 at 05:01 PM, HamApps Support (VK3AMA) wrote:
Perhaps there is a port collision between the new ports used by JTAlert
and what MarineTraffic is using. Is there a configurable port(s) used by
your MarineTraffic app? If there is a port collision I would expect
MarineTraffic support to say so.

de Laurie VK3AMA


locked Re: New JTAlert 2.15.1

Barry <boat.anchor@...>
 

Mike
You will also note in earlier msg that MT updated their SW on the COMAR box recently as well.
TVM
Barry

On Sat, Nov 9, 2019 at 09:06 PM, Michael Black wrote:
It wouldn't matter unless JTAlert was sending data to marinetraffic.com.  Wouldn't matter if they both used the same port...two different IPs can't collide unless it's multicast and  or unicast to the same machine and I doubt either of those situations is happening.
 
I have a marinetraffic receiver too and no such problems.  I think this was just coincidental with JTAlert upgrades since they've been coming fast and furious lately so good chance of coincidental blaming.
 
Without more info from marinetraffic on what was being sent we'll never know what the problem was.
 
Mike
 
 
 
 
On Saturday, November 9, 2019, 07:01:33 PM CST, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
 
 
Perhaps there is a port collision between the new ports used by JTAlert
and what MarineTraffic is using. Is there a configurable port(s) used by
your MarineTraffic app? If there is a port collision I would expect
MarineTraffic support to say so.
 
de Laurie VK3AMA
 
 
 
 


locked Re: New JTAlert 2.15.1

Barry <boat.anchor@...>
 

Laurie
I have reverted to 2.14.5 for a couple days and will try 2.15.12 again in the new week.
TVM
Barry


On Sat, Nov 9, 2019 at 05:01 PM, HamApps Support (VK3AMA) wrote:
Perhaps there is a port collision between the new ports used by JTAlert
and what MarineTraffic is using. Is there a configurable port(s) used by
your MarineTraffic app? If there is a port collision I would expect
MarineTraffic support to say so.

de Laurie VK3AMA


locked How to give B4 highest Alert priority?

Uwe, DG2YCB
 

Hi,

Today I started JTAlert with logging into Standard ADIF File enabled. (That adif file contains all my QSOs including information about DXCC, CQ zone, ITU zone, State, and QSL.) Works well so far.

But: Now B4 is no longer highest alert priority. Means when I am getting an alarm about "New Zone", work a station within that zone, QSO is logged and the station is calling CQ again, I am now getting again the alert "New Zone". Before I enabled logging into an adif file, in such a case the callsign came as B4 and no alert was played again for the same station on the same band.

How can I get this behaviour back while adif logging enabled?

I understand that as long the zone is not yet confirmed another callsign within this zone will be alerted. But the same callsign at the same band? Makes no sense for me. Generated dupes..

73 de Uwe, DG2YCB


locked Re: JtAlert 2.15.1 installed with no virus hassles

Jim AF5FH
 

Same here on a Windows 10 computer running Windows Security virus and threat protection. No virus scan issues with version 2.15.1. Scanned the whole HamApps folder after install. The previous version (2.15.0) had a file JTAlertPlugins.exe that kept getting flagged by Windows Security as Trojan:Win32/Azden.A!cl.
Thanks for the update!
Jim AF5FH


locked Re: JTAlert ver 2.15.1 no sound.

Andy k3wyc
 

On Sun, Nov 10, 2019 at 09:16 AM, <wa0ruf@...> wrote:
Try going to Settings >> Sound Card, remember your regular audio channel, make a selection other than your regular audio channel, save it, go back and re-select your regular sound channel and save it away.
I thought I had done that but I re-installed 2.15.1 to make sure I followed exactly the procedure you suggest.  Surprise - sound card test works without any need to change sound output device.   I have no clue why the second installation worked but the first did not.

JTAlertV2 manager appeared in Volume Mixer but, after I adjusted the level there, JTAlert 2.15.1 became unresponsive and had to be terminated from task manager.  On restart JTAlert sound level used the setting that had caused it to become unresponsive.  A further change to JTAlertV2 Manager in Volume Mixer did not cause JTAlert to become unresponsive and the new level was applied.

So - it seems to be working now but steps to make it work seem unlikely to be repeatable.

Andy, k3wyc


locked How to reduce volume of "ding" sound when a QSO is saved?

Uwe, DG2YCB
 
Edited

Hi Laurie,

Is there any way to control / reduce volume of the "ding" sound played when a QSO is logged?. My system is Win 10 64 bit. Tried already to reduce JTAlert's volume slider at Windows' volume sound mixer, but that seems to have an impact only on volume of all other JTAlert sounds (but not on the "ding" sound). And within JTAlert program I didn't find any volume control for that. Would also be enough if I there is a way to disable the "ding" entirely.

73 de Uwe, DG2YCB

Btw. JTAlert 2.15.1 works perfect on my computer. No sound delay issue.


locked Re: Config file contains corrupt data

@RolandG
 

Yes, but upon reading the HamApps website I needed to download and install Microsoft Net Framework 4.7.2. It now works ok!

Problem solved. My fault!

Roland


locked Re: JTAlert ver 2.15.1 no sound.

wa0ruf@...
 

Try going to Settings >> Sound Card, remember your regular audio channel, make a selection other than your regular audio channel, save it, go back and re-select your regular sound channel and save it away.  Try the Test Play button and wait.  That may fix your problem.  I had the same problem after installing 2.15.1, and this seem to resolved the problem. 

I'm one of the Flex guys with the delayed audio problem, but the above procedure seemed to fix the no audio problem.

Your mileage may vary.  Good luck.

73,
don
wa0ruf


locked Re: Config file contains corrupt data

Michael Black
 

Did you try deleting that file?

de Mike W9MDB




On Sunday, November 10, 2019, 09:52:22 AM CST, rguidry@... <rguidry@...> wrote:


New install.

I did a search and could not find any previous info on this problem. Running Windows 7 64 bit.
Getting error "C:\Users\Roland\AppData\Local\HamApps\JTALERT.dat"

Tried installing 2.15.0 and 2.15.1 after doing uninstall first, same problem. WSJTX starts ok!

Tried running as Administrator.

Roland


locked Config file contains corrupt data

@RolandG
 

New install.

I did a search and could not find any previous info on this problem. Running Windows 7 64 bit.
Getting error "C:\Users\Roland\AppData\Local\HamApps\JTALERT.dat"

Tried installing 2.15.0 and 2.15.1 after doing uninstall first, same problem. WSJTX starts ok!

Tried running as Administrator.

Roland


locked Re: New JTAlert 2.15.1 delay in audio

wa0ruf@...
 

I have the same problem (both test button and program driven) with a ~5 sec delay running Flex 6300 v3.1.8, rx/tx audio over DAX, control over CAT.  Running Win 10 (latest updates), SmartSDR v3.1.8, WSJT-X v2.1.0, JTAlert 2.15.1, WSJT-X DX Aggregator v2.8, I turned on the Win Audio mixer so I could watch audio delays among various processes. 

I turned off the WSJT-X monitor so there would be no station related traffic flowing from WSJT-X.  There appears to be some sort of keep alive message flowing from WSJT-X to the aggregator.

I opened iTunes to introduce another sound source and noted no noticeable delay between pushing the play / pause button and the presence / absence of audio on the mixer or to the speakers.

I turned on the WSJT-X monitor.

I observed almost simultaneous call related data on WSJT-X, JTAlert and the aggregator.  I have coloration turned on from JTAlert to WSJT-X, and the coloration appeared on WSJT-X at the same time (plus a slight delay).  Audio alerts generated by JTAlert was delayed as previously noted.

With the above running, I periodically pushed the iTunes play / pause button.  I observed on the mixer / speakers the iTunes audio behaved as expected with no delays; the JTAlert audio behaved with delays as noted; data on the WSJT window chain behaved as previously noted - no delays.

I would suspect both iTunes and JTAlert use the audio subsystem (to the same destination) in a similar manner.  The audio mixer shows both iTunes and JTAlert connections existed during the entire test.  Only JTAlert audio is delayed to the mixer and the speakers.  If the audio subsystem was causing a delay, wouldn't it also delay the iTunes audio?

Rather than the audio subsystem, I would suspect the JTAlert software delays sending the audio through the open audio channel.  Did the most recent version make changes to way it connects to the audio subsystem?

I hope this provides some useful information.  JTAlert is an excellent product that keeps improving.  Thanks to all for their work.

73,
don
wa0ruf


locked JTAlert ver 2.15.1 no sound.

Andy k3wyc
 

Another data point on sound issues with ver 2.15.1 -

I just installed 2.15.1 on my Win 8.1 laptop and now have no sound from JTAlert.  Settings/ Sound card / Test Play produces no sound and JTAlert does not appear in Volume Mixer.   Correct output device was shown as selected and changing it makes no difference.

I'm running Windows Defender and program files(x86)/HamApps is a listed exclusion.

I did not record the version that I updated from but it was likely 2.13.0 as that is the next most recent in my downloads folder.   I plan to revert to that version unless there is another solution.

Andy, k3wyc


locked Re: New JTAlert 2.15.1 delay in audio

Chris Morrison
 

Hi Laurie, 
I am experiencing the same issue. The audio alert is played from the previous decode period, so the delay is over 8 seconds for me. I am also using a Flex with DAX audio v3.1.7. 
I'll role back a version of JTalert and wait for a fix. 

73
Chris
MM1PTT


locked Ver 2.15 Fatal Error on startup

Mario Pedreschi GM3MZX
 


Hi,
Been using JTAlert for years without any problems but after installing V 2.15.0 I get an error warning on startup as follows.

FATAL ERROR
There has been an error opening the SQLite database : DXCC
Function:_dxcc-init()
Program will now exit.

Uninstalled V2.15.0 and reinstalled V2.14.5 and all works fine again, would appreciate some help.

73 De Mario  GM3MZX


locked Re: New JTAlert 2.15.1

HamApps Support (VK3AMA)
 

On 10/11/2019 4:06 pm, Michael Black via Groups.Io wrote:
It wouldn't matter unless JTAlert was sending data to marinetraffic.com.  Wouldn't matter if they both used the same port...two different IPs can't collide unless it's multicast and  or unicast to the same machine and I doubt either of those situations is happening.

I have a marinetraffic receiver too and no such problems.  I think this was just coincidental with JTAlert upgrades since they've been coming fast and furious lately so good chance of coincidental blaming.

Without more info from marinetraffic on what was being sent we'll never know what the problem was.

Mike

Mike,

Your correct in what you say. I was thinking that perhaps there are port collisions on the localhost between JTAlert and the MarineTraffic app. Since I saw mention of MarineTraffic hardware I was thinking (without have done any research) that perhaps that hardware was routing all network traffic, both MarineTraffic and Internet, acting like a router.

Since your using this system without the problems reported I am confident any connection to JTAlert is coincidental.

de Laurie VK3AMA