Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Svxlink exporting audio line levels as system variable #684

Open
cbspidi opened this issue Nov 2, 2024 · 11 comments
Open

Svxlink exporting audio line levels as system variable #684

cbspidi opened this issue Nov 2, 2024 · 11 comments

Comments

@cbspidi
Copy link

cbspidi commented Nov 2, 2024

Hi Guys,

Can I request a feature, please?

Working with svxreflector for some time, I find it challenging to find the actual audio line levels.(repeater works in server (CLI) mode only.
It would be super useful to know what the svxlink audio line levels are, reported in dB value.
It would be very nice to have it exported into a system variable called $svx_tx_line_level and $svx_rx_line_level respectively.

This could be partially implemented already, a form of alert has already been produced in the logs for peak detection.

Automated actions can be written based on specific values for those variables.

Please let me know what you think.

@f5vmr
Copy link

f5vmr commented Nov 2, 2024 via email

@f5vmr
Copy link

f5vmr commented Nov 2, 2024 via email

@f5vmr
Copy link

f5vmr commented Nov 2, 2024 via email

@cbspidi
Copy link
Author

cbspidi commented Nov 3, 2024

Hello,
Apologies for not been clear with my initial message, yes there is reflector that i work with but the same hardware also serves a purpose of a local gateway access.
Its the local gateway TX and RX audio line levels I would be interested to see, as @f5vmr mentioned, this has nothing to do with reflector part of configuration.

I think a good way of implementing this feature would be to have a configurable "0/1" variable under below two section.
A simple suggestion would be export_audio_level=0 or 1, this would be very neat and handy feature.

[Rx1]
TYPE=Local
RX_ID=R
AUDIO_DEV=alsa:plughw:1
AUDIO_CHANNEL=0


[Tx1]
TYPE=Local
TX_ID=T
AUDIO_DEV=alsa:plughw:1
AUDIO_CHANNEL=0

@f5vmr , tell me more about your config with alsa, what and how did you do it?

@f5vmr
Copy link

f5vmr commented Nov 3, 2024 via email

@cbspidi
Copy link
Author

cbspidi commented Nov 3, 2024

Hi @f5vmr , i will ping you directly for more info on your way of configuring the svxliink, its always great to see how other engineers have it done.

On the feature request, it will be nice to have an input on the code change for this to be implemented.

@cbspidi
Copy link
Author

cbspidi commented Nov 5, 2024

Hello guys,
It would be amazing to have this available via API call, but I understand there would need to be significant code implementations for the API system to be structured and thought about.
Maybe it would be a good start for other parameters to be available and maybe changeable via API calls.

For now, if developers would be kind enough, it would be great to see this as an integer exported to the system variable

@sm0svx
Copy link
Owner

sm0svx commented Nov 5, 2024

The way to get your audio levels right is to use the devcal utility to calibrate all receivers (and transmitters) to exactly the correct level. That is, the received FM deviation on one receiver should ideally be reproduced on all other transmitters with exactly the same deviation.

But I agree that it would be useful for a reflector sysop being able to monitor audio levels for all nodes to find the nodes that does not have the correct calibration. I may add such a feature but I must be honest and say that it's not at the top of my TODO-list.

@cbspidi
Copy link
Author

cbspidi commented Nov 6, 2024

Hello @sm0svx,
It's great that you can see this being very useful for sysop people.
Going back to your TODO list, is there anything we can do as a temporary solution, something that is not perfect, or maybe not 100% accurate?

I was thinking of measuring peeks every 100ms; we already do it in the code to produce the warning message in the log.

A quick fix with a proper solution to be implemented later.

Im not a coder myself, but if you were to lead me in a direction of what and were would need to be changed for the quick fix I could go out and ask for help with other ham`s

@cbspidi
Copy link
Author

cbspidi commented Nov 13, 2024

Hi Tobias, @sm0svx

Would you have any comments on my last message?

@cbspidi
Copy link
Author

cbspidi commented Mar 2, 2025

Hello Tobias @sm0svx ,
Checking to see if there anything we can assist with in pushing this request forward?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants