wsjt-devel — WSJT software development

Re: [wsjt-devel] Windows compatibility WSJT-X and improved

[Doug B. Sr. <dou...@gm...>]

Switch to Linux already! ;)

On Thu, May 1, 2025, 3:25 PM Joe via wsjt-devel <
wsj...@li...> wrote:

> I agree, My win 10 machine here can outperform 75% of available win 11
> machines ya can buy.
>
> but it can't use Win 11 because of the security crap it insists on having.
>
> let ME decide if i want the extra level of security.
>
> All Win 11 is a way for them to make everyone buy new stuff
>
> Joe WB9SBD
>
> On 5/1/2025 10:57 AM, Larry Banks via wsjt-devel wrote:
>
> $$$ and upgrade difficulty, especially if the CPU is too old.
>
> Larry / W1DYJ
>
>
> On 5/1/2025 11:22, Greg Walls via wsjt-devel wrote:
>
> As a former IT Professional of 32 years, why would anyone be on an
> unsupported platform, especially when upgrades to Windows 11 are free? I
> wonder if these guys are still driving their first car.
>
> Greg
>
>
>
> Sent from my iPad
>
> On May 1, 2025, at 10:06 AM, Uwe, DG2YCB via wsjt-devel
> <wsj...@li...> <wsj...@li...>
> wrote:
>
>  Hi Andy,
>
> You are causing a lot of confusion with such half-baked statements. Like
> always, and for good reasons, the Windows installation packages for all
> WSJT-X Improved versions are being created using Qt 5.12.12. This gives the
> best possible backwards compatibility (down to Windows 7), as well as the
> rest results in terms of rendering the various controls (also when Dark
> Style is enabled). This tool chain has not been changed over the past
> months.
>
> As you know, we've spent many days of work trying to help you with your
> "special" setup on an old Windows 8.1. system. During these tests, you
> confirmed that all is working well on your Windows 10 computer. And no one
> else has ever reported similar issues than you with your setup.
>
> Please do me a favor and stop confusing others. If you don't understand
> why we invest months of work to offer a data set for Qt6 in addition to the
> existing Qt5 source code, then any further discussion about it here is not
> worthwhile anyway. Other OMs who know what this is for are very grateful
> for this work. And if at some point in the future you should buy more
> modern equipment (maybe even Linux-based), then you will be grateful to us
> one day why we were so wise and foresighted in 2024 and 2025 to develop the
> necessary source code for it and keep it up to date.
>
> 73 de DG2YCB,
> Uwe
> ________________________________________
> German Amateur Radio Station DG2YCB
> Dr. Uwe Risse
> eMail: dg...@gm... <dg2ycb@gmxde>
> Info: www.qrz.com/db/DG2YCB
>
>
> Am 01.05.2025 um 13:55 schrieb Andy Durbin via wsjt-devel:
>
> "Both Windows 7 or 8.x version support will not be available for Qt 6.
> Microsoft discontinued the support for both Windows versions some time ago,
> and as a vendor, we can no longer maintain support for these windows
> versions in Qt 6. Windows 7 (both 32bit and 64bit) was supported as a
> target in Qt 5.15 LTS and Windows 8.1 (both 32bit and 64bit) as a target in
> Qt 5.12 LTS. This means that we will not have 32bit Windows support
> available. Additionally, it will no longer be possible to create UWP applications
> on Windows 10."
>
> ref - https://www.qt.io/blog/qt6-development-hosts-and-targets
>
> I have found that 2.8.0 improved is not compatible with Win 8.1 and no one
> has said that it works for them.
>
> Should the WSJT-X Windows compatibility statement be revised?  It
> currently states - " (Windows 7 and later)" which was true for 2.7.0 but
> may not be true if later official releases use Qt6.
>
> 73,
> Andy, k3wyc
>
>
>
> _______________________________________________
> wsjt-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
>
> _______________________________________________
> wsjt-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
>
>
> _______________________________________________
> wsjt-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

Re: [wsjt-devel] Windows compatibility WSJT-X and improved

[Joe <ns...@mw...>]

I agree, My win 10 machine here can outperform 75% of available win 11 
machines ya can buy.

but it can't use Win 11 because of the security crap it insists on having.

let ME decide if i want the extra level of security.

All Win 11 is a way for them to make everyone buy new stuff

Joe WB9SBD

On 5/1/2025 10:57 AM, Larry Banks via wsjt-devel wrote:
> $$$ and upgrade difficulty, especially if the CPU is too old.
>
> Larry / W1DYJ
>
>
> On 5/1/2025 11:22, Greg Walls via wsjt-devel wrote:
>> As a former IT Professional of 32 years, why would anyone be on an 
>> unsupported platform, especially when upgrades to Windows 11 are 
>> free? I wonder if these guys are still driving their first car.
>>
>> Greg
>>
>>
>>
>> Sent from my iPad
>>
>>> On May 1, 2025, at 10:06 AM, Uwe, DG2YCB via wsjt-devel 
>>> <wsj...@li...> wrote:
>>>
>>>  Hi Andy,
>>>
>>> You are causing a lot of confusion with such half-baked statements. 
>>> Like always, and for good reasons, the Windows installation packages 
>>> for all WSJT-X Improved versions are being created using Qt 5.12.12. 
>>> This gives the best possible backwards compatibility (down to 
>>> Windows 7), as well as the rest results in terms of rendering the 
>>> various controls (also when Dark Style is enabled). This tool chain 
>>> has not been changed over the past months.
>>>
>>> As you know, we've spent many days of work trying to help you with 
>>> your "special" setup on an old Windows 8.1. system. During these 
>>> tests, you confirmed that all is working well on your Windows 10 
>>> computer. And no one else has ever reported similar issues than you 
>>> with your setup.
>>>
>>> Please do me a favor and stop confusing others. If you don't 
>>> understand why we invest months of work to offer a data set for Qt6 
>>> in addition to the existing Qt5 source code, then any further 
>>> discussion about it here is not worthwhile anyway. Other OMs who 
>>> know what this is for are very grateful for this work. And if at 
>>> some point in the future you should buy more modern equipment (maybe 
>>> even Linux-based), then you will be grateful to us one day why we 
>>> were so wise and foresighted in 2024 and 2025 to develop the 
>>> necessary source code for it and keep it up to date.
>>>
>>> 73 de DG2YCB,
>>> Uwe
>>> ________________________________________
>>> German Amateur Radio Station DG2YCB
>>> Dr. Uwe Risse
>>> eMail: dg...@gm...
>>> Info: www.qrz.com/db/DG2YCB
>>>
>>>
>>> Am 01.05.2025 um 13:55 schrieb Andy Durbin via wsjt-devel:
>>>> "Both Windows 7 or 8.x version support will not be available for Qt 
>>>> 6. Microsoft discontinued the support for both Windows versions 
>>>> some time ago, and as a vendor, we can no longer maintain support 
>>>> for these windows versions in Qt 6. Windows 7 (both 32bit and 
>>>> 64bit) was supported as a target in Qt 5.15 LTS and Windows 8.1 
>>>> (both 32bit and 64bit) as a target in Qt 5.12 LTS. This means that 
>>>> we will not have 32bit Windows support available. Additionally, it 
>>>> will no longer be possible to create UWP applications on Windows 10."
>>>>
>>>> ref - https://www.qt.io/blog/qt6-development-hosts-and-targets
>>>>
>>>> I have found that 2.8.0 improved is not compatible with Win 8.1 and 
>>>> no one has said that it works for them.
>>>>
>>>> Should the WSJT-X Windows compatibility statement be revised?  It 
>>>> currently states - " (Windows 7 and later)" which was true for 
>>>> 2.7.0 but may not be true if later official releases use Qt6.
>>>>
>>>> 73,
>>>> Andy, k3wyc
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> wsjt-devel mailing list
>>>> wsj...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>>
>>> _______________________________________________
>>> wsjt-devel mailing list
>>> wsj...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
>>
>> _______________________________________________
>> wsjt-devel mailing list
>> wsj...@li...
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Windows compatibility WSJT-X and improved

[John L. B. <2si...@gm...>]

I am sorry but I could not resist. Some of us do have old cars. I am not 
driving my first car, but I do drive a 1957 Pontiac. A 1957 Pontiac was 
my 3rd and 4th car. I had one before I went into the US Army and another 
when I got out and could not resist buying this one when it came up for 
sale here in Prescott Valley, AZ, in 2014. It has won eight trophies at 
car shows since I bought it.:

https://tinyurl.com/My1957pontiacchieftain

John
Retired computer programmer/course developer and instructor/document 
writer AT&T Bell Laboratories/Lucent Technology

John L. Broughton
2si...@gm...
www.wb9vgj.us

On 5/1/2025 8:22 AM, Greg Walls via wsjt-devel wrote:
> As a former IT Professional of 32 years, why would anyone be on an 
> unsupported platform, especially when upgrades to Windows 11 are free? 
> I wonder if these guys are still driving their first car.
>
> Greg
>

-- 
This email has been checked for viruses by AVG antivirus software.
www.avg.com

Re: [wsjt-devel] Windows compatibility WSJT-X and improved

[Greg W. <gw...@po...>]

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">I get it and have two comments.&nbsp;<div><br></div><div>1. I did a quick search on Amazon and found a decent Windows 11 PC that is refurbished for $240. Don’t overlook those. I have helped many friends get those and have never had a problem.&nbsp;</div><div><br></div><div><img src="cid:20C27C8B-1E66-4C5C-AEF3-15455051A0B3" width="834" alt="image"></div><div><br></div><div>2. Make friends with your local Bank’s IT Manager. Community Banks are often very willing to give away old PCs, otherwise they have to pay to dispose of them. Most banks replace their PCs every three or four years. Many IT Managers will require the hard drive be removed before disposing of the PC so all you would have to buy would be a cheap hard drive. You may be able to make a deal with them to come in and remove the hard drives from the old ones the next time they do a refresh and walk out with a bunch of them. Hint; Emphasize ARES. &nbsp;</div><div><br></div><div><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">Over the years I have been privileged to give away literally hundreds of PCs.&nbsp;</span>I am retired now but I may still be able to get a PC for free from time to time. I’m not sure where you are but if you live anywhere close to South Georgia, I’d be happy to let you know when I get another one.&nbsp;</div><div><br></div><div>Greg</div><div><br id="lineBreakAtBeginningOfSignature"><div dir="ltr"><div><br></div><div><br></div>Sent from my iPad</div><div dir="ltr"><br><blockquote type="cite">On May 1, 2025, at 1:36 PM, Tom Hauer &lt;rdr...@gm...&gt; wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div><div class="gmail-aju" style="float:none;padding:0px 16px;display:flex;height:80px;min-width:40px;font-family:&quot;Google Sans&quot;,Roboto,RobotoDraft,Helvetica,Arial,sans-serif;font-size:medium"><div class="gmail-aCi" style=""><br><span style="font-family:Arial,Helvetica,sans-serif;font-size:small">Greg,</span></div></div><div class="gmail-gs" style="margin:0px;min-width:0px;padding:0px 0px 20px;width:auto;font-family:&quot;Google Sans&quot;,Roboto,RobotoDraft,Helvetica,Arial,sans-serif;font-size:medium"><div class="gmail-"><div id="gmail-:2re" class="gmail-ii gmail-gt" style="direction:ltr;margin:8px 0px 0px;padding:0px;font-size:0.875rem;overflow-x:hidden"><div id="gmail-:2rf" class="gmail-a3s gmail-aiL" style="direction:ltr;font-variant-numeric:normal;font-variant-east-asian:normal;font-variant-alternates:normal;font-size-adjust:none;font-kerning:auto;font-feature-settings:normal;font-stretch:normal;font-size:small;line-height:1.5;font-family:Arial,Helvetica,sans-serif;overflow:auto hidden"><div dir="ltr"><div><br></div><div>Your comments are not totally fair.&nbsp; First, many of us are using computers that cannot be upgraded to Windows 11,&nbsp;so it isn't FREE.&nbsp; Sorry, I live on Social Security and cannot afford to just go out and dump a bunch of money on a newer computer.&nbsp; Second, Windows 11 still has compatibility issues with some of the software I run so I am staying put for now.&nbsp; Third, Windows 10 doesn't even play nice at this late stage in its support life with everything I use!</div><div><br></div><div>Yes, I am concerned about what will happen with the .NET framework for Windows 10 after it is no longer supported as there are several things I use (like WinLink Express) that may no longer work on Windows 10, but for now I am where I am and that is that!!</div><div><br></div><div>Thanks for seeing others' perspectives!</div></div></div></div></div></div></div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><blockquote type="cite" style="color:rgb(34,34,34)"><div dir="ltr"><div dir="ltr"><div dir="ltr">Tom Hauer, K0YA<div>ARES Emergency Coordinator</div><div>Blanco, Burnet, Llano and Mason Counties</div><div>ARRL ARES District 8, STX Section</div><div>TDEM RACES District 12-053</div><div>Burnet County CERT</div><div>319 551-9788<br></div><div><a href="mailto:rdr...@gm..." style="color:rgb(17,85,204)" target="_blank">rdr...@gm...</a></div><div>PO Box 1522 (mailing ADR)</div><div>11700 E FM 1431 R37</div><div>Marble Falls, Tx 78654</div><div>EM00wn</div><div>Latitude:&nbsp; 30.568805</div><div>Longitude:&nbsp; -98.140287</div></div></div></div></blockquote></div></div></div><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Thu, May 1, 2025 at 10:25 AM Greg Walls via wsjt-devel &lt;<a href="mailto:wsj...@li...">wsj...@li...</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">As a former IT Professional of 32 years, why would anyone be on an unsupported platform, especially when upgrades to Windows 11 are free? I wonder if these guys are still driving their first car.<div><br></div><div>Greg</div><div><br><div><div><div><div dir="ltr"><div><br></div><div><br></div>Sent from my iPad</div><div dir="ltr"><br><blockquote type="cite">On May 1, 2025, at 10:06 AM, Uwe, DG2YCB via wsjt-devel &lt;<a href="mailto:wsj...@li..." target="_blank">wsj...@li...</a>&gt; wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">

  
    
  
  
    Hi Andy,<br>
    <br>
    You are causing a lot of confusion with such half-baked statements.
    Like always, and for good reasons, the Windows installation packages
    for all WSJT-X Improved versions are being created using Qt 5.12.12.
    This gives the best possible backwards compatibility (down to
    Windows 7), as well as the rest results in terms of rendering the
    various controls (also when Dark Style is enabled). This tool chain
    has not been changed over the past months. <br>
    <br>
    As you know, we've spent many days of work trying to help you with
    your "special" setup on an old Windows 8.1. system. During these
    tests, you confirmed that all is working well on your Windows 10
    computer. And no one else has ever reported similar issues than you
    with your setup.<br>
    <br>
    Please do me a favor and stop confusing others. If you don't
    understand why we invest months of work to offer a data set for Qt6
    in addition to the existing Qt5 source code, then any further
    discussion about it here is not worthwhile anyway. Other OMs who
    know what this is for are very grateful for this work. And if at
    some point in the future you should buy more modern equipment (maybe
    even Linux-based), then you will be grateful to us one day why we
    were so wise and foresighted in 2024 and 2025 to develop the
    necessary source code for it and keep it up to date.<br>
    <div><br>
      73 de DG2YCB,<br>
      Uwe<br>
      ________________________________________<br>
      German Amateur Radio Station DG2YCB<br>
      Dr. Uwe Risse<br>
      eMail: <a href="mailto:dg...@gm..." target="_blank">dg...@gm...</a><br>
      Info: <a href="http://www.qrz.com/db/DG2YCB" target="_blank">www.qrz.com/db/DG2YCB</a><br>
      <br>
      <br>
    </div>
    <div>Am 01.05.2025 um 13:55 schrieb Andy
      Durbin via wsjt-devel:<br>
    </div>
    <blockquote type="cite">
      
      
      <div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
        "Both <span style="font-weight:700">Windows 7 or 8.x</span>&nbsp;version
        support will not be available for Qt 6. Microsoft discontinued
        the support for both Windows versions some time ago, and as a
        vendor, we can no longer maintain support for these windows
        versions in Qt 6. Windows 7 (both 32bit and 64bit) was supported
        as a target in Qt 5.15 LTS and Windows 8.1 (both 32bit and
        64bit) as a target in Qt 5.12 LTS. This means that we will not
        have 32bit Windows support available. Additionally, it will no
        longer be possible to create <span style="font-weight:700">UWP</span>&nbsp;applications
        on Windows 10."</div>
      <div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
        <br>
      </div>
      <div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
        ref - <a href="https://www.qt.io/blog/qt6-development-hosts-and-targets" id="m_802168972057515211LPlnk307179" target="_blank">
          https://www.qt.io/blog/qt6-development-hosts-and-targets</a></div>
      <div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
        <br>
      </div>
      <div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
        I have found that 2.8.0 improved is not compatible with Win 8.1
        and no one has said that it works for them.</div>
      <div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
        <br>
      </div>
      <div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
        Should the WSJT-X Windows compatibility statement be revised?&nbsp;
        It currently states - "&nbsp;(Windows 7 and later)" which was true
        for 2.7.0 but may not be true if later official releases use
        Qt6.</div>
      <div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
        <br>
      </div>
      <div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
        73,</div>
      <div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
        Andy, k3wyc</div>
      <div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
        <br>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      <fieldset></fieldset>
      <pre>_______________________________________________
wsjt-devel mailing list
<a href="mailto:wsj...@li..." target="_blank">wsj...@li...</a>
<a href="https://lists.sourceforge.net/lists/listinfo/wsjt-devel" target="_blank">https://lists.sourceforge.net/lists/listinfo/wsjt-devel</a>
</pre>
    </blockquote>
    <br>
  
  <u></u><u></u>

<span>_______________________________________________</span><br><span>wsjt-devel mailing list</span><br><span><a href="mailto:wsj...@li..." target="_blank">wsj...@li...</a></span><br><span><a href="https://lists.sourceforge.net/lists/listinfo/wsjt-devel" target="_blank">https://lists.sourceforge.net/lists/listinfo/wsjt-devel</a></span><br></div></blockquote></div></div></div></div></div>_______________________________________________<br>
wsjt-devel mailing list<br>
<a href="mailto:wsj...@li..." target="_blank">wsj...@li...</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/wsjt-devel" rel="noreferrer" target="_blank">https://lists.sourceforge.net/lists/listinfo/wsjt-devel</a><br>
</blockquote></div>
</div></blockquote></div></body></html>

Re: [wsjt-devel] Windows compatibility WSJT-X and improved

[Tom H. <rdr...@gm...>]

Greg,

Your comments are not totally fair.  First, many of us are using computers
that cannot be upgraded to Windows 11, so it isn't FREE.  Sorry, I live on
Social Security and cannot afford to just go out and dump a bunch of money
on a newer computer.  Second, Windows 11 still has compatibility issues
with some of the software I run so I am staying put for now.  Third,
Windows 10 doesn't even play nice at this late stage in its support life
with everything I use!

Yes, I am concerned about what will happen with the .NET framework for
Windows 10 after it is no longer supported as there are several things I
use (like WinLink Express) that may no longer work on Windows 10, but for
now I am where I am and that is that!!

Thanks for seeing others' perspectives!

Tom Hauer, K0YA
ARES Emergency Coordinator
Blanco, Burnet, Llano and Mason Counties
ARRL ARES District 8, STX Section
TDEM RACES District 12-053
Burnet County CERT
319 551-9788
rdr...@gm...
PO Box 1522 (mailing ADR)
11700 E FM 1431 R37
Marble Falls, Tx 78654
EM00wn
Latitude:  30.568805
Longitude:  -98.140287



On Thu, May 1, 2025 at 10:25 AM Greg Walls via wsjt-devel <
wsj...@li...> wrote:

> As a former IT Professional of 32 years, why would anyone be on an
> unsupported platform, especially when upgrades to Windows 11 are free? I
> wonder if these guys are still driving their first car.
>
> Greg
>
>
>
> Sent from my iPad
>
> On May 1, 2025, at 10:06 AM, Uwe, DG2YCB via wsjt-devel <
> wsj...@li...> wrote:
>
>  Hi Andy,
>
> You are causing a lot of confusion with such half-baked statements. Like
> always, and for good reasons, the Windows installation packages for all
> WSJT-X Improved versions are being created using Qt 5.12.12. This gives the
> best possible backwards compatibility (down to Windows 7), as well as the
> rest results in terms of rendering the various controls (also when Dark
> Style is enabled). This tool chain has not been changed over the past
> months.
>
> As you know, we've spent many days of work trying to help you with your
> "special" setup on an old Windows 8.1. system. During these tests, you
> confirmed that all is working well on your Windows 10 computer. And no one
> else has ever reported similar issues than you with your setup.
>
> Please do me a favor and stop confusing others. If you don't understand
> why we invest months of work to offer a data set for Qt6 in addition to the
> existing Qt5 source code, then any further discussion about it here is not
> worthwhile anyway. Other OMs who know what this is for are very grateful
> for this work. And if at some point in the future you should buy more
> modern equipment (maybe even Linux-based), then you will be grateful to us
> one day why we were so wise and foresighted in 2024 and 2025 to develop the
> necessary source code for it and keep it up to date.
>
> 73 de DG2YCB,
> Uwe
> ________________________________________
> German Amateur Radio Station DG2YCB
> Dr. Uwe Risse
> eMail: dg...@gm...
> Info: www.qrz.com/db/DG2YCB
>
>
> Am 01.05.2025 um 13:55 schrieb Andy Durbin via wsjt-devel:
>
> "Both Windows 7 or 8.x version support will not be available for Qt 6.
> Microsoft discontinued the support for both Windows versions some time ago,
> and as a vendor, we can no longer maintain support for these windows
> versions in Qt 6. Windows 7 (both 32bit and 64bit) was supported as a
> target in Qt 5.15 LTS and Windows 8.1 (both 32bit and 64bit) as a target in
> Qt 5.12 LTS. This means that we will not have 32bit Windows support
> available. Additionally, it will no longer be possible to create UWP applications
> on Windows 10."
>
> ref - https://www.qt.io/blog/qt6-development-hosts-and-targets
>
> I have found that 2.8.0 improved is not compatible with Win 8.1 and no one
> has said that it works for them.
>
> Should the WSJT-X Windows compatibility statement be revised?  It
> currently states - " (Windows 7 and later)" which was true for 2.7.0 but
> may not be true if later official releases use Qt6.
>
> 73,
> Andy, k3wyc
>
>
>
> _______________________________________________
> wsjt-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

Re: [wsjt-devel] Windows compatibility WSJT-X and improved

[Larry B. <lar...@ve...>]

$$$ and upgrade difficulty, especially if the CPU is too old.

Larry / W1DYJ


On 5/1/2025 11:22, Greg Walls via wsjt-devel wrote:
> As a former IT Professional of 32 years, why would anyone be on an 
> unsupported platform, especially when upgrades to Windows 11 are free? 
> I wonder if these guys are still driving their first car.
>
> Greg
>
>
>
> Sent from my iPad
>
>> On May 1, 2025, at 10:06 AM, Uwe, DG2YCB via wsjt-devel 
>> <wsj...@li...> wrote:
>>
>>  Hi Andy,
>>
>> You are causing a lot of confusion with such half-baked statements. 
>> Like always, and for good reasons, the Windows installation packages 
>> for all WSJT-X Improved versions are being created using Qt 5.12.12. 
>> This gives the best possible backwards compatibility (down to Windows 
>> 7), as well as the rest results in terms of rendering the various 
>> controls (also when Dark Style is enabled). This tool chain has not 
>> been changed over the past months.
>>
>> As you know, we've spent many days of work trying to help you with 
>> your "special" setup on an old Windows 8.1. system. During these 
>> tests, you confirmed that all is working well on your Windows 10 
>> computer. And no one else has ever reported similar issues than you 
>> with your setup.
>>
>> Please do me a favor and stop confusing others. If you don't 
>> understand why we invest months of work to offer a data set for Qt6 
>> in addition to the existing Qt5 source code, then any further 
>> discussion about it here is not worthwhile anyway. Other OMs who know 
>> what this is for are very grateful for this work. And if at some 
>> point in the future you should buy more modern equipment (maybe even 
>> Linux-based), then you will be grateful to us one day why we were so 
>> wise and foresighted in 2024 and 2025 to develop the necessary source 
>> code for it and keep it up to date.
>>
>> 73 de DG2YCB,
>> Uwe
>> ________________________________________
>> German Amateur Radio Station DG2YCB
>> Dr. Uwe Risse
>> eMail: dg...@gm...
>> Info: www.qrz.com/db/DG2YCB
>>
>>
>> Am 01.05.2025 um 13:55 schrieb Andy Durbin via wsjt-devel:
>>> "Both Windows 7 or 8.x version support will not be available for Qt 
>>> 6. Microsoft discontinued the support for both Windows versions some 
>>> time ago, and as a vendor, we can no longer maintain support for 
>>> these windows versions in Qt 6. Windows 7 (both 32bit and 64bit) was 
>>> supported as a target in Qt 5.15 LTS and Windows 8.1 (both 32bit and 
>>> 64bit) as a target in Qt 5.12 LTS. This means that we will not have 
>>> 32bit Windows support available. Additionally, it will no longer be 
>>> possible to create UWP applications on Windows 10."
>>>
>>> ref - https://www.qt.io/blog/qt6-development-hosts-and-targets
>>>
>>> I have found that 2.8.0 improved is not compatible with Win 8.1 and 
>>> no one has said that it works for them.
>>>
>>> Should the WSJT-X Windows compatibility statement be revised?  It 
>>> currently states - " (Windows 7 and later)" which was true for 2.7.0 
>>> but may not be true if later official releases use Qt6.
>>>
>>> 73,
>>> Andy, k3wyc
>>>
>>>
>>>
>>> _______________________________________________
>>> wsjt-devel mailing list
>>> wsj...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
>> _______________________________________________
>> wsjt-devel mailing list
>> wsj...@li...
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Windows compatibility WSJT-X and improved

[Tom H. <rdr...@gm...>]

Greg,

Your comments are not totally fair.  First, many of us are using computers
that cannot be upgraded to Windows 11, so it isn't FREE.  Sorry, I live on
Social Security and cannot afford to just go out and dump a bunch of money
on a newer computer.  Second, Windows 11 still has compatibility issues
with some of the software I run so I am staying put for now.  Third,
Windows 10 doesn't even play nice at this late stage in its support life
with everything I use!

Yes, I am concerned about what will happen with the .NET framework for
Windows 10 after it is no longer supported as there are several things I
use (like WinLink Express) that may no longer work on Windows 10, but for
now I am where I am and that is that!!

Thanks for seeing others' perspectives!

Tom Hauer, K0YA
ARES Emergency Coordinator
Blanco, Burnet, Llano and Mason Counties
ARRL ARES District 8, STX Section
TDEM RACES District 12-053
Burnet County CERT
319 551-9788
rdr...@gm...
PO Box 1522 (mailing ADR)
11700 E FM 1431 R37
Marble Falls, Tx 78654
EM00wn
Latitude:  30.568805
Longitude:  -98.140287



On Thu, May 1, 2025 at 10:25 AM Greg Walls via wsjt-devel <
wsj...@li...> wrote:

> As a former IT Professional of 32 years, why would anyone be on an
> unsupported platform, especially when upgrades to Windows 11 are free? I
> wonder if these guys are still driving their first car.
>
> Greg
>
>
>
> Sent from my iPad
>
> On May 1, 2025, at 10:06 AM, Uwe, DG2YCB via wsjt-devel <
> wsj...@li...> wrote:
>
>  Hi Andy,
>
> You are causing a lot of confusion with such half-baked statements. Like
> always, and for good reasons, the Windows installation packages for all
> WSJT-X Improved versions are being created using Qt 5.12.12. This gives the
> best possible backwards compatibility (down to Windows 7), as well as the
> rest results in terms of rendering the various controls (also when Dark
> Style is enabled). This tool chain has not been changed over the past
> months.
>
> As you know, we've spent many days of work trying to help you with your
> "special" setup on an old Windows 8.1. system. During these tests, you
> confirmed that all is working well on your Windows 10 computer. And no one
> else has ever reported similar issues than you with your setup.
>
> Please do me a favor and stop confusing others. If you don't understand
> why we invest months of work to offer a data set for Qt6 in addition to the
> existing Qt5 source code, then any further discussion about it here is not
> worthwhile anyway. Other OMs who know what this is for are very grateful
> for this work. And if at some point in the future you should buy more
> modern equipment (maybe even Linux-based), then you will be grateful to us
> one day why we were so wise and foresighted in 2024 and 2025 to develop the
> necessary source code for it and keep it up to date.
>
> 73 de DG2YCB,
> Uwe
> ________________________________________
> German Amateur Radio Station DG2YCB
> Dr. Uwe Risse
> eMail: dg...@gm...
> Info: www.qrz.com/db/DG2YCB
>
>
> Am 01.05.2025 um 13:55 schrieb Andy Durbin via wsjt-devel:
>
> "Both Windows 7 or 8.x version support will not be available for Qt 6.
> Microsoft discontinued the support for both Windows versions some time ago,
> and as a vendor, we can no longer maintain support for these windows
> versions in Qt 6. Windows 7 (both 32bit and 64bit) was supported as a
> target in Qt 5.15 LTS and Windows 8.1 (both 32bit and 64bit) as a target in
> Qt 5.12 LTS. This means that we will not have 32bit Windows support
> available. Additionally, it will no longer be possible to create UWP applications
> on Windows 10."
>
> ref - https://www.qt.io/blog/qt6-development-hosts-and-targets
>
> I have found that 2.8.0 improved is not compatible with Win 8.1 and no one
> has said that it works for them.
>
> Should the WSJT-X Windows compatibility statement be revised?  It
> currently states - " (Windows 7 and later)" which was true for 2.7.0 but
> may not be true if later official releases use Qt6.
>
> 73,
> Andy, k3wyc
>
>
>
> _______________________________________________
> wsjt-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

Re: [wsjt-devel] Windows compatibility WSJT-X and improved

[Greg W. <gw...@po...>]

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">As a former IT Professional of 32 years, why would anyone be on an unsupported platform, especially when upgrades to Windows 11 are free? I wonder if these guys are still driving their first car.<div><br></div><div>Greg</div><div><br><div><div><div><div dir="ltr"><div><br></div><div><br></div>Sent from my iPad</div><div dir="ltr"><br><blockquote type="cite">On May 1, 2025, at 10:06 AM, Uwe, DG2YCB via wsjt-devel &lt;wsj...@li...&gt; wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">

  
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  
  
    Hi Andy,<br>
    <br>
    You are causing a lot of confusion with such half-baked statements.
    Like always, and for good reasons, the Windows installation packages
    for all WSJT-X Improved versions are being created using Qt 5.12.12.
    This gives the best possible backwards compatibility (down to
    Windows 7), as well as the rest results in terms of rendering the
    various controls (also when Dark Style is enabled). This tool chain
    has not been changed over the past months. <br>
    <br>
    As you know, we've spent many days of work trying to help you with
    your "special" setup on an old Windows 8.1. system. During these
    tests, you confirmed that all is working well on your Windows 10
    computer. And no one else has ever reported similar issues than you
    with your setup.<br>
    <br>
    Please do me a favor and stop confusing others. If you don't
    understand why we invest months of work to offer a data set for Qt6
    in addition to the existing Qt5 source code, then any further
    discussion about it here is not worthwhile anyway. Other OMs who
    know what this is for are very grateful for this work. And if at
    some point in the future you should buy more modern equipment (maybe
    even Linux-based), then you will be grateful to us one day why we
    were so wise and foresighted in 2024 and 2025 to develop the
    necessary source code for it and keep it up to date.<br>
    <div class="moz-signature"><br>
      73 de DG2YCB,<br>
      Uwe<br>
      ________________________________________<br>
      German Amateur Radio Station DG2YCB<br>
      Dr. Uwe Risse<br>
      eMail: <a class="moz-txt-link-abbreviated" href="mailto:dg...@gm...">dg...@gm...</a><br>
      Info: <a class="moz-txt-link-abbreviated" href="http://www.qrz.com/db/DG2YCB">www.qrz.com/db/DG2YCB</a><br>
      <br>
      <br>
    </div>
    <div class="moz-cite-prefix">Am 01.05.2025 um 13:55 schrieb Andy
      Durbin via wsjt-devel:<br>
    </div>
    <blockquote type="cite" cite="mid:DM4...@DM...">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      
      <div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
        "Both <span style="font-weight: 700;">Windows 7 or 8.x</span>&nbsp;version
        support will not be available for Qt 6. Microsoft discontinued
        the support for both Windows versions some time ago, and as a
        vendor, we can no longer maintain support for these windows
        versions in Qt 6. Windows 7 (both 32bit and 64bit) was supported
        as a target in Qt 5.15 LTS and Windows 8.1 (both 32bit and
        64bit) as a target in Qt 5.12 LTS. This means that we will not
        have 32bit Windows support available. Additionally, it will no
        longer be possible to create <span style="font-weight: 700;">UWP</span>&nbsp;applications
        on Windows 10."</div>
      <div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
        <br>
      </div>
      <div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
        ref - <a href="https://www.qt.io/blog/qt6-development-hosts-and-targets" id="LPlnk307179" moz-do-not-send="true" class="moz-txt-link-freetext">
          https://www.qt.io/blog/qt6-development-hosts-and-targets</a></div>
      <div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
        <br>
      </div>
      <div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
        I have found that 2.8.0 improved is not compatible with Win 8.1
        and no one has said that it works for them.</div>
      <div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
        <br>
      </div>
      <div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
        Should the WSJT-X Windows compatibility statement be revised?&nbsp;
        It currently states - "&nbsp;(Windows 7 and later)" which was true
        for 2.7.0 but may not be true if later official releases use
        Qt6.</div>
      <div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
        <br>
      </div>
      <div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
        73,</div>
      <div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
        Andy, k3wyc</div>
      <div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
        <br>
      </div>
      <br>
      <fieldset class="moz-mime-attachment-header"></fieldset>
      <br>
      <fieldset class="moz-mime-attachment-header"></fieldset>
      <pre wrap="" class="moz-quote-pre">_______________________________________________
wsjt-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wsj...@li...">wsj...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/wsjt-devel">https://lists.sourceforge.net/lists/listinfo/wsjt-devel</a>
</pre>
    </blockquote>
    <br>
  
  <lt-container></lt-container>

<span>_______________________________________________</span><br><span>wsjt-devel mailing list</span><br><span>wsj...@li...</span><br><span>https://lists.sourceforge.net/lists/listinfo/wsjt-devel</span><br></div></blockquote></div></div></div></div></body></html>

Re: [wsjt-devel] Windows compatibility WSJT-X and improved

[Uwe, D. <dg...@gm...>]

Hi Andy,

You are causing a lot of confusion with such half-baked statements. Like 
always, and for good reasons, the Windows installation packages for all 
WSJT-X Improved versions are being created using Qt 5.12.12. This gives 
the best possible backwards compatibility (down to Windows 7), as well 
as the rest results in terms of rendering the various controls (also 
when Dark Style is enabled). This tool chain has not been changed over 
the past months.

As you know, we've spent many days of work trying to help you with your 
"special" setup on an old Windows 8.1. system. During these tests, you 
confirmed that all is working well on your Windows 10 computer. And no 
one else has ever reported similar issues than you with your setup.

Please do me a favor and stop confusing others. If you don't understand 
why we invest months of work to offer a data set for Qt6 in addition to 
the existing Qt5 source code, then any further discussion about it here 
is not worthwhile anyway. Other OMs who know what this is for are very 
grateful for this work. And if at some point in the future you should 
buy more modern equipment (maybe even Linux-based), then you will be 
grateful to us one day why we were so wise and foresighted in 2024 and 
2025 to develop the necessary source code for it and keep it up to date.

73 de DG2YCB,
Uwe
________________________________________
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg...@gm...
Info: www.qrz.com/db/DG2YCB


Am 01.05.2025 um 13:55 schrieb Andy Durbin via wsjt-devel:
> "Both Windows 7 or 8.x version support will not be available for Qt 6. 
> Microsoft discontinued the support for both Windows versions some time 
> ago, and as a vendor, we can no longer maintain support for these 
> windows versions in Qt 6. Windows 7 (both 32bit and 64bit) was 
> supported as a target in Qt 5.15 LTS and Windows 8.1 (both 32bit and 
> 64bit) as a target in Qt 5.12 LTS. This means that we will not have 
> 32bit Windows support available. Additionally, it will no longer be 
> possible to create UWP applications on Windows 10."
>
> ref - https://www.qt.io/blog/qt6-development-hosts-and-targets
>
> I have found that 2.8.0 improved is not compatible with Win 8.1 and no 
> one has said that it works for them.
>
> Should the WSJT-X Windows compatibility statement be revised? It 
> currently states - " (Windows 7 and later)" which was true for 2.7.0 
> but may not be true if later official releases use Qt6.
>
> 73,
> Andy, k3wyc
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Windows compatibility WSJT-X and improved

[Adrian <vk...@gm...>]

Apart from Uwe's special QT6 test branch, which we gave up on recently 
until QT6 is fixed, ... we are building with QT5,

which are the releases yes ? I do not understand the concern with 
existing  regarding QT6 support ?


73


vk4tux

On 1/5/25 23:03, Charles Suckling via wsjt-devel wrote:
> Andy
>
> 2.8.0 works fine on Windows 7.  I use it daily.
>
> 73
>
> Charlie
>
> On Thu, 1 May 2025 at 14:34, Andy Durbin via wsjt-devel 
> <wsj...@li...> wrote:
>
>     "Both Windows 7 or 8.x version support will not be available for
>     Qt 6. Microsoft discontinued the support for both Windows versions
>     some time ago, and as a vendor, we can no longer maintain support
>     for these windows versions in Qt 6. Windows 7 (both 32bit and
>     64bit) was supported as a target in Qt 5.15 LTS and Windows 8.1
>     (both 32bit and 64bit) as a target in Qt 5.12 LTS. This means that
>     we will not have 32bit Windows support available. Additionally, it
>     will no longer be possible to create UWP applications on Windows 10."
>
>     ref - https://www.qt.io/blog/qt6-development-hosts-and-targets
>
>     I have found that 2.8.0 improved is not compatible with Win 8.1
>     and no one has said that it works for them.
>
>     Should the WSJT-X Windows compatibility statement be revised?  It
>     currently states - " (Windows 7 and later)" which was true for
>     2.7.0 but may not be true if later official releases use Qt6.
>
>     73,
>     Andy, k3wyc
>
>     _______________________________________________
>     wsjt-devel mailing list
>     wsj...@li...
>     https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Windows compatibility WSJT-X and improved

[Charles S. <g3...@gm...>]

Andy

2.8.0 works fine on Windows 7.  I use it daily.

73

Charlie

On Thu, 1 May 2025 at 14:34, Andy Durbin via wsjt-devel <
wsj...@li...> wrote:

> "Both Windows 7 or 8.x version support will not be available for Qt 6.
> Microsoft discontinued the support for both Windows versions some time ago,
> and as a vendor, we can no longer maintain support for these windows
> versions in Qt 6. Windows 7 (both 32bit and 64bit) was supported as a
> target in Qt 5.15 LTS and Windows 8.1 (both 32bit and 64bit) as a target in
> Qt 5.12 LTS. This means that we will not have 32bit Windows support
> available. Additionally, it will no longer be possible to create UWP applications
> on Windows 10."
>
> ref - https://www.qt.io/blog/qt6-development-hosts-and-targets
>
> I have found that 2.8.0 improved is not compatible with Win 8.1 and no one
> has said that it works for them.
>
> Should the WSJT-X Windows compatibility statement be revised?  It
> currently states - " (Windows 7 and later)" which was true for 2.7.0 but
> may not be true if later official releases use Qt6.
>
> 73,
> Andy, k3wyc
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

[wsjt-devel] Windows compatibility WSJT-X and improved

[Andy D. <a.d...@ms...>]

"Both Windows 7 or 8.x version support will not be available for Qt 6. Microsoft discontinued the support for both Windows versions some time ago, and as a vendor, we can no longer maintain support for these windows versions in Qt 6. Windows 7 (both 32bit and 64bit) was supported as a target in Qt 5.15 LTS and Windows 8.1 (both 32bit and 64bit) as a target in Qt 5.12 LTS. This means that we will not have 32bit Windows support available. Additionally, it will no longer be possible to create UWP applications on Windows 10."

ref - https://www.qt.io/blog/qt6-development-hosts-and-targets

I have found that 2.8.0 improved is not compatible with Win 8.1 and no one has said that it works for them.

Should the WSJT-X Windows compatibility statement be revised?  It currently states - " (Windows 7 and later)" which was true for 2.7.0 but may not be true if later official releases use Qt6.

73,
Andy, k3wyc

Re: [wsjt-devel] No Comm from WSJT-X

[Wil <vd...@xs...>]

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Seems familiar. Switch of the firewall to check.<div><br></div><div>Wil</div><div>PE3T<br id="lineBreakAtBeginningOfSignature"><div dir="ltr">Verstuurd vanaf mijn iPhone</div><div dir="ltr"><br><blockquote type="cite">Op 30 apr 2025 om 22:17 heeft Tom Hauer via wsjt-devel &lt;wsj...@li...&gt; het volgende geschreven:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div>This is new and could be the result of a Windows 10 update. I always use UDP to communicate between WSJT-X (Version 7.0) and N3FJT ACLOG (V7.0.11).&nbsp; I used 127.0.0.1 and 2237.&nbsp; That stopped working and I changed to 224.0.0.1 and 2237.&nbsp; That works intermittently, NEVER on first contact, maybe on those after the first.</div><div><br></div><div>Has anybody else seen this?&nbsp; Not just one computer either, same problem on others too.</div><div><br></div><div>The only thing that has changed is the Windows 10 updates I get.&nbsp; No other settings have been changed.</div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><blockquote type="cite" style="color:rgb(34,34,34)"><div dir="ltr"><div dir="ltr"><div dir="ltr">Tom Hauer, K0YA<div>ARES Emergency Coordinator</div><div>Blanco, Burnet, Llano and Mason Counties</div><div>ARRL ARES District 8, STX Section</div><div>TDEM RACES District 12-053</div><div>Burnet County CERT</div><div>319 551-9788<br></div><div><a href="mailto:rdr...@gm..." style="color:rgb(17,85,204)" target="_blank">rdr...@gm...</a></div><div>PO Box 1522 (mailing ADR)</div><div>11700 E FM 1431 R37</div><div>Marble Falls, Tx 78654</div><div>EM00wn</div><div>Latitude:&nbsp; 30.568805</div><div>Longitude:&nbsp; -98.140287</div></div></div></div></blockquote></div></div></div></div>
<span>_______________________________________________</span><br><span>wsjt-devel mailing list</span><br><span>wsj...@li...</span><br><span>https://lists.sourceforge.net/lists/listinfo/wsjt-devel</span><br></div></blockquote></div></body></html>

[wsjt-devel] v2.8.0 "250501" available

[Uwe, D. <dg...@gm...>]

Dear Users,

I'm glad to announce a "250501" update of WSJT-X Improved 2.8.0, which 
brings the following improvements:

In programs QMAP and MAP65:

  * Introduction of a new "LiveCQ" feature. It allows messages that you
    decode with QMAP and/or MAP65 to be uploaded automatically via the
    internet to the new website: https://w3sz.com/livecq.html
    <https://w3sz.com/livecq.html>. The idea is to provide spots of
    active EME stations so that others will know where to look. Read
    section 16.14 of the User Guide
    <https://wsjt-x-improved.sourceforge.io/wsjtx-main_en.html#_livecq>
    for more information.
  * Fixed a long-standing flaw in QMAP which could cause the program to
    crash after a few hours of operation.

In program WSJT-X:

  * The dial frequency can now be controlled via mouse (useful for EME
    operations, or when a DXpedition is not on the standard DXp QRGs). 
    If you hover the mouse pointer over the frequency display, you have
    two new options:
      o Left-click to decrease the rig dial frequency by 1 kHz, or
        right-click to increase it by 1 kHz.
      o Turn the mouse wheel to scroll the kHz values.
  * You can now choose between “worked today” and “worked today or
    yesterday” for the three respective Hide/Ignore/Highlight Quick
    Filters. Switching is done via a new checkbox under Settings/Filters.
  * Fixed some inconsistencies around the Tx watchdog. The countdown now
    only starts when Enable Tx is active (important for Wait & Call).
  * Repeated use of the rig (ATU) tuning function now works more reliably.
  * Minor bug fixes and performance improvements.
  * Slightly more detailed explanations in the WSJT-X Improved User
    Guide <https://wsjt-x-improved.sourceforge.io/wsjtx-main_en.html>.
  * Update to Hamlib 4.6.2.
  * Last not least: The Qt6 source code can now also be compiled with Qt
    6.8.x (important for Linux Fedora, etc.).

As usual, you will *find the downloadable files on my SourceForge page* 
<https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/>. 
Here are the direct links to download the most important packages:

  * *wsjtx-2.8.0-win64_improved_PLUS_250501*
    <https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_PLUS_250501.exe/download>*.exe
    <https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_PLUS_250501.exe/download>
    (Windows 64-bit, WSJT-X GUI)*
  * *wsjtx-2.8.0-win64_improved_AL_PLUS_25**0501*
    <https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_AL_PLUS_250501.exe/download>*.exe
    <https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_AL_PLUS_250501.exe/download>
    (Windows 64-bit, AL GUI)*
  * *wsjtx-**2.8.0-win64**_improved_widescreen_PLUS_25**0501*
    <https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_widescreen_PLUS_250501.exe/download>*.exe
    <https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/wsjtx-2.8.0-win64_improved_widescreen_PLUS_250501.exe/download>
    (Windows 64-bit, widescreen GUI)*
  * *wsjtx_2.8.0_improved_PLUS_**25**0501*
    <https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/Linux/wsjtx_2.8.0_improved_PLUS_250501_amd64.deb/download>*_amd64.deb
    <https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/Linux/wsjtx_2.8.0_improved_PLUS_250501_amd64.deb/download>
    (Linux**, WSJT-X GUI**)*
  * *wsjtx_2.8.0_improved_AL_PLUS_**25**0501*
    <https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/Linux/wsjtx_2.8.0_improved_AL_PLUS_250501_amd64.deb/download>*_amd64.deb
    <https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/Linux/wsjtx_2.8.0_improved_AL_PLUS_250501_amd64.deb/download>
    (Linux**, AL GUI**)*
  * *wsjtx-2.8.0_improved_PLUS_**25**0501*
    <https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/macOS/wsjtx-2.8.0_improved_PLUS_250501_Darwin.dmg/download>*_Darwin.dmg
    <https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/macOS/wsjtx-2.8.0_improved_PLUS_250501_Darwin.dmg/download>
    (macOS x86_64**, WSJT-X GUI**)*
  * *wsjtx-2.8.0_improved_PLUS_**25**0501*
    <https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/macOS/wsjtx-2.8.0_improved_PLUS_250501_M1.zip/download>*_M1.zip
    <https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v2.8.0/macOS/wsjtx-2.8.0_improved_PLUS_250501_M1.zip/download>
    (macOS M1**, WSJT-X GUI**)*

Thanks to everyone who contributed to this great new release!

73 de DG2YCB,
Uwe
________________________________________
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg...@gm...
Info: www.qrz.com/db/DG2YCB

[wsjt-devel] No Comm from WSJT-X

[Tom H. <rdr...@gm...>]

This is new and could be the result of a Windows 10 update. I always use
UDP to communicate between WSJT-X (Version 7.0) and N3FJT ACLOG (V7.0.11).
I used 127.0.0.1 and 2237.  That stopped working and I changed to 224.0.0.1
and 2237.  That works intermittently, NEVER on first contact, maybe on
those after the first.

Has anybody else seen this?  Not just one computer either, same problem on
others too.

The only thing that has changed is the Windows 10 updates I get.  No other
settings have been changed.

Tom Hauer, K0YA
ARES Emergency Coordinator
Blanco, Burnet, Llano and Mason Counties
ARRL ARES District 8, STX Section
TDEM RACES District 12-053
Burnet County CERT
319 551-9788
rdr...@gm...
PO Box 1522 (mailing ADR)
11700 E FM 1431 R37
Marble Falls, Tx 78654
EM00wn
Latitude:  30.568805
Longitude:  -98.140287

Re: [wsjt-devel] Subject: Feature request: Audio device selection

[DG2YCB <DG...@gm...>]

Hi Erik,

Feel free to try it out. As you know, the source code is publicly 
available, and I am always open to useful code improvements.

73 de DG2YCB,
Uwe
_________________________________________
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: DG...@gm...
Info: www.qrz.com/db/DG2YCB

Am 28. April 2025 22:37:12 schrieb "Erik Icket" <run...@gm...>:
> Hi Uwe,
>
> I can understand that the AudioDeviceInfo for the AudioInput or AudioOutput 
> can become invalid within WSJTX but wouldn’t a fresh 
> QAudioDeviceInfo::availableDevices find it back ?
> Note that the soundcard with its explicit name (f.e. “USB Audio CODEC”) is 
> not gone but the device info is gone or the device list is now incorrect.
>
> I have observed this in two situations which are easily reproducible on my 
> end :
>
> When you connect or disconnect a PNP device (or it goes to sleep ..), a 
> HDMI monitor (with sound) goes on or off
> At a remote station, when one connects or disconnects with Windows remote 
> desktop.
>
> Again, and this is only for Windows, my suggestion would be to lock the 
> audio on its explicit device name, and do a fresh search if the device is lost.
>
> My apologies if I have it all wrong …
>
> 73’s Erik
> ON4PB
>
> From: DG2YCB <DG...@gm...>
> Sent: Monday, 28 April 2025 19:35
> To: WSJT software development <wsj...@li...>
> Cc: Erik Icket <run...@gm...>
> Subject: Re: [wsjt-devel] Subject: Feature request: Output audio device 
> selection
>
> Erik,
>
> Locking anything in our program doesn't help when this device is no longer 
> available on OS level. You would then only see something like "... (not 
> found)".
>
> 73 de DG2YCB,
> Uwe
> _________________________________________
> German Amateur Radio Station DG2YCB
> Dr. Uwe Risse
> eMail: DG...@gm...
> Info: www.qrz.com/db/DG2YCB
>
>
> Am 28. April 2025 13:45:54 schrieb Erik Icket via wsjt-devel 
> <wsj...@li...>:
>
> May I suggest a different feature update to the audio / soundcard / input -
> output device selection logic ?
>
> What about the ability to lock the selection for the input / output
> soundcard ?
>
> This to prevent WSJTX losing the sound device :
> - whenever Windows re-assigns / re-enumerates the devices after a USB PNP
> device update
> - or worse, whenever you connect to a remote desktop where WSJTX is running.
>
> Once the audio devices are locked in the settings panel, and would be lost,
> WSJTX could go into a retry cycle to recover the devices ...
>
> Any thoughts ?
> 73's Erik
> ON4PB
>
> ------------------------------
>
> Message: 3
> Date: Mon, 28 Apr 2025 12:34:31 +0200
> From: "Uwe, DG2YCB" <dg...@gm...>
> To: WSJT software development <wsj...@li...>
> Subject: Re: [wsjt-devel] Subject: Feature request: Output audio
> device selection for alert sounds
> Message-ID: <18f...@gm...>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
> Bonjour Olivier,
>
> Thanks for your suggestion. I would just like to briefly explain why we have
> not done this so far.
> Firstly: A second sound card selection menu would not solve the fact that
> alerts can only be played if you have at least 2 sound cards on your PC.
> Secondly, something like this would only make things more complicated.
> Because then it would have to be programmed in such a way that the settings
> in both are mutually exclusive. Imagine Windows resetting all sound card
> numbering after a Windows update (or after you have plugged in a new USB
> audio device). This would then cause quite a mess, because you have to
> correct two sets of settings which are dependent of each other.
> Thirdly: Honestly, many OMs don't really understand these technical details
> one way or another. That's why the alerts are switched off by default. This
> means that those OMs who have never heard of an Audio Alerts feature and
> have never reached the Alerts tab in Settings will find the Soundcard menu
> in Settings/Audio exactly as it has always been.
>
> However, we have now explained the correct audio settings in more detail in
> the User Guide for the upcoming ?250501? update. It will be released on
> Thursday.
>
> Allow me one general comment: My recommendation is that Windows users who
> also use JTAlert should use the audio alerts from JTAlert, because JTAlert
> does this best. The Alerts feature in WSJT-X Improved was primarily
> developed for Linux and macOS, because JTAlert is only available for
> Windows, and for those OMs who do not use JTAlert.
>
> 73 de DG2YCB,
> Uwe
> ________________________________________
> German Amateur Radio Station DG2YCB
> Dr. Uwe Risse
> eMail: dg...@gm...
> Info: www.qrz.com/db/DG2YCB
>
>
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Subject: Feature request: Audio device selection

[Erik I. <run...@gm...>]

Hi Uwe,

 

I can understand that the AudioDeviceInfo for the AudioInput or AudioOutput
can become invalid within WSJTX but wouldn't a fresh
QAudioDeviceInfo::availableDevices find it back ?

Note that the soundcard with its explicit name (f.e. "USB Audio CODEC") is
not gone but the device info is gone or the device list is now incorrect.

 

I have observed this in two situations which are easily reproducible on my
end :

 

*	When you connect or disconnect a PNP device (or it goes to sleep
..), a HDMI monitor (with sound) goes on or off
*	At a remote station, when one connects or disconnects with Windows
remote desktop.

 

Again, and this is only for Windows, my suggestion would be to lock the
audio on its explicit device name, and do a fresh search if the device is
lost.

 

My apologies if I have it all wrong .

 

73's Erik

ON4PB

 

From: DG2YCB <DG...@gm...> 
Sent: Monday, 28 April 2025 19:35
To: WSJT software development <wsj...@li...>
Cc: Erik Icket <run...@gm...>
Subject: Re: [wsjt-devel] Subject: Feature request: Output audio device
selection

 

Erik,

 

Locking anything in our program doesn't help when this device is no longer
available on OS level. You would then only see something like "... (not
found)".

 

73 de DG2YCB,

Uwe

_________________________________________

German Amateur Radio Station DG2YCB

Dr. Uwe Risse

eMail: DG...@gm... <mailto:DG...@gm...> 

Info: www.qrz.com/db/DG2YCB <http://www.qrz.com/db/DG2YCB> 

 

 

Am 28. April 2025 13:45:54 schrieb Erik Icket via wsjt-devel
<wsj...@li... <mailto:wsj...@li...>
>:

 

May I suggest a different feature update to the audio / soundcard / input -

output device selection logic ?

 

What about the ability to lock the selection for the input / output

soundcard ?

 

This to prevent WSJTX losing the sound device :

- whenever Windows re-assigns / re-enumerates the devices after a USB PNP

device update

- or worse, whenever you connect to a remote desktop where WSJTX is running.

 

Once the audio devices are locked in the settings panel, and would be lost,

WSJTX could go into a retry cycle to recover the devices ...

 

Any thoughts ?

73's Erik

ON4PB

 

------------------------------

 

Message: 3

Date: Mon, 28 Apr 2025 12:34:31 +0200

From: "Uwe, DG2YCB" <dg...@gm... <mailto:dg...@gm...> >

To: WSJT software development <wsj...@li...
<mailto:wsj...@li...> >

Subject: Re: [wsjt-devel] Subject: Feature request: Output audio

 device selection for alert sounds

Message-ID: <18f...@gm...
<mailto:18f...@gm...> >

Content-Type: text/plain; charset="utf-8"; Format="flowed"

 

Bonjour Olivier,

 

Thanks for your suggestion. I would just like to briefly explain why we have

not done this so far.

Firstly: A second sound card selection menu would not solve the fact that

alerts can only be played if you have at least 2 sound cards on your PC.

Secondly, something like this would only make things more complicated. 

Because then it would have to be programmed in such a way that the settings

in both are mutually exclusive. Imagine Windows resetting all sound card

numbering after a Windows update (or after you have plugged in a new USB

audio device). This would then cause quite a mess, because you have to

correct two sets of settings which are dependent of each other.

Thirdly: Honestly, many OMs don't really understand these technical details

one way or another. That's why the alerts are switched off by default. This

means that those OMs who have never heard of an Audio Alerts feature and

have never reached the Alerts tab in Settings will find the Soundcard menu

in Settings/Audio exactly as it has always been.

 

However, we have now explained the correct audio settings in more detail in

the User Guide for the upcoming ?250501? update. It will be released on

Thursday.

 

Allow me one general comment: My recommendation is that Windows users who

also use JTAlert should use the audio alerts from JTAlert, because JTAlert

does this best. The Alerts feature in WSJT-X Improved was primarily

developed for Linux and macOS, because JTAlert is only available for

Windows, and for those OMs who do not use JTAlert.

 

73 de DG2YCB,

Uwe

________________________________________

German Amateur Radio Station DG2YCB

Dr. Uwe Risse

eMail: dg...@gm... <mailto:dg...@gm...> 

Info: www.qrz.com/db/DG2YCB <http://www.qrz.com/db/DG2YCB> 

 

 

 

 

 

_______________________________________________

wsjt-devel mailing list

wsj...@li... <mailto:wsj...@li...> 

https://lists.sourceforge.net/lists/listinfo/wsjt-devel

 

Re: [wsjt-devel] Subject: Feature request: Output audio device selection

[DG2YCB <DG...@gm...>]

Erik,

Locking anything in our program doesn't help when this device is no longer 
available on OS level. You would then only see something like "... (not 
found)".

73 de DG2YCB,
Uwe
_________________________________________
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: DG...@gm...
Info: www.qrz.com/db/DG2YCB

Am 28. April 2025 13:45:54 schrieb Erik Icket via wsjt-devel 
<wsj...@li...>:

> May I suggest a different feature update to the audio / soundcard / input -
> output device selection logic ?
>
> What about the ability to lock the selection for the input / output
> soundcard ?
>
> This to prevent WSJTX losing the sound device :
> - whenever Windows re-assigns / re-enumerates the devices after a USB PNP
> device update
> - or worse, whenever you connect to a remote desktop where WSJTX is running.
>
> Once the audio devices are locked in the settings panel, and would be lost,
> WSJTX could go into a retry cycle to recover the devices ...
>
> Any thoughts ?
> 73's Erik
> ON4PB
>
> ------------------------------
>
> Message: 3
> Date: Mon, 28 Apr 2025 12:34:31 +0200
> From: "Uwe, DG2YCB" <dg...@gm...>
> To: WSJT software development <wsj...@li...>
> Subject: Re: [wsjt-devel] Subject: Feature request: Output audio
> device selection for alert sounds
> Message-ID: <18f...@gm...>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
> Bonjour Olivier,
>
> Thanks for your suggestion. I would just like to briefly explain why we have
> not done this so far.
> Firstly: A second sound card selection menu would not solve the fact that
> alerts can only be played if you have at least 2 sound cards on your PC.
> Secondly, something like this would only make things more complicated.
> Because then it would have to be programmed in such a way that the settings
> in both are mutually exclusive. Imagine Windows resetting all sound card
> numbering after a Windows update (or after you have plugged in a new USB
> audio device). This would then cause quite a mess, because you have to
> correct two sets of settings which are dependent of each other.
> Thirdly: Honestly, many OMs don't really understand these technical details
> one way or another. That's why the alerts are switched off by default. This
> means that those OMs who have never heard of an Audio Alerts feature and
> have never reached the Alerts tab in Settings will find the Soundcard menu
> in Settings/Audio exactly as it has always been.
>
> However, we have now explained the correct audio settings in more detail in
> the User Guide for the upcoming ?250501? update. It will be released on
> Thursday.
>
> Allow me one general comment: My recommendation is that Windows users who
> also use JTAlert should use the audio alerts from JTAlert, because JTAlert
> does this best. The Alerts feature in WSJT-X Improved was primarily
> developed for Linux and macOS, because JTAlert is only available for
> Windows, and for those OMs who do not use JTAlert.
>
> 73 de DG2YCB,
> Uwe
> ________________________________________
> German Amateur Radio Station DG2YCB
> Dr. Uwe Risse
> eMail: dg...@gm...
> Info: www.qrz.com/db/DG2YCB
>
>
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Subject: Feature request: Output audio device selection

[Erik I. <run...@gm...>]

May I suggest a different feature update to the audio / soundcard / input -
output device selection logic ?

What about the ability to lock the selection for the input / output
soundcard ?

This to prevent WSJTX losing the sound device :
- whenever Windows re-assigns / re-enumerates the devices after a USB PNP
device update
- or worse, whenever you connect to a remote desktop where WSJTX is running.

Once the audio devices are locked in the settings panel, and would be lost,
WSJTX could go into a retry cycle to recover the devices ...

Any thoughts ?
73's Erik
ON4PB

------------------------------

Message: 3
Date: Mon, 28 Apr 2025 12:34:31 +0200
From: "Uwe, DG2YCB" <dg...@gm...>
To: WSJT software development <wsj...@li...>
Subject: Re: [wsjt-devel] Subject: Feature request: Output audio
	device selection for alert sounds
Message-ID: <18f...@gm...>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

Bonjour Olivier,

Thanks for your suggestion. I would just like to briefly explain why we have
not done this so far.
Firstly: A second sound card selection menu would not solve the fact that
alerts can only be played if you have at least 2 sound cards on your PC.
Secondly, something like this would only make things more complicated. 
Because then it would have to be programmed in such a way that the settings
in both are mutually exclusive. Imagine Windows resetting all sound card
numbering after a Windows update (or after you have plugged in a new USB
audio device). This would then cause quite a mess, because you have to
correct two sets of settings which are dependent of each other.
Thirdly: Honestly, many OMs don't really understand these technical details
one way or another. That's why the alerts are switched off by default. This
means that those OMs who have never heard of an Audio Alerts feature and
have never reached the Alerts tab in Settings will find the Soundcard menu
in Settings/Audio exactly as it has always been.

However, we have now explained the correct audio settings in more detail in
the User Guide for the upcoming ?250501? update. It will be released on
Thursday.

Allow me one general comment: My recommendation is that Windows users who
also use JTAlert should use the audio alerts from JTAlert, because JTAlert
does this best. The Alerts feature in WSJT-X Improved was primarily
developed for Linux and macOS, because JTAlert is only available for
Windows, and for those OMs who do not use JTAlert.

73 de DG2YCB,
Uwe
________________________________________
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg...@gm...
Info: www.qrz.com/db/DG2YCB

Re: [wsjt-devel] Subject: Feature request: Output audio device selection for alert sounds

[Alan <al...@al...>]

That resetting after update has happened to my setup, and USB device 
enumeration can be an issue unless it's plugged in permanently.

Alan G0TLK, sent from my mobile device
On 28 April 2025 11:37:16 "Uwe, DG2YCB via wsjt-devel" 
<wsj...@li...> wrote:

> Bonjour Olivier,
>
> Thanks for your suggestion. I would just like to briefly explain why we
> have not done this so far.
> Firstly: A second sound card selection menu would not solve the fact
> that alerts can only be played if you have at least 2 sound cards on
> your PC.
> Secondly, something like this would only make things more complicated.
> Because then it would have to be programmed in such a way that the
> settings in both are mutually exclusive. Imagine Windows resetting all
> sound card numbering after a Windows update (or after you have plugged
> in a new USB audio device). This would then cause quite a mess, because
> you have to correct two sets of settings which are dependent of each other

Re: [wsjt-devel] Subject: Feature request: Output audio device selection for alert sounds

[Uwe, D. <dg...@gm...>]

Bonjour Olivier,

Thanks for your suggestion. I would just like to briefly explain why we 
have not done this so far.
Firstly: A second sound card selection menu would not solve the fact 
that alerts can only be played if you have at least 2 sound cards on 
your PC.
Secondly, something like this would only make things more complicated. 
Because then it would have to be programmed in such a way that the 
settings in both are mutually exclusive. Imagine Windows resetting all 
sound card numbering after a Windows update (or after you have plugged 
in a new USB audio device). This would then cause quite a mess, because 
you have to correct two sets of settings which are dependent of each other.
Thirdly: Honestly, many OMs don't really understand these technical 
details one way or another. That's why the alerts are switched off by 
default. This means that those OMs who have never heard of an Audio 
Alerts feature and have never reached the Alerts tab in Settings will 
find the Soundcard menu in Settings/Audio exactly as it has always been.

However, we have now explained the correct audio settings in more detail 
in the User Guide for the upcoming “250501” update. It will be released 
on Thursday.

Allow me one general comment: My recommendation is that Windows users 
who also use JTAlert should use the audio alerts from JTAlert, because 
JTAlert does this best. The Alerts feature in WSJT-X Improved was 
primarily developed for Linux and macOS, because JTAlert is only 
available for Windows, and for those OMs who do not use JTAlert.

73 de DG2YCB,
Uwe
________________________________________
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg...@gm...
Info: www.qrz.com/db/DG2YCB


Am 26.04.2025 um 18:34 schrieb F4HTB via wsjt-devel:
> Hello everyone,
>
> I would like to suggest a small but useful improvement for WSJT-X 
> regarding audio handling.
>
> Currently, WSJT-X uses the system’s default audio output to play alert 
> sounds.
> In some setups, this can lead to problems: I have noticed, both 
> personally and among other operators, that when using the same audio 
> interface for radio transmission and for WSJT-X, the alert sounds may 
> accidentally be transmitted over the air.
>
> I have observed this behavior both under Windows and Linux.
>
> To prevent this issue, I propose adding an option in the Audio tab of 
> the configuration menu to allow users to select a specific output 
> device for alert sounds, independently of the device used for radio 
> transmissions.
>
> For reference, Fldigi has provided this capability for a long time, 
> which helps avoid this kind of problem.
>
> Thank you very much for considering this request, and thank you for 
> all the excellent work on WSJT-X.
>
> 73,
>
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Subject: Feature request: Output audio device selection for alert sounds

[F4HTB <ol...@f4...>]

Hello,

Indeed, there was no sound alert; it was caused by other third-party 
software, namely DX Maps.
Sorry for this mistake.

73!


Le 28/04/2025 à 08:30, Alan via wsjt-devel a écrit :
> On my W11 PC not so.
>
> I've got complete control over the soundcard, through both Windows 
> settings and its driver.
>
> Changes in one of those are reflected in the other.
>
> Other hardware may vary.
>
> Alan G0TLK, sent from my mobile device
>
> On 27 April 2025 23:16:21 Fons Adriaensen via wsjt-devel 
> <wsj...@li...> wrote:
>
>> On Sun, Apr 27, 2025 at 09:15:40PM +0100, alan2--- via wsjt-devel wrote:
>>
>>> I do it the other way around - cheap dongle set as Windows default, 
>>> in-built
>>> soundcard for WSJT-X and SDR's as on my PC it's better resolution etc.
>>
>> Using the default Windows device for SDR (or anything technical) might
>> be a bad idea. Signals to/from it may be mangled by 'advanced audio
>> processing' - stereo widening, binaural rendering, speech enhancement,
>> noise reduction, automatic gain changes, echo candellation... That same
>> device will also be used for all desktop beeps and jingles. You basically
>> have no control over it.
>>
>> The same may be true on Macs and even on Linux machines depending
>> on which desktop flavour is used.
>>
>> Using a dedicated device with fixed levels and controlled only by
>> the SDR application will usually provide much more stable results.
>>
>> Ciao,
>>
>> -- 
>> FA
>>
>>
>>
>> _______________________________________________
>> wsjt-devel mailing list
>> wsj...@li...
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Subject: Feature request: Output audio device selection for alert sounds

[Alan <al...@al...>]

On my W11 PC not so.

I've got complete control over the soundcard, through both Windows settings 
and its driver.

Changes in one of those are reflected in the other.

Other hardware may vary.

Alan G0TLK, sent from my mobile device
On 27 April 2025 23:16:21 Fons Adriaensen via wsjt-devel 
<wsj...@li...> wrote:

> On Sun, Apr 27, 2025 at 09:15:40PM +0100, alan2--- via wsjt-devel wrote:
>
>> I do it the other way around - cheap dongle set as Windows default, in-built
>> soundcard for WSJT-X and SDR's as on my PC it's better resolution etc.
>
> Using the default Windows device for SDR (or anything technical) might
> be a bad idea. Signals to/from it may be mangled by 'advanced audio
> processing' - stereo widening, binaural rendering, speech enhancement,
> noise reduction, automatic gain changes, echo candellation... That same
> device will also be used for all desktop beeps and jingles. You basically
> have no control over it.
>
> The same may be true on Macs and even on Linux machines depending
> on which desktop flavour is used.
>
> Using a dedicated device with fixed levels and controlled only by
> the SDR application will usually provide much more stable results.
>
> Ciao,
>
> --
> FA
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Subject: Feature request: Output audio device selection for alert sounds

[Fons A. <fo...@li...>]

On Sun, Apr 27, 2025 at 09:15:40PM +0100, alan2--- via wsjt-devel wrote:

> I do it the other way around - cheap dongle set as Windows default, in-built
> soundcard for WSJT-X and SDR's as on my PC it's better resolution etc.

Using the default Windows device for SDR (or anything technical) might
be a bad idea. Signals to/from it may be mangled by 'advanced audio
processing' - stereo widening, binaural rendering, speech enhancement,
noise reduction, automatic gain changes, echo candellation... That same
device will also be used for all desktop beeps and jingles. You basically
have no control over it. 

The same may be true on Macs and even on Linux machines depending
on which desktop flavour is used. 

Using a dedicated device with fixed levels and controlled only by
the SDR application will usually provide much more stable results.

Ciao,

-- 
FA

Re: [wsjt-devel] Subject: Feature request: Output audio device selection for alert sounds

[<al...@al...>]

I do it the other way around - cheap dongle set as Windows default, 
in-built soundcard for WSJT-X and SDR's as on my PC it's better 
resolution etc.

Each PC hardware is probably different but might be worth a look.

Alan G0TLK

On 27/04/2025 15:00, Hasan N0AN via wsjt-devel wrote:
> There is no need for your feature request. WSJT-X should not be using 
> the only audio device available  to your computer, or put it another 
> way, X should not be using the windows default audio device.
>
> Add a simple sound card usb dongle (less than $10 on Amazon). Use that 
> for WSJT-X, use the default Windows audio device for your warnings.
>
> Or...if you have a modern radio with USB interface, use the Radio's 
> USB interface for both Audio and CAT control in WSJT-X, and use the 
> computer's default sound card for alerts from WSJT-X
>
> Don't use windows' default audio device (built in audio/sound card in 
> the computer) for WSJT-X  TX and RX
>
> 73, N0AN
>
> Hasan
>
>
> On Sat, Apr 26, 2025 at 11:51 AM F4HTB via wsjt-devel 
> <wsj...@li...> wrote:
>
>     Hello everyone,
>
>     I would like to suggest a small but useful improvement for WSJT-X
>     regarding audio handling.
>
>     Currently, WSJT-X uses the system’s default audio output to play
>     alert
>     sounds.
>     In some setups, this can lead to problems: I have noticed, both
>     personally and among other operators, that when using the same audio
>     interface for radio transmission and for WSJT-X, the alert sounds may
>     accidentally be transmitted over the air.
>
>     I have observed this behavior both under Windows and Linux.
>
>     To prevent this issue, I propose adding an option in the Audio tab of
>     the configuration menu to allow users to select a specific output
>     device
>     for alert sounds, independently of the device used for radio
>     transmissions.
>
>     For reference, Fldigi has provided this capability for a long time,
>     which helps avoid this kind of problem.
>
>     Thank you very much for considering this request, and thank you
>     for all
>     the excellent work on WSJT-X.
>
>     73,
>
>
>
>
>     _______________________________________________
>     wsjt-devel mailing list
>     wsj...@li...
>     https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel