pietrop / subtitlescomposer-app

A simple os x desktop app built in electron, using Aeneas under the hood to generate captions files from media(audio or video) and plain text transcriptions without time-codes.

subtitleComposer App

A simple os x desktop app built in electron, using Aeneas under the hood to generate captions files from media(audio or video) and plain text transcriptions without time-codes.

Usage

1. --> See user manual for more details <--

2. Go to release section and download, packaged version, ready to use version.

Dev setup

git clone, cd into folder, npm install, npm start.

Build

After having done step fo dev setup, do

npm run build:mac

To package dmg for mac, when done, check the ./dist folder in the repo.

There's also a travis CI continuos integration build that is triggered on very commit for the Linux version, some notes on this setup here

Stack

The app uses electron, bootstrap with bootswatch paper theme, and purpously does not make use of any front end framework to keep things simple a this stage, where the UI/UX and functionality are being defined.

For the alignement it uses the Aeneas open source project, see user manual for more details on how to get setup with that locally.

Issues

Feel free to get in touch if you have any issues, thoughts, questions, or ideas.

Active Contributors

• Pietro

subtitlescomposer-app's Issues

Alignment Process Fails

I use the sample "Sonnet" from the original Aeneas project, however, other language samples and formats lead to the same situation: The attempt of aligning a text to an audio file just gets always stuck. The button changes to "processing ", that's it.

Aeneas was already installed on the Mac, but I also installed it again using the linked DMG.

Are there any suggestions how to find out what could cause the alignment process to always fail? THX!

Select already segmented Text file as input

Is your feature request related to a problem? Please describe.

Current file import, removes any line break and re run the pre-segmentation steps.
Unable to add/use a file has been pre-segmented already.

Describe the solution you'd like

Have an option to import a pre-segmented file in alternative to the plain text one.

Describe alternatives you've considered

NA

Additional context

It be good to add this as an additional option vs replace the current input.

Request by Michele Gianella

Adjust Subtitles

Is your feature request related to a problem? Please describe.

A way to automatically adjust/fix subtitles to be more in line with TED guidelines.

Describe the solution you'd like

A checkbox, on by default, that runs a separate function to provide a second pass to add those fixes programmatically.

Describe alternatives you've considered

NA

Additional context

• There is a subfixer9 executable that provides those changes. which can be used as ./subfixer9 -file TestFile.srt 20.999 -speed_epsilon 0.5 however it be good to look a the code, and see if this can be brought into the app as a node/js module, to keep consistency with the rest of the project.

Request by Michele Gianella

captions output not utf-8

as raised by @bfasenfest the caption output, from Aeneas, is not utf-8 when imported in Premiere. This is noticeable because the special characters, are mumbled up.

Change "Head Tail" and "End Tail" options to "Start sync at" and "Stop sync at"

Is your feature request related to a problem? Please describe.

"Head Tail" and "End Tail" options are difficult to recognise what the functionality do for the user. And not immediate for the user to compute in case of the "End Tail".

Describe the solution you'd like

• To replace the text "Head Tail" with "Start sync at"
• To replace the text "End Tail" --> "Stop sync at"

And the duration of the synchronization interval should be calculated accordingly for the second option. Coz Aeneas takes it as "Head Tail" and "End Tail".

Describe alternatives you've considered

NA

Additional context

Request by Michele Gianella

Characters per Line default to 42 instead of 35.

Is your feature request related to a problem? Please describe.
To follow Ted Talk subtitles specs of 42 char per line.

Describe the solution you'd like
Characters per Line default to 42 instead of 35.

Describe alternatives you've considered
Keep it to 35

Additional context

Request by Michele Gianella

BBC Guidelines, say 37 for Broadcast, Youtube I think is 35 (can't find a link), and Netflix seems to be 42

Adding input format of type "subtitle"

Could you please consider to add files of type "subtitles" as an input option?

https://www.readbeyond.it/aeneas/docs/clitutorial.html#input-text-formats
https://www.readbeyond.it/aeneas/docs/textfile.html#aeneas.textfile.TextFileFormat.SUBTITLES

Thanks a lot!

Possibility to set output destination & file name for srt file

Is your feature request related to a problem? Please describe.

Default srt output is on Desktop. User's asked for more flexibility, eg when working external drives.

Describe the solution you'd like

Possibility to set output destination & file name for srt file

Describe alternatives you've considered

NA
Additional context

NA

Remember Aeneas appImage path on Linux

Is your feature request related to a problem? Please describe.

When opening the app on linux you need to set the path to the Aeneas AppImage.
If you close and re-open the app you have to re-do that every time.

Describe the solution you'd like

It be good if it could retain the path of the executable app image. so that when re-opening the app it will work. If the executable has not been moved.

Describe alternatives you've considered

re-connect it every time the app is opened.

Additional context

• closer look at handling the "edge case" where the executable has been moved
• applies to linux only at the moment as Mac users do a system wide Aeneas installation. Altho Mac users could use a Mac executable as well, to make the process a bit cleaner as well.

Request by Michele Gianella

Some characters and symbols in file name cause issues when trying to generate a caption via Aeneas. eg `(`

Describe the bug
Some characters and symbols in file name cause issues when trying to generate a caption via Aeneas.

The issue might be: "How to properly escape characters and symbols not allowed in (unix) file path"?

To Reproduce
Steps to reproduce the behavior:

1. npm start
2. add a video, that contains a ( in the name
3. add a tex file transcription of that file
4. click create subtitles
5. click cmd + alt + i and read the error message.

Expected behaviour
Expect to be able to add any video/audio file name in respective of whether it contains characters and symbols not allowed in unix file path.

Screenshots

Desktop (please complete the following information):

• Device: Mac OSX
• OS: 10.12.6
• Version: 1.8.7 - subtitlesComposer-app

Additional context
Need to double check a list of char an symbols not allowed in unix

• What characters are forbidden in Windows and Linux directory names?
• Naming Files, Paths, and Namespaces

Also needs double checking if that is the actual problem, as it might be something else. As ( does not seem to be in that list.