How to change and edit aproaching beep in igo nextgen ?

**eliel77** · 3rd May 2017, 05:03 PM

Its the aproaching beep, not the one that is activated together with the speech of the tts voice.
Im using Gift edition 9.18.27.687519 Pongo Sking, but I guess any version should do the trick if its possible to edit it someway.
this one:

Spoiler: pic1

and not this one

Spoiler: pic2

My aproaching beep sound is always !sectionbeepB.wav, there is no lines in the sys.txt or plugin.ini that point to this sound.
and it is starting to beep before 100M of the alert, I wanted to increase this valor and control the frequency.

I tried to change the valors of aproach beep distances, but it does nothing, the beep always behave the same way, no matter how I edit the plugin.ini.

i tried to create new line under the desired [speedcam_category:XXX], but no success
approach_beep_distances="50,150,300,600"
approach_beep_spoken_type=sound
approach_beep_sound="!alert2"

my plugin.ini of the speedcam.zip UX is like this:

Spoiler: plugin.ini

the line warn_distances is for activating the speech of TTS VOICE and the beep sound with it (in my case no sound)
it does not change the distance of aproaching beep.

Any clues ,nextgen is very stubborn to accept changing the beep behavior.

**osiris4isis** · 3rd May 2017, 09:47 PM

Hint: Any settings done in sys.txt will override any other settings done elsewhere.

**eliel77** · 4th May 2017, 01:38 AM

I have also tried something in the sys.txt creating aproach beep distances there. without success.
I will try again, with something more under the [warning] section in the syst.txt
How about this ? is there any code done wrong here ? Im using oasis alarm for test as the ui_nextgen/audio folder has this file.

Spoiler: Test for creating continuous beep

**osiris4isis** · 4th May 2017, 01:45 AM

If you set the correct settings in sys.txt it should override any settings done elsewhere. My suggestion is to test without using any skin first.

**eliel77** · 4th May 2017, 01:56 AM

Ok. I will wait to see if anybody has tips about the correct settings, im guessing with the one I created, reading others users settings.
I dont know if its necessary to create the line "activated_spoken_type=sound" and I dont know if it causes conflict with the other line in the plugin.ini,
it is there but to activate speech, "activated_spoken_type=speech".
I need the speech to be active too.

**osiris4isis** · 4th May 2017, 01:58 AM

There is no such thing as "conflict" when dealing with .ini related settings, just overridden by the last one read.

**jorgeultra** · 4th May 2017, 11:33 AM

Read the content of the link below and see if help.

Spoiler: show

**eliel77** · 4th May 2017, 05:12 PM

i read that topic, but still cant change the aproaching beep distances. As 1 year forum material was lost, I will have a hard time finding specific information about alerts.
And its pretty hard to understand if the lines are to configure the beep that comes with the tts speech or the independent aproaching beep.
Im trying now to add "activated_tonal_type="alert"
to see if it fix the beep not being activated the way I want.

**osiris4isis** · 6th May 2017, 11:04 PM

There is no "beep" that comes BEFORE TTS speech, it's a "ding." That being said, having built-in tone before alert is possible, I've done it a LONG time ago. I don't have a need to do it now since TTS is much better. But you could configure it to play any audio file of your choice, I've done it recently with NextGen.

**eliel77** · 9th May 2017, 12:32 AM

I didnt say it comes before TTS speech. And I dont need a ding. The beep comes with the TTS speech. The TTS voice warning is activated and the beep also start (for all kinds of speedcams / alerts). You can either select a sound for the beep for all at once, or mute it for all.

Ill I wanted is an aproaching beep sound in 100, 200, 400 , 600 meters, only for the speedcam category : 0
but Im giving up and using it the default way the navigator offers me.

I tried all lines I have read in the other topics, but the command

Spoiler: aproaching beep line

does not seem to work well with next generation TTS voice activated. I tried it in the sys.txt and in the plugin.ini, in dozens of different combinations, without success.