Phenomizer expects a list of strs, not one giant str #236
Labels
No Label
bug
duplicate
enhancement
help wanted
insufficient info
invalid
news
not a bug
question
wontfix
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: mrq/ai-voice-cloning#236
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
On a Ubuntu 22.04 LTS environment, running the latest commit of this repo (
74bd0f0cdc
) when I attempt to phenomize, I'm running into this issue:I think simple enough to fix, but I wasn't sure if there's an easier way (aside from brute force regex) to strip the Whisper-generated transcript of extra punctuation and whitespace.
Oh right, I forgot that instantiating the phonemizer backend yourself rather than using its API to instantiate one-use backends requires it to be by array rather than string.
I'll see what I can do with whatever environments I have left.
Fixed in commit
cbe21745df
. Apologies.I noticed in the VALL-E implementation I did hotfix this with
text = [ text ]
, and I suppose I neglected to copy that part when I was porting it over to "fix" the memleaking when using the phonemizer there for IPA-based tokenizers (which I honestly haven't touched in ages now; the phonemizer for VALL-E datasets get handled through the VALL-E module).Thanks, that commit fixed the phonemizer. I am running into a new problem when trying to train on the phonemized Whisper transcript (I had no issues with the vanilla tokens).
I am running into the same AssertionError when tring to train on a phonemized script, any updates on that issue?
Ok, found it, the phonemizer also outputs the phonemized text as a list. I just fixed it in my train.txt for now, but the assertion error is gone and training is running without problems so far...
Hi stlohrey, can you explain the solution for this assertion error? In which way did you edit the train.txt?