Thanks sutex.
The dev team is fortunately a mixed team of VA and standalone EDDI users, so that both sides are represented. I'm standalone whereas T'Kael and Hoodathunk are VA. I'll leave it to them to respond to this particular issue.
- Status
Thanks sutex.
The dev team is fortunately a mixed team of VA and standalone EDDI users, so that both sides are represented. I'm standalone whereas T'Kael and Hoodathunk are VA. I'll leave it to them to respond to this particular issue.
I disagree with the idea spending dev resources to make the EDDI API work well with the Voice Attack API. I have been both an EDDI and Voiceattack for a very long time. I actually do not use the voice attack API as I like being able to customize responses using EDDI. It is awesome that there are so many tools available to allow each person to make a choice about what they want to use, but sacrificing development to make one tool work with another is not a good idea I believe.
To cut through the verbiage: we welcome concrete issue reports at https://github.com/EDCD/EDDI/issues
Sorry mate, but its not the case, if you don't use the HCS Plugin API, the new round of HCS voice packs do.
EDDI has already lost one DEV, ( maybe back) and if the current EDDI Dev's build on EDDI and ignore HSC plugin, issues no doubt will arise, which in the long run is just more work, one would assume.
At the moment conflicts between the two API EDDI & HSC plugin, seem to be non-existent, but as the commercial HSC Voice packs gets more complex, I dare say this will change.
My personal use of the HSC plugin with Voice Attack , is to let it do, what it's been setup to do, and that's remember my current Game States, this is done throughout the new Astra HCS voice packs
and hopefully just allowing EDDI, to be more specific, given EDDI ability to script, in an easy way.
Just wanted to give the new EDDI dev's a heads up. A Voice Attack thread http://voiceattack.com/SMF/index.php?topic=1486.0
Last edited:
Just responding to Sutex about HCS and Eddi....I don't think we particularly need to work in sync with each other, more of a mutual love kind of thing is all that is needed. If any conflicts are found between the 2 then I'm sure we'd happily work together and resolve the problem. We do recognise eddi's awesomeness and believe the 2 working side by side for users that want to is better for everyone's enjoyment.
+1 to this.
@Sutex I don't think you appreciate just how radical of a change this suggestion would require "under the hood" for EDDI. What you are describing is a very different application than the one we are currently supporting, and I'm afraid it'd be easier to build a new app from scratch than to convert EDDI per your suggestion.
Thank you TheThingIs, ever the voice of reason. Very happy to work together.
sutex, I am sorry but as a native English speaker I find it very hard to understand you. Your grammar is incoherent and placing commas randomly makes it much harder to understand what you are trying to say.
I want to be very clear about one thing "EDDI has already lost one DEV" is a very misleading statement. "EDDI's sole developer has handed over maintanance to a team of three developers" would be a more accurate statement.
Last edited:
Are you reading my post ,or some revolutionary pamphlet .
"radical of a change this suggestion would require "under the hood" ..... "I'm afraid it'd be easier to build a new app from scratch than to convert EDDI per your suggestion."
@Tkael the basics of my post has been , Hey EDDI DEV'S keep in mind the HSC Plugin, when coding...... so radical..... lol
Last edited:
*plonk*
whoa chill m8e, we were reassuring you that we would resolve any issues if they arose, not having a go at you. You're points are valid ones but you are simply worrying for no reason.
o7 Commander.
I agree that there is no reason to be concerned that EDDI's VA plugin and the HCS plugin will conflict with each other, given that HCS uses sound files and would not compete with EDDI's use of the TTS drivers.
For the record, I'm a huge fan of HCS and CMDR TheThingIs' work... I own and use several Voice Packs, myself... excluding the HCS plugin.
For those who prefer the HCS plugin alone, EDDI provides the flexibility to disable the VA plugin and run EDDI like it was standalone, with VA running.
For those who find it beneficial to their playing experience to run both plugins concurrently, we will absolutely work with the HCS folks if a conflict does arise.
I think that's all that needs to be said about this issue and hope everyone will now consider this particular discussion closed.
Last comment on this, I swear!
I would like to 'second' VerticalBlank's comment here. The current dev team, from the start, had sought jgm's blessing to continue the mission.
For those who are interested, we have received both his blessing and his approval of our work thus far.
We will endevour to continue to move EDDI forward, being mindful of jgm's vision, and will treat all reasonable comments and requests with due consideration and will always return the respect given.
o7 and out!
"Can the new Dev EDDI team working on EDDI, keep in mind Voice Attack's HSC Plugin, as the NEW 2.4 Astra profile ( other voices will catch up) is using HSC plugin to keep Voice Attack in sync."
We all know there was nothing to my post, expect to draw attention to the new Voice packs coding, and to give the EDDI Dev's a heads ups
Last edited:
HSC plugin API and EDDI API
Can the new Dev EDDI team working on EDDI, keep in mind Voice Attack's HSC Plugin, as the NEW 2.4 Astra profile ( other voices will catch up) is using HSC plugin to keep Voice Attack in sync.
As a result of this newer better coding and layout within HSC voices like Astra, Ive started a new ED Voice Attack profile. This is the full thread http://voiceattack.com/SMF/index.php?topic=1486.0
At the moment CONFLICTS are 'not happening' ?, between HSC plugin API and EDDI API, but I feel that is more by luck than by design
EDDI can be used as a 'stand alone', BUT many Players are using EDDI with Voice Attack, so these API readers need to work in harmony
In short would like the new EDDI dev team to view Voice Attack HSC API plugin as the default API for Voice Attack, which it is now, as the new HSC Voice Profiles are heavily relying on the HSC API plugin, to work its magic within Voice Attack. Please check out the new Astra Profile, and you'll see.
The last thing anyone wants is these forums ( EDDI & Voice Attack / HSC voices ) is players running back and forth, tying to fix API conflicts.
...
I now have both TheThingIs, and VerticalBlank blocked..
I got My Astra and Jazz updates today, so just kinda of waiting for Eden and Verity and I'll be happy
Celeste will be the next I add
Last edited:
Ummm... as usual, they talk to each other and work it out?
I got My Astra and Jazz updates today, so just kinda of waiting for Eden and Verity and I'll be happy
Celeste will be the next I add
Yeah Astra setup & layout is great, makes editing in VA way better.
Ive just started re-coding for my new 2.4 ED profile , since most of the checks I had in my Old profile are semi incorporated into Astra now, but I will be adding, more error checking.
I'm very sure their talking ...lol
Last edited:
Arguendo
Volunteer Moderator
Sorry, I guess my answer didn't come out the way it was intended. I wasn't trying to snipe at you at all, and I really appreciate the work you do. I also understand what a pain FDev can be, seeing how they seem to change the API without warning at every junction.
My point was that I don't install betas unless I want to test things and report bugs. I also hadn't seen an announcement here that explained that 2.3 wouldn't be updated to the new API, so I never thought to install the Beta version. That is all.
The last part is a snipe however, but it's directed at how most ED Beta players conceive ED Betas; as a place to find the new stuff, not to test bugs
Last edited:
Sorry, I guess my answer didn't come out the way it was intended. I wasn't trying to snipe at you at all, and I really appreciate the work you do. I also understand what a pain FDev can be, seeing how they seem to change the API without warning at every junction.
My point was that I don't install betas unless I want to test things and report bugs. I also hadn't seen an announcement here that explained that 2.3 wouldn't be updated to the new API, so I never thought to install the Beta version. That is all.
The last part is a snipe however, but it's directed at how most ED Beta players conceive ED Betas; as a place to find the new stuff, not to test bugs
No worries, man... it's all good.
Regardless of if you are using EDDI with VoiceAttack or standalone, you should start by firing up the EDDI application so that you can configure the relevant information. Note that you should not have the EDDI application running at the same time as VoiceAttack.
Doh! I didn't know this, what happens if you do?
Btw love EDDi, great program!
Is there anyway I can extract data from it? Specifically the NHSSs I've dropped into & the systems they were in.
TIA
Doh! I didn't know this, what happens if you do?
Btw love EDDi, great program!
Is there anyway I can extract data from it? Specifically the NHSSs I've dropped into & the systems they were in.
TIA
Regardless of if you are using EDDI with VoiceAttack or standalone, you should start by firing up the EDDI application so that you can configure the relevant information. Note that you should not have the EDDI application running at the same time as VoiceAttack.
Doh! I didn't know this, what happens if you do?
Btw love EDDi, great program!
Is there anyway I can extract data from it? Specifically the NHSSs I've dropped into & the systems they were in.
TIA
EDDI isn't really designed for extracting historical data from the journal, but there are several other excellent 3rd party tools that fill that niche quite nicely. Check out http://edcodex.info/?m=tools&cat=3&sort=mostlike. o7
- Status