as you can see, the issue is that the newlines in the file laxTrainWavList.txt aren't being detected. It turns out this because she saved it in an editor which used the Macintosh '\r' convention for newlines, and these open commands in auto_vot_extract_features.py only work if the textgrid_list and wav_list have '\n' newlines:
you can get around this kind of issue by using open( x.txt, 'rU') instead of open(x.txt) -- see here in the "in addition to the standard.." paragraph.
Since it will probably be common that users save their text file on a Mac or Windows text editor, should we change these lines (and any others in the .py scripts) to end in ,'rU'?
A student of mine is using autovot, and got this error when she tried to use wav and textgrid files for training:
as you can see, the issue is that the newlines in the file laxTrainWavList.txt aren't being detected. It turns out this because she saved it in an editor which used the Macintosh '\r' convention for newlines, and these open commands in auto_vot_extract_features.py only work if the textgrid_list and wav_list have '\n' newlines:
you can get around this kind of issue by using open( x.txt, 'rU') instead of open(x.txt) -- see here in the "in addition to the standard.." paragraph.
Since it will probably be common that users save their text file on a Mac or Windows text editor, should we change these lines (and any others in the .py scripts) to end in ,'rU'?