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
We need to find a way to render these .ogg files as they've HISTORICALLY sounded like (e.g. using Audacity on Windows) so that projects don't change sound as a result of a library update.
I find a discrepancy between the ffprobe listed length and the Audacity-shown length for three of the listed files. Assuming Audacity behaves the way LMMS does for the ogg files, these files seem to have issue:
e-organ01 sounds like a vehicle horn, so it may not necessarily seem to need fixing upon first sight, but the length of the file could cause compatibility issues.
This issue was originally reported in #dev-casual on Discord.
drums/crash01.ogg
923
ms1311
msSome baselines:
ffprobe drums/crash.ogg
shows1311
ms1311
ms923
ms923
msAccording to this article, the files are most likely at fault, quoting:
If this is true, this should be a way to detect faulty files:
Notice
crash01.ogg
appears here:We need to find a way to render these
.ogg
files as they've HISTORICALLY sounded like (e.g. using Audacity on Windows) so that projects don't change sound as a result of a library update.Tagging @StakeoutPunch @Monospace-V.
The text was updated successfully, but these errors were encountered: