Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: Include granularity #6

Open
MysteryPancake opened this issue May 23, 2019 · 6 comments
Open

Suggestion: Include granularity #6

MysteryPancake opened this issue May 23, 2019 · 6 comments

Comments

@MysteryPancake
Copy link

MysteryPancake commented May 23, 2019

As stated in the README:

A text fragment can have arbitrary granularity:
a paragraph,
a sentence,
a portion of a sentence (i.e., a group of words),
a word, or
a phoneme (i.e., a single sound).

This information would be useful to include in the table.

While aligners such as Gentle and SPPAS allow phone-level alignment, others such as aeneas can only perform word-level alignment.

Perhaps there could be a column indicating the granularity of each aligner?

@ArtemisZGL
Copy link

i think the Maximum length of audio and the granularity can be really useful

@DonaldTsang
Copy link

DonaldTsang commented Jan 22, 2020

Can someone here please start editing the page?
It appears that @pettarin has been inactive for one and a half years
same goes for Aeneas which is co-owned by him.
EDIT by AP: removed link to an irrelevant page
His email would be EDIT by AP: removed email address
and his twitter is EDIT by AP: removed twitter username
If it is possible please contact him.

CC to @pfriesch @peteruhrig because this project is in a bad state.

@pettarin
Copy link
Owner

@DonaldTsang I edited your post above. No need to post links that are irrelevant to the issue, albeit referencing to publicly-accessible information.

Here I replied exactly in the same way as I did in the issue tracker of the aeneas repository: the PR tab for this repository ( https://github.com/pettarin/forced-alignment-tools/pulls ) has zero open PRs. In the past, I happily merged PRs within a reasonable time ( https://github.com/pettarin/forced-alignment-tools/pulls?q=is%3Apr+is%3Aclosed ). If you want to submit a PR, I will be happy to evaluate it, and merge it if in line with the contents of the repository.

@pettarin
Copy link
Owner

@MysteryPancake that is indeed a useful suggestion.

@DonaldTsang
Copy link

DonaldTsang commented Jan 23, 2020

@pettarin the reason I posted the contacts, is that your GitHub has been inactive for the last year (at least in the dashboard) and I was concerned regarding your absense. Hope you can understand.

@arcman7
Copy link

arcman7 commented Oct 1, 2020

Please include the level of granularity or remove aeneas from the list.

In the readme to this repo forced alignment is defined as follows:

Given an audio file containing speech, and the corresponding transcript, computing a forced alignment is the process of determining, for each fragment of the transcript, the time interval (in the audio file) containing the spoken text of the fragment.
A text fragment can have arbitrary granularity:

a paragraph,
a sentence,
a portion of a sentence (i.e., a group of words),
a word, or
a phoneme (i.e., a single sound).

but aeneas does not provide phoneme level alignment. In the issue linked below:
readbeyond/aeneas#199

Q: Does aeneas supports phonetic level alignment?
A: In short, no. Long answer here:

I and various others as well were mistaken in thinking aeneas was an available option for phoneme level forced alignment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants