Hello. I use two different radios and two callsigns. For SW I use a IC-7700
radio and call SM4RGD. But on VHF I use a Kenwood TS-2000 and call SM4R. It
is a hard way to allways change in the WSJT-X meny all this every time I
change VHF - SW. It is possible to have two different configuration files?
On 24/11/2018 12:36, Charlie Carlsson wrote:
Hello. I use two different radios and two callsigns. For SW I use a
IC-7700 radio and call SM4RGD. But on VHF I use a Kenwood TS-2000 and
call SM4R. It is a hard way to allways change in the WSJT-X meny all
this every time I change VHF - SW. It is po
Hello Bill TNX for ur reply. I use different logs and only one radio at
time. And my RigExpert TI-5 interface shift with relay to used radio.
I do this with my MixW software, and It work perfect. I use two different
config files for mix. One for WHF and one for SW and different logbooks
de SM4RGD
I agree, we need to start telling people. May I make a suggestion as to the
WSJT-X web page itself? I just went there to check before I spoke. There is
no "BIG RED NOTICE" there to warn people that the new version is not going
to decode FT8 from the older version. Wouldn't it be a good idea to but
I see a lot of problem in a drastic change
May I suggest to change the name of the new FT8 so something like FT8-B
or FT77
and allow a double mode (like it was JT9+JT65) to FT77+FT8.
73
Pino ZP4KFX
___
wsjt-devel mailing list
wsjt-devel@lists.s
Also remove v1.9.1 from the downloads as well. Will create a "black
marked" for the file, but at least the casual downloader will get the
current file.
On Sat, Nov 24, 2018 at 7:12 AM Mike wrote:
> I agree, we need to start telling people. May I make a suggestion as to
> the WSJT-X web page its
On 24/11/2018 13:09, Charlie Carlsson wrote:
Hello Bill TNX for ur reply. I use different logs and only one radio
at time. And my RigExpert TI-5 interface shift with relay to used radio.
I do this with my MixW software, and It work perfect. I use two
different config files for mix. One for WHF a
TNX Bill I go to try this. I dont nead simultaneous running of the radios.
Only one at every time. So I think two ICON:s and the first solution. I do
like this whith my MixW two ICON:s and starting different configfiles, but
running same soft.
If I understand U correctly I now nead two installation
Also there have been no notices placed on QRZ, EHAM or other websites about
the latest changes that I have seen.73 Morris wa4mit
On Saturday, November 24, 2018, 7:19:09 AM CST, WB5JJJ
wrote:
Also remove v1.9.1 from the downloads as well. Will create a "black marked"
for the file, but
Hi,
Found out that in the Preference files, the following file marked
lotw-user-activity(1).csv.
I changed the name to lotw-user-activity.csv. ((roving the (1) )) and 2.0 RC4
now initiates properly…
No idea if my problem is sitting between the chair and the keyboard but it now
starts correctly
STREAM of solar wind is approaching Earth and experts fear it could hit us as
early as November 26
FYI
BCNU DE N2LO~>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Solar winds happen all the time. Where did you see a warning about this?
NOAA doesn't show any alerts
https://www.swpc.noaa.gov/products/notifications-timeline
de Mike W9MDB
On Saturday, November 24, 2018, 10:42:32 AM CST, n...@comcast.net
wrote:
STREAM of solar wind is approaching
https://www-express-co-uk.cdn.ampproject.org/v/s/www.express.co.uk/news/science/1049501/space-weather-forecast-solar-storm-met-office-solar-flare/amp?amp_js_v=a2&_gsa=1&usqp=mq331AQECAFYAQ%3D%3D#referrer=https%3A%2F%2Fwww.google.com&_tf=From%20%251%24s&share=https%3A%2F%2Fwww.express.co.uk%2Fnews%2
Another horrible article by a "science writer". No references and the article
itself says "not expected to be overly powerful"...apparently not even power
enough for NOAA to pay any attention to it.
I'm reminded of Chicken Little
de Mike W9MDB
On Saturday, November 24, 2018, 11:00:
How do I get Verizon 2.0 until all the bugs are out of revision 4.?
I put 1.9 back on but want 2.0!
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
How do I get Verizon 2.0 until all the bugs are out of revision 4.?
I put 1.9 back on but want 2.0!
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
On 24/11/2018 20:16, Microsoft Outlook wrote:
How do I get Verizon 2.0 until all the bugs are out of revision 4.?
I put 1.9 back on but want 2.0!
OM,
you will have to use your time machine. You did purchase one on Black
Friday?
WSJT-X v2.0.0 is scheduled for release on December 10th 2018.
Good afternoon, even if it's repetitive, I'll say again that after several
days, I look for stations by the different bands, I only decode very few
... understandable that there are not many that come out in 77 bits, until
here, it has its logic .. .
However, before, as a rule, to work European sta
I notice only the USA CQ calls show the correct colours.
>> Other non-USA, although new call, show white.
>> If not an issue in RC4 I apologize for bringing this up.
>> None of my logged CQs are shown as logged. Jtalert 2.12.7 indicates B4.
>>
>> Win 10 1803 WSIT-X RC3 IC-7300. 40M
>> Regards and
LOL..👾
Sent from BlueMail
On Nov 24, 2018, 12:03, at 12:03, n...@comcast.net wrote:
>https://www-express-co-uk.cdn.ampproject.org/v/s/www.express.co.uk/news/science/1049501/space-weather-forecast-solar-storm-met-office-solar-flare/amp?amp_js_v=a2&_gsa=1&usqp=mq331AQECAFYAQ%3D%3D#referrer=https
Jesus,
I am making similar observations – well its hard to observe at the moment as I
am seeing little here in VK; issues are beyond propagation as v1 signals boom
in (especially for some reason from EA).
One must always delete the wsjtx.ini when one heads back to a different
version; the best
On 24/11/2018 23:56, Stephen Ireland wrote:
Jesus,
I am making similar observations – well its hard to observe at the
moment as I am seeing little here in VK; issues are beyond propagation
as v1 signals boom in (especially for some reason from EA).
One must always delete the wsjtx.ini when
On 11/24/2018 4:14 PM, Bill Somerville wrote:
The only way to check the sensitivity of the 75-bit and 77-bit decoders on air
is to do a controlled test.
Exactly. A *controlled* test, that is reproducible. Let me introduce an
invaluable
tool for this:
http://www.moetronix.com/ae4jy/pathsim.
On 25/11/2018 00:44, Dana Myers wrote:
On 11/24/2018 4:14 PM, Bill Somerville wrote:
The only way to check the sensitivity of the 75-bit and 77-bit
decoders on air is to do a controlled test.
Exactly. A *controlled* test, that is reproducible. Let me introduce
an invaluable
tool for this
On 11/24/2018 5:04 PM, Bill Somerville wrote:
You can resample the 12kHz WSJT-X .WAV files down to 8kHz (there are several tools that can do that) degrade them then resample
back to 12kHz as a work around.
Audacity has long been my tool of choice for that. Not really sure I'd say
"degrade",
si
On 25/11/2018 01:51, Dana Myers wrote:
On 11/24/2018 5:04 PM, Bill Somerville wrote:
You can resample the 12kHz WSJT-X .WAV files down to 8kHz (there are
several tools that can do that) degrade them then resample back to
12kHz as a work around.
Audacity has long been my tool of choice for tha
Will rc5 restore the "nextcall" contesting feature?
Ed W0YK
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
On 25/11/2018 02:12, Ed Muns wrote:
Will rc5 restore the "nextcall" contesting feature?
Ed W0YK
Hi Ed,
no it will not, sorry about that. The first attempt at implementation
proved to be quite buggy and we feel that it is too near GA date to
implement the scale of changes required to make it
Disappointed, but understand, Bill. Thanks for the quick reply (and, all
the great effort on these releases!).
Ed W0YK
-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: 24 November, 2018 18:22
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Ver
This raises the interesting question: Do you expect to create a 2.0.1 version
after the dust settles and small number of bugs appear that need swatting?
This would be bug fixes only, not new features. Just wondering about your
point of view on this.
Dave / NX6D
On 25/11/2018 02:50, David Fisher wrote:
This raises the interesting question: Do you expect to create a 2.0.1
version after the dust settles and small number of bugs appear that
need swatting? This would be bug fixes only, not new features. Just
wondering about your point of view on this.
Hi,
I am using the V2.0 wsprd in a stand-alone 8 band simultaneous WSPR
decoding appliance built from a KiwiSDR and a Raspberry Pi.
However when I process my 2 minute wav files with 'wsprd -d -C 5000 -o 4'
I get different SNRs than when the same file is processed by WSJT-x.
So I infer that WSJT-x
On 11/24/2018 5:57 PM, Bill Somerville wrote:
On 25/11/2018 01:51, Dana Myers wrote:
Audacity has long been my tool of choice for that. Not really sure I'd say
"degrade",
since 8ks/s is perfectly adequate for the usual <= 3KHz FT8 audio; downsample
is true, but that's not degradation.
73,
Dana
> On Nov 24, 2018, at 9:10 PM, Rob Robinett wrote:
>
> Hi,
>
> I am using the V2.0 wsprd in a stand-alone 8 band simultaneous WSPR decoding
> appliance built from a KiwiSDR and a Raspberry Pi.
> However when I process my 2 minute wav files with 'wsprd -d -C 5000 -o 4' I
> get different SNRs
Hi Steve,
Thanks for correcting me. I inserted the “-C 5000 -o 4” and
overlooked that I left the '-d'. I'l try to be more attentive next time.
Rob
On Sat, Nov 24, 2018 at 7:13 PM Steven Franke via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
>
> On Nov 24, 2018, at 9:10 PM, Rob Robi
35 matches
Mail list logo
