Closed John-Keyberg closed 10 months ago
I believe that the error has something to do with pressing backspace during the recording of one of the sounds included. The sound "pt-zu" was the only one in which I pressed backspace and the problem was gone after removing it.
I had the same issue on debian 12. making a new recording (where I didn't press backspace) solved it for me as well
had the exact same issue, except I used backspace for almost all the recordings!! and it took me so long to record them too... please fix this issue!
to salvage my corrupted audio files, I looped back the output of my computer as a recording input so I can make parrot listen again to everything I've already saved. It would be a lot easier though if I could just tell it to import pre-existing .wav files (that I would fix). Is there a way to do that? the [v] menu doesn't seem to include an import option but then I barely understand what most of the options do...
I've done a quick debugging and what seems to be the problem is that the SRT files that it generates when backspacing is used aren't made well. While I investigate how to fix this, there is a workaround that won't require you to re-record any sounds.
The workaround is as follows: Go to the segments folder inside of the faulty recording label and delete all the files ending with .srt. When you next open the settings page using py settings.py
, it will do resegmenting which seemed to have allowed me to learn the backspaced labels.
I'll have a crack at fixing this in the weekend.
Thank you so much for this solution! I had already wasted an hour recording again two of my folders, I am so glad that I am not going to have to do that for the others!
I am using Windows 11. Not a programmer.