开云体育

I've noticed one oddity since 0.38 when I engage in a contact with a station on WSJT-X I see the callsign lookup in qLog like before but then it clears away if I have never worked the station before,

I have experienced #4 as well. I don’t have near the log this size but I just deleted one of the QSOs then let LoTW download again. But would be nice to just update all the entries.

1. Backup is longish at 70K QSO but I live with it, I'd actually prefer the backup at exit rather than startup though ;-) I am usually less worried about shutdown time than start up time. 2. Works OK

I don't know how Log4OM behaves with such a volume, but I know how QLog behaves - it is not fast enough for comfortable work. Based on your emails, I tried to look into areas where improvements could

Not really looking for any bug fixes or new features, just some observations and suggestions. Qlog 0.37.2 (built from source, yes I need to upgrade) O/S Manjaro Linux KDE HP Laptop 8th gen i7 with 32

I'm at 70K QSO nearly and it's still going OK, I would venture to say it works better than Log4OM with the same number of QSO. And Log4OM using the same backend. HRD was a dog even at 50K QSO. The

Same issue here. Qlog v 0.38.0 Linux Mint 21.2 Cinnamon The name field width seems to be the culprit for me.

I looked at the code over the weekend and there are many possibilities to improve the performance. Unfortunately, if you have 1M QSOs, you are not a target group for QLog. QLog was designed as a

Hi Ladislav I notice when I set the column widths in the QSO table, the columns do not stay as intended (or as set). My o bservation is that that any text contained in the field affects the width of

Hello Robert, That's what I'm using on my Windows machine, home-made. 73 Norby

Norby, If you have over a million contacts to put it a database, you need a client server database. The only logbook I know of that uses a client server model would be CQRLOG, https://www.cqrlog.com/

Thank you for the explanations and hints. I think that QLog would not fit my needs in the long run, as I have another 1 million contacts to import, even though spread across 130 logs. I'll continue to

Deselecting the >>MODE<<? option in the Rig Settings has made a world of difference when using a Yaesu transceiver when allowing QLog to communicate with the radio from the DX Spot window.

One thing you may can try is to create a custom QSO Filter to limit the contacts. My log is way smaller than yours only about 22,000 entries. I created a filter like this that limits to just QSOs this

This is something I would also like to see implemented in QLog. Regards, Diego

Hi, Thank you for your feedback. *Performance: * I'm probably going to disappoint a lot of people, but to be honest, 300k QSO is the limit for which QLog is not designed and in my opinion I am not

Hi, I installed QLog since I was looking for a logger on Linux. I installed the latest flatpack version (v0.38). It's running on an AMD Ryzen 7 4800U with Radeon Graphics and 32GB RAM. Linux flavor is

I'm sorry, but even the upgrade to the latest Hamlib version (static linking) did not solve this problem. Based on the QLog trace file, I can see that QLog is sending requested modes correctly, but

I am in contact with Mark. We are testing different variants of QLog. Currently it is clear that it is not the command timing from Qlog. út 3. 9. 2024 v 13:28 odesílatel Michael Morgan via groups.io

I am using a Flex radio here and I am not seeing the issue either on Mac or Windows. My son has a Yaesu 710 so I may can run up to his house this evening and test/play with it.