EDDI: A(nother) Voice Attack Plugin

[jgm]

Voice Attack - EDDI Plugin suggestions / Ideas.


1. The filename of EDDI's VA profile is called 'EDDI-Profile.vap' which is fine. However, the actual profile name you used, which is displayed in Voice Attack is 'elite dangerous'. Now this profile name is quite commonly used, one of my earlier Elite Dangerous profiles was called 'elite dangerous'. Now, each time we import a new EDDI profile, VA will automaticaly add a (1) after the profile name, since it conflicts with your previous, same named profile name. After a while we can end up with a number of profiles that look the same and dont remind us that they belong to EDDI.

So, as a suggestion, would it not be better to use EDDI-(version number) as the profile name, would make it much easier to spot out-of-date profiles and wont conflict with any other profiles the User's may already have in their Voice Attack.

I have to admit that I generally import the EDDI commands in to whatever existing profile I'm using rather than create a new one, so don't meet this problem. As EDDI is not really designed to be a complete standalone plugin I'd expect this to be the way that it would be loaded.

Changing the profile name every time I updated EDDI would be another manual step and one that could cause its own confusions.

2. Would it be possible for EDDI to create-on-the-fly, random ship callsigns in the future?

Yep this is easy enough to do, although it might be that random callsigns without any attachment to a ship isn't what you really want. The idea of having it for ship talk is nice but does require tracking of a ship's identity. The ideal situation would be for EDDI to generate more events when other ships enter the area, are given docking clearance, etc. and put the callsign in there.

3. Perhaps the following falls outside EDDI's primary function of game data collection, but will throw it out just in case. Is it possible for EDDI to interface with the chat window, then, via voice commands, act as a dictaphone for inserting short phrases into the chat window and sending them off to [Direct] or to another commander via [/r].

VoiceAttack uses Windows' built-in voice recognition system for dictation so you should be able to do something like that alongside EDDI. That said, when I've attempted to use it there have been some rough edges. I'm talking to Voice Attack support to see if they can provide a simpler dictation mode for single-line dictations.

 

[Red Zodiac]

I have battled through Manflu to emerge with VA showing "Plugins enabled" followed by "Plugin EDDI 0.9.3. initialized", but no commentary from VA, have I not completed the installation yet? Are there more steps to carry out? Any assistance appreciated.

 

[CMD Malandark]

@Red Zodiac Lets now check a couple of things..

Fire up Voice Attack, then press the following keys together. Left Ctrl+Left Shift+Left Alt+E


You should see in Voice Attack's log window something like this:-

EDDI raw event is Not set
EDDI debug is False
Access to NetLog is Enabled
Access to EDSM is Disabled
Access to profile is Enabled
EDDI status is Operational

My gut feeling is that you havent yet imported the EDDI profile into VA yet.

 

[Red Zodiac]

Good Morning Malandark. Thanks for your quick response. Fired up Voice Attack but no response from the Left keys +E. Just the chime sound.

 

[foxpur]

@Red Zodiac Lets now check a couple of things..

Fire up Voice Attack, then press the following keys together. Left Ctrl+Left Shift+Left Alt+E


You should see in Voice Attack's log window something like this:-

EDDI raw event is Not set
EDDI debug is False
Access to NetLog is Enabled
Access to EDSM is Disabled
Access to profile is Enabled
EDDI status is Operational

My gut feeling is that you havent yet imported the EDDI profile into VA yet, but we need to check that EDDI is fully functional before we do that.

Note, STILL not gotten 'Interaction Mode On' to work BUT...

10:43:02 - EDDI raw event is Not set
10:43:02 - Access to NetLog is Enabled
10:43:02 - Access to EDSM is Enabled
10:43:02 - Access to profile is Enabled
10:43:02 - EDDI status is Operational

So we know the log files ARE being seen, regardless of what configuration has to say about it.
Note, all the rest of the stuff from the .vap is running just fine and I made some minor starting scripts.

 

[jgm]

Note, STILL not gotten 'Interaction Mode On' to work BUT...

10:43:02 - EDDI raw event is Not set
10:43:02 - Access to NetLog is Enabled
10:43:02 - Access to EDSM is Enabled
10:43:02 - Access to profile is Enabled
10:43:02 - EDDI status is Operational

So we know the log files ARE being seen, regardless of what configuration has to say about it.
Note, all the rest of the stuff from the .vap is running just fine and I made some minor starting scripts.

The 'Access to NetLog is Enabled' confirms that EDDI is monitoring for netlog changes, but if the path is wrong it won't ever see any.

From your previous posts it looks like the path to your logs should be C:\Program Files (x86)\Frontier\EDLaunch\Products\elite-dangerous-64\Logs Could you set this in the configuration app and restart Voice Attack to see if it works when you change system?

 

[CMD Malandark]

Good Morning Malandark. Thanks for your quick response. Fired up Voice Attack but no response from the Left keys +E. Just the chime sound.

As I suspected, you need to now 'import' the EDDI commands into Voice Attack.


Here's how to do this...


From the Main Voice Attack Screen, Press ALT + I

This will open the 'Import Profile Window'.


Now you need to find the file EDDI-Profile.vap and select THIS file and then click on the OPEN button for VA to import this profile.

The EDDI-Profile.vap file is found here:-

C:\Program Files (x86)\VoiceAttack\Apps\EDDI


--------

Once you have carried out the above, press the following keys again (Left Ctrl+Left Shift+Left Alt+E)

Now you *should* see the following!

EDDI raw event is Not set
EDDI debug is False
Access to NetLog is Enabled
Access to EDSM is Disabled
Access to profile is Enabled
EDDI status is Operational


Now issue one of the following Voice Commands.

'Ship handover complete' or,
'I have docked'

 

[foxpur]

The 'Access to NetLog is Enabled' confirms that EDDI is monitoring for netlog changes, but if the path is wrong it won't ever see any.

From your previous posts it looks like the path to your logs should be C:\Program Files (x86)\Frontier\EDLaunch\Products\elite-dangerous-64\Logs Could you set this in the configuration app and restart Voice Attack to see if it works when you change system?

That is the path, and just for continuity I cut/paste yours and put it in and still couldn't find it.... But it certainly IS the correctly entered path.

I will do some in game test changed later today, I will be sure to have a current log in there as well.

 

[jgm]

That is the path, and just for continuity I cut/paste yours and put it in and still couldn't find it.... But it certainly IS the correctly entered path.

I will do some in game test changed later today, I will be sure to have a current log in there as well.

If it doesn't work please could you send me the contents of the netlog, along with %APPDATA%\EDDI\eddi.log (if anything).

 

[CMD Malandark]

@jgm Just a quick question.

Does EDDI still use the file netlog.json? As I understand it, EDDI stores the path to the User's netlog directory here.

{
"path": "C:\\Program Files (x86)\\Steam\\steamapps\\common\\Elite Dangerous\\Products\\elite-dangerous-64\\Logs"
}


However, the path it stores seems 'wrong', it has way to many \\ to be valid. If you paste the path as it stands into Windows file/directory browser it cant make any sense of it.

 

[jgm]

@jgm Just a quick question.

Does EDDI still use the file netlog.json? As I understand it, EDDI stores the path to the User's netlog directory here.

{
"path": "C:\\Program Files (x86)\\Steam\\steamapps\\common\\Elite Dangerous\\Products\\elite-dangerous-64\\Logs"
}


However, the path it stores seems 'wrong', it has way to many \\ to be valid. If you paste the path as it stands into Windows file/directory browser it cant make any sense of it.

JSON needs to escape the backslashes, which is why they double up. You can find details at http://json.org/ (if you care that deeply).

 

[CMD Malandark]

JSON needs to escape the backslashes, which is why they double up. You can find details at http://json.org/ (if you care that deeply).

Ouch, ok, my bad.


*Since EDDI is almost ready for public release, now is a good time for me to leave the Beta Testing and go back to playing Elite Dangerous. For those still pm'ing me with support questions etc, please instead post them here or to jgm.

 

[foxpur]

If it doesn't work please could you send me the contents of the netlog, along with %APPDATA%\EDDI\eddi.log (if anything).

I'll game later today and do some testing, working on the help manual for the ED Tookbox at the moment

 

[Red Zodiac]

My dear CMD Malandark
Thank you for all your assistance. I have now managed to incorporate EDDI into my own profile, 46 commands, 11 voice commands. Not completed all voice commands but think they will work under appropriate circumstances. Will try them out in 'anger' in the near future.
Once again I thank you.
CMD Eccles Zodiac aka Red Zodiac

 

[jgm]

I've updated EDDI to .0.9.4, which contains mainly bugfixes.

It seems to be relatively stable but I'll leave this version out there for a day or so. If there are no problems reported I'll move it to a 1.0 release.

Thank you again to everyone who has used EDDI so far, be it for testing or just for their own enjoyment. All of your feedback and questions have helped to make the product what it is, and will no doubt continue to improve it further.

 

[Jetkar]

I've updated EDDI to .0.9.4, which contains mainly bugfixes.

It seems to be relatively stable but I'll leave this version out there for a day or so. If there are no problems reported I'll move it to a 1.0 release.

Thank you again to everyone who has used EDDI so far, be it for testing or just for their own enjoyment. All of your feedback and questions have helped to make the product what it is, and will no doubt continue to improve it further.

@jgm this just an observation but you seem to be updating EDDI to quickly to final release. I am still using 0.9.1 lol

 

[jgm]

@jgm this just an observation but you seem to be updating EDDI to quickly to final release. I am still using 0.9.1 lol

Yes it's been a little hectic. The changes have mainly been bugfixes and the like, so that new users aren't confused when it doesn't do what it should.

It will slow down once 1.0 is released, promise

 

[bAdbUd]

Hi, starting to get used to this great plug-in now.

ISSUE when I press: Left Ctrl+Left Shift+Left Alt+C for Call sign VA says everything in the command (below) verbatim, rather than just saying: yankee victor delta tree seven six fawer

Spoiler

20:04:41 - Ship callsign (spoken): <phoneme alphabet="ipa" ph="ˈjænki">yankee</phoneme> <phoneme alphabet="ipa" ph="ˈvɪktə">victor</phoneme> <phoneme alphabet="ipa" ph="ˈdeltɑ">delta</phoneme> <phoneme alphabet="ipa" ph="ˈtriː">tree</phoneme> <phoneme alphabet="ipa" ph="ˈsɛvɛn">seven</phoneme> <phoneme alphabet="ipa" ph="ˈsɪks">six</phoneme> <phoneme alphabet="ipa" ph="ˈfoʊ.ər">fawer</phoneme>

Funnily for '>' VA says 'furious'

Left Ctrl+Left Shift+Left Alt+E result below, is "EDDI raw event is Not set" an issue or is that normal behaviour?

Spoiler

20:12:07 - EDDI raw event is Not set
20:12:07 - Access to NetLog is Enabled
20:12:07 - Access to EDSM is Enabled
20:12:07 - Access to profile is Enabled
20:12:07 - EDDI status is Operational

 

[jgm]

Hi, starting to get used to this great plug-in now.

ISSUE when I press: Left Ctrl+Left Shift+Left Alt+C for Call sign VA says everything in the command (below) verbatim, rather than just saying: yankee victor delta tree seven six fawer

Spoiler

20:04:41 - Ship callsign (spoken): <phoneme alphabet="ipa" ph="ˈjænki">yankee</phoneme> <phoneme alphabet="ipa" ph="ˈvɪktə">victor</phoneme> <phoneme alphabet="ipa" ph="ˈdeltɑ">delta</phoneme> <phoneme alphabet="ipa" ph="ˈtriː">tree</phoneme> <phoneme alphabet="ipa" ph="ˈsɛvɛn">seven</phoneme> <phoneme alphabet="ipa" ph="ˈsɪks">six</phoneme> <phoneme alphabet="ipa" ph="ˈfoʊ.ər">fawer</phoneme>

Funnily for '>' VA says 'furious'

Yep this is a bug with the VA profile, where it isn't feeding the spoken callsign to EDDI's speak command. I'll fix this for the next release. Thanks for reporting it.

Left Ctrl+Left Shift+Left Alt+E result below, is "EDDI raw event is Not set" an issue or is that normal behaviour?

Spoiler

20:12:07 - EDDI raw event is Not set
20:12:07 - Access to NetLog is Enabled
20:12:07 - Access to EDSM is Enabled
20:12:07 - Access to profile is Enabled
20:12:07 - EDDI status is Operational

That should contain whatever the last event was. Current events include changing system or environment (supercruise/normal space), docking and changing ship. The former two should be triggered automatically whenever you jump, the latter two when you say "i have docked" or "ship handover complete".

If you aren't seeing any events when you jump system (more easily recognised by EDDI telling you about your destination) then it's probably down to the path to the netlog files being incorrect. The best way of obtaining this is to start up Elite itself, then go in to EDDI's configuration options and hit 'obtain'. This will try to fetch the path from the running process, which is the more reliable way of doing this.

 

[foxpur]

That should contain whatever the last event was. Current events include changing system or environment (supercruise/normal space), docking and changing ship. The former two should be triggered automatically whenever you jump, the latter two when you say "i have docked" or "ship handover complete".

If you aren't seeing any events when you jump system (more easily recognised by EDDI telling you about your destination) then it's probably down to the path to the netlog files being incorrect. The best way of obtaining this is to start up Elite itself, then go in to EDDI's configuration options and hit 'obtain'. This will try to fetch the path from the running process, which is the more reliable way of doing this.

This is the problem I am currently facing, but haven't does enough in game testing to give a proper debugging report. Been kind busy doin other stuff for the "other" app