I have read in posts that .MP3 files sometimes "skip". I realize that .WAV files are larger than .MP3 files. But, if .MP3 files skip, why would the preference not be to use only .WAV files (they are not that much bigger)?
Related Question: If the POILoader files both .MP3 and .WAV files named exactly the same, what does it do?
If a MP3 has "skip" in it I would think it was from the recording or during the recording process. I cant see a skip happen during playback from a file.
Most times a WAV is 5 times bigger than a MP3.
I would also guess the GPS would play the file listed first when a sound.MP3 and sound.WAV are loaded to together.
The major difference between MP3 and WAV audio files is in compression. WAV files are not compressed in any manner while MP3 files use a lossy compression algorithm. Neither are prone to skipping. If you have an MP3 file that skips then you have a digital file that recorded a skip or a faulty / buggy program for playback.
The size difference will depend on the sample rate of the WAV file vs the sample rate and data speed of the MP3 file.
Your GPS isn't concerned, in most cases, with high fidelity sound reproduction. An MP3 file encoded at 64 kB/s with a sample rate of 22.2 KHz should be fine for announcements.
MP3 files will only play on those units having an MP3 player. To get audible alerts (other than the 'BONG') you need to load the WAV driver - SOX.exe.
All 2XX series and 1XXX series units do not have MP3 capability.
The skip issue is when an MP3 compatible unit is playing a selection and an alert is required, the alert plays normally but the selection that was playing skips to the end and the next selection starts.
Those units that are MP3 compliant can use WAV alert sounds as long as they use SOX as well.
My 750 is MP3 compatible. It does NOT skip to the end of the MP3 when an alert is played. It stops playing the MP3, plays the alert and then resumes playing the MP3 where it stopped. This happens even when the alert audio is another MP3 file as well as the bing bing.
My 780 does exactly like you describe for the your 750.
This problem was finally solved with the latest firmware update, your 700 series probably got it sooner.
terms | privacy | contactCopyright © 2006-2020