TTS and Ventrillo

Haldir · 10-23-2008, 12:04 AM

I recently converted my timers for ACT to relay into a seperate ventrillo for our raid and put tts on most of our timers specifying what to do when the timers warn or go off. For instance on maestro when he emotes it says GET OUT. This is working great except for one little detail....

On almost every AE in the game the voice will repeat itself multiple times... as though it is triggering for each player the AE hit. I have selected only one of this timer can exist and several other options with no success. In addition the repeating is worse the shorter the tts message which kinda makes sense with it is trying to repeat for each player the ae hit. For instance on the maestro's Chains of Rancor the ae will hit and my tts says "Cure Trauma" about 3 times then at the end of that it will relay "Chains in 10" which was the tts warning to the AE... so it appears that ACT saw the AE multiple times and triggered the warning tts too at the end.

If anyone knows a way to get this to quit repeating other than creating a super long message for each timer please let me know! If there is no other way it would be really nice if the tts messages were limited to one trigger or there was a user option to quit repeating of tts messages on that specific spell timer for ___ amount of time.

Haldir

Anap KaSplat · 10-23-2008, 03:12 AM

Does it say "Cure Trauma" over and over, or more like "cu cu cu cure trauma" ?

If it's actually saying "cure trauma cure trauma cure trauma" over and over, that sounds more like a vent echoing problem, or your parser box is really, really slow at parsing.

My ACT sometimes does the stuttering bit with TTS like "Ch ch ch chains hit" or whatever, but never goes on and on until the "chains in 10" tts fires.

EDIT: "would be really nice if the tts messages were limited to one trigger"

... in a given amount of time. That would rock. I was playing around with Taskmaster's Fire Nova AE with a custom trigger to let people know when it's cool to joust back in, but hah, don't to it. "no no no no no no no no no no no no no no no no no no no no no no no no no nova hit" LOL

EQAditu · 10-23-2008, 01:07 PM

Well, spell timers attempt to only notify once but due to buffering of the timer to allow TS mod removal on death, it doesn't always work. In that case, if a single AE is split across several timestamps(IE the first person is hit at 16:10:05 and the last person is hit at 16:10:06) you will probably hear the same notification twice. Though looking at the code, I wonder if it would be okay to increase the ignore time to two seconds. Things stay in the buffer a maximum of 1000ms and there's no reason to call an AE or even care if there's a DoT tick less than two seconds apart. Though this is a minor problem anyhow.

Custom triggers on the other hand don't even try to restrict that much. If it takes EQ2 a full second to output a collection of AE hits to the log file, ACT will be repeating it that long... probably in 100ms increments if ACT is reading faster than EQ2 is outputting. In actuality ACT will be doing them in several groups... IE if there are 30 hits over 300ms, ACT will play the same sound nearly instantaneously 10 times, then wait 100ms to do the next. Again, that assumes that ACT is reading the log file faster than EQ2 outputs it(which is normal).

Since Custom Triggers don't have to deal with buffering etc, I don't see why I couldn't easily restrict audio output to once per 1-2s per trigger.

Haldir · 10-23-2008, 10:03 PM

Thank you for the quick response Aditu! I think a two second delay would kill the problem as I did notice that it didn't do it as much when I used the default tts and more with the custom ones. So I think you got it spot on. I can't see any reason why we would need to see the same ae within even 5 to 10 seconds of each other.... but you never know what soe will come up with in the future so 2 is a pretty safe bet and would probably kill the issue for the most part.

From your description of the problem Aditu... i'm not completly sure that what you are proposing would eliminate the trigger for the warning tts though. As it appears it was firing off for some reason at the end of the spam of text.

P.S. the output was more of a stutter than the full text

EQAditu · 10-24-2008, 09:18 AM

I released an unrelated hotfix today which I think included the 1->2s change for spell timers. I haven't touched Custom Triggers though.

Haldir · 10-28-2008, 12:22 AM

So we did trak again tonight and several other zones and the fix has stopped the spam as long as the default tts is used. However, a couple things still seem to make it go stutter crazy.

1. Having a custom tts (this I know hasn't been looked at yet).
2. I set up the timer on trak as default for the event and for the warning. If I did not select only one of this timer can exist also then we would get the event call and a raids worth of the warning tts. I think it was calling the warning for each player in the raid.
3. When I did select only one of this even on Arcane maelstrom it would call the event and warning on que, however, every now and then it would call the event immediatly followed by the warning. Not sure why it was doing this.

Went through almost every other zone this week and the 2 seconds fix to the default timers has curbed the issue greatly.

Thank you Aditu for all your hard work on ACT!