AV Linux Experiments with the RECRI KEYER

[df7t...@gmail.com]

AV Linux Experiments - RECRI KEYER

only a few days ago I have installed the present version of AV Linux

which has been published in April 2024.

As a first experiment I tried to build the recri keyer from scratch with the

help of Chuck's video and the information of its author at github.com

May be, that I made the one or other mistake...

But well this has been the first program I built from scratch and I am a

beginner in Linux. This keyer may be configured in so many ways, that, at

present, I can't think of any parameter of a Morse Code audio signal missing.

The first version here is only for keyboard input, but I plan to add Linux (LV2 ?) plugins

to convert the output signal of a square wave generator (connected to the LINE IN of the PC)

into a MIDI signal, that then will key the recri keyer. In that way an electronic keyer and a straight key

may be used in addition to the keyboard input.

73

Tom

---

AV Linux Experiments - RECRI KEYER

menu and options-selector missing

Even though I may set all parameters via the dial:

The menu and options-selector seem to be missing.

See this image from Chuck's video:

Any idea what the reason may  be ? (packages missing ?)

When I turn the dial for the parameter "cas-window", there are the options "none", "." and "dial" --

but the appearance does not change.

Thank you in advance

73

Tom

[df7t...@gmail.com]

AV Linux Experiments - RECRI KEYER

menu and options-selector missing

Here are the two images mentioned in the last message:

DF7TV:

AA0HW:

73

Tom

[Chuck Vaughn]

the command line needs this to see those controls:   -grid 1    

at the end

./keyer kbd -grid 1

--

---
You received this message because you are subscribed to the Google Groups "iCW - internet CW" group.
To unsubscribe from this group and stop receiving emails from it, send an email to i_cw+uns...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/i_cw/113cb6d3-be16-491f-9f6e-532e5906d36dn%40googlegroups.com.

[df7t...@gmail.com]

Hello Chuck,

v e r y  g o o d !!

That made it.

I have been looking to "info keyer" to see some description of options, but I did not see the "-grid 1"

Thank you so much!

(now going back to optimizing the audio setup and to learn a bit about jack, pulseaudio and pipewire...)

Is there a command line parameter to get the menu as shown in your video (SETTINGS, INPUT, DETAILS, SAVE) as well?

73

Tom

[df7t...@gmail.com]

AV Linux Experiments - RECRI KEYER

CW2MIDI plugin

Hello,

At present I am testing a "CW2MIDI" VST3 plugin, which I have made with SynthEdit.

The structure/circuit is the same as for the detector for the keyed time of a Morse Code audio signal, that I made for the sineCW60 (Windows) project.

This sub-circuit proved to work reliably in sineCW60 -- so I just copied it and added a MIDI output, which is ON for the duration of the input signal and sends

a MIDI note (note 69 at present) to the output of the plugin.

CW2MIDI is made available to the recri keyer via Wine/Yabridge in the host CARLA in AV Linux.

Input signal to CW2MIDI is a 4 to 5 kHz keyed square wave, the same as for sineCW60.

 

First tests to connect a straight key and the key output of an electronic keyer to the recri keyer in this way were successfull. The Midi Monitor is there just for testing and may be removed later.

kbd (keyboard input), kbdo (keyboard oscillator/tone) and keyo (key/keyer oscillator/tone) are part of recri keyer.

73

Tom

[aa0hw]

be interesting to see if the new synthedit audio in to midi out plugin,  has any , if at all,  timing jitter...

can you set up a test to send external dits at a high rate into the plugin's input port,  and measure the final midi output to new cw note   ELEMENT LENGTH and space between elements  ?

and the latency between audio input from the actual tone input to final cw output(you may have already reported that one)

in the past using a couple of other audio to midi apps,   everything was pretty good with very minimal timing jitter when using JACK MIDI, but not so using ALSA MIDI

alsa midi had way too much timing jitter where the cw element length was quite varied by a few milliseconds plus and minus

i have found it is much easier to recreate a harsh cw tone, than trying to FILTER it to the max to get a clean tone out of it...

just some thoughts on the matter

c

...

[df7t...@gmail.com]

Hello Chuck,

Making CW2MIDI with Synthedit is a quick & dirty first trial.

The disadvantage being that Wine & Yabridge have to be used - at present I do not know if that introduces latency or other unwanted effects on timing.

The advantage being that CW2MIDI is simple and only capable of what is necessary.

A native LV2 Linux plugin (https://lsp-plug.in/?page=manuals&section=trigger_midi_mono etc.) for the same purpose might be better.

At present, the midi output of CW2MIDI keys the recri keyer's "keyo". It may be that the "Trigger to MIDI" module of SynthEdit is not perfect -- but I do not know now.

I'll come back to your questions / suggestions of measurements later...still at the beginning here :)

BTW: Any idea how I may get the menu to the recri keyer GUI as shown in your video (SETTINGS, INPUT, DETAILS, SAVE) ?

I have sent an email to the author ("rec...elf.com"), but got no answer so far.

It would help to be able to save the settings of recri keyer and get them back at next start.

73

Tom

[Chuck Vaughn]

RE: SETTINGs, INPUT, DETAILs, SAVE

i have not used the SAVE function , so can offer no solution at this time...

you can also register an ISSUE at his github recri keyer site and he will get a notice

c

...

To view this discussion visit https://groups.google.com/d/msgid/i_cw/2145cbd3-af41-40b6-9193-dbda7773b4a1n%40googlegroups.com.

[df7t...@gmail.com]

"RE: SETTINGs, INPUT, DETAILs, SAVE

i have not used the SAVE function , so can offer no solution at this time...

you can also register an ISSUE at his github recri keyer site and he will get a notice

c"

Thanks! I'll do that.

Tom

[df7t...@gmail.com]

SETTINGs, INPUT, DETAILs, SAVE

Roger (rec) has been so kind to answer my question concerning saving settings or adding command line parameters, and the command line parameters work.

Here is our short exchange:

Am 29.11.2024 um 18:55 schrieb Roger E Critchlow Jr:

Hi Thomas --

Sorry for the delay in responding. I got behind in cleaning up my spam
folder where you were filed with 163 other messages.

I can't see how to save settings offhand, I went through a lot of one-off
variations working with Chuck, but you can add settings to the command line
easily.

Each of the parameters listed in the UI is listed by its command line
option name, so

~/keyer/bin/keyer kbd -grid 1 -kbd-wpm 55 -kbdo-freq 600

would start with the keyboard keyer speed set to 55 WPM and the keyboard
keyer oscillator set to 600 Hz.

I'd like to believe that the component and option names are
self-explanatory, but I'm not that deluded.

Running ~/keyer/bin/keyer with no arguments will list the 'setups' that
have been defined with a one line description.

That may be too much information already. Happy to try to answer any
questions.

-- rec -- ad5dz --

---

Thank you Roger!

Just tried it according to your info in my setup and

~/keyer/bin/keyer keyo -grid 1 -keyo-note 69 -keyo-freq 650 -keyo-rise 8.0 -keyo-fall 8.0

behaves as intended :)

FYI: I made an "external" CW2MIDI (VST plugin in VST host Carla) to convert a square wave CW at the sound card input to the MIDI event (NOTE nr. 69) controlling keyo; 

see

 https://groups.google.com/g/i_cw/c/1fDkamby1xk/m/30VDl0AUAwAJ

In that way I may use my Logikey keyer in combination with a square wave generator for paddle input to keyo. I am used to the CMOS Super Keyer timing available as emulation V0 in the K-5 keyer.

Thanks again

73

Tom

--

[df7t...@gmail.com]

Just to share my newly gained knowledge thanks to rec, AD5DZ:

--

Am 10.12.2024 um 18:19 schrieb Roger E Critchlow Jr:

Hi Tom --

Sorry, got behind on emptying my spam folder again.

Using -ramp on the command line sets both -rise and -fall to the same
value.

Using -window2 specifies a second window function to multiply with -window
to form the actual ramp function. It turns out that many of the named
window functions are already such products of simpler window functions, so
this appeared to give Chuck a way to build more ramp functions. They get
multiplied together element by element.

-- 73 -- rec -- ad5dz --

[Chuck Vaughn]

combining the raised cosine WINDOWs, 1 & 2 , multiplying them,   testing this combo/that combo , etc  may create

amazing new CW NOTE SOUNDs, audiophile quality  etc..

... mostly noticeable at the higher speeds, where cw note edge noise becomes a serious distractor 

To view this discussion visit https://groups.google.com/d/msgid/i_cw/b297ad43-0f43-4336-948c-0894203b7e51n%40googlegroups.com.