Подскажите пожалуйста,что означает звездочка справа от строчки в JTDX?
Ссылки jtdx_2.2.159:
Подскажите пожалуйста,что означает звездочка справа от строчки в JTDX?
Ссылки jtdx_2.2.159:
Последний раз редактировалось RW6AVK; 06.03.2022 в 16:59. Причина: jtdx_2.2.159
16-bit audio builds:There is 160-rc4, changelog:
- reworked autoAGC math, push snr and noise values for every interval, getting autoAGC values prior start of decoding,
changes in noise calculation math, use autoAGC at TCI start
- support autoAGC through Hamlib, added 'Try Auto AGC' option control in settings of Radio tab: it is working
with TCI and some radios via Hamlib
- save/restore AGC value by band
- restore ReplyTx state when QSO broken at ReplyTx state, do not change Rx when entering into ReplyTx
- fixed bug for setting tx period from udp message, thanks to Andy ZL1VAH
- spot CQ messages without grid for nonstandard callsigns
- set TX frequency correctly when VFO changed from rig
- fix band definition frequencies, thanks to Yukio JG1APX
- attempt to fix unneeded ClearDx when 'reply to other' detected, thanks to Fred K1IO
- do not change RX audio frequency when entering into ReplyTx
- unified band detection, improve performance of Notification checks
- added polling transceiver change from WSJT-X
- QO-100 preliminary support
- fix to exact frequencies for QSO loggig
- increase shared memory size for Mac builds
- display time offset on Sync button
- filter out false AP mask decodes with wrong report
- new tooltips to Enable Tx, Sync, AGCc UI buttons
- added some 'prefix to grid' mapping patches
- added debug extension to revision name
- display logos into 'About' window
- fixed TCI transmission for long intervals
- attempt to handle band memory with TCI
- added TCI audio buffering time control
- attempt to reduce Configuration UI window size
- implemented US State notification, add State to logbook at QSO logging
- implemented GRID square and US State databases, compact databases
- user can open pskreporter map from UI with users's callsign and current band/mode
- disable TX when message from called station was not decoded at 4 consecutive RX intervals
- changed functionality from 'Halt TX if operator I called answered to other operator' to
'Halt/Resume TX if operator I called answered to other operator', calling will be resumed at end of QSO
- patch to 4-char CQ direction
- move CRC computation to Fortran code in FT8 decoders, use Fortan code for crc computation in TX message encoding
- split TX/RX FT8 message and wave generations
- fixed Autoselect for old JT modes
- added distro name and version to package name for deb based distros
- DXCC name changed from 'United States' to 'United States of America'
- use common parameter to limit maximum number of decoded in an interval messages, set value to 160
- added download database file updates from Internet, grid_data.bin state_data.bin changed to compressed format
- ALLCALL7.TXT update as of 20230825
- translation updates
- JTDX 2.2.160-rc4 builds made with modified Hamlib, based on Hamlib commit https://github.com/Hamlib/Hamlib/com...ee2370a45959a0 as of August 29th, 2023
MS Windows, 64bit
https://drive.google.com/file/d/1AG3...ew?usp=sharing
File name: jtdx-2.2.160-rc4-win64.exe
SHA-256: 78A17C8533E12E5AD082B33118C149D95C4FAD82908BEF122A 74725770027CF6
MS Windows, 32bit
https://drive.google.com/file/d/1ZOS...ew?usp=sharing
File name: jtdx-2.2.160-rc4-win32.exe
SHA-256: F657450B484958C0600A2B96A5FA89B4BCA24AFA40601D71A6 124CFA68E023B4
32-bit audio builds:
MS Windows, 64bit
https://drive.google.com/file/d/1vkj...ew?usp=sharing
File name: jtdx-2.2.160-32A-rc4-win64.exe
SHA-256: 682EFB525FB700D916A7CB54943A25AD91B32641B438EFF466 49390299D93244
MS Windows, 32bit
https://drive.google.com/file/d/1yzA...ew?usp=sharing
File name: jtdx-2.2.160-32A-rc4-win32.exe
SHA-256: BC91B919F8DCE5DEA9EC0AA7D8A22790F56D02397B3C1EA5AB 5A9B4AFD71AD86
ADD #919:
Сообщение от ES1JA
73. Roman.
вышел тестовый релиз 160-rc7 c SUPERFOX....
MS Windows builds:
File: jtdx-2.2.160-rc7-win64.exe
SHA256 checksum A5F24DE1084DCF44501FE5DAD576AC891AE91AC9A86A807389 EE663093147F48
https://drive.google.com/file/d/12Ck...ew?usp=sharing
File: jtdx-2.2.160-rc7-win32.exe
SHA256 checksum C77669AF7C4C848720012F2F9970A259EFC4F4DB3893CB411A A84F39A262F7A3
https://drive.google.com/file/d/1ifx...ew?usp=sharing
File: jtdx-2.2.160-32A-rc7-win64.exe
SHA256 checksum CEA6DE5AB6E0B5C24768278821C32C093727D2CB40FCF86F05 A1D71BE189D841
https://drive.google.com/file/d/1SyF...ew?usp=sharing
File: jtdx-2.2.160-32A-rc7-win32.exe
SHA256 checksum 1EB23210B5E58CD095E4CE58D5876E61B68EB9C7F0D32EA1BA 132595F0B5D1EF
https://drive.google.com/file/d/1mmD...ew?usp=sharing
MS Windows debug builds:
File: jtdx-2.2.160-rc7-d2-win64.exe
SHA256 checksum A7C906FC4E59099BC145AAFD55706A4BE6B32DD993A7A38E3E 2279930B6D0EE3
https://drive.google.com/file/d/1ODS...ew?usp=sharing
File: jtdx-2.2.160-32A-rc7-d2-win64.exe
SHA256 checksum 444B3261D7F5FAB1FD2DC00DA0CBDA84BF16936449CBBD291C D2FDC180A14338
https://drive.google.com/file/d/1O1-...ew?usp=sharing
de Mike
Hello.
I need 32A-amd64 debian version (linux) of that release (160-rc7).
Its filename is something like jtdx_2.2.###-32A_amd64_ub20.deb
Can you help me?
Thank you in advance.
73
Sergio
Привет.
Мне нужна версия Debian 32A-amd64 (linux) этого релиза (160-rc7).
Его имя файла что-то вроде jtdx_2.2.###-32A_amd64_ub20.deb
Вы можете мне помочь?
Заранее спасибо.
73
Серхио
Sorry Sergio...I have only windows version....
de Mike
Hello all,
There is 160rc7, changelog:
- added WSJT-X SuperFox mode decoder
- added some changes to Hamlib Tranceiver from WSJT-X code
- validate last grid from sources when size is the same
- databases updated, ALLCALL7.TXT update as of 20240724
- translation updates
- JTDX 2.2.160-rc7 builds made with modified Hamlib, based on Hamlib code with last commit https://github.com/Hamlib/Hamlib/com...e7aa783f519f91 as of August 3rd, 2024
Builds of JTDX 2.2.160-rc7 are made with shared Hamlib libraries,
such approach shall allow on Windows and Linux OS to apply recent Hamlib patches with no need to rebuild JTDX. On Windows OS users can replace libhamlib-4.dll file to apply Hamlib patch,
Mac and Windows users can update Hamlib or revert update to previousversion in JTDX configuration Radio tab.
Linux OS: Hamlib build is supplied as standalone package and shall be installed first (prior to JTDX installation). Hamlib patches can be applied via Hamlib upgrade.
Information on Hamlib changes is available via this link: https://github.com/Hamlib/Hamlib/commits/master
Hamlib open/resolved issues: https://github.com/Hamlib/Hamlib/issues
Language translation: there are minor changes, translation is not needed.
Templates and related source code 160-rc7 as of August 3rd, 2024, can be downloaded from https://drive.google.com/file/d/1iIf...ew?usp=sharing
Linux builds:
File: hamlib_4.6~git.20240803_arm64.deb
SHA256 checksum 6B0EC7E4AA0D6861C96DDE19AEB83371111226E5E2B7A92B04 E097DB877CAA58
https://drive.google.com/file/d/1Xb_...ew?usp=sharing
File: hamlib_4.6~git.20240803_armhf.deb
SHA256 checksum B20161B9C1B69C8AA418F66A851EB21E3AF985D60AB1FDF721 B3547C82FD7004
https://drive.google.com/file/d/1KbS...ew?usp=sharing
File: hamlib_4.6~git.20240803-Ubuntu22.04_amd64.deb
SHA256 checksum 05A57843EA06DE7C8A7C816B78DEBBC9FCEBD5EFEE54DABEBA 0BC43CC3C49264
https://drive.google.com/file/d/1YdK...ew?usp=sharing
File: jtdx_2.2.160-rc7-Ubuntu22.04_amd64.deb
SHA256 checksum 1AA306F5F81768F49548C37AFBC15264525E1173E1C0E8F503 8995C85E4B8AF5
https://drive.google.com/file/d/1jD_...ew?usp=sharing
File: jtdx_2.2.160-32A-rc7-Ubuntu22.04_amd64.deb
SHA256 checksum 10ADD32E7A33D9AF75B5113581482C864110B7DC065B467958 549D6CD3373C01
https://drive.google.com/file/d/1C-l...ew?usp=sharing
File: jtdx_2.2.160-rc7_arm64.deb
SHA256 checksum 53554972D8C4DFC2460614988F1480A5C54497FFB4A13BF058 08B4BB5F8E2577
https://drive.google.com/file/d/1jgV...ew?usp=sharing
File: jtdx_2.2.160-rc7_armhf.deb
SHA256 checksum 51D0785B40E8F597C41B21C8F80E8C6E96B301E7087499CED0 4BB4C0D3EA4AD8
https://drive.google.com/file/d/1Mu8...ew?usp=sharing
MS Windows builds:
File: jtdx-2.2.160-rc7-win64.exe
SHA256 checksum A5F24DE1084DCF44501FE5DAD576AC891AE91AC9A86A807389 EE663093147F48
https://drive.google.com/file/d/12Ck...ew?usp=sharing
File: jtdx-2.2.160-rc7-win32.exe
SHA256 checksum C77669AF7C4C848720012F2F9970A259EFC4F4DB3893CB411A A84F39A262F7A3
https://drive.google.com/file/d/1ifx...ew?usp=sharing
File: jtdx-2.2.160-32A-rc7-win64.exe
SHA256 checksum CEA6DE5AB6E0B5C24768278821C32C093727D2CB40FCF86F05 A1D71BE189D841
https://drive.google.com/file/d/1SyF...ew?usp=sharing
File: jtdx-2.2.160-32A-rc7-win32.exe
SHA256 checksum 1EB23210B5E58CD095E4CE58D5876E61B68EB9C7F0D32EA1BA 132595F0B5D1EF
https://drive.google.com/file/d/1mmD...ew?usp=sharing
MS Windows debug builds:
File: jtdx-2.2.160-rc7-d2-win64.exe
SHA256 checksum A7C906FC4E59099BC145AAFD55706A4BE6B32DD993A7A38E3E 2279930B6D0EE3
https://drive.google.com/file/d/1ODS...ew?usp=sharing
File: jtdx-2.2.160-32A-rc7-d2-win64.exe
SHA256 checksum 444B3261D7F5FAB1FD2DC00DA0CBDA84BF16936449CBBD291C D2FDC180A14338
https://drive.google.com/file/d/1O1-...ew?usp=sharing
Mac OS X builds:
Intel CPU: Sonoma(not tested), Ventura, Big Sur, High Sierra, Mojave, Catalina
File: jtdx-2.2.160-rc7-Darwin-x86_64.dmg
SHA256 checksum 9412A198E8A223DA4F8BDBDD152C6E964E13D553494403AAE8 A4295FB6316462
https://drive.google.com/file/d/1OCr...ew?usp=sharing
File: jtdx-2.2.160-32A-rc7-Darwin-x86_64.dmg
SHA256 checksum D7D098AA63F62F337B385A7BD83C519F50190771F2FFEB7957 17C5AA59CDED9D
https://drive.google.com/file/d/1TVN...ew?usp=sharing
M1 CPU: Sonoma, Ventura, Big Sur
File: jtdx-2.2.160-rc7-Darwin-arm64.dmg
SHA256 checksum D4023DE53741B159809E03830CE37CED9F25D058993D144D9F 04AEEF6932748F
https://drive.google.com/file/d/1VrK...ew?usp=sharing
File: jtdx-2.2.160-32A-rc7-Darwin-arm64.dmg
SHA256 checksum 26FD961A3E89AF16B064CA105DD6EDDA2A3E462EEDCE6E8EF9 FC906B0DA00A65
https://drive.google.com/file/d/1hRW...ew?usp=sharing
MS Windows debug build is dedicated to trace down possible JTDX and TCI bugs, it also logging Hamlib errors, this build can be installed in case any related issue being observed.
Debug log will be recorded in JTDX QSO log directory, file name is jtdx_debug.txt
Also in JTDX log directory tx.wav file will be recorded with TX signal for transmission over TCI interface.
WhatsApp Image 2024-08-12 at 10.52.18.jpeg WhatsApp Image 2024-08-12 at 10.52.26.jpeg
из https://forum.qrz.ru/377-jt65-jt9-ws...ml#post2044465
Должно в зелоёном поле быть "SHound"
При каждом перезапуске программы JTDX, режим SHound нужно переподключать. По-умолчанию будет запускаться "обычный" FT8
Проводил сегодня сравнение по приему FT8 ("обычного") между JTDX RC3 и RC7. Сразу оговорюсь - т.к. я использую SunSDR2, то звук был через TCI.
Сравнение проводилось на диапазоне 24 Мгц, принимал слабый сигнал RI1ANE. Диапазон был достаточно сильно загружен.
Итог сравнения - RC3 безоговорочно по чувствительности выигрывает у RC7. На RC7 RI1ANE практически не принимался, на RC3 спокойно принимался с уровнем -21.
Хочу особо отметить, почему я решил провести это сравнение: у меня JTDX RC3 и RC7 на прием FT8 работают очень сильно "по разному" - в чем это заключается: в RC3 я ручку усиления ПЧ выкручиваю практически до максимума, в результате чего становится возможным прием слабых сигналов, в RC7 так сделать нельзя - если установить усиление ПЧ больше, чем на половину, прием сигналов вообще прекращается из-за перегрузки.
Итог: я себе установил и JTDX RC3 и RC7 - в RC7 я работаю SF, а при работе в обычном FT8 переключаюсь на RC3.
73. Roman.
Many many many thanks!!!
Большое-большое спасибо!!!
Sergio
Ciao! A piece of information, it is possible to make a change in the "wait Call" command after the 4 Tx ", that is Insert the call in the "Gen msg" and put the "wait call" command without sending in tx 4 times the call without answer. This is to facilitate the waiting for a cq call dx, and automatically the answer in tx starts. I hope you understood the question. Thanks Mauro ik3sso.
Mauro
Ваши права
Ответить с цитированием