From 31c6280e608b70d6dfac5fff47bbc1ecaacbf515 Mon Sep 17 00:00:00 2001 From: Christos Angelopoulos Date: Wed, 23 Mar 2022 00:12:48 +0200 Subject: [PATCH] update README.md --- README.md | 38 ++++++++++++++++++++++++++++++-------- 1 file changed, 30 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index 37ef301..a90c67d 100644 --- a/README.md +++ b/README.md @@ -19,14 +19,16 @@ https://dirk.net/2021/10/31/tts-fix-max-decoder-steps/ > sudo apt install sed yad sox jq * As a text editor I use _xed_. If you prefer, however, another text editor by default (gedit, geany, mousepad etc), please substitute __xed__ in _line 93_ of __Sapo.sh__ with the respective command of your preffered editor. - * Likewise, instead of _celluloid_ audio player, you can use any other player you prefer, like _xplayer, mplayer, smplayer, vlc, mpv etc._ Just make sure to substitute celluloid with your preffered player in lines 197 & 223 of __Sapo.sh__. + * Likewise, instead of _celluloid_ audio player, you can use any other player you prefer, like _xplayer, mplayer, smplayer, vlc, mpv etc._ Just make sure to substitute celluloid with your preffered player in line 223 of __Sapo.sh__. * The same applies for _Audacity_ and any other preffred wave editor in line 222 of Sapo.sh. While _audacity_ is not considered an absolute dependency for the functionality of the script, having a wave editor installed might as well be of use in cases, so, such a choice exists in fixing potential errors. ### SCREENSHOTS - * File selection dialogue + * File selection dialogue: + +--- ![0.png](screenshots/0.png) @@ -65,15 +67,30 @@ The lines that _possibly_ present this problem are written down in the errors.ts ![8.png](screenshots/8.png) -After that each line one by one can be examined. The user is presented with *a few options* for each line: +--- +At this point the user will be prompted to select editing: + ++ All the lines of the file, one by one, where the user can make any change they wish on any word of any line, or + ++ Just the lines that were reported with an error during their rendering. These errors have to do with the length of the line, and not with mispronounced words. --- + +![9.png](screenshots/9.png) + + +--- + + +Either way, the user is presented with *a few options* for each line: + +--- + + ![5.png](screenshots/5.png) - - --- These options include: @@ -111,8 +128,10 @@ These options include: * __🎜Edit__ the respective audio file with a wave editor(e.g._Audacity) * __✗Remove__ the respective audio file directly. + + * __⬅️Previous Line__ takes the user back to the previous line - * By hitting __😀Keep/Next__ the user can accept the audio file as is, or after correcting it, and proceed to the next. + * By hitting __➡️Next Line__ the user can accept the audio file as is, or after correcting it, and proceed to the next. **After that, the audio files from all the lines will be concatenated into one.** @@ -132,7 +151,7 @@ The list of words is growing as the script gets used more, this will be an on go A better pronunciation would be found and recorded in the sapofonetix.sed database. Thus, the percentage of the mispronounced words would be made less and less.__ -___ + --- @@ -152,10 +171,13 @@ ___ > cd ~/Desktop > > sox {1..3}f.wav final.wav -> + +--- ![4.png](screenshots/4.png) +--- + ### Sapo-fix.sh Sapo-fish.sh is the error-correcting routine included in Sapo.sh, that can be run on its own, when the user wants to correct the lines detected and written in errors.tsv.