Date   

Re: CTCSS plugin #sdrsharp

jdow
 

OK, I saw the discussion as moving into the programmers' realm and your question hit me out of left field. It might be interesting to try to explain what the programmer would have to do. It's an issue involved in making modular portions of the program work well together. In the jargon data of this sort if moved in buffers or arrays of values. The modules work on the array of values and pass their output in buffers, sometimes the same ones it came in on and other times new buffers, on to the next module(s). Sometimes, as with some forms of filters, the software works better or even requires a specific size of buffer to work with. Smart modules which face this problem read the incoming data into a work buffer. If it runs out of data on any load of data through the chain of modules it saves the work buffer and waits for the next incoming buffer, Then it reads either until it has its work buffer full or it again runs out of input. As soon as it's work buffer is full, it performs its calculations, passes along the work buffer, switches to another work buffer, and starts filling it with the remaining incoming data. Of course, a good program module either is known to never get too much data or makes provisions for large incoming buffers and fills work buffer, calculates, feeds it on, switches to a new work buffer, and repeats at fills work buffer.

It appears the CTCSS plugin module does not do this and gets confused. The fix should not be very difficult. And there is a real chance it might make the module work better than it used to . Alas, the source code is nowhere to be found.

(Of course, a really enterprising programmer might obtain and install a copy of Ghidra from github and decompile the module. But, that's cheating - and not at all easy.)

Out of curiosity did I manage to make the above nearly understandable to a non-programmer? (It rather points out that programming is keeping your thinking process clear and organized. Math beyond basic MDAS is not often a major factor even for most of an SDR processing module.)

{^_^}

On 20210827 07:21:56, Patrick wrote:
Joanne : I'm not a programmer, just a basic user.
But I first thought the reply from Prog ("Buffer the samples you get and only process when you reach the right size") was intended for me, hence my question !


Le ven. 27 août 2021 à 16:16, jdow <jdow@...> a écrit :
"Concretely, how is this done?"

I guess it was you. If you are a programmer I'd expect you to understand concepts such as multiple buffers, fifos, and the like. If you are not the explanation gets a little boringly long.

And I'm feeling a lot more blunt than usual. I woke up at a very low energy level and that makes be cranky. "It's a featuer" of Aspergers,

{^_^}   Joanne

On 20210827 03:00:08, Patrick wrote:
@jdow : Who is your comment for ?

Le ven. 27 août 2021 à 11:50, jdow <jdow@...> a écrit :
You are kidding, right? Or else you are 100.000% not a programmer. Which is it so I can pitch my reply to your level.
{o.o}

On 20210827 02:22:43, Patrick wrote:
Concretely, how is this done ?

Le ven. 27 août 2021 à 11:05, prog <info@...> a écrit :
On Fri, Aug 27, 2021 at 10:25 AM, Patrick wrote:
Indeed ! I just found his message.
 
" As for the CTCSS plug-in, I don't see an immediate solution to fixing this.
The method the plug-in uses requires a few zero crossings to occur in the audio buffer to detect the tone.
Because the new SDR# (1822) has reduced its audio buffer size, the plug-in is no longer able to see the minimum amount of zero crossings to detect any tones. For me the number of samples in the buffer went from 1664 to 256".
 
I hope Prog will find a way to fix this glitch.
So basically this plugin never worked with low latency sound cards.
=> Buffer the samples you get and only process when your reach the right size.





Re: CTCSS plugin #sdrsharp

Patrick
 

Joanne : I'm not a programmer, just a basic user.
But I first thought the reply from Prog ("Buffer the samples you get and only process when you reach the right size") was intended for me, hence my question !


Le ven. 27 août 2021 à 16:16, jdow <jdow@...> a écrit :
"Concretely, how is this done?"

I guess it was you. If you are a programmer I'd expect you to understand concepts such as multiple buffers, fifos, and the like. If you are not the explanation gets a little boringly long.

And I'm feeling a lot more blunt than usual. I woke up at a very low energy level and that makes be cranky. "It's a featuer" of Aspergers,

{^_^}   Joanne

On 20210827 03:00:08, Patrick wrote:
@jdow : Who is your comment for ?

Le ven. 27 août 2021 à 11:50, jdow <jdow@...> a écrit :
You are kidding, right? Or else you are 100.000% not a programmer. Which is it so I can pitch my reply to your level.
{o.o}

On 20210827 02:22:43, Patrick wrote:
Concretely, how is this done ?

Le ven. 27 août 2021 à 11:05, prog <info@...> a écrit :
On Fri, Aug 27, 2021 at 10:25 AM, Patrick wrote:
Indeed ! I just found his message.
 
" As for the CTCSS plug-in, I don't see an immediate solution to fixing this.
The method the plug-in uses requires a few zero crossings to occur in the audio buffer to detect the tone.
Because the new SDR# (1822) has reduced its audio buffer size, the plug-in is no longer able to see the minimum amount of zero crossings to detect any tones. For me the number of samples in the buffer went from 1664 to 256".
 
I hope Prog will find a way to fix this glitch.
So basically this plugin never worked with low latency sound cards.
=> Buffer the samples you get and only process when your reach the right size.




Re: CTCSS plugin #sdrsharp

jdow
 

"Concretely, how is this done?"

I guess it was you. If you are a programmer I'd expect you to understand concepts such as multiple buffers, fifos, and the like. If you are not the explanation gets a little boringly long.

And I'm feeling a lot more blunt than usual. I woke up at a very low energy level and that makes be cranky. "It's a featuer" of Aspergers,

{^_^}   Joanne

On 20210827 03:00:08, Patrick wrote:
@jdow : Who is your comment for ?

Le ven. 27 août 2021 à 11:50, jdow <jdow@...> a écrit :
You are kidding, right? Or else you are 100.000% not a programmer. Which is it so I can pitch my reply to your level.
{o.o}

On 20210827 02:22:43, Patrick wrote:
Concretely, how is this done ?

Le ven. 27 août 2021 à 11:05, prog <info@...> a écrit :
On Fri, Aug 27, 2021 at 10:25 AM, Patrick wrote:
Indeed ! I just found his message.
 
" As for the CTCSS plug-in, I don't see an immediate solution to fixing this.
The method the plug-in uses requires a few zero crossings to occur in the audio buffer to detect the tone.
Because the new SDR# (1822) has reduced its audio buffer size, the plug-in is no longer able to see the minimum amount of zero crossings to detect any tones. For me the number of samples in the buffer went from 1664 to 256".
 
I hope Prog will find a way to fix this glitch.
So basically this plugin never worked with low latency sound cards.
=> Buffer the samples you get and only process when your reach the right size.




Re: CTCSS plugin #sdrsharp

Patrick
 

Hi Scott,

Yes, I  use the CTCSS plugin simply to help identify unknown signals on VHF (mainly ski resorts, mountain rescue).
I know that KG Tone is a good alternative, but I really appreciate CTCSS decoder because it integrates perfectly and discreetly with SDR#. I'll still give KG tone a try, but will probably use an older version of SDR# for my VHF listening that requires this tool, if no fix was found for the other plugin.

In any case, thank you for your kind reply.

Regards,
Patrick



Le ven. 27 août 2021 à 13:57, Scott/KC1UA via groups.io <shalligan15=protonmail.com@groups.io> a écrit :
Patrick,

I'm not sure exactly what you're trying to accomplish with the CTCSS plug-in. Is it simply to help identify unknown signals or are you trying to use it for actual tone squelch purposes? Again, in either case, the aforementioned KGTone will do either job until and unless this issue is resolved. It's free software and it can even handle processing audio if you simply pipe the audio out of SDR# via a virtual audio cable (some of which are free as well). It also does an admirable job of decoding DCS as well, along with DTMF, and if it is legal in your area, it can do a fair job of unscrambling some voice inversion. In my opinion it is worth a try for anyone who wishes to accomplish any of this.

I read the comments at RR as well and it doesn't seem as though it will be fixable in the short term, anyway. 
--
Scott - KC1UA
Marstons Mills, Cape Cod, MA USA


Re: CTCSS plugin #sdrsharp

prog
 

On Fri, Aug 27, 2021 at 11:50 AM, jdow wrote:
You are kidding, right? Or else you are 100.000% not a programmer. Which is it so I can pitch my reply to your level.
{o.o}
I won't expect all the end users to be also programmers. I will check with the dev. 


Re: CTCSS plugin #sdrsharp

Patrick
 

<< This is for plugins developers >>
Aaah OK !

For those who wonder where the CTCSS plugin developer's answer comes from : https://forums.radioreference.com/threads/sdr-plug-in-frequency-scanner-updated.402110/page-24#post-3558794).
I just copied/pasted his message here, in case someone could help or provide a remedy.


Le ven. 27 août 2021 à 13:51, prog <info@...> a écrit :
On Fri, Aug 27, 2021 at 11:23 AM, Patrick wrote:
Concretely, how is this done ?
This is for plugins developers. 


Re: CTCSS plugin #sdrsharp

Scott/KC1UA
 

Patrick,

I'm not sure exactly what you're trying to accomplish with the CTCSS plug-in. Is it simply to help identify unknown signals or are you trying to use it for actual tone squelch purposes? Again, in either case, the aforementioned KGTone will do either job until and unless this issue is resolved. It's free software and it can even handle processing audio if you simply pipe the audio out of SDR# via a virtual audio cable (some of which are free as well). It also does an admirable job of decoding DCS as well, along with DTMF, and if it is legal in your area, it can do a fair job of unscrambling some voice inversion. In my opinion it is worth a try for anyone who wishes to accomplish any of this.

I read the comments at RR as well and it doesn't seem as though it will be fixable in the short term, anyway. 
--
Scott - KC1UA
Marstons Mills, Cape Cod, MA USA


Re: CTCSS plugin #sdrsharp

prog
 

On Fri, Aug 27, 2021 at 11:23 AM, Patrick wrote:
Concretely, how is this done ?
This is for plugins developers. 


Re: CTCSS plugin #sdrsharp

Patrick
 

@jdow : Who is your comment for ?

Le ven. 27 août 2021 à 11:50, jdow <jdow@...> a écrit :
You are kidding, right? Or else you are 100.000% not a programmer. Which is it so I can pitch my reply to your level.
{o.o}

On 20210827 02:22:43, Patrick wrote:
Concretely, how is this done ?

Le ven. 27 août 2021 à 11:05, prog <info@...> a écrit :
On Fri, Aug 27, 2021 at 10:25 AM, Patrick wrote:
Indeed ! I just found his message.
 
" As for the CTCSS plug-in, I don't see an immediate solution to fixing this.
The method the plug-in uses requires a few zero crossings to occur in the audio buffer to detect the tone.
Because the new SDR# (1822) has reduced its audio buffer size, the plug-in is no longer able to see the minimum amount of zero crossings to detect any tones. For me the number of samples in the buffer went from 1664 to 256".
 
I hope Prog will find a way to fix this glitch.
So basically this plugin never worked with low latency sound cards.
=> Buffer the samples you get and only process when your reach the right size.



Re: CTCSS plugin #sdrsharp

jdow
 

You are kidding, right? Or else you are 100.000% not a programmer. Which is it so I can pitch my reply to your level.
{o.o}

On 20210827 02:22:43, Patrick wrote:
Concretely, how is this done ?

Le ven. 27 août 2021 à 11:05, prog <info@...> a écrit :
On Fri, Aug 27, 2021 at 10:25 AM, Patrick wrote:
Indeed ! I just found his message.
 
" As for the CTCSS plug-in, I don't see an immediate solution to fixing this.
The method the plug-in uses requires a few zero crossings to occur in the audio buffer to detect the tone.
Because the new SDR# (1822) has reduced its audio buffer size, the plug-in is no longer able to see the minimum amount of zero crossings to detect any tones. For me the number of samples in the buffer went from 1664 to 256".
 
I hope Prog will find a way to fix this glitch.
So basically this plugin never worked with low latency sound cards.
=> Buffer the samples you get and only process when your reach the right size.



Re: Virtual Audio Cable ( Muzychenko)

Chris van Lint
 

Derek,

Have you recently updated your version of VAC? I had an issue with VAC a few months ago and nothing I did could fix it, until I thought of updating my version of VAC which at that time was about 3 years old.

Chris VK4CVL

On 27/08/2021 18:20, 6vc8 wrote:
Not going to help much Derek but I haven't noticed any issues with VAC/Windows 10 when using it to route audio to various decoder software (including Tekmanoid/Jaero/DSD) on three different machines.
Can only suggest you recheck your system for any changes which could have affected the audio transport.






Re: CTCSS plugin #sdrsharp

Patrick
 

Concretely, how is this done ?

Le ven. 27 août 2021 à 11:05, prog <info@...> a écrit :
On Fri, Aug 27, 2021 at 10:25 AM, Patrick wrote:
Indeed ! I just found his message.
 
" As for the CTCSS plug-in, I don't see an immediate solution to fixing this.
The method the plug-in uses requires a few zero crossings to occur in the audio buffer to detect the tone.
Because the new SDR# (1822) has reduced its audio buffer size, the plug-in is no longer able to see the minimum amount of zero crossings to detect any tones. For me the number of samples in the buffer went from 1664 to 256".
 
I hope Prog will find a way to fix this glitch.
So basically this plugin never worked with low latency sound cards.
=> Buffer the samples you get and only process when your reach the right size.


Re: CTCSS plugin #sdrsharp

prog
 

On Fri, Aug 27, 2021 at 10:25 AM, Patrick wrote:
Indeed ! I just found his message.
 
" As for the CTCSS plug-in, I don't see an immediate solution to fixing this.
The method the plug-in uses requires a few zero crossings to occur in the audio buffer to detect the tone.
Because the new SDR# (1822) has reduced its audio buffer size, the plug-in is no longer able to see the minimum amount of zero crossings to detect any tones. For me the number of samples in the buffer went from 1664 to 256".
 
I hope Prog will find a way to fix this glitch.
So basically this plugin never worked with low latency sound cards.
=> Buffer the samples you get and only process when your reach the right size.


Re: Virtual Audio Cable ( Muzychenko)

Derek Henderson
 

Yes everything was fine The only thing I can think of is I have installed the new version of Jaero & Jaero  Display 
both work ok but showing only low volume Tekmanoid especially very dull waterfall I did mention this to Jonti 
author of Jaero about the vol indicator but he said his works O,K

Will go over things again and check Thanks for the reply

Derek H


Re: CTCSS plugin #sdrsharp

Patrick
 

Indeed ! I just found his message.

" As for the CTCSS plug-in, I don't see an immediate solution to fixing this.
The method the plug-in uses requires a few zero crossings to occur in the audio buffer to detect the tone.
Because the new SDR# (1822) has reduced its audio buffer size, the plug-in is no longer able to see the minimum amount of zero crossings to detect any tones. For me the number of samples in the buffer went from 1664 to 256".

I hope Prog will find a way to fix this glitch.


Le ven. 27 août 2021 à 10:16, 6vc8 <6vc8g7e0ovnn@...> a écrit :
On Fri, Aug 27, 2021 at 06:53 AM, Patrick wrote:

>
> No one knows how to reach thewraith2008 ?
>
.....................He replied to your post on Radioreference






Re: Virtual Audio Cable ( Muzychenko)

6vc8
 

Not going to help much Derek but I haven't noticed any issues with VAC/Windows 10 when using it to route audio to various decoder software (including Tekmanoid/Jaero/DSD) on three different machines.
Can only suggest you recheck your system for any changes which could have affected the audio transport.


Re: CTCSS plugin #sdrsharp

6vc8
 

On Fri, Aug 27, 2021 at 06:53 AM, Patrick wrote:


No one knows how to reach thewraith2008 ?
.....................He replied to your post on Radioreference


Re: CTCSS plugin #sdrsharp

Patrick
 

No one knows how to reach thewraith2008 ?

Last year, he quickly stepped in to make changes to his Frequency Manager and Frequency Scanner plugins to address Telerik issues, among others, and I seem to have read a few posts from him on the Airspy forum, but maybe he doesn't check it anymore.

Le jeu. 26 août 2021 à 21:53, prog <info@...> a écrit :
On Thu, Aug 26, 2021 at 09:01 PM, Bob Dengler wrote:
When they did they worked poorly,
Supporting arbitrary buffer sizes is part of the plugin specifications.


Re: Optimizing Samplerate to avoid crackling

Juan - EA5XQ
 

Increased to 100ms (from 50ms default) and indeed has improved, now I am using SR 384Kbps and seems to be better, still testing
Thanks
--
Juan, EA5XQ
AirSpy Hf+ Discovery
MLA 30+ /  PA0RDT MiniWhip


Re: CTCSS plugin #sdrsharp

prog
 

On Thu, Aug 26, 2021 at 09:01 PM, Bob Dengler wrote:
When they did they worked poorly,
Supporting arbitrary buffer sizes is part of the plugin specifications.

2521 - 2540 of 43124