![]() It would be neat to have the decoded CW clickable to fill in certain log fields. But rarely will use a decoder in a normal QSO. I also like to use a decoder to check the quality of my own sending. I like to sometimes use a decoder as a fall back for trying to copy 30/35 plus WPM in my head. I like to use a decoder to check CW speed of another QSO I am trying to head copy. Also I would want FRLogger to magically configure everything for me :) Yes, I'm that lazy ! So for me there is not a great interest in this feature but it can be useful in certain cases. I would much rather pay for CW Skimmer which is very useful for contesting. I would not want to have to pay for CwGet to make this work. However, everyone seems to want modern day radios to contain CW, PSK and RTTY decoders for some reason. I am also a proficient CW operator and rarely use a decoder. Would it be better in the slices?įrom: On Behalf Of N3HEE Sent: Monday, J8:50 AM To: Subject: Re: CW decode This makes the display a little tricky if we pile it all into the CW panel. ![]() I’ve not tested this fully yet but I believe it is possible to startup multiple CWGet instances feeding each one a different DAX number and decode from multiple slices. I was planning to allow you to enable/disable CW decode on the CW panel but I’m open to suggests on where the decode should be displayed. This means the actual CWGet window can be minimized if desired. Then using inter app communication FRLogger will receive the decoded characters from CWGet. ![]() FRLogger would start CWGet passing it the dax channel to use. You would need to have Dax enabled for the slice you want to decode. This means it has to be installed and FRLogger needs to know where. In this interim mode using CwGet the process to have FRLogger decode would be to allow FRLogger to startup CWGet. But registering is not difficult or expensive. It runs for a while in non registered mode and you may be able to get by in that mode. This means you’ll have to buy his program. The point of this long winded message is to get a feel for the interest in CW decode in FRLogger.įor V15 I think I am going to add a mode that relies on CwGet. I’ve contacted him several times but he seems to be too busy and has lost interest even in maintaining CWSkimmer or adding new features to it. In my ideal view if I could get the author of CWSkimmer to release a usable library that would basically take in I/Q and return some structure full of various decoded CW that would be a fantastic solution usable by many pieces of software. ![]() But I was looking for a simple solution for the time being. CW decode, to do it well is not trivial and some day I might undertake the task of trying to create a good decoder within FRLogger. I have also had requests from a few people that wondered about CW decode within FRLogger. I don’t use this all the time as I try hard to rely on my head copy but sometimes I find I need it. To get around this when working high speed CW and also to help me “check” myself to make sure I’m getting what I think I’m getting I make use of CwGet which is a program by UA9OV. My head copy is about 30 WPM but due to my nature I will get distracted and sometimes lose a word or copy something incorrectly that doesn’t make sense then I lose my head buffer for a few seconds until I resync.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |