Re: [wsjt-devel] WSJT-X Tx = 1000 Hz, can't change

On 29/04/2016 23:05, Jim Pennino wrote: > I generally agree, but think it should be a pull down for general operating > mode, as > in HF, EME, meteor scatter with only the appropriate modes selectable. > > I realize this would be a lot of changes, but it would simplify operating if, > for

Re: [wsjt-devel] WSJT-X Tx = 1000 Hz, can't change

Did you update hamlib too? r6558 and up require a re-build of hamlib too. RRR Mike W9MDB On Fri, Apr 29, 2016 at 3:54 PM, Jim Pennino wrote: > I just built 1.7.0 devel, r6659 and now Tx is always 1000 Hz, the Lock > Tx=Rx button is greyed > out, and the Tx <-- Rx button

Re: [wsjt-devel] WSJT-X Tx = 1000 Hz, can't change

On 29/04/2016 22:04, Molnar, George J wrote: > I wonder if this option should move out of the setup screen and to the > main operating one (say, next to the frequency display)? > > It would make it easier for those of us who operate both HF and VHF > regularly. > > Perhaps a "Configuration" is the

Re: [wsjt-devel] WSJT-X Tx = 1000 Hz, can't change

On 29/04/2016 21:54, Jim Pennino wrote: > I just built 1.7.0 devel, r6659 and now Tx is always 1000 Hz, the Lock Tx=Rx > button is greyed > out, and the Tx <-- Rx button does nothing. > > Mode doesn't make any difference. Hi Jim, You have "Settings->General->Behavior->Enable VHF/UHF/Microwave

[wsjt-devel] WSJT-X Tx = 1000 Hz, can't change

I just built 1.7.0 devel, r6659 and now Tx is always 1000 Hz, the Lock Tx=Rx button is greyed out, and the Tx <-- Rx button does nothing. Mode doesn't make any difference. Windows 10, TS-2000. -- Find and fix

Re: [wsjt-devel] Release candidate?

Hi Joe Just bringing back to the discussion for consideration the issues I found with using a Type 1 callsign when operating as HA/G3WDG on 3cm JT4: https://drive.google.com/file/d/0B116IwQIUFNTWXhsdUVfVW16S00/view?usp=sharing Charlie > Hi Joe > > A few more items if you are able to fit them

Re: [wsjt-devel] r6658 breaks JTSDK builds on windows

Bill, I did just recompile r6659 on the RasPi about 10 mins ago (11:04Z) and now it works. 73 Ross Sent from my iPhone 6 > On 29 Apr 2016, at 11:06, Bill Somerville wrote: > >> On 29/04/2016 06:32, T61AA Ross wrote: >> Have just updated hamlib and recompiled WSJTX

Re: [wsjt-devel] Release candidate?

Hi Joe A few more items if you are able to fit them in: 1. Resolve double decode issue on JT4 when it decodes both on FT and DS - should only need some logic that prevents a DS decode if it decodes on FT. 2. Addition of single tone facilities on JT65 in the same way as for JT4 - this is not

Re: [wsjt-devel] r6658 breaks JTSDK builds on windows

On 29/04/2016 06:32, T61AA Ross wrote: Have just updated hamlib and recompiled WSJTX r6659 on the RaspberryPi and it still doesn't compile. Hi Ross, elsewhere you reported that the Windows build issues you had are resolved, is that the case with this issue and if not, what errors are you

Re: [wsjt-devel] Release candidate?

On 29/04/2016 08:55, Mark Turner (EI3KD) wrote: > There's certainly no reluctance to try new modes in Europe; as soon as a > new one appears, there's always a flurry of experimenters trying it out. > There are plenty of people who've used ISCAT and JTMSK extensively but > have migrated back to

Re: [wsjt-devel] r6658 breaks JTSDK builds on windows

On 29/04/2016 04:21, Ross T61AA wrote: > 6659 does not compile on either of my Windows machines either, indeed, > earlier visions did. > > It comes up with a cmake error > > ming32-make.exe[1]: ***[Cmakefiles/wsjt_qt.rir/all] Error 2 > makefile:136: recipe for target “all” failed >

Re: [wsjt-devel] Release candidate?

Hi Joe, There's certainly no reluctance to try new modes in Europe; as soon as a new one appears, there's always a flurry of experimenters trying it out. There are plenty of people who've used ISCAT and JTMSK extensively but have migrated back to JT6M, and they seem to be of the opinion (when