Help for Editing Audio on Waze

[vm53]

Hi everyone, I need help with this macro.
When I use waze, if I go slow the phone volume is too loud and annoying, so I have to turn it down.
If I'm on a fast road, obviously I have to turn it up otherwise I can't hear anything.
I created this macro to automate this thing, but for some reason it doesn't seem to work, I'm definitely doing something wrong.
Can anyone help me correct it?
A thousand thanks

 

[vm53]

Please help with this

 

[RSF]

What is the macro's current behavior (which isn't what you want or expected)? Can you check the MacroDroid System Log to see if the triggers are being triggered as you expect? Do you hear either or both of your two phrases at all?

A couple of initial observations:

• The current macro doesn't set the volume up or down based on velocity; it just speaks one of your two phrases. I assume you were going to add the volume change later, is that accurate?
• Checking the speed every 1 second requires a lot of battery power. Do you need it to check that frequently?

 

[vm53]

What is the macro's current behavior (which isn't what you want or expected)? Can you check the MacroDroid System Log to see if the triggers are being triggered as you expect? Do you hear either or both of your two phrases at all?

Thank you for answering me. The current behavior of the macro is that it says the first sentence every second, when the trigger is activated at the desired speed.

A couple of initial observations:

• The current macro doesn't set the volume up or down based on velocity; it just speaks one of your two phrases. I assume you were going to add the volume change later, is that accurate?

Fair observation, I put the sentences instead of the volume, to test the macro on the road.

• Checking the speed every 1 second requires a lot of battery power. Do you need it to check that frequently?

Frequent speed control will certainly impact the battery, but I think that having Waze in the foreground with GPS active, I don't think it changes much in consumption. It might be enough to simply increase the waiting time to one minute, but in this case the volume will go up or down, after a minute, too much if it gives me vocal directions while I'm at high speed and the volume is still low. If you have any other advice on this matter it is well appreciated!

 

[RSF]

increase the waiting time to one minute, but in this case the volume will go up or down, after a minute, too much

A minute would be too much, yes. But I'd recommend something like 5 or 10 or 15 seconds.

The current behavior of the macro is that it says the first sentence every second

Seems like it always thinks the velocity is low... So, it's either that the velocity value isn't being set reliably, or there's something wrong with the comparison actions.
Couple possibilities regarding that:

1. One thing to try would be to change the type of your variable "velocità" from string to integer. Instead of having an "S" next to the name in the Local Variables list...
   
   it should have an "I" like this:
   
   To do that, just delete the variable and re-create it specifying its type as "Integer" (I don't think there's a way to change the type of an existing variable).
   I actually doubt this is the cause of the problem, since I think MacroDroid converts the string to a number as needed, in the "Compare Values" action. But it's worth cleaning that up.
   You could also just get rid of the local variable entirely, using the built-in ("Magic Text") value in the Compare Values actions:
   
   
   
2. The main thing would be to ensure that the velocity is indeed getting set periodically. Try logging the value for a while, and looking in the user log to make sure the value is set as expected. To create the log event:
   
   Then you can look into the user log via the "User Log" button on MacroDroid's home page. Paste a screenshot of that log to this forum post; that'll help diagnose the situation.

 

[vm53]

A minute would be too much, yes. But I'd recommend something like 5 or 10 or 15 seconds.......

After many tests, following your advice, this is the best solution I have found that works.
Thanks for the help much appreciated.