broken sound level block / feature request

[leoklein -]

Hi,

I'm new to google groups, so I don't know if my message has already been sent on another old thread, but I cannot see it.

I'm trying to use automate as a long term noise logger, but the broken noise level block is hindering me.

As I understand it is working in the block-properties view because there it samples the audio input continuously (and longer) and finally the syste turns the mic "on". 

So my feature request / proposal is: Add a property to the block to "sample data x seconds" before doing the actual measurement, which should fix this(?)

Would be great if this could be implemented! Btw: Great tool!

Best Regards, leo

[Henrik "The Developer" Lindqvist]

I'm aware of the problems with some devices recording silence, i'll rework it for continuous recording then only proceed when it's heard something, then i may also consider adding a sample duration field.

[Manfred Simonet]

Hi,

I'm using Automate for some years on my OnePlus 2 (for more than 6 years a valuable companion) and now moved to a new OnePlus 10Pro.

One flow adjusts ringer volume along surrounding noise level. This worked and still works fine on the OnePlus 2, however on the OnePlus 10Pro the values in the output variable are strange.

Let's say, in edit mode the block shows a sound level from the microphone of 50dB. That works fine on both devices. However, the output variable on the OnePlus 10Pro shows a value of something between 0.7 and 0.8. If it is louder the value might reach a value above 1.

That happens when source is "default" or "Microphone". However, choosing source "Output Mix" and playing some music, the output variable receives a proper dB value.

Any idea how to fix that?

Thanks,

Manfred

[Henrik "The Developer" Lindqvist]

dB is a relative value so i guess is should expected, unless the microphone is calibrated.

[Manfred Simonet]

But why then in edit mode the block shows a proper dB value? It's just the output variable that shows that strange value.

[Henrik "The Developer" Lindqvist]

That's probably because it samples continuously, so it's not noticeable if the device reports silence at the beginning of the sampling period, which some device seems to do.

Reworking how the sampling is done is on the to-do list.

[Simonet, Manfred]

Hi Henrik,

Any news on the mic sound level issue?

Still the variable to store the sound level receives a value of 3. something, but in the block I can see much more ( see screenshot).

Thanks, 

Manfred

--
You received this message because you are subscribed to a topic in the Google Groups "Automate" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/automate-user/k40sEmRH72Q/unsubscribe.
To unsubscribe from this group and all its topics, send an email to automate-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/automate-user/79cf978e-e799-48ff-aeb8-f115dcf1230en%40googlegroups.com.

[Henrik "The Developer" Lindqvist]

Sorry, no news, it's still on the to-do list. Using a minimum sound level should avoid the issue.

[Simonet, Manfred]

Thanks, Henrik, for the hint. 

It helps, although it's not perfect.

Br, Manfred

To view this discussion on the web visit https://groups.google.com/d/msgid/automate-user/d8bf08c0-7274-4a83-9793-2b8ed6ff594fn%40googlegroups.com.