Though just this morning I was given instructions by TomTom to install 8.010 to fix the voices. I'm installing now and will let everyone know if it actually is fixed.
Joined: 07 Nov 2008 Posts: 29 Location: Massachusetts TomTom 920T
Mon Mar 02, 2009 5:59 pm
Hey all you lucky people that have stuttering issues ... if you can post back whether this update fixes it for you or not, that would be great. I've been waiting months (literally) for this fix before I purchase a 730 or 930, so this is great news if it works.
... 'course Navigon just announced the 7300, so I've got another decision to make.
Joined: 29 Nov 2007 Posts: 123 Location: Ottawa Senators
Mon Mar 02, 2009 6:16 pm
Did the pin reset twice and factory reset as well, but no go. Also all the english language files under the folder 'LoquendoTTS' had files dated on April 2008.
WOW you guys are correct a new firmware - fingers crossed
www.tomtom.com/6141
TomTom FAQ:6141
Here are the direct download links for people that don't use home.
http://download.tomtom.com/sweet/navcore/8.302.gox20.CAB-navcore-GO.cab
http://download.tomtom.com/sweet/navcore/8.302.go530-go730-go930.CAB-navcore-GO.cab
Looking at the included bootloaderversion.txt
I see that it still is suppose to have 5.5015
I hope those of us that tried the x40 will not have problems with running a different bootloader.
Those that tried 8.320 WORK should have the same 5.5015
If you did the x40 8.203 or 8.204 then you will have 5.5106
And if you did the x40 8.310 you will have 5.5112
I need to install 8.302 now and look forward to seeing positive reports for this new firmware this week.
Nope, I let HOME install it over the top of the x40 firmware without any issues........ so far
I did not mean installing the firmware.
I meant I hope having a different bootloader does not cause things to behave differently.
After all the other bootloaders were designed for the x40 not the x20/x30
Why was 8.302 created on Wednesday 25 February 2009-17:33:33 and not released until today?
There are apparently 10829 changes according to release.nfo
8.301 had 285359 and 8.302 has 296188
I don't know anything previous as release.nfo was introduced with 8.301
File differences between a 8.301 install and new 8.302 cab
New release.nfo in the TomTom-Cfg folder
The original antitheftw.bmp in the root
The NEW ttsystem in the root
7.93 MB of changed files if you count the antitheftw.bmp yet we got a 36.1 MB CAB again will a lot of redundant data with TimeStamp changes.
So here is a heads up if you use a custom antitheftw.bmp it will get replaced because TomTom decided to include it in the CAB.
Joined: 16 Jan 2008 Posts: 171 Location: Baltimore
Mon Mar 02, 2009 10:56 pm
BigwigXXX wrote:
Operate my Go does not work within HOME (PC)
I just downloaded the update and for the first time in months Operate My Go does work on macs again. When I clicked on it Home said a file needed to be downloaded which it did and then the function once again worked.
John
I had the opposite happen... Operate My GO has been working fine until the application update today. I downloaded the new emulator file but just get errors trying to use the function.
Joined: 16 Jan 2008 Posts: 171 Location: Baltimore
Tue Mar 03, 2009 12:41 am
Mine functions with both our 920 and 930 after the file downloaded. It crashed the program once but when I relaunched it it did seem to work properly. For me it hasn't functioned for so long I don't really remember the last time it did.
John
I downloaded 8.302, disconnected, did a pin reset, and now I cannot operate my GO 930 from TT Home. I'll find out tomorrow if it fixes the TTS problem. Hopefully, by then, I'll be able to get it to work on TT Home.
The stuttering problem is better than before, but still not fixed. TTS was not a major issue for me, but I've been checking it out lately to see what ya'll have been fussin' about.
I don't know about any other PNDs, but if TTS was important to me, I would not recommend either the GO 730 or GO 930. I may be too picky, but as far as I'm concerned, TomTom's text-to-speech is not ready for prime time.
I have not been able to determine if there is a pattern of names that it cannot handle. So far, it has failed on:
"Bryant Irvin" (cut off all but the "t" in "Bryant")
"White Settlement Road" (cut off the "Wh" in "White")
"Windwood Trail" (cut off the "W" in "Windwood")
"Oakmont Boulevard" (cut off the "Oa" in "Oakmont", but prounounced "Boulevard" without any problems)
However, it handled "State Highway 183 northbound" without a hitch.
Susan, the computer voice I use, also garbles some words......I find it humourous and don't really dwell on it; mind you, I never had the stuttering by her, either.
Have you found all computer voices tend to garble the same words or are some better than others?
Susan, the computer voice I use, also garbles some words......I find it humourous and don't really dwell on it; mind you, I never had the stuttering by her, either.
Have you found all computer voices tend to garble the same words or are some better than others?
I don't know that's the fault of any particular Navcore version. I didn't go back and check but I think I commented on the clipping of some instructions in my review of the 930 back in June of last year when I first bought it. Not a big issue, but I didn't find TT's speech quality quite as good as Garmins.
I didn't find TT's speech quality quite as good as Garmins.
I agree that Garmins TTS Engine is better.
Shooter I do know that the maps do have a shorthand for some of the directions that get replaced before spoken.
But none of those replacements are for things like Bryant or Windwood etc
I am also thinking that it is not a parsing error causing this.
Parsing meaning extracting the map directions and converting to send the directions to the Loquendo TTS Engine.
I think what you are sometimes noticing is that there can be a delay were there is silence for the Oak part for example and you will just hear Mont Boulevard or if there is a longer delay you will hear just Boulevard.
Sounds like there are not enough resources to have the sound played when requested so there is silence but then the rest of it is heard when some resources are freed.
Susan, the computer voice I use, also garbles some words......I find it humourous and don't really dwell on it; mind you, I never had the stuttering by her, either.
Have you found all computer voices tend to garble the same words or are some better than others?
I'll try a different voice tomorrow.
Try Kate.
Susan is normally the worst, as it is the smallest of the 4 TTS voice packages.
I am also thinking that it is not a parsing error causing this.
Parsing meaning extracting the map directions and converting to send the directions to the Loquendo TTS Engine.
I think what you are sometimes noticing is that there can be a delay were there is silence for the Oak part for example and you will just hear Mont Boulevard or if there is a longer delay you will hear just Boulevard.
Sounds like there are not enough resources to have the sound played when requested so there is silence but then the rest of it is heard when some resources are freed.
It sounds to me like an inexperienced radio operator who starts talking before pressing the transmit key. Only it is not consistent.
I tried the "Kate" voice today; it was not any better at pronouncing street names than Susan. Directions for both voices are fine.
Some of the street names were so garbled, that I'm not sure I would have understood if I didn't already know what is was. I would not want to rely soley on my GO 930's TTS capablility, especially in an area I'm not familiar with.
Last edited by Shooter on Fri Mar 06, 2009 4:00 am; edited 1 time in total
Some of the street names were so garbled, that I'm not sure I would have understood I didn't already know what is was. I would not want to rely solely on my GO 930's TTS capability, especially in an area I'm not familiar with.
By any chance have you ever heard a Garmin's TTS Engine?
I don't know if they use different engines for the different classes of models like TomTom does. But my friends Garmin TTS sounded superior to my TomTom's.
Speaking of the different engine used for the different models has anyone heard how a lower end TomTom sounds?
I tried the "Kate" voice today; it was not any better at pronouncing street names than Susan. Directions for both voices are fine.
Some of the street names were so garbled, that I'm not sure I would have understood if I didn't already know what is was. I would not want to rely soley on my GO 930's TTS capablility, especially in an area I'm not familiar with.
Strange, I dont get this much in Europe, and I have complex French names here!
I don't know if they use different engines for the different classes of models like TomTom does. But my friends Garmin TTS sounded superior to my TomTom's.
I have a TT 720 and a Garmin 760 and the Garmin is far far superior in it's pronunciation. It's not even close.
I just tried Kate instead of Susan, and she's just as pathetic!
Both Kate and Susan sound like the "Aquaphibians" on the old 60's marionet shjow "Stingray"
Navigon does some nice things but has its share of problems as well. I am hoping to get back to Tomtom now that the stuttering is finally fixed. I still find I prefer the Tomtom. I only wish they would have a brighter screen because in bright daylight, it is almost impossible to read.
Joined: 27 Nov 2008 Posts: 38 Location: western New York
Sat Mar 07, 2009 1:36 am
Malouff wrote:
jimbir wrote:
I have a 720 and all I'm being offered on TT home is update 8.3
What version do you have installed now?
I have ver. 7.221 installed now. I've downloaded ver 8.32.cab but am reluctant to install it because I've heard it still has the stuttering problem. Do you know if thats true? If I were to upgrade, should it be 8.302 or 8.32?
Well, 8.302 was meant for the 720 to fix the stuttering. 8.32 never was meant for the consumer 720 market. The fact it reduced stuttering was sort of a bonus.
Joined: 27 Nov 2008 Posts: 38 Location: western New York
Sat Mar 07, 2009 1:52 am
dhn wrote:
Well, 8.302 was meant for the 720 to fix the stuttering. 8.32 never was meant for the consumer 720 market. The fact it reduced stuttering was sort of a bonus.
The stuttering problem is better than before, but still not fixed. TTS was not a major issue for me, but I've been checking it out lately to see what ya'll have been fussin' about.
Stuttering is totally fixed for me with no apparent loss of other functionality, so much for those who thought it was a hardware limitation.
The stuttering problem is better than before, but still not fixed. TTS was not a major issue for me, but I've been checking it out lately to see what ya'll have been fussin' about.
Stuttering is totally fixed for me with no apparent loss of other functionality, so much for those who thought it was a hardware limitation.
I am still not 100% sure. What I have noticed that although the audio stuttering is completely gone, I now see some screen stuttering. In area's where there are a lot of turns and instructions, the screen is lagging way behind the instructions. It almost looks like a video stutter at times. It is not nearly as annoying as the verbal stuttering as the map remains readable plus thw screen finally catches up with the commands.
I think these units are really maxed out as far as hardware is concerned. Fixing the stuttering means taking resources away elsewhere. My 920 is finally useable but any more features will require more hardware resources.
I am still not 100% sure. What I have noticed that although the audio stuttering is completely gone, I now see some screen stuttering. In area's where there are a lot of turns and instructions, the screen is lagging way behind the instructions. It almost looks like a video stutter at times. It is not nearly as annoying as the verbal stuttering as the map remains readable plus thw screen finally catches up with the commands.
I think these units are really maxed out as far as hardware is concerned. Fixing the stuttering means taking resources away elsewhere. My 920 is finally useable but any more features will require more hardware resources.
Even with the older fw I noticed screen delay, and I have also witnessed it on models from other makes as well, especially in those conditions.
And we are not engineers here...so who knows exactly what the problem was....could have been a memory leak in their application
The big thing is the stuttering is 100% gone and all of the existing functionality is still present...for those like me that got a 720 under $200 that is an amazing feature set for a rock bottom price.
Also what other features would one want on these units within reason...
I remember many here saying that they couldn't fix the units without turning off options and crippling the devices...seems like tomtom managed a fix afterall.
Joined: 08 Mar 2009 Posts: 23 Location: New Hampshire
Sun Mar 08, 2009 4:26 pm
Mathew J wrote:
Shooter wrote:
The stuttering problem is better than before, but still not fixed. TTS was not a major issue for me, but I've been checking it out lately to see what ya'll have been fussin' about.
Stuttering is totally fixed for me with no apparent loss of other functionality, so much for those who thought it was a hardware limitation.
Didn't you LOSE FM transmitting of instructions with the 8.302 update?
Didn't you LOSE FM transmitting of instructions with the 8.302 update?
My understanding was that this was not from any technical limitation but rather legal....so it is a feature that could be easily enabled, personally it isn't something I care about FWIW.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
