Re: [wsjt-devel] ft8code -c (minor bug)

Hi Pengo, No, the Git repo at SourceForge is not our working directory. That is why merge requests do not work. Better send us your patch (diff file) by e-mail. 73 de DG2YCB, Uwe German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg2...@gmx.de Info:

Re: [wsjt-devel] Update after v2.7.0-rc6

Hi John, If you have an M1 or M2, I recommend the 240730 version of my i+ version of WSJT- X

Re: [wsjt-devel] ALSA sound

Jarmo, Mike meant: Those don't have "CARD" in there. See this topic on our WSJT GROUP forum <https://groups.io/g/wsjtgroup/topic/107494081> for more information. But I think we'll make it an optional feature. 73 de Uwe, DG2YCB Am 23.07.2024 um 18:00 schrieb Bl

Re: [wsjt-devel] Super Issue on Apple MAC with M1 Processor

G2YCB, Uwe German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg2...@gmx.de Info: www.qrz.com/db/DG2YCB Am 14.07.2024 um 19:43 schrieb Uwe, DG2YCB via wsjt-devel: Hi Dan, Unfortunately, also for our standard WSJT-X we are not yet able to offer a solution for this err

Re: [wsjt-devel] Super Issue on Apple MAC with M1 Processor

Hi Dan, Unfortunately, also for our standard WSJT-X we are not yet able to offer a solution for this error. 73 de DG2YCB, Uwe German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg2...@gmx.de Info: www.qrz.com/db/DG2YCB Am 14.07.2024 um 12:23 schri

Re: [wsjt-devel] MacOS - error in SuperFox mode

Hi Gary, Unfortunately, we are not yet able to offer a solution. We thought we had one, but the hoped-for solution did not produce the desired results. I will therefore no longer offer specific M1 versions for my i*+ variants of WSJT-X until further notice. 73 de DG2YCB, Uwe

Re: [wsjt-devel] WSJT-X v2.7.1-devel 240712 improved widescreen PLUS => Crash in SuperHound mode

Hi Kari and all, Unfortunately, this means that our commit a87aacf has not yet completely fixed this error (which we had hoped for), because the "240712" code already has this commit. 73 de DG2YCB, Uwe German Amateur Radio Station DG2YCB Dr. Uwe Risse eMa

Re: [wsjt-devel] Adjustable frequency shift for split operation?

Richard, Please email me the settings you have made for the various menu items on your FT-991A. I have an FT-991 (without the "A"), and I don't have such problems with the bandwidth. I therefore suspect that either something is wrong with your rig or with your settings. 73

Re: [wsjt-devel] Question about transmit hazard via mouse wheel

would ask. --73, Glenn, AF8C On 6/2/2024 11:21 AM, Uwe, DG2YCB wrote: Hi Glenn, One question: Are your considerations theoretical or have you actually found that you stay transmitting when you make a such band change? Because I have just tried to reproduce this. Result: WSJT-X stopped transmi

Re: [wsjt-devel] Question about transmit hazard via mouse wheel

Hi Glenn, One question: Are your considerations theoretical or have you actually found that you stay transmitting when you make a such band change? Because I have just tried to reproduce this. Result: WSJT-X stopped transmitting immediately when I changed the band during transmission. 73 de DG2Y

Re: [wsjt-devel] Release Candidate WSJT-X 2.7.0-rc4

Uwe, DG2YCB via wsjt-devel: Will check this. 73 de DG2YCB, Uwe German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg2...@gmx.de Info: www.qrz.com/db/DG2YCB Am 11.03.2024 um 17:55 schrieb Dwayne Sinclair via wsjt-devel: The Darwin disk image for

Re: [wsjt-devel] Release Candidate WSJT-X 2.7.0-rc4

Will check this. 73 de DG2YCB, Uwe German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg2...@gmx.de Info: www.qrz.com/db/DG2YCB Am 11.03.2024 um 17:55 schrieb Dwayne Sinclair via wsjt-devel: The Darwin disk image for RC4 is corrupt. Only has a 281

Re: [wsjt-devel] Updated swedish translation of WSJT-X user guide..

Hi Anders, You can send such files to me. 73 de DG2YCB, Uwe German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg2...@gmx.de Info: www.qrz.com/db/DG2YCB Am 05.03.2024 um 15:53 schrieb Anders Rhodin via wsjt-devel: Good day all, I have an updated

Re: [wsjt-devel] Another fun hash collision P97USI

Jon and all, For your information, we have already made two modifications to our WSJT-X code that significantly reduce the likelihood of 10-bit hash collisions occurring. The few OMs who are currently testing this have all reported positive results. These improvements will be rolled out to everyo

Re: [wsjt-devel] 2.7.0-rc3 UI defect

Laurie, I have to set other priorities at the moment. A serious illness in the family turned into a bereavement yesterday. Therefore, only briefly: Please try wsjt-x_improved 2.7.1-devel "240202"

Re: [wsjt-devel] Response to CQ ignored

already been fixed. 73 de Uwe, DG2YCB Am 30.01.2024 um 13:40 schrieb Sam W2JDB via wsjt-devel: Hi Uwe, I sent this email earlier, somehow it did not go through. Hi Ed, Make sure you have the right option selected  "CQ:First" 73, Sam W2JDB On Tuesday, January 30, 2024 at 06:53:47 A

Re: [wsjt-devel] Response to CQ ignored

Hi Ed, At the moment, I have no explanation why it doesn't work with the "231202" i+ version. What I can say is that it definitely works well with the current "240106" code, as well as with the new "240202" version that will be released on Friday this week. I recommend that you download this vers

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 46

40202 update at your "find it here" link. It points tohttps://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.7.1/ Mike W9MDB On Saturday, January 27, 2024 at 04:14:00 AM CST, Uwe, DG2YCB via wsjt-devel wrote: Hi all, Short information: Although I could not repro

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 46

ble to use this instead.  Your call always has a space before/after. contains(" " + m_baseCall +" ")) Mike W9MDB On Saturday, January 27, 2024 at 04:14:00 AM CST, Uwe, DG2YCB via wsjt-devel wrote: Hi all, Short information: Although I could not reproduce this unwan

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 46

Hi all, Short information: Although I could not reproduce this unwanted effect so far, I have now added another line of code as a test for my upcoming 'improved' 2.7.1-devel "240202" update, which has the effect that if you are in FT8 Hound mode, all messages (below 1000 Hz) are really displayed

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45

n Jan 26, 2024, at 10:51 AM, Uwe, DG2YCB via wsjt-devel wrote:  But it worked also when I set my Rx QRG manually 275 Hz next to the Fox offset. 73 de DG2YCB, Uwe German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45

when the fox offset for your callsign changes? I think I've seen that. On Friday, January 26, 2024 at 09:15:37 AM CST, Uwe, DG2YCB via wsjt-devel wrote: Hi Rich, Last night I ran some tests with our good old standard WSJT-X (latest code) using three instances all connecte

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45

dow. So, I can really not reproduce this unwanted effect. 73 de DG2YCB, Uwe German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg2...@gmx.de Info: www.qrz.com/db/DG2YCB Am 26.01.2024 um 16:12 schrieb Uwe, DG2YCB via wsjt-devel: Hi Rich, Last night

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45

Hi Rich, Last night I ran some tests with our good old standard WSJT-X (latest code) using three instances all connected via virtual audio.  One in FT8 Fox mode and the other two in FT8 Hound mode. Then I simulated just such QSO situations, but each time the reports appeared in the right-hand win

Re: [wsjt-devel] I have in trouble JT65B of WSJT-X

This is because I just use one side of TX which both IC-746pro. Of course, I use it the same as WSJT-X and JTDX. Is it okay to use the output audio port of the only one port to all of the instances as share on one PC? Taka, JP3EXR *From:*Uwe, DG2YCB via wsjt-devel *Sent:* Friday, January 5, 20

Re: [wsjt-devel] I have in trouble JT65B of WSJT-X

Hi Taka, Larry, and all I would really like to help you, but the error simply does not occur on my PC. I have run numerous tests with two instances this morning. Both with WSJT-X v2.6.1 and v2.7.0-rc3 and with wsjt-x_improved v2.7.1-devel. I tested various settings (EME delay on/off, with FT-991

Re: [wsjt-devel] WSJT-X parsing of the country file, specifically 4U1A (and others)

r EU Turkey? How do you see it? 73 de Uwe, DG2YCB Am 08.12.2023 um 18:50 schrieb Uwe, DG2YCB via wsjt-devel: This may all be correct, but at least to me, the decisive factor is what the DXCC rules are. And according to the DXCC list <https://www.arrl.org/files/file/DXCC/2022_DXCC_Curre

Re: [wsjt-devel] WSJT-X parsing of the country file, specifically 4U1A (and others)

t of land that sticks out in the Black Sea and was a NATO listening post just south of Crimea and might still be. Incirlik is still a very busy base down near the Mediterranean Sea. Merhaba Arkadaslar. Nasiliniz? On 12/08/2023 11:38 AM EST Uwe, DG2YCB via wsjt-devel wrote: Hi Jim and all, I hav

Re: [wsjt-devel] WSJT-X parsing of the country file, specifically 4U1A (and others)

Hi Jim and all, I have analyzed our WSJT-X code regarding this aspect. Results: There seems to be nowhere specified which countries the WAE entities shall be assigned to when the "Include extra WAE entites" checkbox is *not* checked, neither in the CTY.DAT file nor in WSJT-X. This means, if these

Re: [wsjt-devel] WSJT-X 2.7.0-rc2 Switching caller in TX1 message

Hi Clay, Thanks for this issue report. With WSJT-X, CQ: Max Dist only works with certain contest messages, and when you have the Active Stations window open. I have changed this with my wsjt-x_improved program. There it works also for normal messages. Thi

Re: [wsjt-devel] Button sizes not correct

Hi Mark, In most cases, this effect is triggered by App Scaling. Try setting this to 100%. Probably everything will look normal then. Please try a few combinations of App Scaling and font size to find the best settings for you. It is almost impossible to compensate for all the unsightly side eff

Re: [wsjt-devel] Problem with Hamlib

all the parameters again and see if I'm wrong. I'll keep you informed. ON4CKT Rudy *Van: *"Uwe, DG2YCB" <mailto:dg2...@gmx.de> *Aan: *"on4ckt" <mailto:on4...@telene

Re: [wsjt-devel] Problem with Hamlib

Hello Rudy, Your settings for the FT-991 seem to be fine. I have the same settings here (and 028=RS232C), and everything works well. How is your PTT connected? I use CAT. If you have DTR or RTS selected, make sure the COM port for that is different from the CAT serial port. Is COM3 the right one?

Re: [wsjt-devel] WSJTX 2.6.1 fails to initialize with a misleading error "Failed to start OmniRig COM server"

Hi Chris, Do I understand you correctly that you are using OmniRig but have selected "Icom IC-7300" as Rig in WSJT-X? Of course this can't work then. You must then select "OmniRig 1" in WSJT-X. And in the OmniRig Settings you have to select your IC-7300 as Rig type in RIG 1 and enter the correct

Re: [wsjt-devel] WSJTX V2.7 sample files error

Hi Sandro and all, I created the missing contents_2.7.json file and put it on our WSJT SourceForge page. This should make downloading samples work again. 73 de DG2YCB, Uwe German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg2...@gmx.de Info: www.qr

Re: [wsjt-devel] Possible bug related to CQ with individual contest name

Hi Mark, Thank you for reporting this. However, this bug was fixed months ago (February 15, 2023). Allow me to make a general comment on this topic. It is always good when you detect a bug to try the latest available version first. This is v2.7.0-rc1

Re: [wsjt-devel] wsjt-x Hungarian localization

Hi Janos, Thank you for your Hungarian translation file. I have added it to our source code. I will send you a WSJT-X test version with your file by private email soon. 73 de DG2YCB, Uwe German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg2...@gmx.

[wsjt-devel] "U.S.A" displayed as "U.S.A. of America"

le. However, the good news is: You can change it very easily yourself. Either delete any cty.dat file in your log directory, or edit this file and change "United States of America" to "United States". I will inform the maintainers of the cty.dat file about this annoying side

Re: [wsjt-devel] Error Loading LOTW Users Data

Hi Jim, This is something for Brian, N9ADG. He programmed this feature. Have you followed the steps described in chapter 3.1 of the user guide and installed the Windows OpenSSL Packages ? 73 de DG2YCB, Uwe

[wsjt-devel] Hamlib hotfixes

-improved/files/WSJT-X_v2.7.0/hamlib/ 73 de Uwe, DG2YCB ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Head of a new Hamlib Beta Testing Group found

h from the bottom of my heart much success! 73 de Uwe, DG2YCB Am 13.05.2023 um 09:09 schrieb Uwe, DG2YCB via wsjt-devel: Dear WSJT-X users, Please allow me to summarize again here on this email reflector a topic that is very important to me and to all of us. My original post was on https://g

[wsjt-devel] Hamlib Beta Testing Group needed

ow*, because we can't get the next frustration after every new WSJT-X release. Makes no sense! So, again: *Who of you will take this in hand and organize such a systematic beta testing? *I do not want to see one more "stupid" post as long as this problem is

Re: [wsjt-devel] Permanent solution for a new forum found: wsjtgr...@groups.io

Here is the URL: https://groups.io/g/wsjtgroup 73 de Uwe, DG2YCB Am 26.04.2023 um 20:37 schrieb Uwe, DG2YCB: Dear WSJT-X Users, The overwhelming success of the temporary WSJT-XY forum has brought us close to the limit of 100 users within one day. The good news is that a permanent solution

[wsjt-devel] Permanent solution for a new forum found: wsjtgr...@groups.io

reasons, groups.io requires messages from new members to be approved once. After that, posts are possible without further hurdles. 73 de Uwe, DG2YCB ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo

[wsjt-devel] Statement regarding WSJTX.groups.io

want to report bugs or discuss with us developers. 4. With immediate effect, I have therefore disabled the mention of the WSJTX.group.io forum on the official WSJT-X homepage. 73 de Uwe, DG2YCB Core WSJT Development Group P.S.: As a temporary solution, I just created a new private forum

[wsjt-devel] Today is the PACCdigi Contest

Hi all, Today is the PACCdigi Contest , which will be held for the first time with our new extended FT Roundup protocol. So those who want to test it have a good opportunity to do so today. Follow the Contest Rules

[wsjt-devel] Sourceforge fixed the download issue

possible again. 73 de Uwe, DG2YCB ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Sourceforge download from https://wsjt.sourceforge.io/wsjtx.html should work again

Download of the v2.6.1 WSJT-X installer packages via our https://wsjt.sourceforge.io/wsjtx.html homepage should work again now. There seems to be some problem with SourceForge at the moment. But I found another solution that seems to work, at least for now. 73 de Uwe DG2YCB

Re: [wsjt-devel] wsjtx-2.6.1: TX is activated when frequency is changed in the hound mode

Thanks for the report, Jaroslav. I have changed the code accordingly to prevent this. 73 de Uwe, DG2YCB Am 13.02.2023 um 12:51 schrieb Jaroslav Skarvada via wsjt-devel: If hound mode is enabled and frequency is manually changed by entering the frequency directly to the "band" box a

Re: [wsjt-devel] Transmit Audio Source

Karl, Is the audio source perhaps disabled at Windows level? Have a look at the Windows Sounds settings (right-click on the speaker icon at the bottom right and then "Sounds"). It may be that your FT-991 is now recognized as a "new" audio source, and the old one no long

Re: [wsjt-devel] UDP Status message defect. WD status not set when in Hound mode.

Yes, Laurie, but exactly this is (hopefully) being done with the two test installers I sent you. Please confirm that it works with them. 73 de DG2YCB, Uwe German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg2...@gmx.de Info: www.qrz.com/db/DG2YCB

Re: [wsjt-devel] WSJT-X 2.6.0 GA Release

Sillanmäki via wsjt-devel wrote: Hi Uwe, I just downloaded the tarball. It still has the wrong CmakeLists.txt entry... I used this link to download: https://sourceforge.net/projects/wsjt/files/wsjtx-2.6.0/wsjtx-2.6.0.tgz Is this the correct link?? 73's de Kari, oh2gqc On 6.1.2023 18.05

Re: [wsjt-devel] WSJT-X 2.6.0 GA Release

Hi Stefan, Yes, it must be 4.5.3. I have updated the tarball. Please download again and see if it works better now. 73 de DG2YCB, Uwe Am 06.01.2023 um 16:57 schrieb Stefan HB9TMC via wsjt-devel: Hi, cmake generated an error: CMake Error at CMakeLists.txt:56 (file):   file failed to open for

Re: [wsjt-devel] WSJT-X Wrong name for audio CODEC

The reason is that Windows has internally two sets of audio names. One is for the new Windows Settings menus, but the "true" name is still that which is used when you open the old "Sounds" menu. And in the registry, it is stored somewhere else. It is a known Windows bug, that sometimes, these two

Re: [wsjt-devel] Help with Omni-Rig

Hi Andy, WSJT-X gets the path to OmniRig from Windows. No settings are required for this within WSJT-X. Usually, OmniRig installs into "C:\Program Files (x86)\Afreet\OmniRig" but the only thing that matters is which path is stored in the registry, and whether this path is correct. Please check i

Re: [wsjt-devel] Some comments for WSJT-X 2.6.0-RC4

Hello Marco, FYI. The second issue should be fixed with v2.6.0-rc5. We have fine-tuned some GUI settings so that it now works better with different font sizes and on different operating systems. And issue #1 can also be RFI. Does it also happen on all bands or only on some? Check whether the err

Re: [wsjt-devel] 2.6.0-RC4 GUI error

. Therefore, the fix is not quite as easy as one might think. Currently, I can only suggest you to reduce the font size (e.g. to 9 pt). 73 de Uwe, DG2YCB Am 17.10.2022 um 00:56 schrieb Barry Jackson via wsjt-devel: An annoying error has crept in that chops half the leading character in the band field

Re: [wsjt-devel] WSJT-X 2.6.0-rc3 ALL_WSPR.TXT error

Hi Josh, Thanks for reporting this bug. We found and fixed the root cause. The fix will be included in the next release. The error occurred when the user transmitted at t < 0.6 * TRPeriod after a band change. This is typically the case with WSPR when band hopping is enabled, but almost never wit

Re: [wsjt-devel] Second wsjt-x2.6.0-rc4-Linux64 Hound issue

Hi Saku, Thanks for the bug report. Should be fixed with the next release. Under certain conditions, some special operating modes were not fully initialized when WSJT-X was started in such a mode. 73 de Uwe, DG2YCB Am 18.09.2022 um 15:13 schrieb Saku via wsjt-devel: Hi! Found also another

Re: [wsjt-devel] V. 2.6 Error and Crash

y in size. * Delete the "logs" folder if you don't need it anymore. Perhaps also helpful to know: I recently did the same procedure with an OM who also reported occasional sudden program crashes. It turned out that HRD caused the crashes for him. 73 de Uwe, DG2YCB Am 28.07.2022

Re: [wsjt-devel] WSJT-X 2.6.0-rc2 - possible bug (WSPR messages truncated)

-rc2/Tests/wsjtx-2.6.0-rc2_WSPR_bug_fixed.tgz I have also created a 64-bit Windows installer that contains the same bug fix: https://sourceforge.net/projects/wsjt/files/wsjtx-2.6.0-rc2/Tests/wsjtx-2.6.0-rc2-win64_WSPR_bug_fixed.exe Would be nice if you could give us feedback if it works. 73 de Uwe

Re: [wsjt-devel] hamlib test

fixes the VFOB error on IC7100 and IC7610. The installer comes already with the latest hamlib files. Only in case the VFOB error is really still there with this version, replace also the libhamlib-4.dll file afterwards, and try again. 73 de Uwe, DG2YCB Am 08.07.2022 um 18:31 schrieb Al Flapan

Re: [wsjt-devel] Release Candidate WSJT-X 2.6.0-rc1

Hi Tony, As you already mentioned, this can have several reasons. My tip: If you are working on Windows, just open the task manager in such a case. Most likely, you will see a hanging wsjtx.exe or jt9.exe process. Close this process manually and WSJT-X should start again. 73 de Uwe, DG2YCB

Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc2

Yellow color means New DXCC. 73 de Uwe, DG2YCB Uwe Am 26. September 2018 22:32:37 schrieb Joe Taylor : Hi Uve, I cannot reproduce the problem you describe. See the attached screen shot. OE1KFV is in the log, at JN88. OE1KFV is identified as a new call, which is correct. I don't

Re: [wsjt-devel] Ver. 2.0 problems

I saw the same here from my QTH yesterday on 14078 kHz. A couple of very strong stations which could not be decoded. Neiher with v2.0.0-rc1 legacy enabled, nor with v2.0.0-rc1 legacy disabled, nor with v1.9.1. No idea what was the reason. It did not seem to be a time sync issue. 73 de DG2YCB,