Search Archive

Let the Avic don't bable as much

By paQ · Feb 07, 2009in Hacks/Mods💬 13 posts👁️ 2,278 views
Posted Feb 07, 2009 · 13:17 UTC#1

Has someone figured out a way to let the avic stop given an overload on navigation instructions?

 

"enter the highway in 400 meters"

"enter the highway in 150 meters"

"enter the highway"

 

You'dd almost be expecting:

"you've just entered the highway"

"you are now driving on the highway"

 

What I would like to is that the thing qould just shut up when you don;t need to take any action whilst driving. And only instruct that you should bear right (ONCE!) and take a turn or something.

It now sometimes just is too much.

 

Why bother saying to keep straight on?

Posted Feb 07, 2009 · 16:58 UTC#2

Which voice are you using? I edited the Samantha voice a while back to make her not talk so much, but i've since switched to the male voice and have been wanting to edit that one too. Inside the zip file for the voice there is a commands file, and each spoken instruction has a "minsilence" parameter. This is how much silence, in seconds, must be left inbetween each instruction. Most them are set for 3 or 6 seconds, so i upped them to 10-15 and that cut down the number of instructions pretty good. I'm probably going to do that to the male voice pretty soon, so when I do i'll post it up here.

Posted Feb 07, 2009 · 17:43 UTC#3
Inside the zip file for the voice there is a commands file, and each spoken instruction has a "minsilence" parameter.

 

Where exactly is this file?

Posted Feb 07, 2009 · 17:59 UTC#4
Which voice are you using? I edited the Samantha voice a while back to make her not talk so much, but i've since switched to the male voice and have been wanting to edit that one too. Inside the zip file for the voice there is a commands file, and each spoken instruction has a "minsilence" parameter. This is how much silence, in seconds, must be left inbetween each instruction. Most them are set for 3 or 6 seconds, so i upped them to 10-15 and that cut down the number of instructions pretty good. I'm probably going to do that to the male voice pretty soon, so when I do i'll post it up here.

 

I have Jason do my instructions. (still haven' t been able to get the Dutch voice working)

Would be a good intermediate solution though to extend the pause period.

Posted Feb 07, 2009 · 22:24 UTC#5

I have not tried this and it might absolutely not work but it's a thought.

 

If you take something like this:

"800[equal,minsilence=10,if_not_1,streetname]","*02-tts-nua-m07","02-1-6 Prepare to turn %* in %dist [destname]."

 

And change to this:

"800[equal,minsilence=10,if_not_1,streetname]","*02-tts-nua-m07"," "

 

Not sure if that would bomb out or it would just "speak" the silence.

Posted Feb 08, 2009 · 08:54 UTC#6

Surely could try that yes,

But than it will not at all say to prepare I guess.

 

I'll keep a close eye on what I would not like the avic to instruct.

 

The minsilence treshold seems a good idea as well.

Posted Feb 08, 2009 · 22:26 UTC#7

Where I got that code there were multiple lines of code for different distances. Something like 500ft, 300ft and 100ft so in theory you could leave blank the ones you don't want to hear.

Posted Feb 09, 2009 · 07:55 UTC#8
Where I got that code there were multiple lines of code for different distances. Something like 500ft, 300ft and 100ft so in theory you could leave blank the ones you don't want to hear.

 

:D

 

What file is this?

Posted Feb 09, 2009 · 23:34 UTC#9

TTS - Voice_TTS-nua-eng-us-f1 - config - commands.csv

 

Just understand that I have not looked any further than finding these commands :wink:

Posted Feb 10, 2009 · 03:42 UTC#10

I went through that file and edited all of the "minsilence values to 10 seconds. I have only tested it a few times but Im not sure if I could tell much of a difference. What I would like to do is just reduce the frequent announcements. to make the next maneuver. If any of you have further info, Im all ears.

Posted Feb 17, 2009 · 14:52 UTC#11

Seems to be a little more complicated then just upping the silence time.

The intrcutions scheme in my opnion is quite a good one (at least, this revised Dutch version below is)

 

For instance, it could quite possible occur that a certain instruction must be given, for it hasn't been given before, but is muted, or remains unspoken because the silence time isn't over yet. It is like punishing the lady in the map, instead of given her clearer instructions on when to speak.

 

for instance:

30[then,X=1]*dda	DAN_DIRECT %*
30[then,X>1]*da2	DAN %X %*
30[then,!X]	*dda
100[then,X=1]*da	DAN %*
100[then,X>1]	*da2
100[then,!X]	*da
300[then1,X=1]	*dda
300[then1,X>1]	*da2
300[then1,!X]	*dda
900[then1,X=1]	*da
900[then1,X>1]	*da2
900[then1,!X]	*da

3000[more]*wv	DEZE_WEG BLIJVEN_VOLGEN
1000[more]	
500[more,set_1]*na	%dist %*
200[more,set_2]*nad	%dist %* %then
50[!X,more,near,set_3]	*nad
50[X=1,more,near,set_3]	*nad
50[X>1,more,near,set_3]*nad2	%X %* %then
10[more,near]*ad	%* %then
0[more,near]*nuad	NU %* %then

500[equal,minsilence=10,if_not_1]	*na
100[!X,near,minsilence=10,if_not_2]	*nad
100[X=1,near,minsilence=10,if_not_2]	*nad
100[X>1,near,minsilence=10,if_not_2]	*nad2
50[!X,near,minsilence=10,if_not_3]	*nad
50[X=1,near,minsilence=10,if_not_3]	*nad
50[X>1,near,minsilence=10,if_not_3]	*nad2
10[near,minsilence=5]	*nuad

It seems to me that the "if not" part is as follows:

if it is not like X is specified, then don't speak for 3 seconds. If it is like X is specified, then shut up for 10.

 

 

The above scheme doesn't talk all the time, but it DOES overkill the instructions when approaching a roundabout for instance.

In 800 meters, take the second exit on the roundabout.

In 250 meters, take the second exit on the roundabout

in 100 meters take the second exit on the roundabout

Take the second exit on the roundabout.

 

(for instance)

the roundabout instructions table:

template rotonde_l		

100[then,exit]*r5	DAN OP_DE_ROTONDE %* %exit NEMEN
900[then1,exit]	*r5

3000[more]	*wv
1000[more]	
500[more,set_1,exit]*r1	%dist OP_DE_ROTONDE %* %exit NEMEN
500[more,set_1,!exit]*r2	%dist KOMT_U_BIJ_EEN_ROTONDE
200[more,set_2,exit]	*r1
200[more,set_2,!exit]	*r2
50[more,set_3,exit]	*r1
50[more,set_3,!exit]	*r2
10[more,near,exit]*r3	OP_DE_ROTONDE %* %exit NEMEN
10[more,near,!exit]*r4	U_NADERT_EEN_ROTONDE
0[more,near,exit]	*r3
0[more,near,!exit]	*r4

500[equal,minsilence=10,if_not_1,exit]	*r1
500[equal,minsilence=10,if_not_1,!exit]	*r2
100[near,exit,minsilence=10,if_not_2]	*r1
100[near,!exit,minsilence=10,if_not_2]	*r2
50[near,exit,minsilence=10,if_not_3]	*r3
50[near,!exit,minsilence=10,if_not_3]	*r4
10[near,exit,minsilence=5]	*r3
10[near,!exit,minsilence=5]	*r4


template rotonde_h		

100[then,exit]	*r5
900[then1,exit]	*r5

3000[more]	*wv
1100[more]	
1000[more,set_1,exit]	*r1
1000[more,set_1,!exit]	*r2
400[more,set_2,exit]	*r1
400[more,set_2,!exit]	*r2
100[more,set_3,exit]	*r1
100[more,set_3,!exit]	*r2
20[more,near,exit]	*r3
20[more,near,!exit]	*r4
0[more,near,exit]	*r3
0[more,near,!exit]	*r4

1000[equal,minsilence=10,if_not_1,exit]	*r1
1000[equal,minsilence=10,if_not_1,!exit]	*r2
200[near,exit,minsilence=10,if_not_2]	*r1
200[near,!exit,minsilence=10,if_not_2]	*r2
100[near,exit,minsilence=10,if_not_3]	*r3
100[near,!exit,minsilence=10,if_not_3]	*r4
20[near,exit,minsilence=5]	*r3
20[near,!exit,minsilence=5]	*r4


template rotonde_verlaten		

30[then,exit]	*r3
100[then,exit]	*r5
300[then1,exit]	*r3
900[then1,exit]	*r5

50[more,minsilence=15,exit]	*r3
20[more,minsilence=15,exit]	*r3

 

Can anyone clearify the above X= / near / if not thingy?

Posted Feb 18, 2009 · 18:21 UTC#12

*bump*

 

anyone can help me crack this code?

Posted Feb 19, 2009 · 05:39 UTC#13

I played around with this a while ago. I haven't pursued it lately, but you can read my findings the second post by me (dericn) in THIS THREAD (about two-thirds of the way down the page).

 

Please let us know if you make any headway!... 8)

 

-Eric