You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing open and closed issues
Software version
3.3
What operating system are you using?
MacOS 11.7.10
What GPU are you using?
No response
What problem did you encounter?
This has happened a few times - maybe from me crashing a quad - but I sometimes get the situation where I open some files and the SRT file doesn't appear to open. If I look at the little cli window I get, I can see the error message:
2024-05-24T09:52:12.299280Z ERROR backend::srt::srt_file: error: Failed to parse data from STR file, source: field `bitrate_mbps` parse failed.
at backend/src/srt/srt_file.rs:18
in backend::srt::srt_file::open with path: "/Users/wayneandrews/Desktop/WalkSnail/Recordings/AvatarG0032.srt"
If I then look in the SRT file, I can indeed see that we have some odd/corrupted data in the last line of the file:
If I go ahead and simply edit the SRT file to take the dodgy entry out (making sure to remove the blank line as well, as it also throws a wobbly at that. Then I can process the file without a problem.
My thinking that it would be useful to include an option where you could ignore any lines you couldn't parse - perhaps with some warnings, rather than not let the use see any of his recording with the OSD
Link to screenshots
No response
Link to video, OSD and font files
No response
Log output
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Software version
3.3
What operating system are you using?
MacOS 11.7.10
What GPU are you using?
No response
What problem did you encounter?
This has happened a few times - maybe from me crashing a quad - but I sometimes get the situation where I open some files and the SRT file doesn't appear to open. If I look at the little cli window I get, I can see the error message:
If I then look in the SRT file, I can indeed see that we have some odd/corrupted data in the last line of the file:
If I go ahead and simply edit the SRT file to take the dodgy entry out (making sure to remove the blank line as well, as it also throws a wobbly at that. Then I can process the file without a problem.
My thinking that it would be useful to include an option where you could ignore any lines you couldn't parse - perhaps with some warnings, rather than not let the use see any of his recording with the OSD
Link to screenshots
No response
Link to video, OSD and font files
No response
Log output
No response
The text was updated successfully, but these errors were encountered: