Gents, I think you overcomplicating the stuff again.
Just to make it clear: I am using SunSDR2 version (not Pro) since 2014 and my dominant mode is CW (very rare I use JT). I am using CT599 iambic for "hand operations", however I have tested various single paddle and/or vibro with SunSDR2. I have tested CW on Pro and DX versions as well. Through the years I have tested number software-generated keyers, most of them are Logs with CW key-in support. And I am using SW-generated keyers for my DXpeditions.
The absolute most problems heard about CW and SunSDR2 are clearly not related to SunSDR itself, neither to ESDR2, but to user setup. And the most mistake user is doing while setting up CW with SunSDR - is creating setup with to big unequal path for "key" and "controlling sound", introducing significant delay between signals. (BTW, Enzo told you that few posts above, but it seems he was not heard).
Please note that there is a difference when setting up CW with SunSDR in hand (keyer) or auto (any kind of "automated") mode.
When it comes to hand CW operations. The easiest way for SunSDR newbee to understand how to setup CW with SunSDR correctly is to use "single device" connectivity rule. Either:
- Option1 (preferred) - connect keyer to SunSDR key jack AND connect headphones to SunSDR HP jack
or
- Option2 - connect keyer and headphones via PC.
Please note that Option2 has "variations". While entering "variations" field, the absolute prerequisite for the user would be "know what I am doing". If you "do not know" and use "guess (or 'lets try', or any other guesstimate approach) the most likely outcome will be hours spent for nothing, ending up in panic posts in forums.
Please note two significant parameters we are dealling while setting up CW with SunSDR: signal delay (between key-in and controlling audio) and signal path (for each - key signal and controlling audio signal). The ideal is to keep both - delay and paths - to minimum. Choosing Option 1 gives you both parameters in absolutely minimal achievable values for SunSDR ecosystem. Due to individual shack setup Option 1 may be not achievable (it is understood, common and does not require further expansion).
Setting up Option 2 requires you to find the way to keep both parameters to as minimum as possible and try to not cross the absolute threshold of hearing (ATH) line (which is individual dependent and resides in between 20-200ms). The problem is that PC manufacturers do not give you the information about the delay (in ms) for their products (i.e. Sound Cards, HDMI controllers, Headphones, Sound systems, etc), hence in most cases there is a guess instead of figure. However what you can be sure - longer path for the signal causes bigger delay.
Please note that in most connectivity scenarios the "key signal path" will always be shorter than "sound signal path", introducing delay anyway. If the delay between "key" and "sound" is above user individual ATH sencitivity - that is when the missmatch is heard. Most newbies in SunSDR world are mistakenly identifying this mismatch as SunSDR problem. Fortunately, most "correct" connectivity scenarios are below ATH.
Please note that there is no unified recepy how to setup Option 2 (it is for Option 1 though). We all have different PC, headphones, wires, loggers and other systems in line.
If you have chosen guesstimate way to setup Option 2 and have achieved predicted outcome already, then please think about the following option:
- Analyse your setup for "key signal" and "sound signal"
- Try to find weak points and eliminate them. It can be even wire connector, by experience. It can be slow/old codec in you sound card. It can be too many digital conversions.
- if nothigs helps, post your setup in this forum and explain the symptoms - this would be most productive way.
And try to understand - SunSDR has very flexible and simple design for CW. Perhaps, CW is the only part of SunSDR desing, which did not require any changes already for years. And it can certainly haldle most of imaginable connectivity scenarios. All it requires is the user who knows what he is doing.
Hope that helps.