-
Notifications
You must be signed in to change notification settings - Fork 17
MPEG-4 audio file not working correctly #21
Comments
Sometimes no, sometimes yes. I can't predict if it'll appear normally. It doesn't seem to be format-specifc either, as I've had this issue with FLAC and MP3 files now. In my tests I've noticed it doesn't seem to happen with OGG or WAV files though. |
it seems to be just GStreamer reporting the duration incorrectly. can you check if the issue happens when you play a file for the first time (i.e. immediately after opening decibels) or play it after playing another file. |
It happens regardless of how I open it. |
This bug now also happened to me. When this issue appears, the following message is printed on the console:
This happens with all my Bildschirmaufzeichnung.vom.2023-12-16.03-16-25.webm
Hmm, that's weird. For me, it happens just as often when opening the files through the app. |
Can you check if this hasn't been solved in the recent commits? |
It definitely hasn't been fixed (I tried 0.1.7-d386eae). I have even found an album whose mp3 files always reliably crash the new version of decibels, but not the last stable version from flathub. |
The issue seems to occur when a file (or different files) is repeatedly opened quickly right? |
No, it occurs randomly and seems to have nothing to do with the speed. Also, I have found out exactly which mp3 files cause the program to crash. Since a basic MP3 file is just a raw series of audio frames, a program normally wouldn't be able to find out the audio file's length. Decibels now seems to have issues with mp3 files not including this metadata because it can't accurately find out the audio length. You can convert any song to a "stripped" mp3 file via ffmpeg (causing decibels to not respond):
|
Thanks, @BlobCodes, for diagnosing this issue. It turns out that GStreamer returns an "undefined" value when it can't get the duration of a track initially. However, that "undefined" value is actually The issue is that that value is larger than The solution is somewhat of a workaround, as we now have a function called Please test the changes and let me know if anything has changed by downloading the latest artefact. Thanks! |
For me it never gets updated to the actual length, see video Screencast.from.2024-02-23.17-45-46.webm |
When I play this specific audio file, the display bugs out and I can't scroll through the sound file:
![image](https://private-user-images.githubusercontent.com/74428438/273479478-7130df74-8f9d-4a7b-be96-44d5a7c110a1.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjUxMjI5NDIsIm5iZiI6MTcyNTEyMjY0MiwicGF0aCI6Ii83NDQyODQzOC8yNzM0Nzk0NzgtNzEzMGRmNzQtOGY5ZC00YTdiLWJlOTYtNDRkNWE3YzExMGExLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MzElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODMxVDE2NDQwMlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTFkYjVhYzFhMjA4M2E1ZjRhMTY5MmI1YzJjNWU1YzhjMWFhNDhkNmVhNDE1Y2RjMDgyMjMyMmE3NmUwNjIxZDAmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.hcwVEIEXI5kPno46zlhbaeRgxmU4LDuiG_FzwxSFGKg)
I can still skip ahead or back using the buttons next to play/pause. Everything works except for scrolling.
I've tested this with other M4A files and the same thing happens.
The text was updated successfully, but these errors were encountered: