Re: [wsjt-devel] Updating the WSJT-X User Guide; OS X sample rate

Title: Re: [wsjt-devel] Updating the WSJT-X User Guide; OS X sample rate Hello Joe, yes, unfortunately ... iMac OSX 10.13.3 connected via usb to an IC-7300 port speed is 4800 Baud and the sampling had to be set to 44100, if it is set to 48000 the OSX will switch after two or three TX

Re: [wsjt-devel] Updating the WSJT-X User Guide; OS X sample rate

Joe, I have not experienced this issue using virtual audio cables (Flex 6000-series DAX support) running at 48k. However, using an external USB sound card, the problem does intermittently rear its head. Am not sure if the 44.1k “fix” is anecdotal or not, or if it covers all versions of MacOS.

Re: [wsjt-devel] Working same station on more than one band

FWIT, my home-brew software (Mac) reads the ALL.TXT file every time it updates. It also keeps my log in a separate list and a matrix of grids worked on various bands. If the reported station shows a grid, that grid is checked against the matrix for grids already worked on the current band.

Re: [wsjt-devel] Updating the WSJT-X User Guide; OS X sample rate

On 08/02/2018 18:07, Joe Taylor wrote: "Use the Mac’s Audio MIDI Setup utility to configure your sound card for 48000 Hz, two-channel, 16-bit format." But several Mac users have reported losing audio unless they set the sample rate to 44100 Hz.  Is this always the case with OS X? Should this

Re: [wsjt-devel] Working same station on more than one band

Is JTAlert available for Macintosh? > On Feb 8, 2018, at 7:31 AM, Black Michael via wsjt-devel > wrote: > > JTAlert has that capability as chosen by the user. You can choose band/mode > or all. > I imagine some DX want to work somebody they haven't before

Re: [wsjt-devel] Working same station on more than one band

A forme of it called JT-bridge is the version on mac > On Feb 8, 2018, at 10:50, Ed Stokes wrote: > > Is JTAlert available for Macintosh? > >> On Feb 8, 2018, at 7:31 AM, Black Michael via wsjt-devel >> wrote: >> >> JTAlert has that

[wsjt-devel] Updating the WSJT-X User Guide; OS X sample rate

Hi all, In preparation for an upcoming release candidate of WSJT-X v1.9.0, I am updating the WSJT-X User Guide. If you are aware of anything that needs work in the User Guide, please post a message here or otherwise let me know. Here's a specific question for Mac users. In Section 3.3 we

Re: [wsjt-devel] Working same station on more than one band

As I said in my original post, I have home-brew software that performs this, and other useful, tricks. The question was whether this capability might be built into the WSJT-X software. Thanks, Ed W1KOK > On Feb 8, 2018, at 7:54 AM, Lorin Tremblay wrote: > > A forme of it

[wsjt-devel] 73 not being detected for auto-logging, CW ID

With the latest GA version of WSJT-X (1.8.0), running Windows 10, I am running into the problem where the auto-logging and CW ID features are highly unreliable, at least using standard messages. As far as I can tell, the only time that the 73 is detected is 1) It must be at the end of the TX 5

Re: [wsjt-devel] 73 not being detected for auto-logging, CW ID

Forgot to add: I have two profiles on this installation, both identical save for the callsigns. I seem to recall not having issues with this release until recently when the second op finally had time to get on, and we switched to the second profile then back to mine after she was done. We used

Re: [wsjt-devel] Working same station on more than one band

AFAIK, it's only CQ's that are checked. If someone calls you on a band you have already worked on it will look the same if it was unique. I've thought about this question as well since 1.6.x, calling it "per band dupe/CQ check" or something like that in my todo list. At a first glance the problem

[wsjt-devel] Working same station on more than one band

Is it possible to have the software recognize that although you have already worked a given station you have NOT worked on the current band? I have home-brew software that tells me whether the station is new on the current band, but I suspect that sometimes the DX station will not respond