Voice Keyer in 2.0.x problem

[Steve Harbin]

When I click the voice keyer button, it momentarily keys up then immediately unkeys the rig. This wasn’t the case in 1.x.x versions. Is this a known issue or is it something only I am experiencing?

I am using CAT interface with IC-740. PTT button works as expected.

73,
Steve KT5G

Steve Harbin

[Mooneer Salem]

Hi Steve,

Some stuff did change internally with the voice keyer feature between 1.x and 2.x. Can you try right-clicking on the Voice Keyer button and choosing "Use another voice keyer file...", followed by the one you were originally using? After reselecting it, left-click the Voice Keyer button and let me know if it still immediately stops transmitting.

Thanks,

-Mooneer K6AQ

--
You received this message because you are subscribed to the Google Groups "digitalvoice" group.
To unsubscribe from this group and stop receiving emails from it, send an email to digitalvoice...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/13CA700D-B4D9-4941-8ADA-811F4EE7839F%40gmail.com.

[Steve Harbin]

Hi Mooneer,

I did select the file again. Unfortunately, the same results. 

[Mooneer Salem]

Hi Steve,

Can you go to Tools->Options->Debugging and do the following:

* Check "Verbose" (if not already checked).

* If on Windows, check "Show Console".

After doing so, try kicking off the voice keyer again, then copy/paste the text that shows up in the console to a text file and email that to me off-list.

Thanks,

-Mooneer K6AQ

To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/afc4704d-afb6-438c-ad9b-9f77a03f7256n%40googlegroups.com.

[Barry Jackson]

I do recall an issue recently (in 2.0.2-dev) where I was seeing the same
sort of behaviour.

An existing VK CQ file exhibited this and I realized that it had quite a
long intro of silence, which I assumed (rightly or wrongly) was maybe
being detected as the end of the message.

I used audacity to trim most of the silence at start and finish of the
message and it then worked fine, and is still working in 2.0.2/3dev.

73
Barry

[Steve Harbin]

Thanks for the suggestion Barry.  I used Audacity to trim any preceding
and succeeding silence on the file.  Unfortunately, that didn't help in
my case.

73,

Steve

[Steve Harbin]

After tinkering around with Audacity, I think I have discovered a remedy
for the problem.  The original file was stored in stereo format.  If I
save the same file as mono, the voicekeyer function now works as expected.

Thanks,
Steve KT5G

[Mooneer Salem]

Hi Steve,

Good to hear that the problem's resolved! We probably do want to detect this case, though, and either alert the user or perhaps mix down the two channels into one. I'll think about it some more.

Thanks,

-Mooneer K6AQ

--
You received this message because you are subscribed to the Google Groups "digitalvoice" group.
To unsubscribe from this group and stop receiving emails from it, send an email to digitalvoice...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/e5c3bbf1-cd75-4d57-8b69-63e1e5588422%40gmail.com.

[Steve Harbin]

Thanks Mooneer.  That sounds good.

[Barry Jackson]

On 06/10/2025 21:13, Steve Harbin wrote:
> After tinkering around with Audacity, I think I have discovered a remedy
> for the problem.  The original file was stored in stereo format.  If I
> save the same file as mono, the voicekeyer function now works as expected.
>
> Thanks,
> Steve KT5G

Good catch!
That is probably what I did without realizing.
I'm not a regular Audacity user and find the 'modern' GUI rather
non-intuitive.

Cheers,
Barry