by oblivioncth » Wed Jan 09, 2019 10:11 am
aag wrote: ↑Sun Dec 09, 2018 12:58 pm
It seems that when navigation uses "Search by letter" mode, the resulting list is limited to 12 entries when driving. Not sure if it's AA/Google, or MMA limitation. In either case, the list presented includes 6 entries forward, and 6 entries back, so for example, when searching for 'S', there would be 6 entries for 'S', and 6 entries for 'R', and maybe 'Q'.
Would it be possible to always present the relevant letter only, and maybe (Google gods allowing), present the entire list for that letter? Because the voice search is close to useless, currently some music may be inaccessible while driving.
I believe this is an Android Auto limitation that it automatically applies to ListViews within apps while moving. Technically, it probably could be circumvented but it would require purposely awkward and less efficient programming from the dev's and could land them in hot water if anyone at google noticed and cared to do something about it. Potentially could be a legal issue in terms of liability.
Given that MMA is already a tad less prioritized than MM desktop, I'm guessing the Android Auto functionality is decently down the pipeline (for example the recentish change to album art music on Android Auto broke the display of said art in MMA while in AA mode and I'm curious to see how long it will be before a fix; though, I did just start using it with Android Auto so I could be wrong and they care more about it then I think (even if they don't its understandable because the people using the app with Android Auto is definitely a small part of their userbase).
What would ultimately make this less of an issue is if the voice search was excellent, and as you touched on it ranges from hit and miss to outright sucking. I'm not sure of the specific problems you have with it, but I know the main case I'd like to use it in is when you hit the end of a list and click the "Search By Voice" button. Google assistant should know the context since you're pressing the button from MediaMonkey, but I'll I get is "Sorry I'm offline blah blah blah, you can still play music or blah blah blah" well no shit that's what I'm trying to do, but you're clearly trying to look for the song on Google Play Music instead of the music player I'm already in like would be obvious. Even if I specify "in MediaMonkey (which I shouldn't have to since the button was from that app) it still doesn't work. I'm pretty sure my 4G has been on when I've tried this, though it shouldn't need it.
Clearly that button in MediaMonkey is just bringing up the generic Google Assistant prompt and not a special "in context" version that is just listening for what you say so that it can basically speech-to-text it and put that into a search box for the app. While I would hope by now Google would have several methods for this in the Android language where you can pass context (in language) from the call to assistant and that feature different returns types depending on what you need (i.e. String TextSpeechFromAssistant() ). If that was the case they could easily have a search function in the Android Auto view of MMA that searches just like you do when using it on your phone alone, but grabs your input from the speech Assistant hears instead of your keyboard. Heck, you can essentially already do this in non-Android Auto MMA by hitting the microphone button on the keyboard.
While it is possible that Google Assistant has this functionality and that MMA is simply not implementing it properly/making use of it (or that they are and there's simply something wrong with my Android Auto setup in particular), I'm more willing to suspect that the calls to Assistant in Android Auto supported apps are heavily restricted/basic due to limitations imposed by Google in the Android language.
All-in-all, it would be really nice if the letter search (and all list searches for that matter) had more entries, or the voice search worked... well, at all. My most used playlist is one entry short of making it to the restricted list so I have to browse through E to get to it instead and can't start it from the Playlist section directly. If I feel like listening to a certain Artist, Track, Genre, etc, I better pray its within that entry limit. If not, like you said its litterally inaccessible unless I pull out my phone, which is dumb because that's way less convenient and safe then if the Auto interface was just more usable
I get wanting to give themselves as little liability as possible, but the only option before AA and CarPlay was to pick music from your phone directly, unless your car could read the files on your android device correctly. But let's be honest, most these days use a streaming app and dont store local media, therefore most likely using it via bluetooth and therefore choosing songs through their phone except when skipping. I'm willing to bet (and admit for myself in my old car without AA) that people were using their phones to pick more specific tracks and not simply saying "Well this is unsafe so I can't hear that song". All that being said, I think even a fully unrestricted version of AA is already way safer than fumbling with your phone in your car, so I feel like there should be an option to turn off the limitations even if you have to agree to something to do so. But we know that's never gonna happen in a million years. All we can do is pray they drastically improve voice search.
[quote=aag post_id=453377 time=1544378289 user_id=55563]
It seems that when navigation uses "Search by letter" mode, the resulting list is limited to 12 entries when driving. Not sure if it's AA/Google, or MMA limitation. In either case, the list presented includes 6 entries forward, and 6 entries back, so for example, when searching for 'S', there would be 6 entries for 'S', and 6 entries for 'R', and maybe 'Q'.
Would it be possible to always present the relevant letter only, and maybe (Google gods allowing), present the entire list for that letter? Because the voice search is close to useless, currently some music may be inaccessible while driving.
[/quote]
I believe this is an Android Auto limitation that it automatically applies to ListViews within apps while moving. Technically, it probably could be circumvented but it would require purposely awkward and less efficient programming from the dev's and could land them in hot water if anyone at google noticed and cared to do something about it. Potentially could be a legal issue in terms of liability.
Given that MMA is already a tad less prioritized than MM desktop, I'm guessing the Android Auto functionality is decently down the pipeline (for example the recentish change to album art music on Android Auto broke the display of said art in MMA while in AA mode and I'm curious to see how long it will be before a fix; though, I did just start using it with Android Auto so I could be wrong and they care more about it then I think (even if they don't its understandable because the people using the app with Android Auto is definitely a small part of their userbase).
What would ultimately make this less of an issue is if the voice search was excellent, and as you touched on it ranges from hit and miss to outright sucking. I'm not sure of the specific problems you have with it, but I know the main case I'd like to use it in is when you hit the end of a list and click the "Search By Voice" button. Google assistant should know the context since you're pressing the button from MediaMonkey, but I'll I get is "Sorry I'm offline blah blah blah, you can still play music or blah blah blah" well no shit that's what I'm trying to do, but you're clearly trying to look for the song on Google Play Music instead of the music player I'm already in like would be obvious. Even if I specify "in MediaMonkey (which I shouldn't have to since the button was from that app) it still doesn't work. I'm pretty sure my 4G has been on when I've tried this, though it shouldn't need it.
Clearly that button in MediaMonkey is just bringing up the generic Google Assistant prompt and not a special "in context" version that is just listening for what you say so that it can basically speech-to-text it and put that into a search box for the app. While I would hope by now Google would have several methods for this in the Android language where you can pass context (in language) from the call to assistant and that feature different returns types depending on what you need (i.e. String TextSpeechFromAssistant() ). If that was the case they could easily have a search function in the Android Auto view of MMA that searches just like you do when using it on your phone alone, but grabs your input from the speech Assistant hears instead of your keyboard. Heck, you can essentially already do this in non-Android Auto MMA by hitting the microphone button on the keyboard.
While it is possible that Google Assistant has this functionality and that MMA is simply not implementing it properly/making use of it (or that they are and there's simply something wrong with my Android Auto setup in particular), I'm more willing to suspect that the calls to Assistant in Android Auto supported apps are heavily restricted/basic due to limitations imposed by Google in the Android language.
All-in-all, it would be really nice if the letter search (and all list searches for that matter) had more entries, or the voice search worked... well, at all. My most used playlist is one entry short of making it to the restricted list so I have to browse through E to get to it instead and can't start it from the Playlist section directly. If I feel like listening to a certain Artist, Track, Genre, etc, I better pray its within that entry limit. If not, like you said its litterally inaccessible unless I pull out my phone, which is dumb because that's way less convenient and safe then if the Auto interface was just more usable
I get wanting to give themselves as little liability as possible, but the only option before AA and CarPlay was to pick music from your phone directly, unless your car could read the files on your android device correctly. But let's be honest, most these days use a streaming app and dont store local media, therefore most likely using it via bluetooth and therefore choosing songs through their phone except when skipping. I'm willing to bet (and admit for myself in my old car without AA) that people were using their phones to pick more specific tracks and not simply saying "Well this is unsafe so I can't hear that song". All that being said, I think even a fully unrestricted version of AA is already way safer than fumbling with your phone in your car, so I feel like there should be an option to turn off the limitations even if you have to agree to something to do so. But we know that's never gonna happen in a million years. All we can do is pray they drastically improve voice search.