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
Description of the the bug
While running deew in a Ubuntu VM, my vdisk wasn't large enough (only 25GB). So when encoding certain files, it would run out of space. However this wasn't clear because deew swallowed the real exception from FFMPEG and continued on as if it was successful. By manually running the ffmpeg step myself I was able to find the real issue. How this would end up presenting though deew would be:
Run deew for a set of files
ffmpeg portion runs
Behind the scenes a .wav file is generated but it is incomplete because ffmpeg ran out of space to write the file
deew starts the measure step
Exception is thrown:
wav: DEE Exception: Mediainfo xml parse failed (-1).
input[0]:audio[0]:wav[0]: Input stage (input[0]:audio[0]:wav[0]) run failed.
Version
deew 3.2.1
OS
Ubuntu 24.04 LTS
The text was updated successfully, but these errors were encountered:
Hmmm it may have been a warning, I remember it was highlighted in red, but I fixed the vdisk size on my VM so I can't replicate it anymore. Either way, the issue ends up suppressed when ideally deew would see that the wav has issues during its export and not use it.
Thanks! I'm sure it would save someone else a ton of digging in the future if they did the same thing I did. At the very least having my issue documented here should at also make the error message more searchable.
Description of the the bug
While running deew in a Ubuntu VM, my vdisk wasn't large enough (only 25GB). So when encoding certain files, it would run out of space. However this wasn't clear because deew swallowed the real exception from FFMPEG and continued on as if it was successful. By manually running the ffmpeg step myself I was able to find the real issue. How this would end up presenting though deew would be:
Version
deew 3.2.1
OS
Ubuntu 24.04 LTS
The text was updated successfully, but these errors were encountered: