fixed a few things for M1 arm64 release

[pietrop]

Is your Pull Request request related to another issue in this repository ?

#79

Describe what the PR does

fixed dialog by moving to main process via ipc, fixed ffmpeg and ffprobe bin by adding arm64 arch folder and logic in that module, tested locally with npm start prod and dev, haven't tried packaging yet

State whether the PR is ready for review or whether it needs extra work

Work in progress

Additional context

NA

[dgw]

If I understand the templating language correctly here, this snippet restricts the display of DeepSpeech as an option to only x64 Mac (platform === 'darwin' is required). In 1.6.5-alpha.0 I can't see the DeepSpeech option any more on Windows 10.

digital-paper-edit-electron/src/stt-settings/index.html

Lines 268 to 272 in 6d0a438

	{/* TODO: M1 - Apple M1 disabling deepspeech until can figure out how to make module compatible -*/}
	{process.platform==="darwin" && process.arch !=='arm64' &&(
	<option value="deepspeech">
	Mozilla Deepspeech (offline){" "}
	</option>)}

Would a condition like {!(platform === 'darwin' && platform.arch === 'arm64') && (<option etc.> work? That would display the DeepSpeech option on any platform that is not both Mac and M1.

[pietrop]

Sorry for the delay at @dgw

Does deepspeech work on Windows 10?

I wanted to remove the deepspeech option for mac M1 (arm64) because it doesn't support it yet.

I wasn't sure if it worked on linux and windows(?) so thought I'd remove that too.

You could change it to

- {process.platform==="darwin" && process.arch !=='arm64' &&( 
+ {process.platform==="darwin"  
+ && process.platform==="win32"
+ && process.platform === "linux" 
+ && process.arch !=='arm64' &&( 
 <option value="deepspeech"> 
   Mozilla Deepspeech (offline){" "} 
 </option>)} 

To bring back deepspeech to windows and linux (provided deepspeech is compatible with those OS)

I'd welcome a PR, if you got time to try it out (on a windows machine?) 😇

---

Node docs, links

• os.arch()
• os.platform()

[dgw]

Hi @pietrop,

I ultimately moved on from this tool for the current project as it has too many limitations—especially given that I need to collaborate with others. A cloud service seemed to be the best option for something that "just works" for my employer. I'm happy to toy with stuff like this on my own projects, but the project timeline from work didn't allow for it here.

Another thing I tried was tying together a couple of tools built on deepspeech using the WSL2 command line, which certainly got me farther than the paper-edit GUI. In that way, deepspeech "works on Windows 10", but it won't help with paper-edit until the promised graphical interface support rolls out. At that point it would become possible to install and run paper-edit inside WSL and use any STT library that works on a normal Linux desktop (but there's obviously no Windows Subsystem for macOS 😅).

As far as testing deepspeech compatibility within the app, natively on Windows 10, I can try to do so but there seem to be other places where it's been disabled in the paper-edit code. For example (from this patch):

digital-paper-edit-electron/src/ElectronWrapper/lib/transcriber/index.js

Line 10 in e79f318

// const deepspeechSTT = require("./deepspeech/index.js");

Code later in that file references the imported module:

digital-paper-edit-electron/src/ElectronWrapper/lib/transcriber/index.js

Line 89 in e79f318

const deepspeechTranscript = await deepspeechSTT(newAudioFile, deepspeechModelsPath);

I saw a lot of commented-out stuff while poking around the code a bit just now to refresh my memory of what's where. Based on that, I doubt I'm up to tracking down all of the things I'd have to change just to try deepspeech under Windows, if it will even run.

Plus, I still don't understand how the templating works. You suggested a change that—to me—would enable deepspeech if the platform matches darwin, win32, and (&&) linux, when the platform can't be all 3 at the same time. Maybe the biggest limitation is just that I don't have any Electron experience, and can't justify spending the time to learn it just for this purpose.