Using Linux software , a CW KEYER, iambic paddles, and a straight key are demo'd in this video...all morse code instruments are ready to send cw at any time in "near zero" low latency so there is no lag felt when keying any of these virtual Linux software morse code generators with your actual hardware iambic paddles, or straight key...
or keyboard (both paddles & st key are directly connected and using their own serial port on the computer where cwirc is listening to the closing of the dtr with the dsr or cts pins)(2 serial ports are needed)
THE CW KEYBOARD:
please contact wa0eir for a beta version of his latest source for building TWQRQ CW KEYER.
THE IAMBIC PADDLES:
if you have Pulseaudio 6.0 or later, alsa-oss, and are using Jack Audio Connection Kit with the Pulseaudio-jack-module: https://launchpad.net/ubuntu/trusty/+package/pulseaudio-module-jack, you can create as many pulseaudio module-jack-sinks as required and name them according to the morse code apps.
You will see in the video TWQRQ, Iambic Paddles, and Straight Key
module-jack-sinks that use these pulseaudio bridges...you select which jack-sink you want to use in PAVUCONTROL for each app. https://launchpad.net/ubuntu/trusty/+package/pavucontrol
here are the commands i used to bridge pulseaudio with the apps:
pacmd load-module module-jack-sink client_name=TWQRQ
pacmd load-module module-jack-sink client_name=iambic_paddles
pacmd load-module module-jack-sink client_name=straight_key
to get 2 instances of cwirc, you have to bring up 2 terminals and use this command for lowest latency --- aoss xchat ---
then you have to log into some server with both terminals and then immediately disconnect...then click on the cwirc userlist button to bring up cwirc for each xchat instance(userlist buttons must be enabled in the Xchat menu in order to see them)
NOTE: if you hear any audio pops or clicks from TWQRQ when using the low buffer frames as shown in this video(128 buffer frames at 48k sample rate) you can click on CATIA and increase the buffer frames to 512, then back again to 128...this is just a workaround to get rid of the audio dropouts from TWQRQ at 128
The goal in this setup was to use only native Linux apps for all the morse code instruments to send cw to the sound card and also to key the rig(via an audio derived cw keying circuit)