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 „AAAAA..“).
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 <[email protected]>:
>
> 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 +0000
>> From: Bill Somerville <[email protected]>
>> Subject: Re: [wsjt-devel] Bug Report (WSJT-X v1.7.0 r7405 on Mac OS X)
>> (Keith Laaks)
>> To: [email protected]
>> Message-ID: <[email protected]>
>> 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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Greetings
Siegfried Hanisch
mailto:[email protected]
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
