Skip to content

Commit 32af744

Browse files
committed
Fix naming, update readme, add additonal instructions in the requirements.txt
1 parent 3589e7f commit 32af744

File tree

2 files changed

+21
-19
lines changed

2 files changed

+21
-19
lines changed

README.md

Lines changed: 16 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -104,11 +104,11 @@ Now that you have all of the requirements installed we will install the Transcri
104104
1. use "cd" to change directory to where you want to install the transcriber
105105
example: to your Documents folder:
106106
`cd ~/Documents`
107-
1. Clone the Transcriber repo:
108-
`git clone https://github.com/Noah-Jaffe/Transcriber.git`
109-
_NOTE: If you get the error: `fatal: destination path 'Transcriber' already exists and is not an empty directory.`, you will need to either delete the existing Transcriber folder, or rename the existing one. Or install to a custom directory by replacing NEW_FOLDER_NAME in the following command: `git clone https://github.com/Noah-Jaffe/Transcriber.git NEW_FOLDER_NAME`._
110-
1. Enter the Transcriber directory in the terminal
111-
`cd Transcriber` or `cd ~/Documents/Transcriber`
107+
1. Clone the Transcribble repo:
108+
`git clone https://github.com/Noah-Jaffe/Transcribble.git`
109+
_NOTE: If you get the error: `fatal: destination path 'Transcribble' already exists and is not an empty directory.`, you will need to either delete the existing Transcribble folder, or rename the existing one. Or install to a custom directory by replacing NEW_FOLDER_NAME in the following command: `git clone https://github.com/Noah-Jaffe/Transcribble.git NEW_FOLDER_NAME`._
110+
1. Enter the Transcribble directory in the terminal
111+
`cd Transcribble` or `cd ~/Documents/Transcribble`
112112
1. Setup a python virtual environment if you want, skip this step if you are unfamiliar.
113113
`python -m venv .venv`
114114
- <a id="start-activate-venv"></a>Start/Activate your virtual python environment with
@@ -119,8 +119,8 @@ Now that you have all of the requirements installed we will install the Transcri
119119
- `source ./.venv/bin/activate`
120120

121121
1. <a id="pip install"></a>`pip install -r requirements.txt`
122-
- if the pip install fails try `pip install -r explicit_requirements.txt --no-cache`
123-
- if that fails, [report the issue to the maintainer or your point of contact](https://github.com/Noah-Jaffe/Transcriber/issues)
122+
- if the pip install fails try installing each package one at a time, by line as it is written in the requirements.txt file.
123+
- if that fails, [report the issue to the maintainer or your point of contact](https://github.com/Noah-Jaffe/Transcribble/issues)
124124
- The only requirements not in the txt files are `torch` `torchaudio` and `torchvision`
125125
1. Install requirements not in requirements.txt
126126

@@ -142,7 +142,7 @@ Now that you have all of the requirements installed we will install the Transcri
142142
- Example for windows:
143143
Save anywhere as "`Transcribe.ps1`"
144144
```sh
145-
cd ~/Documents/Transcriber
145+
cd ~/Documents/Transcribble
146146
# if you used a virtual environment uncomment the next line (remove the #)
147147
#./venv/Scripts/activate
148148
python main.py
@@ -151,7 +151,7 @@ Now that you have all of the requirements installed we will install the Transcri
151151
Save anywhere as "`Transcribe.sh`"
152152
```
153153
#!/bin/bash
154-
cd ~/Documents/Transcriber
154+
cd ~/Documents/Transcribble
155155
# if you used a virtual environment uncomment the next line (remove the #)
156156
# source .venv/bin/activate
157157
python main.py
@@ -201,15 +201,14 @@ To attempt patch #1:
201201
- If using a virtual environment start/activate that now. [See here](#start-activate-venv)
202202
- Run `pip install transformers==4.38.2`
203203

204-
If you are already using this version of transformers, I'm sorry but the only known workaround is to split up the original file into smaller segments, and run the smaller segments through the transcriber again. Eventually you may hit a small section of the original audio file that crashes constantly, for that you will have to transcribe by hand.
204+
If you are already using this version of transformers, I'm sorry but the only known workaround is to split up the original file into smaller segments, and then run the smaller segments through the transcriber again. Eventually you may hit a small section of the original audio file that crashes constantly, for that you will have to transcribe by hand.
205205

206-
*NOTE: v1.1.0 is in the works with an automated fix for this*
207206

208-
### How to update my Transcriber app?
207+
### How to update my Transcribble app?
209208

210209
If you followed the instructions on this readme file, or installed this repo with git:
211-
1. Enter the Transcriber directory in the terminal
212-
`cd Transcriber` or `cd ~/Documents/Transcriber`
210+
1. Enter the Transcribble directory in the terminal
211+
`cd Transcribble` or `cd ~/Documents/Transcribble`
213212
1. Update to the latest version with the following commands:
214213
`git pull`
215214
1. Re-install the latest requirements
@@ -227,14 +226,11 @@ If you followed the instructions on this readme file, or installed this repo wit
227226

228227
### How do I get rid of these ugly @debug lines in my .cha file?
229228

230-
Edit your [transcribe_proc.py](transcribe_proc.py) file to update that the line that is
231-
`DEBUG_MODE = True`
232-
to
233-
`DEBUG_MODE = False`
229+
De-select the Debug checkbox before clicking the start transcribe button.
234230

235231
### Where is the core logic for the AI?
236232

237-
See function `transcribe_file` in [transcribe_proc.py](transcribe_proc.py). Note that you can ignore the chunks that reference or are dependant on DEBUG.
233+
See function `transcribe_file` in [transcribe_proc.py](transcribe_proc.py).
238234

239235
### Yall got some Morphosyntax?
240236
In function `transcribe_file` in [transcribe_proc.py](transcribe_proc.py):
@@ -256,5 +252,6 @@ so that it looks like
256252
- [ ] Bundle into single executable to be more user friendly?
257253
- [ ] Select subframe of time to transcribe from?
258254
- [ ] Better error handling
255+
- [ ] Checkboxes for pipeline steps?
259256

260257

requirements.txt

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,16 +2,21 @@
22
# Do these first to prevent pip build errors
33
# nemo-toolkit fixes:
44
# pip version of indic-numtowords is broken, need to manually install. required downstream of nemo-toolkit[asr]
5+
# install from command line with:
6+
# pip install "indic-numtowords @ git+https://github.com/AI4Bharat/indic-numtowords.git"
57
indic-numtowords @ git+https://github.com/AI4Bharat/indic-numtowords.git
68

79
# nemo-toolkit # broken by default, install directly from specific branch on the repo
810
# @todo in the future, when the 2.4.x branch moves to main, update the requirements.txt to use main instead (main is on 2.3.2 @ 2025-07-21)
11+
# install from command line with:
12+
# pip install "nemo-toolkit @ git+https://github.com/NVIDIA/[email protected]"
913
nemo-toolkit @ git+https://github.com/NVIDIA/[email protected]
1014

1115
# Fixes for https://github.com/huggingface/transformers/issues/33552, https://github.com/huggingface/transformers/issues/36228
1216
# merged into https://github.com/huggingface/transformers/pull/36632, but we still experience the issue. An alternative fix
1317
# https://github.com/huggingface/transformers/issues/33552#issuecomment-2880032963 states we should try v4.38.2 which appears to work for some cases
1418
# @todo - occasionally check back in to see if the issue persists in the latest version of transformers
19+
# NOTE that some pip installs will update this version, so you will need to re-install the 4.38.2 version again after completing all pip installs
1520
transformers==4.38.2
1621

1722

0 commit comments

Comments
 (0)