Open
Conversation
Collaborator
Author
|
Note: This won't currently build correctly without the workaround, or our PR (mozilla/DeepSpeech#3702) being accepted on the DeepSpeech side. Workaround: I was able to get MacOS electron binaries built on my fork's PR (dudewheresmycode/DeepSpeech#1). Which allows us to get our app building locally on mac.
I added a patch script to our |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Getting the core speech-to-text / subtitle analysis pipeline working. This is the process that analyzes a media file and compares with a subtitle to check for accuracy. This is all still pretty rough, but wanted to get a PR going to cap this work at some point.
ipcto communicate analyze events with the clientI think we'll eventually do this part in the background. I see it working like: