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

2017-02-19 Thread DI Siegfried Hanisch 
Hi Keith

great news!
Any chance you can share the version you built? I have not (yet) set up a build 
environment for WSJTX on my machine,
and if you already have a built version it would be great to be able to verify 
it is also working here.

73
Siegfried
OE1HXS
> Am 19.02.2017 um 22:26 schrieb 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 
>> <mailto:wsjt-devel-requ...@lists.sourceforge.net> wrote:
>> 
>> Message: 1
>> Date: Sun, 19 Feb 2017 11:20:44 +0100
>> From: Claude Frantz > <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

-- 
Greetings
Siegfried Hanisch
mailto:siegfried.hani...@hanisch.com
http://www.hanisch.com



--
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)

2017-02-19 Thread 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  <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)

2017-02-19 Thread Bill Somerville 
On 19/02/2017 09:12, Keith Laaks wrote:
> Looks like FLDIGI does not use Qt.

Hi Keith,

the lowest level audio library fldigi uses is portaudio. We have 
definitely had reports from fldigi Mac users of problems very similar to 
the one discussed here. It may be that we are talking of two different 
problems but I would be surprised.

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) (Bill Somerville)

2017-02-19 Thread Claude Frantz 
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)

2017-02-19 Thread 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 
> Subject: Re: [wsjt-devel] Bug Report (WSJT-X v1.7.0 r7405 on Mac OS X)
>   (Keith Laaks) (Bill Somerville)
> To: WSJT software development 
> 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)

2017-02-18 Thread Bill Somerville 
On 18/02/2017 20:44, DI Siegfried Hanisch wrote:
> Does anyone know if there is a way I can see the messages which are 
> generated in the source code (Q_EMIT) in some console? Or do I have to 
> build the code to add or enable debug output?
> Q_EMIT error (tr ("An error opening the audio output device has 
> occurred."));

Hi Seigfried,

those SoundOutput::error signals are processed in the WSJT-X MainWindow 
code and will cause a critical error message box to be popped up. The 
relevant code is:

mainwindow.cpp:383  connect (m_soundOutput, &SoundOutput::error, this, 
&MainWindow::showSoundOutError);

and

mainwindow.cpp:1448

void MainWindow::showSoundOutError(const QString& errorMsg)
{
   if (m_splash && m_splash->isVisible ()) m_splash->hide ();
   MessageBox::critical_message (this, tr ("Error in Sound Output"), errorMsg);
}

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) (Bill Somerville)

2017-02-18 Thread Bill Somerville 
On 18/02/2017 20:34, Keith Laaks wrote:
> 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.

Hi Keith,

your reply above was to Ulde IK2TYL's comments not mine although I did 
suggest that his proposed test was a good thing to try.

The loss of Rx audio at the same time as Tx audio is an interesting data 
point. What I assume is happening is that both the speaker and mic/line 
in audio devices are being reset or switched spontaneously. I am fairly 
certain this behaviour is not due to anything we do in WSJT-X or even 
that the Qt framework we use for audio, this dual effect is consistent 
with that since at the level that Qt and hence WSJT-X interacts with the 
audio devices they are separate and apparently unrelated. Only at the 
lower levels of the Mac OS X Core Audio services or the device driver 
are the two audio devices tied to a single physical device. The logical 
conclusion is that there is nothing we can do until the driver or 
operating system authors sort out whatever the issue is.

This needs more users to report the issue to SiLabs and Apple. I also 
suggest that fldigi users get involved as well as I gather it suffers 
the same problem.

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) (Bill Somerville)

2017-02-18 Thread DI Siegfried Hanisch 
Hi Keith
I know it is only a workaround until another solution is found, but on my 
machine the hack with creating a new Audio Device in the "Audio-MIDI-Setup“ 
application works 100% reliably now,
I run WSJTX all evening without the need to restart. Just name the new Audio 
Device (which needs to contain the real USB audio device then) so that it is 
alphabetically first (like „A..“).


Does anyone know if there is a way I can see the messages which are generated 
in the source code (Q_EMIT) in some console? Or do I have to build the code to 
add or enable debug output?
Q_EMIT error (tr ("An error opening the audio output device has 
occurred."));

Siegfried



> Am 18.02.2017 um 21:34 schrieb 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 
>> 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.
>> 
>> 
>> 
> 
> 
> --

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

2017-02-18 Thread 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 
> 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)

2017-02-16 Thread Bill Somerville 
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)

2017-02-16 Thread Ulderico Arcidiaco 
river64
>>> 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 >>> <mailto:wkla...@gmail.com>>:
>>>> 
>>>> Hi John,
>>>> 
>>>> It must be my “SiLabsUSBDriver”.
>>>> 
>>>> I just noticed that ‘sudo dmesg’ shows the following message whenever this 
>>>> issue occurs - always around the 4 or 5th time that WSJTX is switching 
>>>> from TX to RX: 
>>>> 
>>>> "005421.557360 IOUSBHostHIDDevice: IOUSBHostHIDDevice::interruptRetry: 
>>>> resetting device due to IO failures”
>>>> 
>>>> I have uninstalled the SiLabs USB driver v 4.10.14. Then installed an 
>>>> earlier one from an older dmg I found on another machine: v4.10.13.
>>>> That one does exactly the same.
>>>> 
>>>> I don’t have any other issues with any other USB devices on the MacBook - 
>>>> so can only be the driver or radio itself.
>>>> 
>>>> I will go back to SiLabs to see if they can provide advice here. Will also 
>>>> try log this with Yeasu. 
>>>> 
>>>> I would be interested to hear the exact setup that others also using the 
>>>> SiLabs driver (not sure if this is only limited to Yeasu) are using 
>>>> successfully:
>>>>  a) Exact version of MacOS (10.12.3 Beta (16D30a))
>>>>  b) Version of SiLabs driver (I have tried both 4.10.14 and 4.10.13.)
>>>>  c) Radio Firmware version: (On my FT-991, Main Firmware Version = 02-16)
>>>> 
>>>> One can find the version of SiLabs driver by done a  “more 
>>>> /Library/Extensions/SiLabsUSBDriver.kext/Contents/Info.plist” in a 
>>>> terminal:
>>>> —
>>>> 
>>>> >>> "http://www.apple.com/DTDs/PropertyList-1.0.dtd 
>>>> <http://www.apple.com/DTDs/PropertyList-1.0.dtd>">
>>>> 
>>>> 
>>>>BuildMachineOSBuild
>>>>14A283o
>>>>CFBundleDevelopmentRegion
>>>>English
>>>>CFBundleExecutable
>>>>SiLabsUSBDriver
>>>>CFBundleIdentifier
>>>>com.silabs.driver.CP210xVCPDriver
>>>>CFBundleInfoDictionaryVersion
>>>>6.0
>>>>CFBundleName
>>>>SiLabsUSBDriver
>>>>CFBundlePackageType
>>>>KEXT
>>>>CFBundleSignature
>>>>
>>>>CFBundleVersion
>>>>4.10.13.<== 
>>>> THE VERSION YOU ARE RUNNING =
>>>>DTCompiler
>>>>com.apple.compilers.llvm.clang.1_0
>>>>DTPlatformBuild
>>>>6A1052d
>>>>DTPlatformVersion
>>>>GM
>>>>DTSDKBuild
>>>>13F26
>>>>DTSDKName
>>>>macosx10.9
>>>>DTXcode
>>>>0610
>>>>DTXcodeBuild
>>>>6A1052d
>>>>IOKitPersonalities
>>>> —
>>>> 
>>>> 
>>>> 
>>>> Best Regards
>>>> 
>>>> Keith
>>>> Zs6tw
>>>> 
>>>> 
>>>>> 
>>>>> -

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

2017-02-16 Thread Keith Laaks 
;> TX to RX: 
>>> 
>>> "005421.557360 IOUSBHostHIDDevice: IOUSBHostHIDDevice::interruptRetry: 
>>> resetting device due to IO failures”
>>> 
>>> I have uninstalled the SiLabs USB driver v 4.10.14. Then installed an 
>>> earlier one from an older dmg I found on another machine: v4.10.13.
>>> That one does exactly the same.
>>> 
>>> I don’t have any other issues with any other USB devices on the MacBook - 
>>> so can only be the driver or radio itself.
>>> 
>>> I will go back to SiLabs to see if they can provide advice here. Will also 
>>> try log this with Yeasu. 
>>> 
>>> I would be interested to hear the exact setup that others also using the 
>>> SiLabs driver (not sure if this is only limited to Yeasu) are using 
>>> successfully:
>>>  a) Exact version of MacOS (10.12.3 Beta (16D30a))
>>>  b) Version of SiLabs driver (I have tried both 4.10.14 and 4.10.13.)
>>>  c) Radio Firmware version: (On my FT-991, Main Firmware Version = 02-16)
>>> 
>>> One can find the version of SiLabs driver by done a  “more 
>>> /Library/Extensions/SiLabsUSBDriver.kext/Contents/Info.plist” in a terminal:
>>> —
>>> 
>>> >> "http://www.apple.com/DTDs/PropertyList-1.0.dtd 
>>> <http://www.apple.com/DTDs/PropertyList-1.0.dtd>">
>>> 
>>> 
>>>BuildMachineOSBuild
>>>14A283o
>>>CFBundleDevelopmentRegion
>>>English
>>>CFBundleExecutable
>>>SiLabsUSBDriver
>>>CFBundleIdentifier
>>>com.silabs.driver.CP210xVCPDriver
>>>CFBundleInfoDictionaryVersion
>>>    6.0
>>>    CFBundleName
>>>        SiLabsUSBDriver
>>>CFBundlePackageType
>>>KEXT
>>>CFBundleSignature
>>>
>>>CFBundleVersion
>>>4.10.13.<== THE 
>>> VERSION YOU ARE RUNNING =
>>>DTCompiler
>>>com.apple.compilers.llvm.clang.1_0
>>>DTPlatformBuild
>>>6A1052d
>>>DTPlatformVersion
>>>GM
>>>DTSDKBuild
>>>13F26
>>>DTSDKName
>>>macosx10.9
>>>DTXcode
>>>0610
>>>DTXcodeBuild
>>>6A1052d
>>>IOKitPersonalities
>>> —
>>> 
>>> 
>>> 
>>> Best Regards
>>> 
>>> Keith
>>> Zs6tw
>>> 
>>> 
>>>> 
>>>> --
>>>> 
>>>> 
>>>> Message: 3
>>>> Date: Mon, 13 Feb 2017 20:32:34 +
>>>> From: John Nelson mailto:j...@rmnjmn.co.uk>>
>>>> Subject: Re: [wsjt-devel] Bug Report (WSJT-X v1.7.0 r7405 on Mac OS X)
>>>>(Keith Laaks)
>>>> To: WSJT software development >>> <mailto:wsjt-devel@lists.sourceforge.net>>
>>>> Message-ID: >>> <mailto:ae663efb-ac0b-46b0-a587-daa14c39a...@rmnjmn.co.uk>>
>>>> Content-Type: text/plain; charset=utf-8
>>>> 
>>>> Hi Keith,
>>>> 
>>>> I managed to get the waterfall to freeze but only by disconnecting the USB 
>>>> cable (Audio) from the SignaLink box which wasn?t turned on anyway.   
>>>> WSJT-X configuration still reported USB Audio Codec as did Sytem 
>>>> Preferences > Sound.  The USB cable was free - unterminated.
>>>> 
>>>> WIth the USB cable terminated in the SignaLink box (not switched on) but 
>>>> no audio from the rig (audio cable to the rig disconnected) the waterfall 
>>>> continues to drop.   So the waterfall does not depend on audio input.  
>>>> 
>>>> What seems to freeze the display are unexpected problems on USB such as a 
>>>> disconnection when live.
>>>> 
>>>> Can there be some problem with the USB on your Mac?
>>>> 
>>>> ? John G4KLA
>>>> 
>>> 
>>> 
>>> --
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, SlashDot.org <http://slashdot.org/>! 
>>> http://sdm.link/slashdot <http://sdm.link/slashdot>
>>> ___
>>> wsjt-devel mailing list
>>> wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel 
>>> <https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
>> 
>> -- 
>> Greetings
>> Siegfried Hanisch
>> mailto:siegfried.hani...@hanisch.com 
>> <mailto:siegfried.hani...@hanisch.com>
>> http://www.hanisch.com <http://www.hanisch.com/>
>> 
>> 
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org <http://slashdot.org/>! 
>> http://sdm.link/slashdot___ 
>> <http://sdm.link/slashdot___>
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
> -- 
> Greetings
> Siegfried Hanisch
> mailto:siegfried.hani...@hanisch.com 
> <mailto:siegfried.hani...@hanisch.com>
> http://www.hanisch.com <http://www.hanisch.com/>
> 
> 
> 

--
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)

2017-02-16 Thread DI Siegfried Hanisch 
Hi

This path does also not exist on my machine. It is a reference to the source 
code file which Apple uses to compile the USB Audio components inside OS X.
I am still running 10.11.6 on my MacPro 1,1.

To me it looks somehow like the USB connection is resetting for whatever reason 
when switching between Tx and Rx [I guess we will not able to fix this easily],
and then WSJTX or the Qt code layer inside, is picking up the wrong audio 
device after probably receiving some error from OS X.
I think it would be most promising to look into this code, and put some 
workaround in there, which catches
the error (I guess the device is closed or so), and then tries to reopen it, 
maybe with a few retries in case it is not possible immediately. Currently the 
code in this location seems to switch to a different device instead when
the problem occurs. On my machine, this „different device“ is the one which is 
alphabetically first among the Audio Devices configured on my Mac. 
(alphabetically first not in the Combo Box in the WSJTX audio configuration, 
but in OS X).

Siegfried

> Am 16.02.2017 um 09:50 schrieb John Nelson :
> 
> Hi Siegfried,
> 
>> USB Sound assertion in 
>> /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleUSBAudio/AppleUSBAudio-303.3.1/AppleUSBAudioIsocPipe.cpp
>>  at line 127
> 
> What version of OSX are you running?   You mentioned 10.11.6 on 14 Feb.   My 
> version of 10.11.6 has no references to /BuildRoot, nor com.apple.xbs in 
> /System/Library/Caches
> 
> — John G4KLA
> --
> 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

-- 
Greetings
Siegfried Hanisch
mailto:siegfried.hani...@hanisch.com
http://www.hanisch.com



--
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)

2017-02-16 Thread John Nelson 
Hi Siegfried,

> USB Sound assertion in 
> /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleUSBAudio/AppleUSBAudio-303.3.1/AppleUSBAudioIsocPipe.cpp
>  at line 127

What version of OSX are you running?   You mentioned 10.11.6 on 14 Feb.   My 
version of 10.11.6 has no references to /BuildRoot, nor com.apple.xbs in 
/System/Library/Caches

— John G4KLA
--
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)

2017-02-15 Thread DI Siegfried Hanisch 
>>KEXT
>>CFBundleSignature
>>
>>CFBundleVersion
>>4.10.13.<== THE 
>> VERSION YOU ARE RUNNING =
>>DTCompiler
>>com.apple.compilers.llvm.clang.1_0
>>    DTPlatformBuild
>>    6A1052d
>>DTPlatformVersion
>>GM
>>DTSDKBuild
>>13F26
>>DTSDKName
>>macosx10.9
>>DTXcode
>>0610
>>DTXcodeBuild
>>6A1052d
>>IOKitPersonalities
>> —
>> 
>> 
>> 
>> Best Regards
>> 
>> Keith
>> Zs6tw
>> 
>> 
>>> 
>>> --
>>> 
>>> 
>>> Message: 3
>>> Date: Mon, 13 Feb 2017 20:32:34 +
>>> From: John Nelson mailto:j...@rmnjmn.co.uk>>
>>> Subject: Re: [wsjt-devel] Bug Report (WSJT-X v1.7.0 r7405 on Mac OS X)
>>> (Keith Laaks)
>>> To: WSJT software development >> <mailto:wsjt-devel@lists.sourceforge.net>>
>>> Message-ID: >> <mailto:ae663efb-ac0b-46b0-a587-daa14c39a...@rmnjmn.co.uk>>
>>> Content-Type: text/plain; charset=utf-8
>>> 
>>> Hi Keith,
>>> 
>>> I managed to get the waterfall to freeze but only by disconnecting the USB 
>>> cable (Audio) from the SignaLink box which wasn?t turned on anyway.   
>>> WSJT-X configuration still reported USB Audio Codec as did Sytem 
>>> Preferences > Sound.  The USB cable was free - unterminated.
>>> 
>>> WIth the USB cable terminated in the SignaLink box (not switched on) but no 
>>> audio from the rig (audio cable to the rig disconnected) the waterfall 
>>> continues to drop.   So the waterfall does not depend on audio input.  
>>> 
>>> What seems to freeze the display are unexpected problems on USB such as a 
>>> disconnection when live.
>>> 
>>> Can there be some problem with the USB on your Mac?
>>> 
>>> ? John G4KLA
>>> 
>> 
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org <http://slashdot.org/>! 
>> http://sdm.link/slashdot <http://sdm.link/slashdot>
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
> -- 
> Greetings
> Siegfried Hanisch
> mailto:siegfried.hani...@hanisch.com 
> <mailto:siegfried.hani...@hanisch.com>
> http://www.hanisch.com <http://www.hanisch.com/>
> 
> 
> 
> --
> 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

-- 
Greetings
Siegfried Hanisch
mailto:siegfried.hani...@hanisch.com
http://www.hanisch.com



--
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)

2017-02-14 Thread DI Siegfried Hanisch 
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 :
> 
> Hi John,
> 
> It must be my “SiLabsUSBDriver”.
> 
> I just noticed that ‘sudo dmesg’ shows the following message whenever this 
> issue occurs - always around the 4 or 5th time that WSJTX is switching from 
> TX to RX: 
> 
> "005421.557360 IOUSBHostHIDDevice: IOUSBHostHIDDevice::interruptRetry: 
> resetting device due to IO failures”
> 
> I have uninstalled the SiLabs USB driver v 4.10.14. Then installed an earlier 
> one from an older dmg I found on another machine: v4.10.13.
> That one does exactly the same.
> 
> I don’t have any other issues with any other USB devices on the MacBook - so 
> can only be the driver or radio itself.
> 
> I will go back to SiLabs to see if they can provide advice here. Will also 
> try log this with Yeasu. 
> 
> I would be interested to hear the exact setup that others also using the 
> SiLabs driver (not sure if this is only limited to Yeasu) are using 
> successfully:
>  a) Exact version of MacOS (10.12.3 Beta (16D30a))
>  b) Version of SiLabs driver (I have tried both 4.10.14 and 4.10.13.)
>  c) Radio Firmware version: (On my FT-991, Main Firmware Version = 02-16)
> 
> One can find the version of SiLabs driver by done a  “more 
> /Library/Extensions/SiLabsUSBDriver.kext/Contents/Info.plist” in a terminal:
> —
> 
>  "http://www.apple.com/DTDs/PropertyList-1.0.dtd";>
> 
> 
>BuildMachineOSBuild
>14A283o
>CFBundleDevelopmentRegion
>English
>CFBundleExecutable
>SiLabsUSBDriver
>CFBundleIdentifier
>com.silabs.driver.CP210xVCPDriver
>CFBundleInfoDictionaryVersion
>6.0
>CFBundleName
>SiLabsUSBDriver
>CFBundlePackageType
>KEXT
>CFBundleSignature
>
>CFBundleVersion
>4.10.13.<== THE 
> VERSION YOU ARE RUNNING =
>DTCompiler
>com.apple.compilers.llvm.clang.1_0
>DTPlatformBuild
>6A1052d
>DTPlatformVersion
>GM
>DTSDKBuild
>13F26
>DTSDKName
>macosx10.9
>DTXcode
>0610
>DTXcodeBuild
>    6A1052d
>    IOKitPersonalities
> —
> 
> 
> 
> Best Regards
> 
> Keith
> Zs6tw
> 
> 
>> 
>> --
>> 
>> 
>> Message: 3
>> Date: Mon, 13 Feb 2017 20:32:34 +
>> From: John Nelson 
>> Subject: Re: [wsjt-devel] Bug Report (WSJT-X v1.7.0 r7405 on Mac OS X)
>>  (Keith Laaks)
>> To: WSJT software development 
>> Message-ID: 
>> Content-Type: text/plain; charset=utf-8
>> 
>> Hi Keith,
>> 
>> I managed to get the waterfall to freeze but only by disconnecting the USB 
>> cable (Audio) from the SignaLink box which wasn?t turned on anyway.   WSJT-X 
>> configuration still reported USB Audio Codec as did Sytem Preferences > 
>> Sound.  The USB cable was free - unterminated.
>> 
>> WIth the USB cable terminated in the SignaLink box (not switched on) but no 
>> audio from the rig (audio cable to the rig disconnected) the waterfall 
>> continues to drop.   So the waterfall does not depend on audio input.  
>> 
>> What seems to freeze the display are unexpected problems on USB such as a 
>> disconnection when live.
>> 
>> Can there be some problem with the USB on your Mac?
>> 
>> ? John G4KLA
>> 
> 
> 
> --

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

2017-02-14 Thread Keith Laaks 
Hi John,

It must be my “SiLabsUSBDriver”.

I just noticed that ‘sudo dmesg’ shows the following message whenever this 
issue occurs - always around the 4 or 5th time that WSJTX is switching from TX 
to RX: 

"005421.557360 IOUSBHostHIDDevice: IOUSBHostHIDDevice::interruptRetry: 
resetting device due to IO failures”

I have uninstalled the SiLabs USB driver v 4.10.14. Then installed an earlier 
one from an older dmg I found on another machine: v4.10.13.
That one does exactly the same.

I don’t have any other issues with any other USB devices on the MacBook - so 
can only be the driver or radio itself.

I will go back to SiLabs to see if they can provide advice here. Will also try 
log this with Yeasu. 

I would be interested to hear the exact setup that others also using the SiLabs 
driver (not sure if this is only limited to Yeasu) are using successfully:
  a) Exact version of MacOS (10.12.3 Beta (16D30a))
  b) Version of SiLabs driver (I have tried both 4.10.14 and 4.10.13.)
  c) Radio Firmware version: (On my FT-991, Main Firmware Version = 02-16)

One can find the version of SiLabs driver by done a  “more 
/Library/Extensions/SiLabsUSBDriver.kext/Contents/Info.plist” in a terminal:
—

http://www.apple.com/DTDs/PropertyList-1.0.dtd";>


BuildMachineOSBuild
14A283o
CFBundleDevelopmentRegion
English
CFBundleExecutable
SiLabsUSBDriver
CFBundleIdentifier
com.silabs.driver.CP210xVCPDriver
CFBundleInfoDictionaryVersion
6.0
CFBundleName
SiLabsUSBDriver
CFBundlePackageType
KEXT
CFBundleSignature

CFBundleVersion
4.10.13.<== THE 
VERSION YOU ARE RUNNING =
DTCompiler
com.apple.compilers.llvm.clang.1_0
DTPlatformBuild
6A1052d
DTPlatformVersion
GM
DTSDKBuild
13F26
DTSDKName
macosx10.9
DTXcode
0610
DTXcodeBuild
6A1052d
IOKitPersonalities
—



Best Regards

Keith
Zs6tw


> 
> --
> 
> 
> Message: 3
> Date: Mon, 13 Feb 2017 20:32:34 +
> From: John Nelson 
> Subject: Re: [wsjt-devel] Bug Report (WSJT-X v1.7.0 r7405 on Mac OS X)
>   (Keith Laaks)
> To: WSJT software development 
> Message-ID: 
> Content-Type: text/plain; charset=utf-8
> 
> Hi Keith,
> 
> I managed to get the waterfall to freeze but only by disconnecting the USB 
> cable (Audio) from the SignaLink box which wasn?t turned on anyway.   WSJT-X 
> configuration still reported USB Audio Codec as did Sytem Preferences > 
> Sound.  The USB cable was free - unterminated.
> 
> WIth the USB cable terminated in the SignaLink box (not switched on) but no 
> audio from the rig (audio cable to the rig disconnected) the waterfall 
> continues to drop.   So the waterfall does not depend on audio input.  
> 
> What seems to freeze the display are unexpected problems on USB such as a 
> disconnection when live.
> 
> Can there be some problem with the USB on your Mac?
> 
> ? John G4KLA
> 


--
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)

2017-02-13 Thread John Nelson 
Hi Keith,

I managed to get the waterfall to freeze but only by disconnecting the USB 
cable (Audio) from the SignaLink box which wasn’t turned on anyway.   WSJT-X 
configuration still reported USB Audio Codec as did Sytem Preferences > Sound.  
The USB cable was free - unterminated.

WIth the USB cable terminated in the SignaLink box (not switched on) but no 
audio from the rig (audio cable to the rig disconnected) the waterfall 
continues to drop.   So the waterfall does not depend on audio input.  

What seems to freeze the display are unexpected problems on USB such as a 
disconnection when live.

Can there be some problem with the USB on your Mac?

— John G4KLA
--
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)

2017-02-13 Thread Keith Laaks 
Hi John, Siegfried.

I have tried Siegfried’s Audio MIDI technique to create a sound device such 
that in the device listing on WSJT, the device appears ‘at the top’. 
However I am not able to accomplish that. When I do "Audio MIDI Setup” -> 
"Audio Devices” -> “Create Aggregate Device”, called ‘AA’, it still appears 
just below “Internal Speakers” and just above “USB Audio CODEC”, which then 
delivers the same behavior in WSJTX.

John, the exact MacOS version I am running here today is: 10.12.3 Beta 
(16D30a). But WSJTX failed similarly from 10.12.1 up to this version. I see 
10.12.4 Beta 2 is out, but have not tried that yet.

This is what I see in ‘dmesg’ when I plug in my FT-991 via USB

——
com_silabs_driver_CP210xVCPDriver: init
com_silabs_driver_CP210xVCPDriver()::attach
com_silabs_driver_CP210xVCPDriver()::probe
com_silabs_driver_CP210xVCPDriver()::detach
com_silabs_driver_CP210xVCPDriver()::attach
com_silabs_driver_CP210xVCPDriver()::start - Registered for Power 
Management
com_silabs_driver_CP210xVCPDriver()::start!
com_silabs_driver_CP210xVCPDriver()::start - Found device at interface 0
com_silabs_driver_CP210xVCPDriver()::SelectInterfaces - BulkInput Pipe is 
 on EP1
com_silabs_driver_CP210xVCPDriver()::SelectInterfaces - BulkOutput Pipe is 
 on EP1
com_silabs_driver_CP210xVCPDriver()::message
com_silabs_driver_CP210xVCPDriver()::setPowerState - Waking up
com_silabs_driver_CP210xVCPDriver()::GetCP210xInfo - Part Number Found: 
0x05
com_silabs_driver_CP210xVCPDriver()::GetCP210xInfo - 
UsbConfigurationDescriptor - 
com_silabs_driver_CP210xVCPDriver()::GetCP210xInfo .bLength = 9 
com_silabs_driver_CP210xVCPDriver()::GetCP210xInfo .bDescriptorType = 
0x02 
com_silabs_driver_CP210xVCPDriver()::GetCP210xInfo .wTotalLength = 55 
com_silabs_driver_CP210xVCPDriver()::GetCP210xInfo .bNumInterfaces = 2 
com_silabs_driver_CP210xVCPDriver()::GetCP210xInfo 
.bConfigurationValue = 1 
com_silabs_driver_CP210xVCPDriver()::GetCP210xInfo .iConfiguration = 0 
com_silabs_driver_CP210xVCPDriver()::GetCP210xInfo .bmAttributes = 
0x80 
com_silabs_driver_CP210xVCPDriver()::GetCP210xInfo .MaxPower = 50 
com_silabs_driver_CP210xVCPDriver()::start - Sucessfully loaded the driver
com_silabs_driver_CP210xVCPDriver: init
com_silabs_driver_CP210xVCPDriver()::attach
com_silabs_driver_CP210xVCPDriver()::probe
com_silabs_driver_CP210xVCPDriver()::detach
com_silabs_driver_CP210xVCPDriver()::attach
com_silabs_driver_CP210xVCPDriver()::start - Registered for Power 
Management
com_silabs_driver_CP210xVCPDriver()::start!
com_silabs_driver_CP210xVCPDriver()::start - Found device at interface 1
com_silabs_driver_CP210xVCPDriver()::SelectInterfaces - BulkInput Pipe is 
 on EP2
com_silabs_driver_CP210xVCPDriver()::SelectInterfaces - BulkOutput Pipe is 
 on EP2
com_silabs_driver_CP210xVCPDriver()::setPowerState - Waking up
com_silabs_driver_CP210xVCPDriver()::GetCP210xInfo - Part Number Found: 
0x05
com_silabs_driver_CP210xVCPDriver()::GetCP210xInfo - 
UsbConfigurationDescriptor - 
com_silabs_driver_CP210xVCPDriver()::GetCP210xInfo .bLength = 9 
com_silabs_driver_CP210xVCPDriver()::GetCP210xInfo .bDescriptorType = 
0x02 
com_silabs_driver_CP210xVCPDriver()::GetCP210xInfo .wTotalLength = 55 
com_silabs_driver_CP210xVCPDriver()::GetCP210xInfo .bNumInterfaces = 2 
com_silabs_driver_CP210xVCPDriver()::GetCP210xInfo 
.bConfigurationValue = 1 
com_silabs_driver_CP210xVCPDriver()::GetCP210xInfo .iConfiguration = 0 
com_silabs_driver_CP210xVCPDriver()::GetCP210xInfo .bmAttributes = 
0x80 
com_silabs_driver_CP210xVCPDriver()::GetCP210xInfo .MaxPower = 50 
com_silabs_driver_CP210xVCPDriver()::start - Sucessfully loaded the driver
Report bytes: input:1 output:0 feature:0Collections : 2Buttons : input:3 
output:0 feature:0Values  : input:0 output:0 feature:0Element value 
capacity 96Report count: 1Report ID: 0 input:8 output:0 feature:0HID: Legacy 
shim 2
SmartBattery: finished polling type 4
—
Running driver: Version 4.x.14 from : 
http://www.silabs.com/Support%20Documents/Software/Mac_OSX_VCP_Driver.zip 


—
To reproduce, I have “Enable TX” enabled, wait for the sequence to start, after 
a few seconds I click “Halt TX”. When back in receive, I immediately “Enable 
TX” and repeat this cycle. 
I can repeat this about 4 or 5 times before it breaks.

Interestingly, sometimes when I have just hit “Halt TX”, I can see that the 
receive has broken - with the waterfall display not updating at all (I guess 
Audio Input not receiving samples).
Then when I try “Enable TX”, the audio always switches to the “Internal 
Speakers”. I need to close and reopen wsjtx to recover.

But mostly after Halt TX, WSJTX is still receiving OK, but then breaks as per 
the above as soon as I “Enable TX”. At that point when I “Halt TX” (to turn off 
the transmitter), the receive is always also broken.

—
Not sure if this is relevan