| Versions |
  |
|
| Author |
 Topic  |
|
userderek
21 Posts |
 Posted - 26 août 2007 : 19:53:38
|
First, thank you for the Rock. I want to share my experience:
1. Yes, you need the Belgium updater & ctype. But if you are behind a fire wall that prevents access to foreign sites and you try to apply the updater, the update will fail without telling you. You would think that it was a successful update when in fact it was not. I tried to do this at work and later discovered (through the Updater's error log) that the updater was unable to download files on demand as you install it. I tried to update again at home. It worked without FFUI error.
2. I found 2 bugs in the Rock icons. I assign the bluetooth button to "Route parameter". When I click on the bluetooth button, then click on "Parameters" and change the Route from one setting to another (i.e. from short to fast, etc.), then if I click on "Back to map" button at the top, the new route is not recalculated. However, if I instead click on the Back Arrow to go back, it will recalculate automatically. In other word, the "Back to map" button only goes back to the map and does not initiate recalculation of the new route based on the new setting.
3. Second bug is that the POI Search does not initiate search during the first time it is used. Instead it takes you back to the Mio's Search screen. To duplicate this phenomenon, assign POI Search to the bluetooth button (or any button), exit MioMap completely (so that all internal memory is clear), then restart MioMap application, then go to Map, click on the bluetooth button, which should bring up the POI Search screen. Click on "Search" button at the bottom left, type in anything you want to search (I did Fedex), then select a POI. At this point, you are prompted the information of the selected POI, click "OK" button at the bottom left. At this point, under normal condition, MioMap should give you options to route to, add via, etc. But instead it brings you back to the search/home screen. If you repeat this whole POI search process again (do not exit MioMap though), it will work as expected. It only fails to work as expected during first time.
I hope this helps. |
Edited by - userderek on 27 août 2007 01:23:38 |
 |
|
|
therock
USA
371 Posts |
Posted - 26 août 2007 : 21:55:35
|
quote:
Originally posted by userderek
First, thank you for the Rock. I want to share my experience:
1. If you need the Belgium updater & ctype. But if you are behind a fire wall (esp. company fire wall) and you try to apply the updater, the update will fail without telling you. You would think that it was a successful update when in fact it was not. I tried to do this at work and later discovered (through error log) that the updater was unable to download files on demand as you install it. I tried to update again at home. It worked without FFUI error.
I guess the above applies to the type of firewall and the configuration. Good info though. I work for a major fortune 500 international company with firewall but it went ok on a friends c520 yesterday.
quote:
2. I found 2 bugs in the Rock icons. I assign the bluetooth button to "Route parameter". When I click on the bluetooth button, then click on "Parameters" and change the Route from one setting to another (i.e. from short to fast, etc.), then if I click on "Back to map" button at the top, the new route is not recalculated. However, if I instead click on the Back Arrow to go back, it will recalculate automatically. In other word, the "Back to map" button only goes back to the map and does not initiate recalculation of the new route based on the new setting.
I'll get on it and the poi thing. Ah, the joys of typing.
I hope this helps.= Yes it will. Thanks for giving her the workout.
[/quote] |
Edited by - therock on 26 août 2007 22:01:10 |
|
|
|
Kustom66
USA
31 Posts |
Posted - 26 août 2007 : 22:49:02
|
thepiecesfit,
Thank you very much for posting your "v_tts_nu_eng_us_f2.zip" file with the silent sound ogg file in place of the "Route Recalculation" voice file. It works perfectly for me.
Another change I made was to open the "info" file in the same zip and change "tts_rate=45" to "tts_rate=55". The higher the number the faster the voice says it commands, and I find that speeding Samantha up makes her sound more natural and helps get the commands out of her mouth in a more timely manner. I'm going to experiment with higher values, but only one or two higher as I originally tried "tts_rate=60" and it was a tad too fast.
Another thing I tried but was unsuccessful at, was going into the "config" folder in the same "v_tts_nu_eng_us_f2.zip" and making changes in the "commands.csv" file. It appears that is where you can make sweeping changes in what the voices say - like changing the words, or the distances they are said at. I tried changing the "pause" value between phrases ("Bear left (pause)then (pause) turn right"), but whenever I re-zipped, loaded and tried running the modified program, I would get an error message as MioMap loaded saying "Fatal Error" and the unit would reboot. I tried many different things and I'm not sure if I'm not re-zipping properly or what. If someone could conquer commands.csv it could be a great way to personalize what your voice is saying and when. |
|
|
|
therock
USA
371 Posts |
Posted - 27 août 2007 : 03:03:25
|
@ userderek,
I see what you are talking about in making route parameter changes and using the back to map button vs. the back arrow or fit to screen button in the route info's screen.
I would not call it a bug as much as a misunderstanding of the buttons function. Like you I expected it would recalculate. After looking at the differences in the back arrow and back to map I see there is a script running on the back arrow, "run sc_advnav_back_run_recalc_yes_orig", this is not in the back to map button's instructions.
So the back to map should be treated as a return without saving changes?
The back arrow, and the route info's screen fit-to-screen button will recalculate as you say.
The back to map was generated across several menus at once for convenience, for the user as well as the person adding it. Although it may have been taken for granted it would.
Nice Catch! Thank You! Now we know! |
|
|
|
therock
USA
371 Posts |
Posted - 27 août 2007 : 03:24:56
|
@ userderek,
On the POI Search thing. I see the differences. I'm not sure if this is a button mod thing or a MIO characteristic . I did find if I tap the line of the POI I want it does OK.
To test, one would have to revert back to the original skin. Maybe you have already. I'm too lazy right now.
Either way you are pointing out some good points, aka, tips and tricks. Thank You! |
|
|
|
userderek
21 Posts |
Posted - 27 août 2007 : 04:12:22
|
To TheRock: here is the deal - I am not going to call it a bug. But you still have to fix those 2 things j/k. Seriouly, it is a feature and not a bug. Whether or not a feature is desirable, it depends on who the user is. Actually, I kind of like the idea of having both the back arrow and the "back to map" on the same page so that I have more options as long as I understand what it does. But one thing is that after you click on the "back to map" button, the new setting does get saved, but the (old) route stays the same. In other words, the setting and the route are not on the same page. That will confuse users who are not aware of this. So, the "back to map" button still needs to revert change.
To Kustom66: I was playing with the "commands.csv" file a while back and successfully configure the direction prompts to my needs. I was just too busy & too lazy to share it. But here it is. In commands.csv, one can cut down the number of prompts such that it is not annoying. Secondly, some people rightly complaint that C520 sometimes declares "you have reached your destination" too prematurely, making it off by many feet away. One can, to some degree, fix this by modifying commands.csv file. The way to do it is to use the logic "near 0" and not "more than 0". The logic NEAR means that when the distance is near 0 ft/meter, announce destination reached. When MORE is used, it means that when the distance to destination is more than 0, make the announcement. The problem with MORE is that it is too vague - it is true that 5ft away from the destination is more than 0. But it is also true that 45ft away is more than 0. When MioMap announces destination reached at 45ft away, that is way off obviously. With NEAR condition, it seems to be more accurate according to my experience. You can also increase the number from 0 to 10 so that announcement is made when it comes close to 10 instead of 0, which may be too late. You gotta play with it to fit your personal tolerance. Here is a partial cut & paste of my command.cvs file. The first line is before the change & the second line is after:
,"0[more,near,set_4]*arrived_goal","You have reached your destination"...
,"1[near,set_4]*arrived_goal","You have reached your destination."...
You can also play with the distance value like changing from 0 to 10:
,"0[X=1,more,near]","*take_next_then"
,"10[X=1,more,near]","*take_next_then"
I also feel that some of the command is unnecessary, which makes MioMap too verbal. You can remove a few of them and MioMap will prompt you less often. But you have to be careful with that because it is all logic. Missing a statement may cause other logic never become true. As a result, you may not get the prompt that you are supposed to get.
Have fun! |
|
|
|
therock
USA
371 Posts |
Posted - 27 août 2007 : 04:45:36
|
Good one on the arrival destination distance tweak.
I'll be mulling over the BTM button thing. Resting. I want a full night mode right now. Where the menus are darker when map is in night mode.
Have you seen the voice command speed up? I love it. |
|
|
|
userderek
21 Posts |
Posted - 27 août 2007 : 05:57:11
|
>>Have you seen the voice command speed up?
Yes, thanks. It is cool. Also in the same file, I changed 2 more things. I set testsound="Hello [my name]". I replaced "route recalculation" with "recalculate" to make it shorter, which means less cpu time wasted for not so important activity & more cpu time available for more important activity, such as actual recalculation of the route. You know there are only 2 more changes on my wish list. One is to get rid of the stuttering. I feel that the original Samantha TTS is bad. I personally don't think it is the ROM as some suggested. If you switch out Samatha voice to some other voice (don't have to be TTS), stuttering is gone. So, I am tempting to conclude that Samantha TTS is not perfect or corrupted. Well, Mio Tech would prefer to call it a feature because it does build some characteristics into Samantha. The other wish is that MioMap routing algorithm is still not as good as TomTom's although the later also uses the same map. I think that if Mio Tech makes its algorithm open source, this problem will get fixed by the community and the company will benefit from such free fix. So far, the company can't seem to be able to fix this problem for the past 2 years. Case in point, Sun Microsystems was able to rapidly develop Java to compete with Microsoft's C++ by opening up Java source codes to the community. Another case in point, "The Rock" skin as well as other mods posted on this forum are great enhancements. Too bad, Mio Tech may not be able to benefit from any of this. The company could have incorporated these improvements through open source distribution. I hope Mio Tech will run into this post/suggestion. Any opinion? |
Edited by - userderek on 27 août 2007 06:07:02 |
|
|
|
thepiecesfit
31 Posts |
Posted - 27 août 2007 : 07:32:42
|
Those commands should help.. MY biggest issue with the commands is the "THEN" commands. Sometimes it unnecessarily says , turn down this street then down this street then keep left which sometimes overlaps the command to turn onto a street! At times it is overwhelming and unnecessarily confusing. I would prefer to be reminded to turn onto a street more than once, instead of having all the "then" commands thrown at me at once. Anyone agree ?
userderek if you have any ideas on how to kill most of the "then" commands im all ears. It would be more preferable to hear the next turn announced more over something that just throws 3 different turns at me.
Update: I erased the lines containing [then3 and lines that related to leaving the highway where it had references to then 3 I changed then3 to then2. Emulation run seems okay , I am only getting turn here then into another street. It doesnt try to sneak a third then in by me .
quote:
Originally posted by userderek
To TheRock: here is the deal - I am not going to call it a bug. But you still have to fix those 2 things j/k. Seriouly, it is a feature and not a bug. Whether or not a feature is desirable, it depends on who the user is. Actually, I kind of like the idea of having both the back arrow and the "back to map" on the same page so that I have more options as long as I understand what it does. But one thing is that after you click on the "back to map" button, the new setting does get saved, but the (old) route stays the same. In other words, the setting and the route are not on the same page. That will confuse users who are not aware of this. So, the "back to map" button still needs to revert change.
To Kustom66: I was playing with the "commands.csv" file a while back and successfully configure the direction prompts to my needs. I was just too busy & too lazy to share it. But here it is. In commands.csv, one can cut down the number of prompts such that it is not annoying. Secondly, some people rightly complaint that C520 sometimes declares "you have reached your destination" too prematurely, making it off by many feet away. One can, to some degree, fix this by modifying commands.csv file. The way to do it is to use the logic "near 0" and not "more than 0". The logic NEAR means that when the distance is near 0 ft/meter, announce destination reached. When MORE is used, it means that when the distance to destination is more than 0, make the announcement. The problem with MORE is that it is too vague - it is true that 5ft away from the destination is more than 0. But it is also true that 45ft away is more than 0. When MioMap announces destination reached at 45ft away, that is way off obviously. With NEAR condition, it seems to be more accurate according to my experience. You can also increase the number from 0 to 10 so that announcement is made when it comes close to 10 instead of 0, which may be too late. You gotta play with it to fit your personal tolerance. Here is a partial cut & paste of my command.cvs file. The first line is before the change & the second line is after:
,"0[more,near,set_4]*arrived_goal","You have reached your destination"...
,"1[near,set_4]*arrived_goal","You have reached your destination."...
You can also play with the distance value like changing from 0 to 10:
,"0[X=1,more,near]","*take_next_then"
,"10[X=1,more,near]","*take_next_then"
I also feel that some of the command is unnecessary, which makes MioMap too verbal. You can remove a few of them and MioMap will prompt you less often. But you have to be careful with that because it is all logic. Missing a statement may cause other logic never become true. As a result, you may not get the prompt that you are supposed to get.
Have fun!
|
Edited by - thepiecesfit on 27 août 2007 22:21:29 |
|
|
|
AKM74
55 Posts |
Posted - 27 août 2007 : 22:29:34
|
thepiecesfit
Can you post actual code example here ?
Also.
Is there any way to make it announce if your destination on the left or on the right? |
Edited by - AKM74 on 27 août 2007 22:31:48 |
|
|
|
Kustom66
USA
31 Posts |
Posted - 27 août 2007 : 23:53:15
|
Hi thepiecesfit,
Your goals with tweaking Samantha's voice in commands.csv seem about the same as mine, except I was also trying to shorten pauses between phrases to speed up her delivery. Once you speed up Samantha's voice rate in the "info" file, those pauses become proportionally longer. Generally there is a pause with the value of 50 (milliseconds?), the word "then", then another pause of 50. Maybe if the word "then" was eliminated entirely along with one of the pauses and the other pause left in, it might sound perfect.
My problem was that when I made changes to commands.csv, MioMap just wouldn't load for me, so I suspect I am not re-zipping the file correctly or something like that.
If you get a really neat version of commands.csv worked up, it would be greatly appreciated if you posted the entire v_tts_nu_eng_us_f2.zip file (with commands.csv in it) for download so I can just drop it into my program and avoid whatever issue is preventing me from doing it.
|
|
|
|
therock
USA
371 Posts |
Posted - 28 août 2007 : 01:36:17
|
I received the power cradle today. Nice!
The good:
* The bigger speaker sound quality is clear, more robust and a bit louder.
* The BEST thing is the Bluetooth sound level matches the map volume level! Hoo Ray! It was very hard to hear at the highest volume level setting with the OE power cradle. I had written this function off. 1 of 2 problems solved. Now to get it to remain paired after re-boot.
* The power connection (Mini USB) is moved to the rear. Ah!
* Allows external antenna connection.
* The GPS slips into place a little easier. The OE cradle took some fumbling sometimes. She now rolls right into place.
* There is a loop that appears to be a stylus clip on the side. Not sure yet.
The Bad: (Very Minor) No wire supplied. I was suprised to see the USB port connection. I expected a hard wire. But I like it. I was hoping to have a hidden hardwire and get the clutter cleaned up. Unless you guys know of another solution, I'm going to get another plug-in adapter and route it out of site. I have an old female plug I will wire up and not have to hack it up and can disconnect it later if need be. I want the original windshield mount and cord ready to grab and go for use in other vehicles.
In case some don't know, you have to keep the power level board used in the plug (From, Input: 10 ~ 24V DC. To, Output: 5V at 2A.) Don't just cut the wire and go straight to 12v DC.
|
Edited by - therock on 28 août 2007 01:38:05 |
|
|
|
AKM74
55 Posts |
Posted - 28 août 2007 : 02:58:02
|
| You mean new cradle not compatable with original car power adaptor ? |
|
|
|
therock
USA
371 Posts |
Posted - 28 août 2007 : 03:27:13
|
Power Cradle Picture. Excuse the dust, nothing hides from a camera. It's in a full size truck and looks larger in proportion in the image than live.
The cradle attaches to the accessory swing arm with the 4-slot & hook MIO factory style. It may mount a little more forward than the OE cradle but not much. The swing arm is nice for having the passenger do the map browsing while the driver keeps eyes forward.
The loop on the side is wire guide, not the stylus holder I presumed. The USB may appear not to be pushed in all the way but it is. We all know the OE adapter's mini USB is connector is longer to allow a full connection through the OE's cradle slot.
I used a really cheap-o FM modulator (before & after) and WoW. It's really nice going through the trucks Bose Premium sound system. The poor bluetooth sound quality is present in all situations without the power cradle.
It outputs, TTS and Bluetooth. It's nice to use for checking the voice mail hands free. It likes the FM 107.5 frequency in my area.
A nice bonus in sound quality.
No regrets, this is a "Must-Have, and should ship with every US c520.
I presume all c520's have the same Bluetooth lack in sound quality?
 |
|
|
|
therock
USA
371 Posts |
Posted - 28 août 2007 : 03:31:08
|
quote:
Originally posted by AKM74
You mean new cradle not compatable with original car power adaptor ?
Yes it is for sure. I just imagined it coming with a hard wired connection but the mini USB connection is a better idea. |
|
|
|
Topic |
|
|
|
| This page was generated in 1,28 seconds. |
 |
|
- 
del.icio.us
* Skins for the C320, C520, C720T *
