Unsolved Porcupine Custom Models
-
I have completed the code changes to support custom models for Porcupine. The changes affect the modules Gateway, EXT-Detect and @bugsounet/porcupine.
The major backwards compatibility breaking change is that it requires using the SDK v2.1+ which in turn requires getting an access key from Picovoice even if you are just using the builtin models.
How should I handle this? I can submit it as a pull request that updates the current Porcupine or I can add a new detector engine Porcupine-v2.
-
Hi, I have not coded it because we have to create (again…) an API key
After purpose your change… I will see what can i do- @bugsounet/porcupine is there
- EXT-Detector is there
- No change is needed in Gateway, if so, that’s a bad way
-
The change in Gateway is required because of a change in EXT-Detector’s config schema. Please review the changes in Robert-Nelson/bugsounet-Gateway, Robert-Nelson/bugsounet-EXT-Detector and Robert-Nelson/bugsounet-porcupine. This is the version that upgrades porcupine to use v2 of the SDK and is not backwards compatible. But you can get a sense of what I had to change to make custom models work and why the changes were required. I will create a version of the patch that creates a new detector engine porcupine-v2 and submit a pull request. You can do as you choose from there.
-
Thanks, I will inspect. I have no time for it yesterday sorry
I back to you soon
-
@VancouverRobert , i just push and correct your purpose in EXT-Detector v2 available in v2 branch.
Can you tell me if it’s ok for you ?
