locked
Re: Sound Not Working in 2.15.4
Laurie,
I embarked on installing this version with some trepidation after all these reports of no sound/sound loss.
It installed without a hitch, but no sound… then I got the warning panel and set the sound device to the Realtek device, still no joy, then picked a couple of other devices and went back to RealTek… still no joy. Restarted JTAlert and THEN noticed that I had never turned on the sound.
After turning on the sound… it worked.
Machine is a Dell i7 based desktop with more than enough memory and storage running the most current update drop of Win10 64 bit. What is the problem now? I just turned on my sound… (I never really used it before anyway).
Oh Well, <headsmack, facepalm>
KD4IZ Jack Spitznagel FM19oo
|
|
locked
Error: Variable used without being declared.
Robert A Wilson
I've received the error below with version 2.15.3 and with version 2.15.4. I've tried uninstalling and reinstalling. Does anyone have any other suggestions?
---------------------------
AutoIt Error
---------------------------
Line 39848 (File "C:\Program Files (x86)\HamApps\JTAlert\JTAlert.exe"):
Error: Variable used without being declared.
|
|
locked
JTAlert 2.15.4 Much Slower?
Chad Kurszewski
After upgrading to 2.15.4, I noticed that there is much delay from when WSJT-X "prints" calls to when JTAlert prints calls in the display slots/lines. No other windows running on JTAlert (no decodes history, callsign history, band activity windows). It's not until about second 5 or 6 or 7 into the cycle (FT8) when JTAlert starts printing calls from the prior sequence.
I reverted back to 2.15.0 and it printed calls starting at second 2. Re-loaded 2.15.4 and it's back to 5 or 6 seconds. 73, Chad WE9V
|
|
locked
Re: Worked B4 Color Isn't Changing
On 6/12/2019 2:46 am, WA8RZR - Jan Blair wrote:
I just updated to Version 2.15.4, where you fixed my issue of:Jan,- Mode not written to the B4Log.mdb file when logging is disabled.Made a contact this morning, and your software properly captured and identified the station as a Worked B4 entity. Thanks for confirming the fix. I suggest you create a new B4Log.mdb file then perform an import of an ADIF export from your primary logger. This will correct the previously recorded entries with the missing mode. de Laurie VK3AMA
|
|
locked
Re: Sound Not Working in 2.15.4
HamApps Support (VK3AMA)
On 5/12/2019 4:24 pm, Barry Murrell
ZS2EZ wrote:
Barry, Please try the following after installing 2.15.4
If the above doesn't get you working, then rollback to 2.15.3 until I am able to reproduce the defect and code a fix. Let me know how you get on. de
|
|
locked
Re: Sound Not Working in 2.15.4
That did not work here .. Tnx Dwight Back to .3
-- 73 Ron, W3RJW
|
|
locked
Re: Worked B4 Color Isn't Changing
Laurie, - follow-up to this reported issue
I just updated to Version 2.15.4, where you fixed my issue of: - Mode not written to the B4Log.mdb file when logging is disabled.Made a contact this morning, and your software properly captured and identified the station as a Worked B4 entity. Again, thank you so very much for all your effort on this excellent software tool, and being so responsive to the users. 73, Jan Blair WA8RZR
|
|
locked
Re: Sound Not Working in 2.15.4
Realtek works on my system. Using 2.15.4.
__________ Dan – K4SHQ CFI/II
From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io]
On Behalf Of Ron W3RJW via Groups.Io
Sent: Thursday, December 5, 2019 8:25 AM To: Support@HamApps.groups.io Subject: Re: [HamApps] Sound Not Working in 2.15.4
[Edited Message Follows] Same problem here Windows default also happens to be Realtek ...
-- Dan - K4SHQ
|
|
locked
Re: Sound Not Working in 2.15.4
Dwight Bosselman
Try going into settings-soundcard and click on a couple of sound cards there, even if Realtek is already checked, ending up with the Realtek. Started working fine after that. 73 Dwight NS9I
On 12/5/2019 8:25 AM, Ron W3RJW via
Groups.Io wrote:
|
|
locked
Re: Sound Not Working in 2.15.4
Same problem here Windows default also happens to be Realtek ...
Went back to 2.15.3 and selected either Windows default or the Realtek and they both work. Realtek does not work in 2.15.4 Win 8.1 -- 73 Ron, W3RJW
|
|
locked
Re: Worked B4??
Laurie,
At the present time I do not use FT4, I of course use FT8 and that is where the problem is. TNX Neil N4FN
|
|
locked
Re: Sound Not Working in 2.15.4
Barry Murrell ZS2EZ
Hi Hasan
Whilst my Realtek card happens to be the Default Sound Card, it was selected in JTAlert by it’s name (REALTEK SPEAKERS (High Definition)
Works perfectly in 2.15.3 ….. I NEVER select Windows Default Sound Card, as I have 6 sound devices (plus a virtual audio cable) set up on my PC!
73 de BARRY MURRELL ZS2EZ KF26ta - Port Elizabeth, South Africa
From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Hasan Schiers N0AN
It says right in the release notes that the Windows Default Sound Card will no longer work, period. You have to use a named sound card. Read the release notes. (If I understand your problem) 73, N0AN Hasan
On Wed, Dec 4, 2019 at 11:24 PM Barry Murrell ZS2EZ <mailgroups@...> wrote:
|
|
locked
Re: V2.15.3 No access to menus, not possibloe to close program without Task Manager
Frode Igland
Thanks to Mike and Laurie. Among my many icons, I didn't even notice the green icon. Once I found, all worked just fine. Always good to climb the learning ladder. Frode LA6VQ
|
|
locked
Re: Sound Not Working in 2.15.4
Hasan Schiers N0AN
It says right in the release notes that the Windows Default Sound Card will no longer work, period. You have to use a named sound card. Read the release notes. (If I understand your problem) 73, N0AN Hasan
On Wed, Dec 4, 2019 at 11:24 PM Barry Murrell ZS2EZ <mailgroups@...> wrote:
|
|
locked
Sound Not Working in 2.15.4
Barry Murrell ZS2EZ
Hi Laurie
Installed the new 2.15.4 version – sound stopped working. Reverted back to 2.15.3 – works perfectly.
I use the onboard Realtek sound card for my alerts/system sounds etc – it is the Windows Default sound card, but is selected by name in JTAlert.
Before reverting back I tried restarting the PC, to no avail. Running Windows 10 64 Bit (1909 update), 16Gb RAM, JTDX 2.1.0-rc144 and logging to DXKeeper.
73 de BARRY MURRELL ZS2EZ KF26ta - Port Elizabeth, South Africa EPC#0558 DMC#1690 30MDG#4081 DXCC HONOR ROLL (332/340) DXCC(mixed)#41,146 DXCC(RTTY)#1,916 DXCC(phone)#34,990 DXCC(CW)#11,714 DXCC 80m,40m,30m,20m,17m,15m,12m,10m 5BDXCC#8,916 WAS Triple Play #492 WAS(RTTY)#538 WAS(Digital)#163-Endorsements JT65,FT8 WAZ(RTTY)#185 WAE-I(mixed)#72 WAZS(mixed)#214 AAA#1569 AS ZR6DXB: VUCC(50MHZ)#1,334 UKSMG WAE(Silver)#75 UKSMG AFRICA#22 WAC (Satellite) website : www.zs2ez.co.za
|
|
locked
Re: UDP port problems
Rick Johnson
That is why I reinstalled JTAlert.....to reload the files and it didn't work of course. I sent my files once before but I don't remember how. The Parkinson's is getting worse. I'll figure it out. Thanks for the help. 73, Rick W3BI
On Wed, Dec 4, 2019 at 6:25 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
|
|
locked
New JTAlert 2.15.4 is available.
#Announcement
#NewRelease
The Latest JTAlert version 2.15.4 is now available @ https://hamapps.com/JTAlert/
This release has a critical fix for "NO Log" users. Please review the Release notes at the end of this message. de Laurie VK3AMA The Release Notes... 2.15.4 (04-DEC-2019) de Laurie VK3AMA
|
|
locked
Re: JTAlert Log issue
Robert T
Laurie,
The log functions have started woring again. The only thing I know I did was close and reopen WSJT-X and JTAlert. I guess the restart fixed the issue.
Tnx
Bob, K2RET
On December 4, 2019 at 5:08 PM "HamApps Support (VK3AMA)" <vk3ama.ham.apps@...> wrote:
|
|
locked
Re: Worked B4??
HamApps Support (VK3AMA)
On 5/12/2019 1:59 am, Neil Foster
wrote:
Hi Mike and Laurie,Neil, A scan Log & rebuild will NOT resolve any B4 issues your having, it only affects the internal lists used by the Wanted Alerts. If your seeing some B4s on the Band and not a total absence of B4s suggests the likely cause is within your Log file and JTAlert is not finding suitable entries when it does a B4 check. Are the missing B4s for previously logged FT4 QSOs? If so you will likely find that HRDLogbook has them recorded as MFSK without a submode (the HRD Log schema doesn't have a SUBMODE column). If an incorrect logged mode is not the answer, send me a copy of your HRD log file for analysis (only if it is an MSAccess type). Don't send the log via the group, send it to me direct. Let me know what you find. de Laurie VK3AMA
|
|
locked
Re: UDP port problems
HamApps Support (VK3AMA)
On 5/12/2019 9:34 am, Rick Johnson
wrote:
Thinking about the problem.....I used Revo Uninstall to remove an Acom program. I think in the list of Revo removing needed JTAlert files would not cause JTAlert to stop receiving UDP data from WSJT-X, if anything it would produce a critical error dialog from JTAlert which would subsequently close. A rerunning of the JTAlert installer will restore any lost files/directories. There have not been any recent changes in how JTAlert receives WSJT-X UDP traffic, internally 2.15.3 is exactly the same as 2.14.5. The most likely cause is another application having exclusive access to the WSJT-X UDP port (2237) or WSJT-X is running with elevated privileges (set to run as administrator). There is never any need to run WSJT-X elevated. If you haven't done so already, perform a PC restart, especially if your running Win10 as that is now the most common fix for unexpected or changed behavior. If you still have no success, use the "Help" (or "? ") -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis. de Laurie VK3AMA
|
|