TomTomGo POI Sound Patcher
UPDATED 22 June 2005 - Added the ability to build voice files too...
UPDATED 19 June 2005 - After a chat with lutz, I've removed the selection of the version of the data file. It wasn't really needed. However the user needs to be aware that the resultant data file will only work on the system the source data file came from - ie don't try to use a v4.42 data.chk file on a v5.1 firmware system
The TTG POI Sound Patcher allows you to change the sounds associated with POI (Point of Interest) entries.
It should all be pretty self explainatory - Start at 1 and go through to 4 - easy huh?
Things to be aware of:
1. Error checking... ooh don't make mistakes ... seriously this is a quick and dirty app - if there's enough interest I'll sort stuff out.
2. Click the name of the sound file to change. At startup the names will have a red background, when they have a filename/path the background changes to yellow
3. The output file will be in the same folder as your selected input file, the file name will be "new_ " followed by the original filename eg if the source file was data.chk the new file will be called new_data.chk
4. If you leave an entry blank then the original sound is used instead, so for example if you only wanted to replace Beep 1 then only supply a filename/path for Beep 1
5. If 'A' is a voice sound file, don't use 'D' (generate file) use 'E' (extract voice). I can't check that the non-english voices extract correctly since I don't speak any foreign languages enough to be sure. I could probably work out the 100,200 etc, but that's about it.
6. 'B' really determines which sound bank in the data.chk file you are changing, if this option is checked then sound bank 1 is changed, otherwise it's sound bank 2
7. You can only extract voices, to recompile them use viftool
8. If POI Sound Patcher doesn't recognise the data.chk file as a known version, it will tell you how many modules are in the file, and warn you that the results may not be correct. You can decide to proceed or not. If you proceed it will attempt to generate a useable file that you can test. If this works please let me know the device that the file came from and what module count POI Sound Patcher reported and I will add it to the next release as a known type.
9. Since the TomTom devices use OGG sound files you will need to convert them, you can download tools for this from vorbis.com or you can use oggdropXPd which allows drag and drop conversion. TomTom Go expects sound files to be 22050Hz, 32-bit or 16 bit, Mono - iirc TT mobile devices expect 16000Hz sounds.
10. If you try and insert a file that's too big (for example a 200kb file), then the application will tell you it's too big and then abort the process.
11. You can build or rebuild voices using the Build Voice button (F) You MUST provide ALL the files, named as per a voice extraction. Simply click the Build Voice button and select the folder that the ogg files are in. The application will check that all the files are there, and if they are, will generate myvoice.chk file in the same folder as the OGG files. You will then need to copy this file to your TTG and rename it as (for example) data98.chk.
Thanks to lutz for posting the excel macro on which this is based.
There are NO issues with the new version of the OS for the TTG (5.2). Download here and here are some sample oggs for your poi warnings. Here's a voice I put together too.
Includes support for NON TTG devices - however I CAN NOT test if this works so please let me know if it works on non TTG devices (eg TomTom Mobile). POI Soundpatcher has been confirmed to be working with TTN5 (keep the "YES, my device is a TomTom Go" checked)
0.3.12 - Added 5.2 as a known version, added the ability to assemble voices too
0.3.11 - removed debug output
0.3.10 - added 'special' feature, and ability to 'have a go' if the file is not a recognised one.