Re: [wsjt-devel] Bug Report (WSJT-X v1.7.0 r7405 on Mac OS X) (Keith Laaks) (Bill Somerville)

[Keith Laaks]

Hi All,

So I installed a fresh copy of the latest Qt 5.8 this afternoon and rebuilt 
WSJTX v1.7.1-devel (@ r7561) expecting to see some build errors I had last time 
round - but there were none!

And I am very happy to report that when using Qt 5.8 - I have not seen the same 
issue again!!

So I recommend using Qt 5.8 now going forward when building WSJTX to run on 
MacOS 10.12.

Thanks for all the information, feedback, etc. from all who assisted and guided 
us on this issue.

Best Regards

Keith
zs6tw 



> On 19 Feb 2017, at 5:11 PM, wsjt-devel-requ...@lists.sourceforge.net wrote:
> 
> Message: 1
> Date: Sun, 19 Feb 2017 11:20:44 +0100
> From: Claude Frantz <claude.fra...@bayern-mail.de 
> <mailto:claude.fra...@bayern-mail.de>>
> Subject: Re: [wsjt-devel] Bug Report (WSJT-X v1.7.0 r7405 on Mac OS X)
>   (Keith Laaks) (Bill Somerville)
> To: wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
> Message-ID: <3843937e-f5a2-7ffd-3132-9edfa91d4...@bayern-mail.de 
> <mailto:3843937e-f5a2-7ffd-3132-9edfa91d4...@bayern-mail.de>>
> Content-Type: text/plain; charset=utf-8
> 
> On 02/19/2017 10:12 AM, Keith Laaks wrote:
> 
> Hi Keith and All,
> 
>> This morning I installed FLRIG (which supports my FT-991) + FLDIGI
>> ver 3.23.21 (no support for FT-991) and re-installed Silicon Labs
>> driver so that FLRIG could control the radio PTT via CAT.
>> 
>> I tested using several modes, the TX->RX->TX etc. No problems at all.
>> 
>> 
>> Looks like FLDIGI does not use Qt.
> 
> Exactly ! It uses fltk 1.3.
> 
> As I have mentioned previously, it is possible to send commands to flrig
> using the adequate XMLRPC interface.
> 
> Best 88 de Claude (DJ0OT)

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Bug Report (WSJT-X v1.7.0 r7405 on Mac OS X) (Keith Laaks) (Bill Somerville)

[Keith Laaks]

Hi,

This morning I installed FLRIG (which supports my FT-991) + FLDIGI ver 3.23.21 
(no support for FT-991) and re-installed Silicon Labs driver so that FLRIG 
could control the radio PTT via CAT.

I tested using several modes, the TX->RX->TX etc. 
No problems at all. 

Looks like FLDIGI does not use Qt. 
Liker includes CoreAudio, AudioToolbox, AudioUnit frameworks + Carbon, Cocoa 
and links in portaudio libs.

I have no idea how these drivers and frameworks are layered. 
But since FLDIGI works perfectly, it does seem to indicate that the "USB AUDIO 
CODEC” drivers seem to be OK - unless the manner in which Qt talks to it is 
different and triggers some issue causing this.

But I guess its more likely a Qt compatibility issue?
I have tried building with the very latest Qt 5.8, but build errors….
With Qt 5.5 through 5.7 I have the audio issue.

Does anyone know of a suitable application that uses Qt which I can use to see 
if the same issue happens there?
If it does, it would confirm a Qt issue.  

If it does not break in a similar manner, I guess it must be some issue with 
the manner in which WSJTX is set up to consume Qt audio services that is 
breaking for some reason on the newer OSX’s.

73s.

Keith
Zs6tw
   

> --
> 
> Message: 4
> Date: Sat, 18 Feb 2017 22:34:29 +0200
> From: Keith Laaks <wkla...@gmail.com>
> Subject: Re: [wsjt-devel] Bug Report (WSJT-X v1.7.0 r7405 on Mac OS X)
>   (Keith Laaks) (Bill Somerville)
> To: WSJT software development <wsjt-devel@lists.sourceforge.net>
> Message-ID: <245970bd-c8d3-432d-90ce-aef2b7a15...@gmail.com>
> Content-Type: text/plain; charset=utf-8
> 
> Hi Bill,
> 
> Regarding: ?
>>> Reading the emails on this issue, it looks like a low level USB reset
>>> due to I/O errors. And this causes the audio devices to change order 
>>> or so, right? Then, why do you think it is the Silicon Labs driver 
>>> that causes this? Isn't that driver only used to interface the CP210 
>>> UART to USB bridge chip (the serial port for CAT stuff), not the
>>> overall low level USB protocol and the audio channels?"
> 
> I was not aware that MacOS natively came with the driver for the USB audio. 
> At some point in the past I was not able to get the audio working till I 
> installed the Silicon Labs driver and I guess that why I just assumed they 
> also did the audio part.
> 
> Anyhow, I implemented your suggestion here and uninstalled the Silicon Labs 
> driver, then rebooted.
> I then repeated experimentation with WSJTX working through some TX->RX->TX 
> cycles.
> 
> It breaks in a similar manner - after 4-6 cycles, audio out switches to the 
> MacBook speakers. 
> And WSJTX then stops receiving completely.
> Need to close and reopen - then receive works properly again.
> 
> I even tried upgrading to 10.12.4 Beta - makes no difference.
> 
> I do not see the 'IOUSBHostHIDDevice: IOUSBHostHIDDevice::interruptRetry: 
> resetting device due to IO failures? messages in the dmesg logs any more. 
> 
> When I run windows 7 within a VM on the Mac, and map the USB port natively to 
> the Windows VM, WSJTX does not give this problem. It never ?freezes? like 
> this.
> But its not really usable for me like this since the audio has a slight 
> ?buffering? effect with a very small ?pause? in the TX audio every second or 
> so. 
> Anyhow this does tend to eliminate any issues with my USB port, cable or 
> radio. Cable + Radio + WSJTX worked 100% on older OS X 10.11 before I 
> upgraded. 
> 
> Very frustrated at this point?.
> 
> 73?s 
> Keith


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Bug Report (WSJT-X v1.7.0 r7405 on Mac OS X) (Keith Laaks) (Bill Somerville)

[Keith Laaks]

Hi Bill,

Regarding: “
>> Reading the emails on this issue, it looks like a low level USB reset
>> due to I/O errors. And this causes the audio devices to change order 
>> or so, right? Then, why do you think it is the Silicon Labs driver 
>> that causes this? Isn't that driver only used to interface the CP210 
>> UART to USB bridge chip (the serial port for CAT stuff), not the
>> overall low level USB protocol and the audio channels?"

I was not aware that MacOS natively came with the driver for the USB audio. 
At some point in the past I was not able to get the audio working till I 
installed the Silicon Labs driver and I guess that why I just assumed they also 
did the audio part.

Anyhow, I implemented your suggestion here and uninstalled the Silicon Labs 
driver, then rebooted.
I then repeated experimentation with WSJTX working through some TX->RX->TX 
cycles.

It breaks in a similar manner - after 4-6 cycles, audio out switches to the 
MacBook speakers. 
And WSJTX then stops receiving completely.
Need to close and reopen - then receive works properly again.

I even tried upgrading to 10.12.4 Beta - makes no difference.

I do not see the 'IOUSBHostHIDDevice: IOUSBHostHIDDevice::interruptRetry: 
resetting device due to IO failures’ messages in the dmesg logs any more. 

When I run windows 7 within a VM on the Mac, and map the USB port natively to 
the Windows VM, WSJTX does not give this problem. It never ‘freezes’ like this.
But its not really usable for me like this since the audio has a slight 
‘buffering’ effect with a very small ‘pause’ in the TX audio every second or 
so. 
Anyhow this does tend to eliminate any issues with my USB port, cable or radio. 
Cable + Radio + WSJTX worked 100% on older OS X 10.11 before I upgraded. 

Very frustrated at this point….

73’s 
Keith



> 
> 
> 
> --
> 
> Message: 1
> Date: Thu, 16 Feb 2017 22:16:48 +
> From: Bill Somerville <g4...@classdesign.com>
> Subject: Re: [wsjt-devel] Bug Report (WSJT-X v1.7.0 r7405 on Mac OS X)
>   (Keith Laaks)
> To: wsjt-devel@lists.sourceforge.net
> Message-ID: <4e7496d6-cbf4-3a41-914e-f08b9a449...@classdesign.com>
> Content-Type: text/plain; charset=windows-1252; format=flowed
> 
> On 16/02/2017 22:00, Ulderico Arcidiaco wrote:
>> Reading the emails on this issue, it looks like a low level USB reset 
>> due to I/O errors. And this causes the audio devices to change order 
>> or so, right? Then, why do you think it is the Silicon Labs driver 
>> that causes this? Isn't that driver only used to interface the CP210 
>> UART to USB bridge chip (the serial port for CAT stuff), not the 
>> overall low level USB protocol and the audio channels?
>> 
>> You can indeed uninstall the Silicon Labs driver and still use the USB 
>> connection for audio I/O with your rig. In fact, if you suspect the 
>> Silicon Labs driver, you should actually try removing it, and using 
>> the USB for audio only, using vox to TX with your rig. If this works, 
>> then maybe the Silicon Labs driver is the bad guy in town, otherwise 
>> it is a different problem.
> 
> Hi Ulde & all,
> 
> this is good advice and is consistent with at least one Mac OS X user 
> solving this issue of unprompted USB audio device switches by installing 
> an older VCP driver. Note that the SILabs VCP driver is not the problem 
> in isolation, there is definitely an o/s version dependency as well 
> since this issue only started from OS X 10.10 onwards.
> 
> 73
> Bill
> G4WJS.
> 
> 
> 


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Bug Report (WSJT-X v1.7.0 r7405 on Mac OS X) (Keith Laaks)

[Keith Laaks]

Hi Siegfried,

I noticed that my Wife’s MacBook was still on 10.11.6 (El Capitan).
So installed the Silicon Labs driver (4.10.14), then WSJTX 1.7.0.
Hooked up using the same cable to the same Radio.

Everything works 100% I am unable to reproduce the problem at all no matter how 
many times I go TX->RX->TX etc.
So I believe the root of the problem here must be that the update to 11.12 
(Sierra) is what broke something in the Silicon Labs USB driver we need to use 
for talking to the FT-991.

My work Laptop is an identical model to what my wife uses, but also already 
updated to 10.12.
This afternoon I installed the exact same Silicon Labs driver and then WSJTX 
1.7.0 and it also fails exactly in the same manner as my shack’s ‘older’ 
MacBook Pro (17”).
So this is definitely not an issue with RF getting in, or USB interface, or 
cable or the radio.

Looks like the only fix here then is to get Silicon Labs / Yaesu to get the 
driver fixed such that it works properly on 10.12.X.

And the recommendation then needs to be that until this is fixed - hams should 
perhaps not upgrade to Sierra - or risk struggling with this dreaded issue.

Its good that you are able to reproduce something similar. Your additional 
debug message may help in pointing Silicon Labs in the right direction to debug 
their driver.


Best Regards

Keith
ZS6TW




> On 16 Feb 2017, at 9:18 AM, DI Siegfried Hanisch 
> <siegfried.hani...@hanisch.com> wrote:
> 
> Hi
> 
> when checking the output of "sudo dmesg“, I saw two strange things:
> 1) I can npt say when this happened, i.e. if the device was still ok then or 
> not
> WARNING: AppleUSBAudio has detected that a connected USB audio device is 
> sending too much audio data.
> WARNING: This USB audio device may not function properly. Please notify the 
> device manufacturer.
> 
> 2) this happens whenever our „problem“ occurs (i.e. the Audio device is 
> switched by fault)
> 001231.836690 IOUSBHostHIDDevice@fd434400,3: 
> IOUSBHostHIDDevice::interruptRetry: resetting device due to IO failures
> USB Sound assertion in 
> /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleUSBAudio/AppleUSBAudio-303.3.1/AppleUSBAudioIsocPipe.cpp
>  at line 127
> 
> 
> I can reproduce the issue very fast now, all I have to do is select „USB 
> Audio CODEC“ (this is the Audio device which the IC3000 provides) for Input 
> and Output,
> and then press the „Tune“ button a few times. Only takes a few clicks, 
> usually 4 Tune on/off cycles. Every time the problem occurs, these two lines 
> are logged (dmesg output):
>   001488.172729 IOUSBHostHIDDevice@fd434400,3: 
> IOUSBHostHIDDevice::interruptRetry: resetting device due to IO failures
>   USB Sound assertion in 
> /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleUSBAudio/AppleUSBAudio-303.3.1/AppleUSBAudioIsocPipe.cpp
>  at line 127
> 
> 
> Siegfried
> OE1HXS
> 
> 
>> Am 14.02.2017 um 21:05 schrieb DI Siegfried Hanisch 
>> <siegfried.hani...@hanisch.com <mailto:siegfried.hani...@hanisch.com>>:
>> 
>> Hi
>> 
>> my driver seems similar but not the same - do you use a 32bit version?
>> 
>> 
>> 
>> CFBundleDevelopmentRegion
>> English
>> CFBundleExecutable
>> SiLabsUSBDriver64
>> CFBundleIdentifier
>> com.silabs.driver.CP210xVCPDriver64
>> CFBundleInfoDictionaryVersion
>> 6.0
>> CFBundleName
>> SiLabsUSBDriver64
>> CFBundlePackageType
>> KEXT
>> CFBundleSignature
>> 
>> CFBundleVersion
>> 3.0.0d1
>> IOKitPersonalities
>> 
>> Mac OS X version 10.11.6 (15G1217)
>> Icom IC7300 with latest firmware.
>> 
>> BTW, contrary to what I thought (and wrote) in a previous mail, the Audio 
>> Devices are not listed alphabetically in my WSJT-X config dialog.
>> „Built-In Line Input“ is first, then „Built-In Digital Input“, and then the 
>> other devices are listed, with „USB Audio CODEC“, and then the devices I 
>> created in Audio-MIDI-Setup.
>> Same pattern for the Outputs.
>> Nonetheless, since I created this new Audio Device in the Audio-MIDI-Setup 
>> application named with „“ at the beginning (and pointing to the USB 
>> Audio CODEC device),
>> the problem did not occur any more.
>> 
>> Siggi
>> 
>> 
>>> Am 14.02.2017 um 20:29 schrieb Keith Laaks <wkla...@gmail.com 
>>> <mailto:wkla...@gmail.com>>:
>>> 
>>> Hi John,
>>> 
>>> It must be my “SiLabsUSBDriver”.
>>> 
>>> I just noticed that ‘sudo dmesg’ shows the following message wheneve

Re: [wsjt-devel] WSJT-X v1.7-rc2

[Keith Laaks]

Hi Steven,

Thanks for confirming. 

I have tested with “Enable VHF/UHF/Microwave features’ disabled - then don’t 
get the crash. 
I have always run with it enabled till now as my station is for 144MHz.

I see I lose ‘Sh; Submode; Sync; Clear Avg” when this is disabled.


73s
Keith
ZS6TW

—
Date: Wed, 02 Nov 2016 20:34:09 +
From: Steven Franke <s.j.fra...@icloud.com <mailto:s.j.fra...@icloud.com>>
Subject: Re: [wsjt-devel] WSJT-X v1.7-rc2
To: Joe Taylor <wsjt-devel@lists.sourceforge.net 
<mailto:wsjt-devel@lists.sourceforge.net>>
Message-ID: <d0fb0f85-b417-4347-b48e-a833db80f...@icloud.com 
<mailto:d0fb0f85-b417-4347-b48e-a833db80f...@icloud.com>>
Content-Type: text/plain; charset=utf-8

Ah. Based on Bill?s clue, I tried checking the ?Enable VHF/UHF/Microwave 
features? option, and now I see the crash that was described by Gary and Keith.

> On Nov 2, 2016, at 7:57 PM, Bill Somerville <g4...@classdesign.com 
> <mailto:g4...@classdesign.com>> wrote:
> 
> On 02/11/2016 18:28, Keith Laaks wrote:
>> I can confirm that I have the exact same issue on rc2.
> 
> Hi Keith,
> 
> are you using WSJT-X for VHF & up with the "Settings->General->Enable 
> VHF/UHF/Microwave features" option checked?
> 
> 73
> Bill
> G4WJS.
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X v1.7-rc2

[Keith Laaks]

Hi Gary,

I can confirm that I have the exact same issue on rc2.
Just to be sure that this was not somehow linked to any MACOS system updates, I 
installed an earlier version I still have the binary for (v1.7.0-rc1 r7152) - 
it runs perfectly on JT65, with the ‘DECODE’ flashing very quickly (not even a 
second) at the 50 second mark. 

On the rc2 (v.1.7.0-rc2 r7279-dirty) at the end of the first full sequence 
received, the ‘DECODE’ comes on and stays on for a long time, even into the 
next sequence. Then only goes off. But at the very next 50 seconds mark, it 
throws this error:

Subprocess Error:
Running: /Applications/wsjtx.app/Contents/MacOS/jt9 -s WSJT-X -w 1 -m 3 -e 
/Applications/wsjtx.app/Contents/MacOS -a "/Users/keithl/Library/Application 
Support/WSJT-X" -t /var/folders/h2/3qh2zy1n5vz72tlzx8tc01j8gn/T/WSJT-X
Process crashed

Its a little random. Sometimes it throws this error the very first time wsjtx 
attempts to decode.

Just tested latest rc2 r7280 and it also throws the same error.

I am not sure how to turn on debugging during the build process to see whats 
cutting here. 
Something must have changed in the JT9 code between r7152 and r7279 thats 
breaking now.


Regards

Keith
ZS6TW
  


Message: 5
Date: Tue, 1 Nov 2016 19:31:18 -0400
From: "C. Gary Rogers" >
Subject: Re: [wsjt-devel] WSJT-X v1.7-rc2
To: WSJT software development >
Message-ID: <298b9ded-59eb-470e-a943-8a345b396...@comcast.net 
>
Content-Type: text/plain; charset="us-ascii"

OK apparently i already had this allocation:

> Last login: Tue Nov  1 03:12:38 on ttys000
> Charless-MacBook-Pro:~ charlesrogers$ sysctl -A | grep shmmax
> kern.sysv.shmmax: 33554432
> Charless-MacBook-Pro:~ charlesrogers$ 

So it must be something else.

--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Enhancement Suggestion - Coloring the "progress bar" to reflect Odd/Even sequence.

[Keith Laaks]

Hi All,

I find that when listening for stations, I often need to go glance at the clock 
to see where we are at that moment with regards to odd/even sequencing.

The "progress bar" at the bottom right is a very convenient real-time 
visualization of the time lapsed/remaining during the current sequence.
It would be even more convenient if the color could indicate whether we are now 
in “odd/2nd (orange)” or “even/1st (blue)” sequence.

Comments?

Thanks

Keith
ZS6TW


--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Enable Deep Search throws error.

[Keith Laaks]

Hi,

Running "WSJT-X v.1.7.0-rc1 r7152-dirty”

I notice when selecting “Decode->Enable Deep Search” - at the end of the first 
sequence, when the code runs its “Decode”, I immediately get an error popup box 
containing the following: 

——
Running: /Applications/wsjtx_dirty.app/Contents/MacOS/jt9 -s WSJT-X -w 1 -m 3 
-e /Applications/wsjtx_dirty.app/Contents/MacOS -a 
"/Users/keithl/Library/Application Support/WSJT-X" -t 
/var/folders/h2/3qh2zy1n5vz72tlzx8tc01j8gn/T/WSJT-X
At line 151 of file /Users/keithl/src/wsjtx/lib/hint65.f90 (unit = 77)
Fortran runtime error: Cannot open file 'fort.77': Permission denied

Error termination. Backtrace:
#0 0x10b41eb99
#1 0x10b41f855
#2 0x10b41ffb9
#3 0x10b4e491a
#4 0x10b4eadd5
#5 0x1050f4e82
#6 0x1050ec7ae
——

I was using JT65 B at the time.

Interestingly, this error only shows at the end of the sequence when the decode 
happens automatically.
If I click on "Decode” to force a decode at some point in time - the above 
error does not show (I would have expected it to).

It could of course just be something broken with my build. 
Does the same also happen for other Mac users?

Thanks
Keith
ZS6TW






--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT-X v.1.7.0-rc1 r7152-dirty and Transmit Audio Source using FT-991

[Keith Laaks]

Hi All,

I have been building and testing on Mac OS Sierra [10.12.1 Beta (16B2338c)]
using FT-991 as radio.

In my settings I see the "Transmit Audio Source" section always remains
greyed-out;
 with the "Front/Mic" radio button ticked by default.

I would like to run using Mode=USB instead of Mode=Data/Pkt since the radio
applies a narrower filter to the audio when in "Data/Pkt" mode as opposed
to "USB" mode, which is perhaps 500Hz or more wider (I want to be able to
'see more' of the spectrum).

But when I select Mode=USB, the "Transmit Audio Source" is then the
Front/Mic and so the WSJT-X generated audio never makes it through - only
the audio that gets picked up via the Microphone.

When I select Mode=Data/Pkt, the TX audio from the PC goes through to the
FT-991 via the usb-cable (of course this usb not to be confused with the
'Upper Side Band / USB).

So is there something I am missing here. I suspect I need to get the
"Transmit Audio Source" set to "Rear/Data" somehow.

(On WSJT I was able to run using USB mode - so know it's possible)

Thanks

Keith
ZS6TW
--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] JTSDK-NIX 2.0.19

[Keith Laaks]

Hi,

I noticed this afternoon using WSJT on my Mac that when I updated the
CALL3.TXT file from the MMMonVHF site, the lockup breaks and in the console
I also start getting the "Error when searching CALL3.TXT, or no such file
present" issue. Older versions of the same file in the SVN works without
problems.

I traced this down to some invalid utf-8 values in the updated CALL3.TXT
file.

To fix this, I just changed the file open statement as follows:

From:
  f=open(appdir+'/CALL3.TXT','r')

To:
f=open(appdir+'/CALL3.TXT','r',encoding='utf-8', errors='ignore')

And then the lookups work fine.

Keith
ZS6TW
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] DMG: WSJT10.0r6470 on OSX El Capitan

[Keith Laaks]

Hi All,

I updated my WSJT build on OSX to the latest revision from the repo.
And used some old scripts I had from some years ago to build a DMG
installer image.

Due to oddities on how OSX works, my script changes some of the key
bindings to Ctrl instead of using Alt.
On OSX, Tkinter' Alt-Key just never fires off events it seems.

Looks like no need for kvasd in this build - but my script threw it into
the build anyhow.

I guess in some upcoming version of OSX, its going to break 'portaudio'
when Apple drops Carbon Manager and that will be the end of that

Has everybody moved on to the other versions?
Or would there be some need for Mac users to be using the original WSJT
version?
If so I can share a download link for the DMG - which makes getting WSJT
running for the Mac users a lot easier.

Keith
ZS6TW
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel