.... Chapeau bas for the idea and compliments to the actress that recorded the responses, great job!
Thankyou!
However - I have some initial constructive feedback - as in not complaints
- that hopefully will allow you to improve your product.
Feedback is always welcome, and we really appreciate how constructive the people in this forum are. I'll address some of your feedback below.
File naming convention. At the moment the files are named in random manner. Some start with numbers, some with 'eng' and some with the actual command being spoken. You really need some consistency there, it's extremely confusing as it is now, and with so many files it's just a mess.
A good example of file names mess is: when I search for "redirecting" - the "eng-redirecting_power_to_engines " does not come up in search results due to file naming convention (eng-redirecting is treated as 1 word and does not return search results when searching for "redirecting").
Ah. Yes. The file naming convention. We started with one, and then realised that being an internal convention it wouldnt make any sense to users.
We have TRIED to improve it my grouping the commands with a prefix, but you've pointed out a problem with the delimiter we have used, it's breaking searches.
This is a hard one to fix, because if we rename files it's going to break a LOT of people's VoiceAttack profiles.
What I THINK I'm going to do is rename EVERY file with a prefix then underscore.. eg eng_full_ahead.wav
Users can extract the pack then without overwriting any files and update their profiles at their leisure. You can expect this in the next update unless someone pipes up with a better suggestion.... all are welcome!
Responses consistency. I only noticed this while setting power distributions commands.
We have:
011_diverting_power_to_weapons
010_diverting_power_to_systems
009_diverting_power_to_shields
But no "diverting_power_to_engines". Instead we have different multiple options for engines power dist, like
We missed the engine commands in the first recording session! The latest updates have engine commands which are consistant, and actually expand upon the ones used in other areas. So there is definitely "eng-diverting_power_to_engines.wav"
But no "all power to engines" or "weapons". I'd like my computer to respond in consistent manner when I speak commands that relate to the same ship system.
I think you'll find this is fixed.. but if you notice any glaring errors after the next update please let me know in case I missed something (again)
I would apply a slight metallic filter to all the sounds to make it sounds slightly computerised. Kind of a very subtle tin can echo effect. Launch Elite and retract the cargo scoop, and listen carefully to the ship computer. You can hear the effect there.
We experimented with a more 'computery' voice, but in the end decided to leave it clean (actually it's still been EQ'd to death) the original is a LOT warmer! One option that can be explored by keen users is to modify the files themselves. With a program like Audacity you can record a series of actions liek a macro, and then apply it to a whole directory of sounds. In this way you could quickly customise her voice to your own liking!
These are the 3 points that I wanted to initially share with you as my feedback. The last one is not the top priority for me, but would be nice to have feature. However the naming convention and response consistency I'd say are the 2 things that put me off slightly. Don't get me wrong, as I've said - you've done a great job and it's awesome sound pack, but it just needs polishing I think.
Hope this helps!
Yes it does! All feedback helps and yours has been great. I hope we continue to improve it and please drop me an email if you want to report any issues.
Other commands that I miss and could be useful:
- Hardpoints Retracted (as we already have Hardpoints Deployed)
- Landing Gear Deployed (consistency with in game command showing on the screen)
- Thank you, Commander. (Thinking of "Anything else, Commander?" - "No, that'll be all" - "Thank you, Commander." scenario
)
- Cancelling Hyperdrive
Hopefully the search will improve with our next release, because these are mostly in there already! But the missing ones are now in my notes
Actually regarding point 1 - naming convention - I can see the pattern now, but I think it's still a bit messy with the numbers for some responses and prefixes for other ones. I'd stick to one method (prefixes seem better, but get rid of dashes and replace them with underscores would be my suggestion).
Thanks!
Suggestion noted and being acted upon.
again, thanks. And we really want this to be as usable as possible so we take these suggestions seriously.
