Menu
▾
▴
wsjt-devel — WSJT software development
You can subscribe to this list here.
| 2007 |
Jan
(30) |
Feb
|
Mar
(10) |
Apr
(60) |
May
(62) |
Jun
|
Jul
(3) |
Aug
(3) |
Sep
(10) |
Oct
(17) |
Nov
(1) |
Dec
(14) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
|
Feb
(21) |
Mar
(4) |
Apr
(15) |
May
(37) |
Jun
(98) |
Jul
(120) |
Aug
(1) |
Sep
(14) |
Oct
|
Nov
(31) |
Dec
(8) |
| 2009 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(25) |
May
(88) |
Jun
(5) |
Jul
(31) |
Aug
(25) |
Sep
(4) |
Oct
(19) |
Nov
(119) |
Dec
(11) |
| 2010 |
Jan
(3) |
Feb
(19) |
Mar
(4) |
Apr
|
May
(7) |
Jun
(17) |
Jul
|
Aug
(4) |
Sep
(20) |
Oct
(3) |
Nov
(29) |
Dec
(86) |
| 2011 |
Jan
(6) |
Feb
|
Mar
(6) |
Apr
(8) |
May
(1) |
Jun
(12) |
Jul
(9) |
Aug
(4) |
Sep
(7) |
Oct
(9) |
Nov
|
Dec
(1) |
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(7) |
Jun
(5) |
Jul
|
Aug
|
Sep
(5) |
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
(10) |
Feb
(7) |
Mar
(4) |
Apr
(76) |
May
(66) |
Jun
(101) |
Jul
(210) |
Aug
(255) |
Sep
(83) |
Oct
(18) |
Nov
(3) |
Dec
(3) |
| 2014 |
Jan
(187) |
Feb
(139) |
Mar
(99) |
Apr
(173) |
May
(106) |
Jun
(61) |
Jul
(50) |
Aug
(66) |
Sep
(342) |
Oct
(238) |
Nov
(251) |
Dec
(189) |
| 2015 |
Jan
(96) |
Feb
(295) |
Mar
(260) |
Apr
(271) |
May
(358) |
Jun
(531) |
Jul
(311) |
Aug
(231) |
Sep
(267) |
Oct
(219) |
Nov
(452) |
Dec
(390) |
| 2016 |
Jan
(367) |
Feb
(128) |
Mar
(208) |
Apr
(308) |
May
(237) |
Jun
(272) |
Jul
(90) |
Aug
(289) |
Sep
(153) |
Oct
(214) |
Nov
(167) |
Dec
(282) |
| 2017 |
Jan
(194) |
Feb
(173) |
Mar
(267) |
Apr
(102) |
May
(39) |
Jun
(201) |
Jul
(1064) |
Aug
(363) |
Sep
(383) |
Oct
(289) |
Nov
(237) |
Dec
(185) |
| 2018 |
Jan
(175) |
Feb
(198) |
Mar
(489) |
Apr
(222) |
May
(414) |
Jun
(297) |
Jul
(329) |
Aug
(136) |
Sep
(383) |
Oct
(590) |
Nov
(834) |
Dec
(1114) |
| 2019 |
Jan
(425) |
Feb
(177) |
Mar
(319) |
Apr
(515) |
May
(337) |
Jun
(447) |
Jul
(525) |
Aug
(252) |
Sep
(119) |
Oct
(108) |
Nov
(211) |
Dec
(228) |
| 2020 |
Jan
(158) |
Feb
(141) |
Mar
(94) |
Apr
(99) |
May
(545) |
Jun
(470) |
Jul
(211) |
Aug
(142) |
Sep
(181) |
Oct
(128) |
Nov
(219) |
Dec
(213) |
| 2021 |
Jan
(243) |
Feb
(514) |
Mar
(279) |
Apr
(101) |
May
(97) |
Jun
(259) |
Jul
(164) |
Aug
(205) |
Sep
(149) |
Oct
(301) |
Nov
(139) |
Dec
(159) |
| 2022 |
Jan
(116) |
Feb
(70) |
Mar
(63) |
Apr
(46) |
May
(50) |
Jun
(114) |
Jul
(173) |
Aug
(106) |
Sep
(127) |
Oct
(65) |
Nov
(117) |
Dec
(102) |
| 2023 |
Jan
(139) |
Feb
(99) |
Mar
(52) |
Apr
(132) |
May
(238) |
Jun
(75) |
Jul
(91) |
Aug
(25) |
Sep
(36) |
Oct
(64) |
Nov
(45) |
Dec
(91) |
| 2024 |
Jan
(156) |
Feb
(56) |
Mar
(30) |
Apr
(16) |
May
(40) |
Jun
(53) |
Jul
(327) |
Aug
(171) |
Sep
(67) |
Oct
(53) |
Nov
(43) |
Dec
(78) |
| 2025 |
Jan
(112) |
Feb
(27) |
Mar
(46) |
Apr
(49) |
May
(58) |
Jun
(54) |
Jul
(42) |
Aug
(10) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <al...@al...> - 2025-04-16 11:17:05
|
Likewise on the GA but I downloaded the Improved version yesterday to take a look when I've got some time. I can only urge the core developers to include high dpi scaling to support 2k and 4k monitors in the GA release ASAP, particularly if it is as simple as just one line of code. Alan G0TLK On 16/04/2025 00:09, Mark Galbraith via wsjt-devel wrote: > > I started using the Gold Standard Original WSJT-X and haven’t really > explored any of the variants at all. Maybe I should, but I’m so used > to the standard interface now. 😃 > > Besides, with the addition of a SINGLE line of code WSJT-X can have > those features turned on and working for everyone. As far as I have > been able to determine, enabling the high-DPI support does not > adversely affect those who are not using a high-DPI card and monitor. > If this is the case, there is probably no reason for this support to > be turned off, unless WSJT-X Improved has code changes other than the > single line I provided. > > 73 > > -.. . / -- .- .-. -.- / -. --... -.-- -.. > > DE MARK N7YD > > *From:*Uwe, DG2YCB <dg...@gm...> > *Sent:* Monday, April 14, 2025 23:54 > *To:* WSJT software development <wsj...@li...> > *Cc:* Mark Galbraith <n7...@mg...> > *Subject:* Re: [wsjt-devel] FW: Button sizes not correct > > Hi Mark, > > Why don't you use WSJT-X Improved v2.8.0? It has high-DPI scaling > built in, as well as dozens of other useful extra features. > > > But if you really want to develop the wheel a second time, feel free > to do so ... > > > 73 de DG2YCB, > Uwe > ________________________________________ > German Amateur Radio Station DG2YCB > Dr. Uwe Risse > eMail: dg...@gm... > Info: www.qrz.com/db/DG2YCB <http://www.qrz.com/db/DG2YCB> > > Am 15.04.2025 um 01:53 schrieb Mark Galbraith via wsjt-devel: > > I suppose the images included in my email are making it too large > for the mailing list. I’m forwarding this back to the wsjt-devel > team with the images removed. Anyone wanting to see the full email > with the images restored can email me for a direct copy. > > 73 > > -.. . / -- .- .-. -.- / -. --... -.-- -.. > > DE MARK N7YD > > *From:*Mark Galbraith > *Sent:* Sunday, April 13, 2025 17:25 > *To:* Black Michael <mdb...@ya...> > <mailto:mdb...@ya...>; WSJT software development > <wsj...@li...> > <mailto:wsj...@li...>; Mark Galbraith > <ma...@mg...> <mailto:ma...@mg...> > *Subject:* RE: [wsjt-devel] Button sizes not correct > > I apologize for the long delay in replying. I had gotten feedback > that this was not something that could be fixed, so I set it > aside. However, my background in programming would not let this > go, and eventually I had time and the drive to dig into this > further. Along the way I determined the use of Qt tools and dug > into this a bit more. I found the location where the UI buttons > are set, and saw they have a minimum size of 32. I couldn’t see > anything else that jumped out of the source code, so I went > looking for other information available. I found a few items on > StackOvervlow and eventually found this article on the Qt Forum > that seemed to be on point. > > https://doc.qt.io/qt-5/highdpi.html > > In reading through, I see that there is a workaround by setting > the environment variable QT_ENABLE_HIGHDPI_SCALING prior to > running the application should enable the high-DPI support. I ran > some experiments, and this is what I found. > > BEFORE > > The buttons on the main UI panel are clipped: > > And the font size on the waterfall display is huge: > > AFTER setting the environment variable: > > The buttons as well asother screen elements are no longer clipped: > > And the waterfall font size is back to normal: > > CONCLUSION > > The WSJT-X program will display properly if the high-DPI support > in Qt is enabled. While setting the environment variable is a > workaround for this, the proper course of action would be to > enable this support in the source code. According to the > StackOverflow pages, the following line, executed prior to > initializing the application will enable the high-DPI support. > > QApplication::setAttribute(Qt::AA_EnableHighDpiScaling); > > In the WSJT-X, the initialization of the Qt application occurs > inside ExceptionCatchingApplication.hpp, which is included into > main.cpp and called at line 118 (as found in the 2.7.0 code on > SourceForge). In my view, inserting the above “setAttribute” just > above line 118 will properly enable the high-DPI support for Qt, > and solve this and possibly many other issues with users of > high-DPI monitors in the userbase. > > Please feel free to reach out if you have any questions or would > like to discuss this issue further. > > 73 > > -.. . / -- .- .-. -.- / -. --... -.-- -.. > > DE MARK N7YD > > *From:*Black Michael <mdb...@ya...> > *Sent:* Friday, September 1, 2023 12:53 > *To:* WSJT software development > <wsj...@li...>; Mark Galbraith > <n7...@mg...>; mark mgg4.com <ma...@mg...> > *Subject:* Re: [wsjt-devel] Button sizes not correct > > Can you provide a screen shot? > > What font are you using -- I have Microsoft Sans Serif 8pt. > > Mike W9MDB > > On Friday, September 1, 2023 at 01:01:45 PM CDT, mark mgg4.com > <ma...@mg...> wrote: > > After switching back, and the problem with the button sizes > returns, I make the following observations. > > 1. The text margins for the “H” button seem to be correct. > 2. The remaining buttons in the column use the same button size > as the “H” button. > 3. Scaling those buttons on one of the longer button labels may > resolve the problem for all resolutions. > > I’m a retired programmer with 45 years of experience. I’ve seen > these types of problems many times. Sometimes, the hard problems > have easy solutions. Other times you grab a big hammer… > > --Mark > > *From:*mark mgg4.com via wsjt-devel > <wsj...@li...> > *Sent:* Friday, September 1, 2023 10:54 AM > *To:* Black Michael <mdb...@ya...>; WSJT software > development <wsj...@li...>; Mark Galbraith > <n7...@mg...> > *Cc:* mark mgg4.com <ma...@mg...> > *Subject:* Re: [wsjt-devel] Button sizes not correct > > All of them. Most annoying is the Log popup which I have > positioned for easy tapping (touch screen). > > --Mark > > *From:*Black Michael <mdb...@ya...> > *Sent:* Friday, September 1, 2023 10:52 AM > *To:* WSJT software development > <wsj...@li...>; Mark Galbraith <n7...@mg...> > *Cc:* mark mgg4.com <ma...@mg...> > *Subject:* Re: [wsjt-devel] Button sizes not correct > > Which windows? > > On Friday, September 1, 2023 at 12:46:50 PM CDT, Mark Galbraith > <n7...@mg... <mailto:n7...@mg...>> wrote: > > After a few more experiments, I’ve reverted this change. The > program no longer remembers where certain windows open on the > screen, opening all windows in the center. This is a bit more > disruptive than the narrow buttons. > > --Mark, N7YD > > *From:*mark mgg4.com via wsjt-devel > <wsj...@li... > <mailto:wsj...@li...>> > *Sent:* Friday, September 1, 2023 10:37 AM > *To:* Black Michael <mdb...@ya... > <mailto:mdb...@ya...>>; WSJT software development > <wsj...@li... > <mailto:wsj...@li...>> > *Cc:* mark mgg4.com <ma...@mg... <mailto:ma...@mg...>> > *Subject:* Re: [wsjt-devel] Button sizes not correct > > Thank you. That does change a few things, and some of the text > seems a bit less sharp, but it does fix the problem and I like the > overall effect better. I very much appreciate your response. > > --Mark, N7YD > > *From:*Black Michael via wsjt-devel > <wsj...@li... > <mailto:wsj...@li...>> > *Sent:* Friday, September 1, 2023 9:25 AM > *To:* WSJT software development <wsj...@li... > <mailto:wsj...@li...>> > *Cc:* Black Michael <mdb...@ya... <mailto:mdb...@ya...>> > *Subject:* Re: [wsjt-devel] Button sizes not correct > > Try this to replace the qt.conf in your bin directory > > [Paths] > > Plugins = ../plugins > > [Platforms] > > WindowsArguments = dpiawareness=0 > > Mike W9MDB > > On Thursday, August 31, 2023 at 10:43:43 PM CDT, Laurie, VK3AMA > via wsjt-devel <wsj...@li... > <mailto:wsj...@li...>> wrote: > > On 01/09/2023 8:15 am, Mark Galbraith via wsjt-devel wrote: > > Not sure what’s happening here, but my guess would be that the > screen resolution may be off, but I was seeing this on other > computers as well. > > > > My computer is a Microsoft Surfacebook 2, with a screen > resolution of 3240 x 2160. I was also seeing the same thing on > my other computer with a 32” ultra widescreen resolution of > 2560 x 1080. I’m also seeing this on v2.6.1 and v2.7.0-rc2. Is > there a setting I need to adjust, or is this something that > requires a program change to fix? > > 73 > > -.. . / -- .- .-. -.- / -. --... -.-- -.. > > DE MARK N7YD > > > > A long standing defect that I gave up on getting the devs to correct. > > All other UI controls inducing the Tx1-6 buttons are scaled > correctly except these buttons! > > Here's mine, like you replicated across multiple devices. > > > de Laurie VK3AMA > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > <mailto:wsj...@li...> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > <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 |
|
From: Reino T. <rei...@ko...> - 2025-04-16 04:41:21
|
Mark, good news to you. On the main window of the WSJT-X v2.8.0 250314 improved PLUS it is hard to tell differences to the GA v2.7.0. You can easily switch off the Band buttons using the View menu, if you don’t like those. There is a new menu Filters, menu items and selection boxes you may just ignore. I would give it a try. 73, Reino OH3mA From: Mark Galbraith via wsjt-devel <wsj...@li...> Sent: Wednesday, April 16, 2025 2:09 AM To: Uwe, DG2YCB <dg...@gm...>; WSJT software development <wsj...@li...> Cc: Mark Galbraith <n7...@mg...> Subject: Re: [wsjt-devel] FW: Button sizes not correct I started using the Gold Standard Original WSJT-X and haven’t really explored any of the variants at all. Maybe I should, but I’m so used to the standard interface now. 😃 Besides, with the addition of a SINGLE line of code WSJT-X can have those features turned on and working for everyone. As far as I have been able to determine, enabling the high-DPI support does not adversely affect those who are not using a high-DPI card and monitor. If this is the case, there is probably no reason for this support to be turned off, unless WSJT-X Improved has code changes other than the single line I provided. 73 -.. . / -- .- .-. -.- / -. --... -.-- -.. DE MARK N7YD From: Uwe, DG2YCB <dg...@gm... <mailto:dg...@gm...> > Sent: Monday, April 14, 2025 23:54 To: WSJT software development <wsj...@li... <mailto:wsj...@li...> > Cc: Mark Galbraith <n7...@mg... <mailto:n7...@mg...> > Subject: Re: [wsjt-devel] FW: Button sizes not correct Hi Mark, Why don't you use WSJT-X Improved v2.8.0? It has high-DPI scaling built in, as well as dozens of other useful extra features. But if you really want to develop the wheel a second time, feel free to do so ... 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 15.04.2025 um 01:53 schrieb Mark Galbraith via wsjt-devel: I suppose the images included in my email are making it too large for the mailing list. I’m forwarding this back to the wsjt-devel team with the images removed. Anyone wanting to see the full email with the images restored can email me for a direct copy. 73 -.. . / -- .- .-. -.- / -. --... -.-- -.. DE MARK N7YD From: Mark Galbraith Sent: Sunday, April 13, 2025 17:25 To: Black Michael <mailto:mdb...@ya...> <mdb...@ya...>; WSJT software development <mailto:wsj...@li...> <wsj...@li...>; Mark Galbraith <mailto:ma...@mg...> <ma...@mg...> Subject: RE: [wsjt-devel] Button sizes not correct I apologize for the long delay in replying. I had gotten feedback that this was not something that could be fixed, so I set it aside. However, my background in programming would not let this go, and eventually I had time and the drive to dig into this further. Along the way I determined the use of Qt tools and dug into this a bit more. I found the location where the UI buttons are set, and saw they have a minimum size of 32. I couldn’t see anything else that jumped out of the source code, so I went looking for other information available. I found a few items on StackOvervlow and eventually found this article on the Qt Forum that seemed to be on point. https://doc.qt.io/qt-5/highdpi.html In reading through, I see that there is a workaround by setting the environment variable QT_ENABLE_HIGHDPI_SCALING prior to running the application should enable the high-DPI support. I ran some experiments, and this is what I found. BEFORE The buttons on the main UI panel are clipped: And the font size on the waterfall display is huge: AFTER setting the environment variable: The buttons as well asother screen elements are no longer clipped: And the waterfall font size is back to normal: CONCLUSION The WSJT-X program will display properly if the high-DPI support in Qt is enabled. While setting the environment variable is a workaround for this, the proper course of action would be to enable this support in the source code. According to the StackOverflow pages, the following line, executed prior to initializing the application will enable the high-DPI support. QApplication::setAttribute(Qt::AA_EnableHighDpiScaling); In the WSJT-X, the initialization of the Qt application occurs inside ExceptionCatchingApplication.hpp, which is included into main.cpp and called at line 118 (as found in the 2.7.0 code on SourceForge). In my view, inserting the above “setAttribute” just above line 118 will properly enable the high-DPI support for Qt, and solve this and possibly many other issues with users of high-DPI monitors in the userbase. Please feel free to reach out if you have any questions or would like to discuss this issue further. 73 -.. . / -- .- .-. -.- / -. --... -.-- -.. DE MARK N7YD From: Black Michael <mdb...@ya... <mailto:mdb...@ya...> > Sent: Friday, September 1, 2023 12:53 To: WSJT software development <wsj...@li... <mailto:wsj...@li...> >; Mark Galbraith <n7...@mg... <mailto:n7...@mg...> >; mark mgg4.com <ma...@mg... <mailto:ma...@mg...> > Subject: Re: [wsjt-devel] Button sizes not correct Can you provide a screen shot? What font are you using -- I have Microsoft Sans Serif 8pt. Mike W9MDB On Friday, September 1, 2023 at 01:01:45 PM CDT, mark mgg4.com <ma...@mg... <mailto:ma...@mg...> > wrote: After switching back, and the problem with the button sizes returns, I make the following observations. 1. The text margins for the “H” button seem to be correct. 2. The remaining buttons in the column use the same button size as the “H” button. 3. Scaling those buttons on one of the longer button labels may resolve the problem for all resolutions. I’m a retired programmer with 45 years of experience. I’ve seen these types of problems many times. Sometimes, the hard problems have easy solutions. Other times you grab a big hammer… --Mark From: mark mgg4.com via wsjt-devel <wsj...@li... <mailto:wsj...@li...> > Sent: Friday, September 1, 2023 10:54 AM To: Black Michael <mdb...@ya... <mailto:mdb...@ya...> >; WSJT software development <wsj...@li... <mailto:wsj...@li...> >; Mark Galbraith <n7...@mg... <mailto:n7...@mg...> > Cc: mark mgg4.com <ma...@mg... <mailto:ma...@mg...> > Subject: Re: [wsjt-devel] Button sizes not correct All of them. Most annoying is the Log popup which I have positioned for easy tapping (touch screen). --Mark From: Black Michael <mdb...@ya... <mailto:mdb...@ya...> > Sent: Friday, September 1, 2023 10:52 AM To: WSJT software development <wsj...@li... <mailto:wsj...@li...> >; Mark Galbraith <n7...@mg... <mailto:n7...@mg...> > Cc: mark mgg4.com <ma...@mg... <mailto:ma...@mg...> > Subject: Re: [wsjt-devel] Button sizes not correct Which windows? On Friday, September 1, 2023 at 12:46:50 PM CDT, Mark Galbraith < <mailto:n7...@mg...> n7...@mg...> wrote: After a few more experiments, I’ve reverted this change. The program no longer remembers where certain windows open on the screen, opening all windows in the center. This is a bit more disruptive than the narrow buttons. --Mark, N7YD From: mark mgg4.com via wsjt-devel < <mailto:wsj...@li...> wsj...@li...> Sent: Friday, September 1, 2023 10:37 AM To: Black Michael < <mailto:mdb...@ya...> mdb...@ya...>; WSJT software development < <mailto:wsj...@li...> wsj...@li...> Cc: mark mgg4.com < <mailto:ma...@mg...> ma...@mg...> Subject: Re: [wsjt-devel] Button sizes not correct Thank you. That does change a few things, and some of the text seems a bit less sharp, but it does fix the problem and I like the overall effect better. I very much appreciate your response. --Mark, N7YD From: Black Michael via wsjt-devel < <mailto:wsj...@li...> wsj...@li...> Sent: Friday, September 1, 2023 9:25 AM To: WSJT software development < <mailto:wsj...@li...> wsj...@li...> Cc: Black Michael < <mailto:mdb...@ya...> mdb...@ya...> Subject: Re: [wsjt-devel] Button sizes not correct Try this to replace the qt.conf in your bin directory [Paths] Plugins = ../plugins [Platforms] WindowsArguments = dpiawareness=0 Mike W9MDB On Thursday, August 31, 2023 at 10:43:43 PM CDT, Laurie, VK3AMA via wsjt-devel < <mailto:wsj...@li...> wsj...@li...> wrote: On 01/09/2023 8:15 am, Mark Galbraith via wsjt-devel wrote: Not sure what’s happening here, but my guess would be that the screen resolution may be off, but I was seeing this on other computers as well. My computer is a Microsoft Surfacebook 2, with a screen resolution of 3240 x 2160. I was also seeing the same thing on my other computer with a 32” ultra widescreen resolution of 2560 x 1080. I’m also seeing this on v2.6.1 and v2.7.0-rc2. Is there a setting I need to adjust, or is this something that requires a program change to fix? 73 -.. . / -- .- .-. -.- / -. --... -.-- -.. DE MARK N7YD A long standing defect that I gave up on getting the devs to correct. All other UI controls inducing the Tx1-6 buttons are scaled correctly except these buttons! Here's mine, like you replicated across multiple devices. de Laurie VK3AMA _______________________________________________ wsjt-devel mailing list <mailto:wsj...@li...> wsj...@li... <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list wsj...@li... <mailto:wsj...@li...> https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Mark G. <n7...@mg...> - 2025-04-15 23:09:52
|
I started using the Gold Standard Original WSJT-X and haven’t really explored any of the variants at all. Maybe I should, but I’m so used to the standard interface now. 😃 Besides, with the addition of a SINGLE line of code WSJT-X can have those features turned on and working for everyone. As far as I have been able to determine, enabling the high-DPI support does not adversely affect those who are not using a high-DPI card and monitor. If this is the case, there is probably no reason for this support to be turned off, unless WSJT-X Improved has code changes other than the single line I provided. 73 -.. . / -- .- .-. -.- / -. --... -.-- -.. DE MARK N7YD From: Uwe, DG2YCB <dg...@gm...> Sent: Monday, April 14, 2025 23:54 To: WSJT software development <wsj...@li...> Cc: Mark Galbraith <n7...@mg...> Subject: Re: [wsjt-devel] FW: Button sizes not correct Hi Mark, Why don't you use WSJT-X Improved v2.8.0? It has high-DPI scaling built in, as well as dozens of other useful extra features. [cid:image001.png@01DBAE20.C188B4F0] But if you really want to develop the wheel a second time, feel free to do so ... 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 15.04.2025 um 01:53 schrieb Mark Galbraith via wsjt-devel: I suppose the images included in my email are making it too large for the mailing list. I’m forwarding this back to the wsjt-devel team with the images removed. Anyone wanting to see the full email with the images restored can email me for a direct copy. 73 -.. . / -- .- .-. -.- / -. --... -.-- -.. DE MARK N7YD From: Mark Galbraith Sent: Sunday, April 13, 2025 17:25 To: Black Michael <mdb...@ya...><mailto:mdb...@ya...>; WSJT software development <wsj...@li...><mailto:wsj...@li...>; Mark Galbraith <ma...@mg...><mailto:ma...@mg...> Subject: RE: [wsjt-devel] Button sizes not correct I apologize for the long delay in replying. I had gotten feedback that this was not something that could be fixed, so I set it aside. However, my background in programming would not let this go, and eventually I had time and the drive to dig into this further. Along the way I determined the use of Qt tools and dug into this a bit more. I found the location where the UI buttons are set, and saw they have a minimum size of 32. I couldn’t see anything else that jumped out of the source code, so I went looking for other information available. I found a few items on StackOvervlow and eventually found this article on the Qt Forum that seemed to be on point. https://doc.qt.io/qt-5/highdpi.html In reading through, I see that there is a workaround by setting the environment variable QT_ENABLE_HIGHDPI_SCALING prior to running the application should enable the high-DPI support. I ran some experiments, and this is what I found. BEFORE The buttons on the main UI panel are clipped: And the font size on the waterfall display is huge: AFTER setting the environment variable: The buttons as well asother screen elements are no longer clipped: And the waterfall font size is back to normal: CONCLUSION The WSJT-X program will display properly if the high-DPI support in Qt is enabled. While setting the environment variable is a workaround for this, the proper course of action would be to enable this support in the source code. According to the StackOverflow pages, the following line, executed prior to initializing the application will enable the high-DPI support. QApplication::setAttribute(Qt::AA_EnableHighDpiScaling); In the WSJT-X, the initialization of the Qt application occurs inside ExceptionCatchingApplication.hpp, which is included into main.cpp and called at line 118 (as found in the 2.7.0 code on SourceForge). In my view, inserting the above “setAttribute” just above line 118 will properly enable the high-DPI support for Qt, and solve this and possibly many other issues with users of high-DPI monitors in the userbase. Please feel free to reach out if you have any questions or would like to discuss this issue further. 73 -.. . / -- .- .-. -.- / -. --... -.-- -.. DE MARK N7YD From: Black Michael <mdb...@ya...<mailto:mdb...@ya...>> Sent: Friday, September 1, 2023 12:53 To: WSJT software development <wsj...@li...<mailto:wsj...@li...>>; Mark Galbraith <n7...@mg...<mailto:n7...@mg...>>; mark mgg4.com <ma...@mg...<mailto:ma...@mg...>> Subject: Re: [wsjt-devel] Button sizes not correct Can you provide a screen shot? What font are you using -- I have Microsoft Sans Serif 8pt. Mike W9MDB On Friday, September 1, 2023 at 01:01:45 PM CDT, mark mgg4.com <ma...@mg...<mailto:ma...@mg...>> wrote: After switching back, and the problem with the button sizes returns, I make the following observations. 1. The text margins for the “H” button seem to be correct. 2. The remaining buttons in the column use the same button size as the “H” button. 3. Scaling those buttons on one of the longer button labels may resolve the problem for all resolutions. I’m a retired programmer with 45 years of experience. I’ve seen these types of problems many times. Sometimes, the hard problems have easy solutions. Other times you grab a big hammer… --Mark From: mark mgg4.com via wsjt-devel <wsj...@li...<mailto:wsj...@li...>> Sent: Friday, September 1, 2023 10:54 AM To: Black Michael <mdb...@ya...<mailto:mdb...@ya...>>; WSJT software development <wsj...@li...<mailto:wsj...@li...>>; Mark Galbraith <n7...@mg...<mailto:n7...@mg...>> Cc: mark mgg4.com <ma...@mg...<mailto:ma...@mg...>> Subject: Re: [wsjt-devel] Button sizes not correct All of them. Most annoying is the Log popup which I have positioned for easy tapping (touch screen). --Mark From: Black Michael <mdb...@ya...<mailto:mdb...@ya...>> Sent: Friday, September 1, 2023 10:52 AM To: WSJT software development <wsj...@li...<mailto:wsj...@li...>>; Mark Galbraith <n7...@mg...<mailto:n7...@mg...>> Cc: mark mgg4.com <ma...@mg...<mailto:ma...@mg...>> Subject: Re: [wsjt-devel] Button sizes not correct Which windows? On Friday, September 1, 2023 at 12:46:50 PM CDT, Mark Galbraith <n7...@mg...<mailto:n7...@mg...>> wrote: After a few more experiments, I’ve reverted this change. The program no longer remembers where certain windows open on the screen, opening all windows in the center. This is a bit more disruptive than the narrow buttons. --Mark, N7YD From: mark mgg4.com via wsjt-devel <wsj...@li...<mailto:wsj...@li...>> Sent: Friday, September 1, 2023 10:37 AM To: Black Michael <mdb...@ya...<mailto:mdb...@ya...>>; WSJT software development <wsj...@li...<mailto:wsj...@li...>> Cc: mark mgg4.com <ma...@mg...<mailto:ma...@mg...>> Subject: Re: [wsjt-devel] Button sizes not correct Thank you. That does change a few things, and some of the text seems a bit less sharp, but it does fix the problem and I like the overall effect better. I very much appreciate your response. --Mark, N7YD From: Black Michael via wsjt-devel <wsj...@li...<mailto:wsj...@li...>> Sent: Friday, September 1, 2023 9:25 AM To: WSJT software development <wsj...@li...<mailto:wsj...@li...>> Cc: Black Michael <mdb...@ya...<mailto:mdb...@ya...>> Subject: Re: [wsjt-devel] Button sizes not correct Try this to replace the qt.conf in your bin directory [Paths] Plugins = ../plugins [Platforms] WindowsArguments = dpiawareness=0 Mike W9MDB On Thursday, August 31, 2023 at 10:43:43 PM CDT, Laurie, VK3AMA via wsjt-devel <wsj...@li...<mailto:wsj...@li...>> wrote: On 01/09/2023 8:15 am, Mark Galbraith via wsjt-devel wrote: Not sure what’s happening here, but my guess would be that the screen resolution may be off, but I was seeing this on other computers as well. My computer is a Microsoft Surfacebook 2, with a screen resolution of 3240 x 2160. I was also seeing the same thing on my other computer with a 32” ultra widescreen resolution of 2560 x 1080. I’m also seeing this on v2.6.1 and v2.7.0-rc2. Is there a setting I need to adjust, or is this something that requires a program change to fix? 73 -.. . / -- .- .-. -.- / -. --... -.-- -.. DE MARK N7YD A long standing defect that I gave up on getting the devs to correct. All other UI controls inducing the Tx1-6 buttons are scaled correctly except these buttons! Here's mine, like you replicated across multiple devices. de Laurie VK3AMA _______________________________________________ wsjt-devel mailing list wsj...@li...<mailto:wsj...@li...> https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list wsj...@li...<mailto:wsj...@li...> https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Uwe, D. <dg...@gm...> - 2025-04-15 06:54:02
|
Hi Mark, Why don't you use WSJT-X Improved v2.8.0? It has high-DPI scaling built in, as well as dozens of other useful extra features. But if you really want to develop the wheel a second time, feel free to do so ... 73 de DG2YCB, Uwe ________________________________________ German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg...@gm... Info: www.qrz.com/db/DG2YCB Am 15.04.2025 um 01:53 schrieb Mark Galbraith via wsjt-devel: > > I suppose the images included in my email are making it too large for > the mailing list. I’m forwarding this back to the wsjt-devel team > with the images removed. Anyone wanting to see the full email with > the images restored can email me for a direct copy. > > 73 > > -.. . / -- .- .-. -.- / -. --... -.-- -.. > > DE MARK N7YD > > *From:*Mark Galbraith > *Sent:* Sunday, April 13, 2025 17:25 > *To:* Black Michael <mdb...@ya...>; WSJT software development > <wsj...@li...>; Mark Galbraith <ma...@mg...> > *Subject:* RE: [wsjt-devel] Button sizes not correct > > I apologize for the long delay in replying. I had gotten feedback > that this was not something that could be fixed, so I set it aside. > However, my background in programming would not let this go, and > eventually I had time and the drive to dig into this further. Along > the way I determined the use of Qt tools and dug into this a bit > more. I found the location where the UI buttons are set, and saw they > have a minimum size of 32. I couldn’t see anything else that jumped > out of the source code, so I went looking for other information > available. I found a few items on StackOvervlow and eventually found > this article on the Qt Forum that seemed to be on point. > > https://doc.qt.io/qt-5/highdpi.html > > In reading through, I see that there is a workaround by setting the > environment variable QT_ENABLE_HIGHDPI_SCALING prior to running the > application should enable the high-DPI support. I ran some > experiments, and this is what I found. > > BEFORE > > The buttons on the main UI panel are clipped: > > And the font size on the waterfall display is huge: > > AFTER setting the environment variable: > > The buttons as well asother screen elements are no longer clipped: > > And the waterfall font size is back to normal: > > CONCLUSION > > The WSJT-X program will display properly if the high-DPI support in Qt > is enabled. While setting the environment variable is a workaround > for this, the proper course of action would be to enable this support > in the source code. According to the StackOverflow pages, the > following line, executed prior to initializing the application will > enable the high-DPI support. > > QApplication::setAttribute(Qt::AA_EnableHighDpiScaling); > > In the WSJT-X, the initialization of the Qt application occurs inside > ExceptionCatchingApplication.hpp, which is included into main.cpp and > called at line 118 (as found in the 2.7.0 code on SourceForge). In my > view, inserting the above “setAttribute” just above line 118 will > properly enable the high-DPI support for Qt, and solve this and > possibly many other issues with users of high-DPI monitors in the > userbase. > > Please feel free to reach out if you have any questions or would like > to discuss this issue further. > > 73 > > -.. . / -- .- .-. -.- / -. --... -.-- -.. > > DE MARK N7YD > > *From:*Black Michael <mdb...@ya...> > *Sent:* Friday, September 1, 2023 12:53 > *To:* WSJT software development <wsj...@li...>; > Mark Galbraith <n7...@mg...>; mark mgg4.com <ma...@mg...> > *Subject:* Re: [wsjt-devel] Button sizes not correct > > Can you provide a screen shot? > > What font are you using -- I have Microsoft Sans Serif 8pt. > > Mike W9MDB > > On Friday, September 1, 2023 at 01:01:45 PM CDT, mark mgg4.com > <ma...@mg...> wrote: > > After switching back, and the problem with the button sizes returns, I > make the following observations. > > 1. The text margins for the “H” button seem to be correct. > 2. The remaining buttons in the column use the same button size as > the “H” button. > 3. Scaling those buttons on one of the longer button labels may > resolve the problem for all resolutions. > > I’m a retired programmer with 45 years of experience. I’ve seen these > types of problems many times. Sometimes, the hard problems have easy > solutions. Other times you grab a big hammer… > > --Mark > > *From:*mark mgg4.com via wsjt-devel <wsj...@li...> > *Sent:* Friday, September 1, 2023 10:54 AM > *To:* Black Michael <mdb...@ya...>; WSJT software development > <wsj...@li...>; Mark Galbraith <n7...@mg...> > *Cc:* mark mgg4.com <ma...@mg...> > *Subject:* Re: [wsjt-devel] Button sizes not correct > > All of them. Most annoying is the Log popup which I have positioned > for easy tapping (touch screen). > > --Mark > > *From:*Black Michael <mdb...@ya...> > *Sent:* Friday, September 1, 2023 10:52 AM > *To:* WSJT software development <wsj...@li...>; > Mark Galbraith <n7...@mg...> > *Cc:* mark mgg4.com <ma...@mg...> > *Subject:* Re: [wsjt-devel] Button sizes not correct > > Which windows? > > On Friday, September 1, 2023 at 12:46:50 PM CDT, Mark Galbraith > <n7...@mg... <mailto:n7...@mg...>> wrote: > > After a few more experiments, I’ve reverted this change. The program > no longer remembers where certain windows open on the screen, opening > all windows in the center. This is a bit more disruptive than the > narrow buttons. > > --Mark, N7YD > > *From:*mark mgg4.com via wsjt-devel <wsj...@li... > <mailto:wsj...@li...>> > *Sent:* Friday, September 1, 2023 10:37 AM > *To:* Black Michael <mdb...@ya... > <mailto:mdb...@ya...>>; WSJT software development > <wsj...@li... > <mailto:wsj...@li...>> > *Cc:* mark mgg4.com <ma...@mg... <mailto:ma...@mg...>> > *Subject:* Re: [wsjt-devel] Button sizes not correct > > Thank you. That does change a few things, and some of the text seems > a bit less sharp, but it does fix the problem and I like the overall > effect better. I very much appreciate your response. > > --Mark, N7YD > > *From:*Black Michael via wsjt-devel <wsj...@li... > <mailto:wsj...@li...>> > *Sent:* Friday, September 1, 2023 9:25 AM > *To:* WSJT software development <wsj...@li... > <mailto:wsj...@li...>> > *Cc:* Black Michael <mdb...@ya... <mailto:mdb...@ya...>> > *Subject:* Re: [wsjt-devel] Button sizes not correct > > Try this to replace the qt.conf in your bin directory > > [Paths] > > Plugins = ../plugins > > [Platforms] > > WindowsArguments = dpiawareness=0 > > Mike W9MDB > > On Thursday, August 31, 2023 at 10:43:43 PM CDT, Laurie, VK3AMA via > wsjt-devel <wsj...@li... > <mailto:wsj...@li...>> wrote: > > On 01/09/2023 8:15 am, Mark Galbraith via wsjt-devel wrote: > > Not sure what’s happening here, but my guess would be that the > screen resolution may be off, but I was seeing this on other > computers as well. > > > My computer is a Microsoft Surfacebook 2, with a screen resolution > of 3240 x 2160. I was also seeing the same thing on my other > computer with a 32” ultra widescreen resolution of 2560 x 1080. > I’m also seeing this on v2.6.1 and v2.7.0-rc2. Is there a setting > I need to adjust, or is this something that requires a program > change to fix? > > 73 > > -.. . / -- .- .-. -.- / -. --... -.-- -.. > > DE MARK N7YD > > > > A long standing defect that I gave up on getting the devs to correct. > > All other UI controls inducing the Tx1-6 buttons are scaled correctly > except these buttons! > > Here's mine, like you replicated across multiple devices. > > > de Laurie VK3AMA > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... <mailto:wsj...@li...> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Mark G. <n7...@mg...> - 2025-04-15 00:26:59
|
I suppose the images included in my email are making it too large for the mailing list. I’m forwarding this back to the wsjt-devel team with the images removed. Anyone wanting to see the full email with the images restored can email me for a direct copy. 73 -.. . / -- .- .-. -.- / -. --... -.-- -.. DE MARK N7YD From: Mark Galbraith Sent: Sunday, April 13, 2025 17:25 To: Black Michael <mdb...@ya...>; WSJT software development <wsj...@li...>; Mark Galbraith <ma...@mg...> Subject: RE: [wsjt-devel] Button sizes not correct I apologize for the long delay in replying. I had gotten feedback that this was not something that could be fixed, so I set it aside. However, my background in programming would not let this go, and eventually I had time and the drive to dig into this further. Along the way I determined the use of Qt tools and dug into this a bit more. I found the location where the UI buttons are set, and saw they have a minimum size of 32. I couldn’t see anything else that jumped out of the source code, so I went looking for other information available. I found a few items on StackOvervlow and eventually found this article on the Qt Forum that seemed to be on point. https://doc.qt.io/qt-5/highdpi.html In reading through, I see that there is a workaround by setting the environment variable QT_ENABLE_HIGHDPI_SCALING prior to running the application should enable the high-DPI support. I ran some experiments, and this is what I found. BEFORE The buttons on the main UI panel are clipped: And the font size on the waterfall display is huge: AFTER setting the environment variable: The buttons as well asother screen elements are no longer clipped: And the waterfall font size is back to normal: CONCLUSION The WSJT-X program will display properly if the high-DPI support in Qt is enabled. While setting the environment variable is a workaround for this, the proper course of action would be to enable this support in the source code. According to the StackOverflow pages, the following line, executed prior to initializing the application will enable the high-DPI support. QApplication::setAttribute(Qt::AA_EnableHighDpiScaling); In the WSJT-X, the initialization of the Qt application occurs inside ExceptionCatchingApplication.hpp, which is included into main.cpp and called at line 118 (as found in the 2.7.0 code on SourceForge). In my view, inserting the above “setAttribute” just above line 118 will properly enable the high-DPI support for Qt, and solve this and possibly many other issues with users of high-DPI monitors in the userbase. Please feel free to reach out if you have any questions or would like to discuss this issue further. 73 -.. . / -- .- .-. -.- / -. --... -.-- -.. DE MARK N7YD From: Black Michael <mdb...@ya...<mailto:mdb...@ya...>> Sent: Friday, September 1, 2023 12:53 To: WSJT software development <wsj...@li...<mailto:wsj...@li...>>; Mark Galbraith <n7...@mg...<mailto:n7...@mg...>>; mark mgg4.com <ma...@mg...<mailto:ma...@mg...>> Subject: Re: [wsjt-devel] Button sizes not correct Can you provide a screen shot? What font are you using -- I have Microsoft Sans Serif 8pt. Mike W9MDB On Friday, September 1, 2023 at 01:01:45 PM CDT, mark mgg4.com <ma...@mg...<mailto:ma...@mg...>> wrote: After switching back, and the problem with the button sizes returns, I make the following observations. 1. The text margins for the “H” button seem to be correct. 2. The remaining buttons in the column use the same button size as the “H” button. 3. Scaling those buttons on one of the longer button labels may resolve the problem for all resolutions. I’m a retired programmer with 45 years of experience. I’ve seen these types of problems many times. Sometimes, the hard problems have easy solutions. Other times you grab a big hammer… --Mark From: mark mgg4.com via wsjt-devel <wsj...@li...<mailto:wsj...@li...>> Sent: Friday, September 1, 2023 10:54 AM To: Black Michael <mdb...@ya...<mailto:mdb...@ya...>>; WSJT software development <wsj...@li...<mailto:wsj...@li...>>; Mark Galbraith <n7...@mg...<mailto:n7...@mg...>> Cc: mark mgg4.com <ma...@mg...<mailto:ma...@mg...>> Subject: Re: [wsjt-devel] Button sizes not correct All of them. Most annoying is the Log popup which I have positioned for easy tapping (touch screen). --Mark From: Black Michael <mdb...@ya...<mailto:mdb...@ya...>> Sent: Friday, September 1, 2023 10:52 AM To: WSJT software development <wsj...@li...<mailto:wsj...@li...>>; Mark Galbraith <n7...@mg...<mailto:n7...@mg...>> Cc: mark mgg4.com <ma...@mg...<mailto:ma...@mg...>> Subject: Re: [wsjt-devel] Button sizes not correct Which windows? On Friday, September 1, 2023 at 12:46:50 PM CDT, Mark Galbraith <n7...@mg...<mailto:n7...@mg...>> wrote: After a few more experiments, I’ve reverted this change. The program no longer remembers where certain windows open on the screen, opening all windows in the center. This is a bit more disruptive than the narrow buttons. --Mark, N7YD From: mark mgg4.com via wsjt-devel <wsj...@li...<mailto:wsj...@li...>> Sent: Friday, September 1, 2023 10:37 AM To: Black Michael <mdb...@ya...<mailto:mdb...@ya...>>; WSJT software development <wsj...@li...<mailto:wsj...@li...>> Cc: mark mgg4.com <ma...@mg...<mailto:ma...@mg...>> Subject: Re: [wsjt-devel] Button sizes not correct Thank you. That does change a few things, and some of the text seems a bit less sharp, but it does fix the problem and I like the overall effect better. I very much appreciate your response. --Mark, N7YD From: Black Michael via wsjt-devel <wsj...@li...<mailto:wsj...@li...>> Sent: Friday, September 1, 2023 9:25 AM To: WSJT software development <wsj...@li...<mailto:wsj...@li...>> Cc: Black Michael <mdb...@ya...<mailto:mdb...@ya...>> Subject: Re: [wsjt-devel] Button sizes not correct Try this to replace the qt.conf in your bin directory [Paths] Plugins = ../plugins [Platforms] WindowsArguments = dpiawareness=0 Mike W9MDB On Thursday, August 31, 2023 at 10:43:43 PM CDT, Laurie, VK3AMA via wsjt-devel <wsj...@li...<mailto:wsj...@li...>> wrote: On 01/09/2023 8:15 am, Mark Galbraith via wsjt-devel wrote: Not sure what’s happening here, but my guess would be that the screen resolution may be off, but I was seeing this on other computers as well. My computer is a Microsoft Surfacebook 2, with a screen resolution of 3240 x 2160. I was also seeing the same thing on my other computer with a 32” ultra widescreen resolution of 2560 x 1080. I’m also seeing this on v2.6.1 and v2.7.0-rc2. Is there a setting I need to adjust, or is this something that requires a program change to fix? 73 -.. . / -- .- .-. -.- / -. --... -.-- -.. DE MARK N7YD A long standing defect that I gave up on getting the devs to correct. All other UI controls inducing the Tx1-6 buttons are scaled correctly except these buttons! Here's mine, like you replicated across multiple devices. de Laurie VK3AMA _______________________________________________ wsjt-devel mailing list wsj...@li...<mailto:wsj...@li...> https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Charles S. <g3...@gm...> - 2025-04-06 06:31:54
|
Hi David I have found the order in which things are plugged in on Win10 to be important. I have a simple adaptor that plugs into the combined mic/headphone socket on my WIn10 shack machine. The cable either needs to be plugged in after a restart or before the restart (can't remember exactly). Certainly if the right procedure isn't done before WSJT-X is started then it doesn't work. 73 Charlie On Sat, 5 Apr 2025 at 19:51, David Hilton-Jones via wsjt-devel < wsj...@li...> wrote: > Thanks Charlie > > > > That seems to be set OK > > > > David > > > > *From:* Charles Suckling via wsjt-devel <wsj...@li...> > > *Sent:* 05 April 2025 17:33 > *To:* WSJT software development <wsj...@li...> > *Cc:* Charles Suckling <g3...@gm...> > *Subject:* Re: [wsjt-devel] Audio problem after changing to Win 11 > computer with single RTTS audio connector > > > > Hi David > > > > I have heard that Win11 may need mic enabling in some sort of security > settings. > > > > 73 > > > > Charlie DL3WDG > > > > On Sat, 5 Apr 2025 at 19:07, David Hilton-Jones via wsjt-devel < > wsj...@li...> wrote: > > I think this has been addressed recently, but I can’t find a solution. > > > > I previously ran a Win 10 system but decided to replace with a new > computer (Geekom) running Win 11 > > > > I use line in and line out, and on my old computer had separate jack > sockets. > > > > The new computer has a single socket which I presume is TRRS. > > > > I bought an interface cable: > > > > > https://www.amazon.co.uk/dp/B0CMJK8B8C?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1 > > > > > > > > When I activate WSJT it sends tones to the rig, so transmit is OK > > > > But I do not see any signal input from the rig. > > > > I’ve seen previous comments about needing to block DC on the Mic line, and > about adding resistor between Mic and sleeve, but trying those things > didn’t work. > > > > Am I using the correct interface cable? Am I doing something else wrong? > > > > Any help gratefully received > > > > In appreciate it’s not a WSJT software development problem, but I wanted > to ask for as wide range of help as possible! > > > David, G4YTL > > _______________________________________________ > 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 > |
|
From: Reino T. <rei...@ko...> - 2025-04-06 05:29:22
|
>Al, Saturday, April 5, 2025 10:35 PM wrote: ... >You may need to set your mic as a Line In device to turn off the mic dc bias supply. To avoid having to always switch to them, you need to set your Line In/out devices as the *default* devices and enable them in the audio settings panel, which should pop up when the devices are plugged in and, also, be accessible from the task bar audio widget. Hi Al, Although that may be handy setting, it is also a dangerous one. In windows all dings and dongs and possible voice such as Youtube are directed into the "default" audio sink. The wsjt-x output 'speaker' needs to be anything else but "default" or otherwise all those are transmitted on band. 73, Reino OH3mA |
|
From: Alan <al...@al...> - 2025-04-05 21:32:14
|
On my two machines W10 and 11 audio controls are different so some experimentation maybe in order. Test your adapter lead with some 3.5mm plugs and a multimeter to make sure the connections all work as you expect. You may also need to turn off port sensing in the sound system driver - if you can. Alternatively maybe get a USB headphone dongle and use that? They usually have separate mic and headphone sockets and are inexpensive from the usual online sources. Alan G0TLK, sent from my mobile device On 5 April 2025 18:04:14 David Hilton-Jones via wsjt-devel <wsj...@li...> wrote: > I think this has been addressed recently, but I can’t find a solution. > > > > I previously ran a Win 10 system but decided to replace with a new computer > (Geekom) running Win 11 > > > > I use line in and line out, and on my old computer had separate jack sockets. > > > > The new computer has a single socket which I presume is TRRS. > > > > I bought an interface cable: > > > > https://www.amazon.co.uk/dp/B0CMJK8B8C?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1 > > > > > > > > When I activate WSJT it sends tones to the rig, so transmit is OK > > > > But I do not see any signal input from the rig. > > > > I’ve seen previous comments about needing to block DC on the Mic line, and > about adding resistor between Mic and sleeve, but trying those things > didn’t work. > > > > Am I using the correct interface cable? Am I doing something else wrong? > > > > Any help gratefully received > > > > In appreciate it’s not a WSJT software development problem, but I wanted to > ask for as wide range of help as possible! > > > David, G4YTL > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Morris W. <wa...@ya...> - 2025-04-05 20:27:49
|
Hi Dave when you go into settings and audio and input you have another spin box to the right of Line-in that gives you Left, right and mono try all three if none of those work go back and select mic and again try the same second three choices. See if any of these work.
73 Morris WA4MIT
On Saturday, April 5, 2025 at 12:49:48 PM CDT, David Hilton-Jones via wsjt-devel <wsj...@li...> wrote:
<!--#yiv6136379186 filtered {}#yiv6136379186 filtered {}#yiv6136379186 filtered {}#yiv6136379186 p.yiv6136379186MsoNormal, #yiv6136379186 li.yiv6136379186MsoNormal, #yiv6136379186 div.yiv6136379186MsoNormal {margin:0cm;font-size:12.0pt;font-family:"Aptos", sans-serif;}#yiv6136379186 a:link, #yiv6136379186 span.yiv6136379186MsoHyperlink {color:blue;text-decoration:underline;}#yiv6136379186 p.yiv6136379186m1306084515971354005msoplaintext, #yiv6136379186 li.yiv6136379186m1306084515971354005msoplaintext, #yiv6136379186 div.yiv6136379186m1306084515971354005msoplaintext {margin-right:0cm;margin-left:0cm;font-size:12.0pt;font-family:"Aptos", sans-serif;}#yiv6136379186 span.yiv6136379186EmailStyle19 {font-family:"Calibri", sans-serif;color:windowtext;}#yiv6136379186 .yiv6136379186MsoChpDefault {font-size:11.0pt;}#yiv6136379186 filtered {}#yiv6136379186 div.yiv6136379186WordSection1 {}-->
Thanks Charlie
That seems to be set OK
David
From: Charles Suckling via wsjt-devel <wsj...@li...>
Sent: 05 April 2025 17:33
To: WSJT software development <wsj...@li...>
Cc: Charles Suckling <g3...@gm...>
Subject: Re: [wsjt-devel] Audio problem after changing to Win 11 computer with single RTTS audio connector
Hi David
I have heard that Win11 may need mic enabling in some sort of security settings.
73
Charlie DL3WDG
On Sat, 5 Apr 2025 at 19:07, David Hilton-Jones via wsjt-devel <wsj...@li...> wrote:
I think this has been addressed recently, but I can’t find a solution.
I previously ran a Win 10 system but decided to replace with a new computer (Geekom) running Win 11
I use line in and line out, and on my old computer had separate jack sockets.
The new computer has a single socket which I presume is TRRS.
I bought an interface cable:
https://www.amazon.co.uk/dp/B0CMJK8B8C?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1
When I activate WSJT it sends tones to the rig, so transmit is OK
But I do not see any signal input from the rig.
I’ve seen previous comments about needing to block DC on the Mic line, and about adding resistor between Mic and sleeve, but trying those things didn’t work.
Am I using the correct interface cable? Am I doing something else wrong?
Any help gratefully received
In appreciate it’s not a WSJT software development problem, but I wanted to ask for as wide range of help as possible!
David, G4YTL
_______________________________________________
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
|
|
From: <k6...@al...> - 2025-04-05 19:52:23
|
I looked at a Win11 laptop i have and tried plugging in a headset. The LT is an ACER with single, combo audio jack and REALTEK drivers/system. When it sees the headset plugged in, it asks for verification of the device types plugged in and has drop down menus to select Line in/out, speaker, headphone, etc. You may need to set your mic as a Line In device to turn off the mic dc bias supply. To avoid having to always switch to them, you need to set your Line In/out devices as the default devices and enable them in the audio settings panel, which should pop up when the devices are plugged in and, also, be accessible from the task bar audio widget. There are also drop downs to select Mono audio which might be necessary and don’t forget to adjust the PC input gain so WSJTx’s rx meter reads in the 50-60 range. The adapter cable you got is probably electrically right, but should be easy to test (multi-meter, scope, etc.) if you look up your PC’s audio jack connections. Al Pawlowski Los Osos, CA USA > On Apr 5, 2025, at 10:47, wsj...@li... wrote: > > Date: Sat, 5 Apr 2025 16:49:04 -0000 > From: "David Hilton-Jones" <g4...@ao... <mailto:g4...@ao...>> > To: "WSJT software development" <wsj...@li... <mailto:wsj...@li...>>, > "Moon Net" <moo...@gr... <mailto:moo...@gr...>> > Subject: [wsjt-devel] Audio problem after changing to Win 11 computer > with single RTTS audio connector > Message-ID: <001901dba64a$a4b22290$ee1667b0$@aol.com <mailto:001901dba64a$a4b22290$ee1667b0$@aol.com>> > Content-Type: text/plain; charset="us-ascii" > > I think this has been addressed recently, but I can't find a solution. > > > > I previously ran a Win 10 system but decided to replace with a new computer > (Geekom) running Win 11 > > > > I use line in and line out, and on my old computer had separate jack > sockets. > > > > The new computer has a single socket which I presume is TRRS. > > > > I bought an interface cable: > > > > https://www.amazon.co.uk/dp/B0CMJK8B8C?ref=ppx_yo2ov_dt_b_fed_asin_title <https://www.amazon.co.uk/dp/B0CMJK8B8C?ref=ppx_yo2ov_dt_b_fed_asin_title> > <https://www.amazon.co.uk/dp/B0CMJK8B8C?ref=ppx_yo2ov_dt_b_fed_asin_title&th <https://www.amazon.co.uk/dp/B0CMJK8B8C?ref=ppx_yo2ov_dt_b_fed_asin_title&th> > =1> &th=1 > > > > > > > > When I activate WSJT it sends tones to the rig, so transmit is OK > > > > But I do not see any signal input from the rig. > > > > I've seen previous comments about needing to block DC on the Mic line, and > about adding resistor between Mic and sleeve, but trying those things didn't > work. |
|
From: David Hilton-J. <g4...@ao...> - 2025-04-05 17:47:39
|
Thanks Charlie That seems to be set OK David From: Charles Suckling via wsjt-devel <wsj...@li...> Sent: 05 April 2025 17:33 To: WSJT software development <wsj...@li...> Cc: Charles Suckling <g3...@gm...> Subject: Re: [wsjt-devel] Audio problem after changing to Win 11 computer with single RTTS audio connector Hi David I have heard that Win11 may need mic enabling in some sort of security settings. 73 Charlie DL3WDG On Sat, 5 Apr 2025 at 19:07, David Hilton-Jones via wsjt-devel <wsj...@li... <mailto:wsj...@li...> > wrote: I think this has been addressed recently, but I can’t find a solution. I previously ran a Win 10 system but decided to replace with a new computer (Geekom) running Win 11 I use line in and line out, and on my old computer had separate jack sockets. The new computer has a single socket which I presume is TRRS. I bought an interface cable: https://www.amazon.co.uk/dp/B0CMJK8B8C?ref=ppx_yo2ov_dt_b_fed_asin_title <https://www.amazon.co.uk/dp/B0CMJK8B8C?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1> &th=1 When I activate WSJT it sends tones to the rig, so transmit is OK But I do not see any signal input from the rig. I’ve seen previous comments about needing to block DC on the Mic line, and about adding resistor between Mic and sleeve, but trying those things didn’t work. Am I using the correct interface cable? Am I doing something else wrong? Any help gratefully received In appreciate it’s not a WSJT software development problem, but I wanted to ask for as wide range of help as possible! David, G4YTL _______________________________________________ wsjt-devel mailing list wsj...@li... <mailto:wsj...@li...> https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Charles S. <g3...@gm...> - 2025-04-05 17:34:09
|
Hi David I have heard that Win11 may need mic enabling in some sort of security settings. 73 Charlie DL3WDG On Sat, 5 Apr 2025 at 19:07, David Hilton-Jones via wsjt-devel < wsj...@li...> wrote: > I think this has been addressed recently, but I can’t find a solution. > > > > I previously ran a Win 10 system but decided to replace with a new > computer (Geekom) running Win 11 > > > > I use line in and line out, and on my old computer had separate jack > sockets. > > > > The new computer has a single socket which I presume is TRRS. > > > > I bought an interface cable: > > > > > https://www.amazon.co.uk/dp/B0CMJK8B8C?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1 > > > > > > > > When I activate WSJT it sends tones to the rig, so transmit is OK > > > > But I do not see any signal input from the rig. > > > > I’ve seen previous comments about needing to block DC on the Mic line, and > about adding resistor between Mic and sleeve, but trying those things > didn’t work. > > > > Am I using the correct interface cable? Am I doing something else wrong? > > > > Any help gratefully received > > > > In appreciate it’s not a WSJT software development problem, but I wanted > to ask for as wide range of help as possible! > > > David, G4YTL > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > |
|
From: David Hilton-J. <g4...@ao...> - 2025-04-05 16:59:43
|
I think this has been addressed recently, but I can't find a solution. I previously ran a Win 10 system but decided to replace with a new computer (Geekom) running Win 11 I use line in and line out, and on my old computer had separate jack sockets. The new computer has a single socket which I presume is TRRS. I bought an interface cable: https://www.amazon.co.uk/dp/B0CMJK8B8C?ref=ppx_yo2ov_dt_b_fed_asin_title <https://www.amazon.co.uk/dp/B0CMJK8B8C?ref=ppx_yo2ov_dt_b_fed_asin_title&th =1> &th=1 When I activate WSJT it sends tones to the rig, so transmit is OK But I do not see any signal input from the rig. I've seen previous comments about needing to block DC on the Mic line, and about adding resistor between Mic and sleeve, but trying those things didn't work. Am I using the correct interface cable? Am I doing something else wrong? Any help gratefully received In appreciate it's not a WSJT software development problem, but I wanted to ask for as wide range of help as possible! David, G4YTL |
|
From: Uwe, D. <dg...@gm...> - 2025-03-27 09:58:40
|
Hi Dawid, I will contact you off-list. I think I have found a solution. But it still needs to be tested further. 73 de DG2YCB, Uwe ________________________________________ German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg...@gm... Info: www.qrz.com/db/DG2YCB Am 27.03.2025 um 10:01 schrieb Dawid SQ6EMM via wsjt-devel: > Some small update. > > "Bug" (from my perspective) was not introduced in wsjtx-2.1.0-rc5, but > AFTER wsjtx-2.1.0-rc5 binary release. > > Test described in the previous email was done in docker containers > with specified versions installed inside. > > <Dockerfile> > from ubuntu:18.04 > ADD files /tmp > ADD JT4 /JT4 > RUN apt -y update && apt -y dist-upgrade && apt -y install > /tmp/wsjtx_2.1.0-rc7_amd64.deb > </Dockerfile> > > Yesterday evening I have built latest version of wsjtx from git and I > reverted the commit 2044b736dad8444272d3dd5f89cf63716ccbf073. > It did not help - so it seems it's more complicated than only this > commit, but this is where my knowledge of Fortran ends;) > > > > śr., 26 mar 2025 o 22:39 Dawid SQ6EMM <sq...@ha...> napisał(a): > > Hey, for some time I have been playing a lot with JT4(g). > During those exercises it was identified that JT4(g) - I was only > playing with G is incorrectly reporting the SNR (meaning values > are never stronger than -13dB and there is no even indirect > connection between signal strength and JT4g report). > > I described that a little bit broader on wsjt users group here: > > https://wsjtx.groups.io/g/main/topic/111843701 > > But just to reach dev community and ask for fix I think its better > here... > > So simple exercise (test files for JT4 - Charles G3WDG) and two > versions of wsjt: > > for i in *.wav; do echo $i; jt9 -4 -d 3 -b G -f 1000 $i ; done > > wsjtx-2.1.0-rc5: > 000000_0002.wav > 0002 -5 -0.1 1006 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0004.wav > 0004 -7 -0.1 1002 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0006.wav > 0006 -9 -0.1 1000 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0008.wav > 0008 -11 -0.1 1004 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0010.wav > 0010 -13 -0.1 995 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0012.wav > 0012 -15 -0.1 1000 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0014.wav > 0014 -17 -0.1 1004 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0016.wav > 0016 -20 -0.1 998 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0018.wav > 0018 -22 -0.0 995 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0020.wav > 0020 -24 -0.1 1000 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0022.wav > 0022 -26 -0.0 1000 $* > <DecodeFinished> 0 1 > > wsjtx-2.1.0-rc7: > 000000_0002.wav > 0002 -15 -0.1 1006 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0004.wav > 0004 -15 -0.1 1002 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0006.wav > 0006 -15 -0.1 1000 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0008.wav > 0008 -15 -0.1 1004 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0010.wav > 0010 -14 -0.1 995 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0012.wav > 0012 -15 -0.1 1000 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0014.wav > 0014 -15 -0.1 1004 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0016.wav > 0016 -16 -0.1 998 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0018.wav > 0018 -18 -0.0 995 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0020.wav > 0020 -17 -0.1 1000 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0022.wav > 0022 -18 -0.0 1000 $* > <DecodeFinished> 0 1 > > > and additionally I guess the commit that was about to fix it - I > guess might be a reason why its not working correctly now: > > > commit 2044b736dad8444272d3dd5f89cf63716ccbf073 > Author: Joe Taylor <joe@...> > Date: Mon May 20 12:46:36 2019 -0400 > > Fix a bug in calculation of S/N in JT4 mode. > > > Thanks for your help in advance. > > -- > Dawid > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Dawid S. <sq...@ha...> - 2025-03-27 09:09:21
|
Some small update. "Bug" (from my perspective) was not introduced in wsjtx-2.1.0-rc5, but AFTER wsjtx-2.1.0-rc5 binary release. Test described in the previous email was done in docker containers with specified versions installed inside. <Dockerfile> from ubuntu:18.04 ADD files /tmp ADD JT4 /JT4 RUN apt -y update && apt -y dist-upgrade && apt -y install /tmp/wsjtx_2.1.0-rc7_amd64.deb </Dockerfile> Yesterday evening I have built latest version of wsjtx from git and I reverted the commit 2044b736dad8444272d3dd5f89cf63716ccbf073. It did not help - so it seems it's more complicated than only this commit, but this is where my knowledge of Fortran ends;) śr., 26 mar 2025 o 22:39 Dawid SQ6EMM <sq...@ha...> napisał(a): > Hey, for some time I have been playing a lot with JT4(g). > During those exercises it was identified that JT4(g) - I was only playing > with G is incorrectly reporting the SNR (meaning values are never stronger > than -13dB and there is no even indirect connection between signal > strength and JT4g report). > > I described that a little bit broader on wsjt users group here: > > https://wsjtx.groups.io/g/main/topic/111843701 > > But just to reach dev community and ask for fix I think its better here... > > So simple exercise (test files for JT4 - Charles G3WDG) and two versions > of wsjt: > > for i in *.wav; do echo $i; jt9 -4 -d 3 -b G -f 1000 $i ; done > > wsjtx-2.1.0-rc5: > 000000_0002.wav > 0002 -5 -0.1 1006 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0004.wav > 0004 -7 -0.1 1002 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0006.wav > 0006 -9 -0.1 1000 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0008.wav > 0008 -11 -0.1 1004 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0010.wav > 0010 -13 -0.1 995 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0012.wav > 0012 -15 -0.1 1000 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0014.wav > 0014 -17 -0.1 1004 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0016.wav > 0016 -20 -0.1 998 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0018.wav > 0018 -22 -0.0 995 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0020.wav > 0020 -24 -0.1 1000 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0022.wav > 0022 -26 -0.0 1000 $* > <DecodeFinished> 0 1 > > wsjtx-2.1.0-rc7: > 000000_0002.wav > 0002 -15 -0.1 1006 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0004.wav > 0004 -15 -0.1 1002 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0006.wav > 0006 -15 -0.1 1000 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0008.wav > 0008 -15 -0.1 1004 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0010.wav > 0010 -14 -0.1 995 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0012.wav > 0012 -15 -0.1 1000 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0014.wav > 0014 -15 -0.1 1004 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0016.wav > 0016 -16 -0.1 998 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0018.wav > 0018 -18 -0.0 995 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0020.wav > 0020 -17 -0.1 1000 $* CQ DL0SHF JO54 f > <DecodeFinished> 0 1 > 000000_0022.wav > 0022 -18 -0.0 1000 $* > <DecodeFinished> 0 1 > > > and additionally I guess the commit that was about to fix it - I guess > might be a reason why its not working correctly now: > > > commit 2044b736dad8444272d3dd5f89cf63716ccbf073 > Author: Joe Taylor <joe@...> > Date: Mon May 20 12:46:36 2019 -0400 > > Fix a bug in calculation of S/N in JT4 mode. > > > Thanks for your help in advance. > > -- > Dawid > > |
|
From: Dawid S. <sq...@ha...> - 2025-03-26 21:40:13
|
Hey, for some time I have been playing a lot with JT4(g). During those exercises it was identified that JT4(g) - I was only playing with G is incorrectly reporting the SNR (meaning values are never stronger than -13dB and there is no even indirect connection between signal strength and JT4g report). I described that a little bit broader on wsjt users group here: https://wsjtx.groups.io/g/main/topic/111843701 But just to reach dev community and ask for fix I think its better here... So simple exercise (test files for JT4 - Charles G3WDG) and two versions of wsjt: for i in *.wav; do echo $i; jt9 -4 -d 3 -b G -f 1000 $i ; done wsjtx-2.1.0-rc5: 000000_0002.wav 0002 -5 -0.1 1006 $* CQ DL0SHF JO54 f <DecodeFinished> 0 1 000000_0004.wav 0004 -7 -0.1 1002 $* CQ DL0SHF JO54 f <DecodeFinished> 0 1 000000_0006.wav 0006 -9 -0.1 1000 $* CQ DL0SHF JO54 f <DecodeFinished> 0 1 000000_0008.wav 0008 -11 -0.1 1004 $* CQ DL0SHF JO54 f <DecodeFinished> 0 1 000000_0010.wav 0010 -13 -0.1 995 $* CQ DL0SHF JO54 f <DecodeFinished> 0 1 000000_0012.wav 0012 -15 -0.1 1000 $* CQ DL0SHF JO54 f <DecodeFinished> 0 1 000000_0014.wav 0014 -17 -0.1 1004 $* CQ DL0SHF JO54 f <DecodeFinished> 0 1 000000_0016.wav 0016 -20 -0.1 998 $* CQ DL0SHF JO54 f <DecodeFinished> 0 1 000000_0018.wav 0018 -22 -0.0 995 $* CQ DL0SHF JO54 f <DecodeFinished> 0 1 000000_0020.wav 0020 -24 -0.1 1000 $* CQ DL0SHF JO54 f <DecodeFinished> 0 1 000000_0022.wav 0022 -26 -0.0 1000 $* <DecodeFinished> 0 1 wsjtx-2.1.0-rc7: 000000_0002.wav 0002 -15 -0.1 1006 $* CQ DL0SHF JO54 f <DecodeFinished> 0 1 000000_0004.wav 0004 -15 -0.1 1002 $* CQ DL0SHF JO54 f <DecodeFinished> 0 1 000000_0006.wav 0006 -15 -0.1 1000 $* CQ DL0SHF JO54 f <DecodeFinished> 0 1 000000_0008.wav 0008 -15 -0.1 1004 $* CQ DL0SHF JO54 f <DecodeFinished> 0 1 000000_0010.wav 0010 -14 -0.1 995 $* CQ DL0SHF JO54 f <DecodeFinished> 0 1 000000_0012.wav 0012 -15 -0.1 1000 $* CQ DL0SHF JO54 f <DecodeFinished> 0 1 000000_0014.wav 0014 -15 -0.1 1004 $* CQ DL0SHF JO54 f <DecodeFinished> 0 1 000000_0016.wav 0016 -16 -0.1 998 $* CQ DL0SHF JO54 f <DecodeFinished> 0 1 000000_0018.wav 0018 -18 -0.0 995 $* CQ DL0SHF JO54 f <DecodeFinished> 0 1 000000_0020.wav 0020 -17 -0.1 1000 $* CQ DL0SHF JO54 f <DecodeFinished> 0 1 000000_0022.wav 0022 -18 -0.0 1000 $* <DecodeFinished> 0 1 and additionally I guess the commit that was about to fix it - I guess might be a reason why its not working correctly now: commit 2044b736dad8444272d3dd5f89cf63716ccbf073 Author: Joe Taylor <joe@...> Date: Mon May 20 12:46:36 2019 -0400 Fix a bug in calculation of S/N in JT4 mode. Thanks for your help in advance. -- Dawid |
|
From: Tom H. <rdr...@gm...> - 2025-03-17 18:18:00
|
I updated to 2.7.0 on my computer and at the same time it did a Windows update (Windows 10 KB5053606). Now WSJT-X does not appear to send any UDP messages! I do not think this is a WSJT-X problem, I believe it is because of the Windows update. I have the laptop I just used on my trip to St. Kitts. Sames Windows 10 and 2.7.0 WSJT-X. It was working fine until this same Windows update! Now it doesn't work either. I am using N3FJP Logging software. The address is correct and verified but the logging software just sits and waits for WSJT-X and nothing happens!! Anybody else have this problem? I now have 2 computers that have exactly the same problem!! 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 |
|
From: Frode I. <fro...@gm...> - 2025-03-11 23:10:09
|
The reference says "in preparation", so it is probably not prepared yet. It will come when prepared. Frode, LA6VQ <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virusfri.www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> tor. 6. mars 2025 kl. 20:02 skrev Scott Armstrong via wsjt-devel < wsj...@li...>: > David, > > I didn't find anything stashed on my PC in regards to the reference 2. > The reference looks incomplete the way it is documented. Maybe Joe or one > of the other developers knows what it is and where it is hiding. > > -Scott > > On Thu, Mar 6, 2025 at 12:19 PM Scott Armstrong <aa5...@gm...> > wrote: > >> >> >> https://wsjt.sourceforge.io/FST4_Quick_Start.pdf >> >> -Scott AA5AM >> >> On Thu, Mar 6, 2025 at 12:12 PM David R. Andersen via wsjt-devel < >> wsj...@li...> wrote: >> >>> Can anyone point me to a copy of Ref. 2 from the FST4 Quick Start >>> guide? >>> >>> [2] Steve Franke, K9AN, Bill Somerville, G4WJS, Joe Taylor, K1JT, in >>> preparation. >>> >>> Thanks and 73, >>> Dave K0RX >>> >>> -- >>> int x=90560580,y=32678;main(){putchar(x);x>>=y&7;y>>=3;return >>> y?main():0;} >>> David Andersen >>> >>> "Of all tyrannies, a tyranny sincerely exercised for the good >>> of its victims may be the most oppressive. It would be better >>> to live under robber barons than under omnipotent moral >>> busybodies. The robber baron's cruelty may sometimes sleep, >>> his cupidity may at some point be satiated; but those who >>> torment us for our own good will torment us without end for >>> they do so with the approval of their own conscience." >>> - C. S. Lewis >>> >>> >>> _______________________________________________ >>> 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 > |
|
From: Scott A. <aa5...@gm...> - 2025-03-06 18:55:09
|
David, I didn't find anything stashed on my PC in regards to the reference 2. The reference looks incomplete the way it is documented. Maybe Joe or one of the other developers knows what it is and where it is hiding. -Scott On Thu, Mar 6, 2025 at 12:19 PM Scott Armstrong <aa5...@gm...> wrote: > > > https://wsjt.sourceforge.io/FST4_Quick_Start.pdf > > -Scott AA5AM > > On Thu, Mar 6, 2025 at 12:12 PM David R. Andersen via wsjt-devel < > wsj...@li...> wrote: > >> Can anyone point me to a copy of Ref. 2 from the FST4 Quick Start >> guide? >> >> [2] Steve Franke, K9AN, Bill Somerville, G4WJS, Joe Taylor, K1JT, in >> preparation. >> >> Thanks and 73, >> Dave K0RX >> >> -- >> int x=90560580,y=32678;main(){putchar(x);x>>=y&7;y>>=3;return y?main():0;} >> David Andersen >> >> "Of all tyrannies, a tyranny sincerely exercised for the good >> of its victims may be the most oppressive. It would be better >> to live under robber barons than under omnipotent moral >> busybodies. The robber baron's cruelty may sometimes sleep, >> his cupidity may at some point be satiated; but those who >> torment us for our own good will torment us without end for >> they do so with the approval of their own conscience." >> - C. S. Lewis >> >> >> _______________________________________________ >> wsjt-devel mailing list >> wsj...@li... >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> > |
|
From: Scott A. <aa5...@gm...> - 2025-03-06 18:20:14
|
https://wsjt.sourceforge.io/FST4_Quick_Start.pdf -Scott AA5AM On Thu, Mar 6, 2025 at 12:12 PM David R. Andersen via wsjt-devel < wsj...@li...> wrote: > Can anyone point me to a copy of Ref. 2 from the FST4 Quick Start > guide? > > [2] Steve Franke, K9AN, Bill Somerville, G4WJS, Joe Taylor, K1JT, in > preparation. > > Thanks and 73, > Dave K0RX > > -- > int x=90560580,y=32678;main(){putchar(x);x>>=y&7;y>>=3;return y?main():0;} > David Andersen > > "Of all tyrannies, a tyranny sincerely exercised for the good > of its victims may be the most oppressive. It would be better > to live under robber barons than under omnipotent moral > busybodies. The robber baron's cruelty may sometimes sleep, > his cupidity may at some point be satiated; but those who > torment us for our own good will torment us without end for > they do so with the approval of their own conscience." > - C. S. Lewis > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > |
|
From: David R. A. <k0...@rx...> - 2025-03-06 18:04:39
|
Can anyone point me to a copy of Ref. 2 from the FST4 Quick Start
guide?
[2] Steve Franke, K9AN, Bill Somerville, G4WJS, Joe Taylor, K1JT, in
preparation.
Thanks and 73,
Dave K0RX
--
int x=90560580,y=32678;main(){putchar(x);x>>=y&7;y>>=3;return y?main():0;}
David Andersen
"Of all tyrannies, a tyranny sincerely exercised for the good
of its victims may be the most oppressive. It would be better
to live under robber barons than under omnipotent moral
busybodies. The robber baron's cruelty may sometimes sleep,
his cupidity may at some point be satiated; but those who
torment us for our own good will torment us without end for
they do so with the approval of their own conscience."
- C. S. Lewis
|
|
From: Charles S. <g3...@gm...> - 2025-03-06 11:35:02
|
Thanks, Nic I had a look at the commits related to QMAP since RC8 and can't see anything there that looks relevant. The only thing that did change with QMAP, that I think was in -RC8 also, was a change to the behaviour of clicking decodes in the Active Stations window. Now, a single click prepares WSJT-X to call the station but does not enable TX. Double click also enables TX. Previously a single click would prepare WSJT-X and also enable TX. 73 Charlie DL3WDG On Thu, 6 Mar 2025 at 11:43, Nic Sears via wsjt-devel < wsj...@li...> wrote: > Hi Charlie, > > My crash was running W11 with all the latest updates and Norton. Only seen > 1 and was running q65. > > Nic G3YEG > > On 6 Mar 2025 10:25, Charles Suckling via wsjt-devel < > wsj...@li...> wrote: > > Hi David > > Strange since as far as I'm aware no changes were made to the QMAP code in > going from final -RC version to the GA version. I will check the commits > though. > > 73 > > Charlie > > On Thu, 6 Mar 2025 at 11:21, David Hilton-Jones <g4...@ao...> wrote: > > Thanks Charlie > > Same Win10 system I’ve been using for many years (as an aside, planning to > change computer and go to Win11 later this month, so rather anticipating > disaster?) > > Never seen a crash with rc versions. Only since latest definitive release > > > David > > > Sent from the all-new AOL app for iOS > <https://apps.apple.com/us/app/aol-news-email-weather-video/id646100661> > > On Thursday, March 6, 2025, 10:12 am, Charles Suckling <g3...@gm...> > wrote: > > Hi David > > It might be a useful start to know what PC operating system was in use. > Not saying that this could be relevant, but perhaps useful to look for > correlations. > > I have never seen QMAP crash here, on Win10 and Win7 machines, using both > WSJT-X and WSJT-X -improved. > > 73 > > Charlie DL3WDG > > On Wed, 5 Mar 2025 at 15:42, David Hilton-Jones via wsjt-devel < > wsj...@li...> wrote: > > Thanks Nic > > > > Same here – no crashes with RC versions, although others say it has for > them > > > David > > > > *From:* Nic Sears via wsjt-devel [mailto:wsj...@li...] > > *Sent:* 05 March 2025 13:33 > *To:* WSJT software development > *Cc:* Nic Sears > *Subject:* Re: [wsjt-devel] QMAP crash > > > > Also seen 1 crash with 2.7.0 released version. More than last 6 months > running RC versions without a crash. > > > > Nic G3YEG > > > > On 5 Mar 2025 12:37, David Hilton-Jones via wsjt-devel < > wsj...@li...> wrote: > > Since I downloaded the latest WSJT (v2.7.0) release, QMAP has on two > occasions crashed/disappeared off screen. SDRC continues to run. Maybe > just > coincidence and something to do with my set up, but any other similar > reports? > > David, G4YTL > > > > _______________________________________________ > 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 > |
|
From: Nic S. <nic...@ta...> - 2025-03-06 10:37:57
|
<div dir='auto'>Hi Charlie,<div dir="auto"><br></div><div dir="auto">My crash was running W11 with all the latest updates and Norton. Only seen 1 and was running q65.</div><div dir="auto"><br></div><div dir="auto">Nic G3YEG </div></div><div class="gmail_extra"><br><div class="gmail_quote">On 6 Mar 2025 10:25, Charles Suckling via wsjt-devel <wsj...@li...> wrote:<br type="attribution" /><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div style="font-size:large">Hi David</div><div style="font-size:large"><br /></div><div style="font-size:large">Strange since as far as I'm aware no changes were made to the QMAP code in going from final -RC version to the GA version. I will check the commits though.</div><div style="font-size:large"><br /></div><div style="font-size:large">73</div><div style="font-size:large"><br /></div><div style="font-size:large">Charlie</div></div><br /><div><div dir="ltr">On Thu, 6 Mar 2025 at 11:21, David Hilton-Jones <<a href="mailto:g4ytl@aol.com">g4ytl@aol.com</a>> wrote:<br /></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb( 204 , 204 , 204 );padding-left:1ex"><div> Thanks Charlie <div><br /></div><div>Same Win10 system I’ve been using for many years (as an aside, planning to change computer and go to Win11 later this month, so rather anticipating disaster?)</div><div><br /></div><div>Never seen a crash with rc versions. Only since latest definitive release </div><div><br /></div><div><br /></div><div>David<br /><br /><br /><div><a style="font-size:12px" href="https://apps.apple.com/us/app/aol-news-email-weather-video/id646100661">Sent from the all-new AOL app for iOS</a><br /></div><br /><p style="font-size:15px;color:rgb( 132 , 115 , 255 );padding-top:15px;margin-top:0px">On Thursday, March 6, 2025, 10:12 am, Charles Suckling <<a href="mailto:g3wdg1@gmail.com">g3wdg1@gmail.com</a>> wrote:</p><blockquote><div><div><div dir="ltr"><div style="font-size:large">Hi David</div><div style="font-size:large"><br clear="none" /></div><div style="font-size:large">It might be a useful start to know what PC operating system was in use. Not saying that this could be relevant, but perhaps useful to look for correlations.</div><div style="font-size:large"><br clear="none" /></div><div style="font-size:large">I have never seen QMAP crash here, on Win10 and Win7 machines, using both WSJT-X and WSJT-X -improved. </div><div style="font-size:large"><br clear="none" /></div><div style="font-size:large">73</div><div style="font-size:large"><br clear="none" /></div><div style="font-size:large">Charlie DL3WDG</div></div><br clear="none" /><div><div><div dir="ltr">On Wed, 5 Mar 2025 at 15:42, David Hilton-Jones via wsjt-devel <<a shape="rect" href="mailto:wsjt-devel@lists.sourceforge.net">wsjt-devel@lists.sourceforge.net</a>> wrote:<br clear="none" /></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb( 204 , 204 , 204 );padding-left:1ex"><div><div><div><p>Thanks Nic<u></u><u></u></p><p><u></u> <u></u></p><p>Same here – no crashes with RC versions, although others say it has for them<u></u><u></u></p><p><br clear="none" />David<u></u><u></u></p><p><u></u> <u></u></p><p><b>From:</b> Nic Sears via wsjt-devel [mailto:<a shape="rect" href="mailto:wsjt-devel@lists.sourceforge.net">wsjt-devel@lists.sourceforge.net</a>] <br clear="none" /><b>Sent:</b> 05 March 2025 13:33<br clear="none" /><b>To:</b> WSJT software development<br clear="none" /><b>Cc:</b> Nic Sears<br clear="none" /><b>Subject:</b> Re: [wsjt-devel] QMAP crash<u></u><u></u></p><p><u></u> <u></u></p><div><p>Also seen 1 crash with 2.7.0 released version. More than last 6 months running RC versions without a crash.<u></u><u></u></p><div><p><u></u> <u></u></p></div><div><p>Nic G3YEG <u></u><u></u></p></div></div><div><p><u></u> <u></u></p><div><p>On 5 Mar 2025 12:37, David Hilton-Jones via wsjt-devel <<a shape="rect" href="mailto:wsjt-devel@lists.sourceforge.net">wsjt-devel@lists.sourceforge.net</a>> wrote:<u></u><u></u></p><p>Since I downloaded the latest WSJT (v2.7.0) release, QMAP has on two <br clear="none" />occasions crashed/disappeared off screen. SDRC continues to run. Maybe just <br clear="none" />coincidence and something to do with my set up, but any other similar <br clear="none" />reports? <br clear="none" /><br clear="none" />David, G4YTL <br clear="none" /><br clear="none" /><br clear="none" /><br clear="none" />_______________________________________________ <br clear="none" />wsjt-devel mailing list <br clear="none" /><a shape="rect" href="mailto:wsjt-devel@lists.sourceforge.net">wsjt-devel@lists.sourceforge.net</a> <br clear="none" /><a shape="rect" href="https://lists.sourceforge.net/lists/listinfo/wsjt-devel">https://lists.sourceforge.net/lists/listinfo/wsjt-devel</a> <u></u><u></u></p></div><p><u></u> <u></u></p></div></div></div>_______________________________________________<br clear="none" /> wsjt-devel mailing list<br clear="none" /> <a shape="rect" href="mailto:wsjt-devel@lists.sourceforge.net">wsjt-devel@lists.sourceforge.net</a><br clear="none" /> <a shape="rect" href="https://lists.sourceforge.net/lists/listinfo/wsjt-devel">https://lists.sourceforge.net/lists/listinfo/wsjt-devel</a><br clear="none" /> </div></blockquote></div></div> </div></div><blockquote></blockquote></blockquote></div> </div></blockquote></div> </blockquote></div><br></div> |
|
From: Charles S. <g3...@gm...> - 2025-03-06 10:25:47
|
Hi David Strange since as far as I'm aware no changes were made to the QMAP code in going from final -RC version to the GA version. I will check the commits though. 73 Charlie On Thu, 6 Mar 2025 at 11:21, David Hilton-Jones <g4...@ao...> wrote: > Thanks Charlie > > Same Win10 system I’ve been using for many years (as an aside, planning to > change computer and go to Win11 later this month, so rather anticipating > disaster?) > > Never seen a crash with rc versions. Only since latest definitive release > > > David > > > Sent from the all-new AOL app for iOS > <https://apps.apple.com/us/app/aol-news-email-weather-video/id646100661> > > On Thursday, March 6, 2025, 10:12 am, Charles Suckling <g3...@gm...> > wrote: > > Hi David > > It might be a useful start to know what PC operating system was in use. > Not saying that this could be relevant, but perhaps useful to look for > correlations. > > I have never seen QMAP crash here, on Win10 and Win7 machines, using both > WSJT-X and WSJT-X -improved. > > 73 > > Charlie DL3WDG > > On Wed, 5 Mar 2025 at 15:42, David Hilton-Jones via wsjt-devel < > wsj...@li...> wrote: > > Thanks Nic > > > > Same here – no crashes with RC versions, although others say it has for > them > > > David > > > > *From:* Nic Sears via wsjt-devel [mailto:wsj...@li...] > > *Sent:* 05 March 2025 13:33 > *To:* WSJT software development > *Cc:* Nic Sears > *Subject:* Re: [wsjt-devel] QMAP crash > > > > Also seen 1 crash with 2.7.0 released version. More than last 6 months > running RC versions without a crash. > > > > Nic G3YEG > > > > On 5 Mar 2025 12:37, David Hilton-Jones via wsjt-devel < > wsj...@li...> wrote: > > Since I downloaded the latest WSJT (v2.7.0) release, QMAP has on two > occasions crashed/disappeared off screen. SDRC continues to run. Maybe > just > coincidence and something to do with my set up, but any other similar > reports? > > David, G4YTL > > > > _______________________________________________ > 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 > > |
|
From: David Hilton-J. <g4...@ao...> - 2025-03-06 10:21:20
|
Thanks Charlie Same Win10 system I’ve been using for many years (as an aside, planning to change computer and go to Win11 later this month, so rather anticipating disaster?) Never seen a crash with rc versions. Only since latest definitive release David Sent from the all-new AOL app for iOS On Thursday, March 6, 2025, 10:12 am, Charles Suckling <g3...@gm...> wrote: Hi David It might be a useful start to know what PC operating system was in use. Not saying that this could be relevant, but perhaps useful to look for correlations. I have never seen QMAP crash here, on Win10 and Win7 machines, using both WSJT-X and WSJT-X -improved. 73 Charlie DL3WDG On Wed, 5 Mar 2025 at 15:42, David Hilton-Jones via wsjt-devel <wsj...@li...> wrote: Thanks Nic Same here – no crashes with RC versions, although others say it has for them David From: Nic Sears via wsjt-devel [mailto:wsj...@li...] Sent: 05 March 2025 13:33 To: WSJT software development Cc: Nic Sears Subject: Re: [wsjt-devel] QMAP crash Also seen 1 crash with 2.7.0 released version. More than last 6 months running RC versions without a crash. Nic G3YEG On 5 Mar 2025 12:37, David Hilton-Jones via wsjt-devel <wsj...@li...> wrote: Since I downloaded the latest WSJT (v2.7.0) release, QMAP has on two occasions crashed/disappeared off screen. SDRC continues to run. Maybe just coincidence and something to do with my set up, but any other similar reports? David, G4YTL _______________________________________________ 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 |
68 messages has been excluded from this view by a project administrator.
