iOS Version 2.0.49.396 [Beta] Now with Voice in Box and Mute in Box

mswlogo

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Nov 1, 2014
3,295
3,011
MA
#1
Enhancement - Use Speaker is now more intelligent. If you are streaming from your phone and have Use Speaker enabled V1Driver will use your current Audio Route (e.g. Bluetooth Car Speaker, Car Play, Head set). Only if you are not streaming will it use the Speaker. This avoids your Stream being routed to the speaker.

Feature - Custom User Voice phrases using new Voice in Box feature for any desired frequency range. See Voice In Box Settings.

Feature - Custom User Muting using new Mute in Box feature for any desired frequency range. See Mute In Box Settings.

Change - The "K Out Of Box Muting" under AutoMute Settings is removed in favor of the more flexible method.

-----------------------------------------------------------------------------------------------------------------

I realized once I had Voice in Box implemented to handle an unlimited number of custom phrases for any frequency range it would be trivial to have the same for mute boxing.
Rather than specify a "range" followed by some sub range to be "in" or "out" I've simply assumed everything is considered "in" and you specify what you want for any exceptions to be "in" (a phrase or a mute).

Any "Mute in Box" that falls into the K range will show up on the "K Band Spectrum Bar" (as it did with the old K Out Of Band Mute).

If say you want a "narrower" active K Range you might need to add TWO Mute in Boxes. One for the lower portion you want excluded and one for the high.
Same might be true for Voice in Box. Example: lets say you want to Spruce up KA 33.8 you might add (don't take these numbers as gospel)
"KA Out of Tune" 33.0 - 33.7
"KA MPH Bee 3" 33.7 - 33.9
"KA Out of Tune" 33.9 - 34.0

I did add a Default Mute in Box to cover K 23.9 to 24.05 (just as it did with the old K Out of Box Mute).

Note 1: Only the first match in either table applies.
Note 2: There is no overlap check or cross check between mute and custom phrase yet
Note 3: If it's Muted (for any reason) you won't get the custom voice phrase.
Note 4: To delete or edit entries in the table use the standard iOS Swipe Left Gesture to expose Edit or Delete buttons.

This was 95% UI. The code to implement the mute or voice was all of 10 lines of code. So it didn't "Blot" the app. I'm hoping this doesn't intimidate new users.

The Android version will be updated to match.
 
Last edited:

Deacon

TXCTG
Premium Member
Advanced User
Intermediate User
Newly Registered
Nov 13, 2016
7,454
8,237
Hill Country, TX
#2
I’ll be honest, I don’t understand the methodology. You’re saying as a user I would define what’s OUT of the valid box, meaning that’s what gets muted? If so that’s the opposite of how I would’ve assumed it would work, but that may just be me. It seems like it would be easier and more intuitive to define boxes of valid frequencies in which to be alerted, while alerts outside those ranges are muted.
 

mswlogo

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Nov 1, 2014
3,295
3,011
MA
#3
It was much simpler to implement it this way.

You had to specify what “a range” for say KA 35.5 (a segment) first then specify what’s valid with in it. I could have hard coded each segment and “assumed” what parts of what segments you were marking as valid with in them.

This way nothing has to be hard coded, specified or assumed. It’s also very efficient and easy to verify. If a frequency in any of the frequency ranges mute it. Dead simple.

With this you just specify what’s invalid. Which is often what folks are doing. Like let’s say they can’t shut off the Ka Pop range and it does not exist in their area. They can just mute that whole range. Otherwise they would have had to define the pop range then define some null range that’s valid. Blah.

Or a perfect example it the low end of K (due to euro mode vs USA) Just mute it. The top end is the same. In fact that is the default. One entry to mute the low end of k.

It kind of hit me to do it this way when I was doing “Voice in box” inclusively. I could just do “mute in box” inclusively as well.
 
Last edited:

HeartDoctor

PSL + 5 never more;)
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
May 30, 2016
1,742
2,974
SE Florida
#5
Just installed. Settings/Mute in box does not display numeric frequency entered, just “GHz” swiping to edit reveals data entered.
upload_2018-6-26_9-44-41.png
 

mswlogo

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Nov 1, 2014
3,295
3,011
MA
#6
I’ll check it out.

Which phone? Which iOS version?

Try in landscape and flipping theme and see if you can get it to appear.

Thanks.
 

Deacon

TXCTG
Premium Member
Advanced User
Intermediate User
Newly Registered
Nov 13, 2016
7,454
8,237
Hill Country, TX
#7
I have the same issue. iPhone 8 Plus (256GB) on iOS 11.4, landscape only changes orientation. That could’ve helped lend to my confusion about what’s I was supposed to put in there, as one GHz+GHz pair of lines showed up, but tapping it did nothing. It wasn’t immediately obvious, but I did eventually figure out you can swipe left to reveal an edit and delete button.

One feature request I’d have for implementation before production is, if existing K-band out of box muting settings are defined, go ahead and retain them by converting them to the new in-box settings. I honestly don’t remember exactly what I had, other than they seemed to work well :)

Since it’s K-band, it seems like that should be doable, right? Take the lower and upper bounds of the box and create two new boxes for it, one from the lowest possible frequency up to the previous lower bound, then one from the upper bound to the highest possible frequency. That is, if I’m thinking about the concept correctly, of course.
 

Deacon

TXCTG
Premium Member
Advanced User
Intermediate User
Newly Registered
Nov 13, 2016
7,454
8,237
Hill Country, TX
#8
PS Also, when editing a previous entry, the control doesn’t look like what I would expect, which is the fields completed with editable text (numbers). It appears to show what would be an example of the kind of numbers to enter. But because I happen know what I just entered, I know the values are represented. For the upper bound of 24.075, for example, I would expect to be able to edit just the 7 to an 8 if I were feeling brave. I think for most people with the way it looks and feels now, they’d assume it’s essentially a blank setting every time. I know I did at first. Took me a few tries to figure it out.

5543AA48-E4D6-4FE0-A6A1-2EFD171F6576.png
 

mswlogo

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Nov 1, 2014
3,295
3,011
MA
#9
Yes, I could migrate the old settings.

I did repeat the issue on iPhone 6s 11.4.
Strange it works correctly on the Voice In Box page and works on both Voice and Mute page on iPhone X 12 Beta.

It’s a layout bug of some sort.
 

HeartDoctor

PSL + 5 never more;)
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
May 30, 2016
1,742
2,974
SE Florida
#10
I have an iPhone 6 with iOS11.4. No change in landscape.
 

HeartDoctor

PSL + 5 never more;)
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
May 30, 2016
1,742
2,974
SE Florida
#11
Perhaps the voice and mute sections could be combined. A frequency range would be selected and a checkbox would select muting while a text box would allow voice entry.
 

HeartDoctor

PSL + 5 never more;)
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
May 30, 2016
1,742
2,974
SE Florida
#12
It would also seem helpful for readability if the list was sorted by frequency upon storing an entry. Since muted alerts don’t get voice, the text entry box would grey or disappear if mute is checked.
 
Last edited:

mswlogo

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Nov 1, 2014
3,295
3,011
MA
#13
Perhaps the voice and mute sections could be combined. A frequency range would be selected and a checkbox would select muting while a text box would allow voice entry.
I had it combined and I didn’t like it.
 

HeartDoctor

PSL + 5 never more;)
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
May 30, 2016
1,742
2,974
SE Florida
#14
Now that we have Ka boxes, any consensus on optimal frequencies?
 

mswlogo

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Nov 1, 2014
3,295
3,011
MA
#15
PS Also, when editing a previous entry, the control doesn’t look like what I would expect, which is the fields completed with editable text (numbers). It appears to show what would be an example of the kind of numbers to enter. But because I happen know what I just entered, I know the values are represented. For the upper bound of 24.075, for example, I would expect to be able to edit just the 7 to an 8 if I were feeling brave. I think for most people with the way it looks and feels now, they’d assume it’s essentially a blank setting every time. I know I did at first. Took me a few tries to figure it out.
I understand your concern. That’s how editing has been with POI’s etc. since the start.

I’ll try to improve it in the near future.
 

Deacon

TXCTG
Premium Member
Advanced User
Intermediate User
Newly Registered
Nov 13, 2016
7,454
8,237
Hill Country, TX
#16
I haven't done much editing with POIs. Just add or remove, so I didn't realize that's how it would work over there.
 

HeartDoctor

PSL + 5 never more;)
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
May 30, 2016
1,742
2,974
SE Florida
#17
Any chance of adding direction to POI’s? Some RLC’s are not all way.
Also, if a pin is accidentally deleted, undo would be nice.
 

mswlogo

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Nov 1, 2014
3,295
3,011
MA
#18
Any chance of adding direction to POI’s? Some RLC’s are not all way.
Also, if a pin is accidentally deleted, undo would be nice.
Typically you can place it before the light with a small radius. To solve that. Problem is it will warn on the other side.

Problem with direction is user entering the direction. It already supports it for Savvy Learn. But it gets that value in degrees from your heading. You don’t have that when adding POIs.

Maybe they should go in as a “pair”. And only the first of the pair is ever tripped. You drop it as 2 pins on either side of the intersection. Then no “direction” is needed and no confusion of approaching versus leaving direction.

Or maybe a drop and drag to indicate direction.
 

HeartDoctor

PSL + 5 never more;)
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
May 30, 2016
1,742
2,974
SE Florida
#19
Typically you can place it before the light with a small radius. To solve that. Problem is it will warn on the other side.

Problem with direction is user entering the direction. It already supports it for Savvy Learn. But it gets that value in degrees from your heading. You don’t have that when adding POIs.

Maybe they should go in as a “pair”. And only the first of the pair is ever tripped. You drop it as 2 pins on either side of the intersection. Then no “direction” is needed and no confusion of approaching versus leaving direction.

Or maybe a drop and drag to indicate direction.
I like drop and drag.
 

mswlogo

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Nov 1, 2014
3,295
3,011
MA
#20
Version 2.0.49.398 Beta released.

Bug - Layout broken on both Voice in Box and Mute in Box tables.
Enhanced - Both Voice in Box and Mute in Box tables are now Sorted (by the low frequency).

Thanks for finding the bugs and suggestions.

I'm still looking into making editing more user friendly.