Ovi Maps Extra Features - Now with voice guidance (early development) - Page 12 - maemo.org

GEONXT | # 111 | 2011-01-17, 11:04 | Report

This sounds great guys well done! just wondering when if at all is someone going to add this to the repo so its easy for anyone to download?

The Following 2 Users Say Thank You to GEONXT For This Useful Post:
elie-7, Wikiwide

travla | # 112 | 2011-01-17, 11:55 | Report

Hi guys,
I've been following this thread for a few days, could one of you please summarise which index file should be used if we want to try navigation beta with ovi maps, and what other changes we need to do to support voice navigation?

I know this is most likely in the thread, but there seems to be several versions of the index file attached to different posts and more than one approach to voice navigaion.

The Following 3 Users Say Thank You to travla For This Useful Post:
bunanson, elie-7, Wikiwide

CormacB | # 113 | 2011-01-17, 13:53 | Report

I think calling it "beta" was a bit premature. I would not recommend trying this stuff yet unless you are a developer.

The Following 4 Users Say Thank You to CormacB For This Useful Post:
OVK, slender, travla, Wikiwide

travla | # 114 | 2011-01-17, 14:00 | Report

Originally Posted by CormacB View Post

I think calling it "beta" was a bit premature. I would not recommend trying this stuff yet unless you are a developer.

Fair enough, I've only recently befun using Ovi Maps on my N900, and it is so frustrating not having real guidance (or even auto route re-calc!).

Thanks to all contributors, I, like many others, am looking forward to trying this out when it is mature enough.

The Following 2 Users Say Thank You to travla For This Useful Post:
cheve, Wikiwide

Blaizzen | # 115 | 2011-01-17, 14:31 | Report

Originally Posted by CormacB View Post

I think calling it "beta" was a bit premature. I would not recommend trying this stuff yet unless you are a developer.

good point... guess I got a little too excited

Fixed

I tried a different method to get voice navigation (since I couldn't figure out the xml parser or get it to work

). So inside the "medos\i18n" folder is all the localized settings, phrases etc. I noticed you used getDescription before to get the direction (which was genius, didn't even know it was there

). I decided to add a .sound to the ends of the important directions and link them straight to the sound file. I had a quick look at other languages and they all seem to have the same structure (ie same sound file names for the same directions). So i basically added this to the end of the locale.js file:

Code:

"nokia.maps.pfw.action.changehighway.sound”:”:g5man_006”,
"nokia.maps.pfw.action.changehighway.sound.street”:”:g5man_006",
"nokia.maps.pfw.action.continuehighway.sound”:”:g5man_008”,
"nokia.maps.pfw.action.continuehighway.sound.street”:”:g5man_008",
"nokia.maps.pfw.action.end.sound”:”:g5ann_001",
"nokia.maps.pfw.action.end.sound.street”:”:g5ann_001",
"nokia.maps.pfw.action.enterhighway.sound”:”:g5man_005",
"nokia.maps.pfw.action.enterhighway.sound.street”:”:g5man_005”,
"nokia.maps.pfw.action.enterhighwayfromleft.sound”:”:g5man_005e|from the left",
"nokia.maps.pfw.action.enterhighwayfromleft.sound.street”:”:g5man_005e|{0} from the left",
"nokia.maps.pfw.action.enterhighwayfromright.sound”:”:g5man_005e|from the right",
"nokia.maps.pfw.action.enterhighwayfromright.sound.street”:”:g5man_005e|{0} from the right",
"nokia.maps.pfw.action.ferry.sound”:”:g5serv_004",
"nokia.maps.pfw.action.ferry.sound.street”:”:g5serv_004",
"nokia.maps.pfw.action.junction.sound”:”:at the junction",
"nokia.maps.pfw.action.junction.sound.street”:”:at the junction",
"nokia.maps.pfw.action.leavehighway.sound”:”:g5ext_000”,
"nokia.maps.pfw.action.leavehighway.sound.street”:”:g5ext_000|{1} to {0}",
"nokia.maps.pfw.action.noaction.sound”:”:g5man_001e”,
"nokia.maps.pfw.action.noaction.sound.street”:”:g5man_001e|on",
"nokia.maps.pfw.action.passjunction.sound”:”:pass the junction",
"nokia.maps.pfw.action.passjunction.sound.street”:”:pass the junction",
"nokia.maps.pfw.action.roundabout.sound”:”:g5mod_005",
"nokia.maps.pfw.action.roundabout.sound.street”:”:g5mod_005",
"nokia.maps.pfw.action.stopover.sound”:”:you have reached a waypoint",
"nokia.maps.pfw.action.stopover.sound.street”:”:you have reached a waypoint",
"nokia.maps.pfw.action.undefined.sound”:”:start your journey",
"nokia.maps.pfw.action.undefined.sound.street”:”:start your journey on",
"nokia.maps.pfw.action.uturn.sound”:”:g5man_004”,
"nokia.maps.pfw.action.uturn.sound.street":":g5man_004|on",
"nokia.maps.pfw.maneuver.joiner.sound”:”:and",
"nokia.maps.pfw.turn.heavyleft.sound”:”:g5tul_004",
"nokia.maps.pfw.turn.heavyleft.sound.street”:”:g5tul_004|onto",
"nokia.maps.pfw.turn.heavyright.sound”:”:g5tur_004",
"nokia.maps.pfw.turn.heavyright.sound.street”:”:g5tur_004|onto",
"nokia.maps.pfw.turn.keepleft.sound”:”:g5tul_001",
"nokia.maps.pfw.turn.keepleft.sound.street”:”:g5tul_001|onto",
"nokia.maps.pfw.turn.keepmiddle.sound”:”:g5man_009”,
"nokia.maps.pfw.turn.keepmiddle.sound.street”:”:g5man_009|onto",
"nokia.maps.pfw.turn.keepright.sound”:”:g5tur_001",
"nokia.maps.pfw.turn.keepright.sound.street”:”:g5tur_001|onto",
"nokia.maps.pfw.turn.lightleft.sound”:”:g5tul_002",
"nokia.maps.pfw.turn.lightleft.sound.street”:”:g5tul_002|onto",
"nokia.maps.pfw.turn.lightright.sound”:”:g5tur_002",
"nokia.maps.pfw.turn.lightright.sound.street”:”:g5tur_002|onto",
"nokia.maps.pfw.turn.noturn.sound”:”:g5man_001”,
"nokia.maps.pfw.turn.noturn.sound.street”:”:g5man_001|onto",
"nokia.maps.pfw.turn.quiteleft.sound”:”:g5tul_003",
"nokia.maps.pfw.turn.quiteleft.sound.street”:”:g5tul_003|onto",
"nokia.maps.pfw.turn.quiteright.sound”:”:g5tur_003",
"nokia.maps.pfw.turn.quiteright.sound.street”:”:g5tur_003|onto",
"nokia.maps.pfw.turn.return.sound”:”:return",
"nokia.maps.pfw.turn.return.sound.street”:”:return onto",
"nokia.maps.pfw.turn.roundabout1.sound”:”:g5ext_001”,
"nokia.maps.pfw.turn.roundabout1.sound.street”:”:g5ext_001|onto",
"nokia.maps.pfw.turn.roundabout10.sound”:”:g5ext_010”,
"nokia.maps.pfw.turn.roundabout10.sound.street”:”:g5ext_010|onto",
"nokia.maps.pfw.turn.roundabout11.sound”:”:take the eleventh exit",
"nokia.maps.pfw.turn.roundabout11.sound.street”:”:take the eleventh exit onto",
"nokia.maps.pfw.turn.roundabout12.sound”:”:take the twelfth exit",
"nokia.maps.pfw.turn.roundabout12.sound.street”:”:take the twelfth exit onto",
"nokia.maps.pfw.turn.roundabout2.sound”:”:g5ext_002”,
"nokia.maps.pfw.turn.roundabout2.sound.street”:”:g5ext_002|onto",
"nokia.maps.pfw.turn.roundabout3.sound”:”:g5ext_003”,
"nokia.maps.pfw.turn.roundabout3.sound.street”:”:g5ext_003|onto",
"nokia.maps.pfw.turn.roundabout4.sound”:”:g5ext_004”,
"nokia.maps.pfw.turn.roundabout4.sound.street”:”:g5ext_004|onto",
"nokia.maps.pfw.turn.roundabout5.sound”:”:g5ext_005”,
"nokia.maps.pfw.turn.roundabout5.sound.street”:”:g5ext_005|onto",
"nokia.maps.pfw.turn.roundabout6.sound”:”:g5ext_006”,
"nokia.maps.pfw.turn.roundabout6.sound.street”:”:g5ext_006|onto",
"nokia.maps.pfw.turn.roundabout7.sound”:”:g5ext_007”,
"nokia.maps.pfw.turn.roundabout7.sound.street”:”:g5ext_007|onto",
"nokia.maps.pfw.turn.roundabout8.sound”:”:g5ext_008”,
"nokia.maps.pfw.turn.roundabout8.sound.street”:”:g5ext_008|onto",
"nokia.maps.pfw.turn.roundabout9.sound”:”:g5ext_009”,
"nokia.maps.pfw.turn.roundabout9.sound.street”:”:g5ext_009|onto",
"nokia.maps.pfw.unit.kilometer.sound”:”:g5unt_004",
"nokia.maps.pfw.unit.mile.sound”:”:g5unt_008",
"nokia.maps.pfw.unit.yard.sound”:”:g5unt_006"

Now it will substitute the wav sound files instead of saying the phrases, and it seems to work fine kinda. This needs jhb's python server to run though, so its not totally dependent on html/javascript.

In terms of a usable ovi maps with guidance, not sure when it will be released (if ever). But personally I'll try share any code that works well enough just for testing purposes, and I assume others will be doing the same

The Following 6 Users Say Thank You to Blaizzen For This Useful Post:
cheve, OVK, slender, TomJ, travla, Wikiwide

Android_808 | # 116 | 2011-01-17, 19:24 | Report

I was thinking that the .desktop file could be modified to be a script to start the python server and then run Ovi Maps. When Maps closes it should then automatically close the python app.

In relation to the other languages, your one step ahead of me there. My reason for looking into parsing the config.xml was in case there were additional files used or sentence structure for a given language. Kind of like "Take the 6th exit at the roundabout" instead of "At the roundabout, take the 6th exit", one language may require action before place, then next place before action. Only way to tell would be to compare config.xml's.

Blaizzen: with your new locale.js definitions we could pretty much drop the config.xml parser (as long as there are no issue like above). We could take the general logic from that, in terms of when each should be said, what we should do if the next maneuver is within x distance etc, and put it as a logic structure in the main javascript code. Maybe putting it in updatePosition rather than its current position?

Edit: One problem with locale.js, there's one for each locale. It would mean maintaining a copy for every locale.

Last edited by Android_808; 2011-01-17 at 21:34.

The Following 4 Users Say Thank You to Android_808 For This Useful Post:
Blaizzen, mike_shenoda, OVK, Wikiwide

Android_808 | # 117 | 2011-01-18, 20:03 | Report

jhb: any idea how to reduce time between wav file playback?

Found the following but it uses mplayer. Don't fancy pulling in lots of extra dependancies. Maybe mpd or something?

Code:

$ mkfifo audiofifo
$ aplay -t raw -c 2 -f S16_LE -r 44100 audiofifo &
$ mplayer -ao pcm:nowaveheader:file=audiofifo <audio files>

The Following 2 Users Say Thank You to Android_808 For This Useful Post:
doughboy, Wikiwide

jhb | # 118 | 2011-01-18, 23:46 | Report

Originally Posted by Android_808 View Post

jhb: any idea how to reduce time between wav file playback?

Found the following but it uses mplayer. Don't fancy pulling in lots of extra dependancies. Maybe mpd or something?

Code:

$ mkfifo audiofifo
$ aplay -t raw -c 2 -f S16_LE -r 44100 audiofifo &
$ mplayer -ao pcm:nowaveheader:file=audiofifo <audio files>

for just playing e.g. wav files this might do:

Code:

sox g5ann_001 g5con_001 -t wav - | aplay

Somehow the delays from aplay are only an issue on my laptop, not on the n900.

I still haven't had a close look at the xml file and its parsing - but from what I get the problem at the moment is triggering the commands? E.g. do we have enough events/info to trigger the commands at the right place and right time? E.g. proper distance, knowing we are still on the route, maybe even triggering recalculation?

Last edited by jhb; 2011-01-18 at 23:51.

The Following User Says Thank You to jhb For This Useful Post:
Wikiwide

Blaizzen | # 119 | 2011-01-19, 03:04 | Report

Originally Posted by Android_808 View Post

I was thinking that the .desktop file could be modified to be a script to start the python server and then run Ovi Maps. When Maps closes it should then automatically close the python app.

In relation to the other languages, your one step ahead of me there. My reason for looking into parsing the config.xml was in case there were additional files used or sentence structure for a given language. Kind of like "Take the 6th exit at the roundabout" instead of "At the roundabout, take the 6th exit", one language may require action before place, then next place before action. Only way to tell would be to compare config.xml's.

Blaizzen: with your new locale.js definitions we could pretty much drop the config.xml parser (as long as there are no issue like above). We could take the general logic from that, in terms of when each should be said, what we should do if the next maneuver is within x distance etc, and put it as a logic structure in the main javascript code. Maybe putting it in updatePosition rather than its current position?

Edit: One problem with locale.js, there's one for each locale. It would mean maintaining a copy for every locale.

I overcame the issue with the different locales by making the array separate. One issue i found though is since ovi voice navigation isn't meant to have spoken street names, there is no sound file for "onto" (and a few others i forgot), so at the moment "onto" is spoken in English meaning non-english speaking users will need to modify the array to say their local equivalent.

I added a bit to say the next turn early after we do a turn (so it kinda prepares us eg In 1.6 km turn right onto blaa street) however the distance sounds wrong, so i need to fix that. But with the distance and units, they are now sound files where possible. Kilometers and miles are sound files, as well as 1 to 10 and 50, 100, 150 ... 900. So if the distance is one of those it will play the sound instead

.

Lastly implementing the python server in the desktop file would be good, i tried to make the server close when i send a command (eg exitServer) but it never closed

maybe jhb if you could add that in please.

If i get the above issues solved, I might release something for others to try tomorrow/friday. I've been using it for navigation for a few days now and its pretty good. Much more advanced than anything i could have even dreamt of, all thanks to all the developers here. So thanks

Last edited by Blaizzen; 2011-01-19 at 03:07.

The Following 6 Users Say Thank You to Blaizzen For This Useful Post:
doughboy, mscion, OVK, Tiboric, travla, Wikiwide

Bingley Joe | # 120 | 2011-01-19, 06:51 | Report

This looks amazing!

I'd really love to give it a try, so just to confirm -- are the links to the most recent versions of the relevant downloads all in the first post or do I need to scour the thread?

The Following User Says Thank You to Bingley Joe For This Useful Post:
Wikiwide