json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) #172
Labels
No Label
bug
duplicate
enhancement
help wanted
insufficient info
invalid
news
not a bug
question
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: mrq/ai-voice-cloning#172
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?
I am once again making a bug report on something that is probably user error, but as I have no understanding on how to tell the difference, I'd rather air on the safe side here and look dumb, but know for sure.
Attempting to 'Transcribe and Process' results in a shorthand error that reads:
'Expecting value: line 1 column 1 (char 0)'
Something that presumably has to do with Whisper being unable to transcribe the .wav files- or could be related to it being unable to either access/create/modify the whisper.json file. The long form error message reads like this:
I had actually assumed that, since I couldn't get the program to work for me, I could just skip this step by manually transcribing each .wav file in the whisper.json file manually; line by line. However after doing so, and telling the program to (Re)Create Dataset, I get the exact same error message.
I am on the most recent update of the software, and I have installed it correctly for my current version of windows.
If you want to create a dataset manually you don't need to bother with the whisper.json at all, the Generate Configuration tab uses only train.txt and validation.txt (and that one is optional). I've attached an example. Per the wiki each entry must be "over 0.6s and under 11.6s and text lengths under 200 characters".
Edit: If you want to find out why it's choking when you click "(Re)Create Dataset" I'd suggest running your whisper.json through a linter.
I see, if that's the case I might not need to even fix this. I'll leave it open for now just in case, but I'll see what I can do. Thank you for pointing me in the right direction!