Losing alert information with POI

inthe128

Its happened again, it seems to happen around upgrading software time, but last week they are all gone away again. I must be missing something simple here but.....

Lets say I am putting distance to a camera position for a warning and then choosing a warning blip or comment. Its all a bit tedious doing this for all the PGPSW camera types, then come the next TT software update it all disappears and I have to start all over again. Is is true that this long winded inputting is the only way to do this and when it comes to software updates can I not save the info somewhere and import it all back in.

The PGPSW database is the important one, all those cameras to redo again and again, you would have thought a global 500m and this blip or voice for everything chosen would be the ticket. I write this after spending 40 minutes doing it all again.
_________________
in the 128

MrT · Posted: Tue Sep 22, 2009 12:11 pm Post subject:

The settings are saved in a file in the map directory called mapsettings.cfg. You can restore this file from a backup if you have one and should make sure you save a copy before an upgrade.

Sometimes this file is copied across during a map upgrade and at other times you need to manually restore it.

If the required format of this file changes due to an upgrade, it can cause a reboot loop if the old format is restored. It seems that if you make a change (such as adding a favourite) whilst operating your TT device under Home, the restored file will be updated to the latest format.
_________________
Drivelux

inthe128 · Posted: Tue Sep 22, 2009 12:55 pm Post subject:

Interesting, thanks for that.

I prefer to give a distance to a POI and then type a word or sentence myself (TT 720) but boy is it pants to to this for every type and speed of camera. I will look to use this file on the next update and see how it goes, but really TT why not do a selection globally.
_________________
in the 128

JockTamsonsBairn · Posted: Tue Sep 22, 2009 11:47 pm Post subject:

If this is something that can be done through "operate my Go" in Home (can you tell this isn't something I've used Laughing

) then it should be possible to reduce the work involved by typing the warnings into a doc or txt file and cutting/pasting them in.
_________________
Jock

TomTom Go 940 LIVE (9.510, Europe v915.5074 on SD & 8.371, WCE v875.3613 on board)

inthe128 · Posted: Wed Sep 23, 2009 9:08 am Post subject:

I have tired that, its a bit quicker for sure although I get no options for typing in words, just the bleeps, maybe this is a Mac OS version thing, so I have done a bleep for everything, but when some new updates arrive then I will do a few as I want them and save the file mentioned and see what happens.
_________________
in the 128

DennisN · Posted: Wed Sep 23, 2009 9:56 am Post subject:

Have you tried our OGG file warnings? They cut out a lot of the effort of setting the audio warnings. Or perhaps make and save your own using Audacity (free download)? I used Audacity (with my Macbook) to record and use grandchildren calling out warnings.
_________________
Dennis

If it tastes good - it's fattening.

Two of them are obesiting!!

inthe128 · Posted: Wed Sep 23, 2009 11:38 am Post subject:

I have Dennis and had no problems on the UK side, but maybe its me the KPH euro ones are not as good/loud and do not seem to cover all the different types of camera. However to make my own would cut out losing them every time, so it might be worth making a few and see how I get on. The UK ones are of no interest to me anymore, so its euro or nothing

Too mark a range of POI and give them 500m and a brief spoken warning and bobs yer uncle.
_________________
in the 128

GerryC · Posted: Wed Sep 23, 2009 11:47 am Post subject:

As an alternative, you can get Kate etc to speak the name of the POI category as part of the alert. This does mean renaming the ov2 and bmp files but a quick batch file can sort that out in a double-click.

Currently, I have Kate saying eg "camera, 30 miles per hour, 300 yards" after renaming the 30mph file to "camera!_30_mph.ov2". I haven't tried it with the EUR files but suspect that 'kmh' or 'kph' will expand likewise.

It also gets around the problem of directions and warnings being at different volumes. Mad

_________________
Gerry
TomTom730T
Cameralert for Android
Brodit ProClip mount

PaulB2005 · Posted: Wed Sep 23, 2009 2:57 pm Post subject:

Oldboy · Posted: Wed Sep 23, 2009 3:31 pm Post subject:

GerryC · Posted: Wed Sep 23, 2009 4:10 pm Post subject:

As Oldboy said, I'm using the "brief spoken warning" option. The ! is just for emphasis - it makes the TTS say it as a single word and not try to say it as part of the sentence. I'm still experimenting at present.

I'm not sure about using it with the voice off as I either set a route or don't. No route = no directions.
_________________
Gerry
TomTom730T
Cameralert for Android
Brodit ProClip mount

inthe128 · Posted: Wed Sep 23, 2009 4:16 pm Post subject:

Well I am having fun with a text to speech converter, Audacity and dumping it all in the sounds folder, thats working very well after boosting the levels in Audacity.
_________________
in the 128

Calomax · Posted: Wed Sep 23, 2009 8:35 pm Post subject:

inthe128 · Posted: Wed Sep 23, 2009 8:49 pm Post subject:

Yes there is an option to type in words, works okay although putting 2 empty spaces between words cab help it sound more normal
_________________
in the 128

mikealder · Posted: Wed Sep 23, 2009 8:57 pm Post subject:

Also try using some punctuation in the typed sentence, semi colon or comma can make a big difference when messing around with how the device actually reads instructions out, the Loquendo web site contains plenty of information on what punctuation is actually understood by the device - Mike

	PocketGPS
	Web