Audio-Files in mp4 Container are not found

Issue description:

When i let Symfonium scan for music the files, the files in mp4-Containers (***.mp4; only with aac-audiostream, 2 channels, no video channel) are not found. They can be played when i look for them about “Files”, but they are not displayed under “Titles”, “Artist”, “Albums” etc.
All my other apps (aimp, poweramp, hifi-cast an more) are able to find an list these titels/ files in these categories.

What is the reason? What i have to do? (I won’t to do changes at these 100-200 files)

I uploaded one file “12345.mp4”.

Logs:

Upload description: no log

Additional information:

 

 

Reproduction steps:

 

 

Media provider:

Local device

Screenshots:

     

Funny how despite writing logs are mandatory everywhere, people still continue to think that they are not and check the box saying they have uploaded the logs when they don’t …

All I can guess is that your device returns a video mimetype for those files, tries to rename them to m4a to confirm.

Thanks, rename solves it, now all files are displayed and played.
Don’t have to get so excited because the log-File. This file was obviously not necessary to give the right answer.

Now all is fine with your app! :+1:

When developing software, especially complex applications like Symfonium, logs play an essential role in diagnosing and solving issues that users report. Logs capture detailed information about the app’s behavior, errors, and interactions with different system components, allowing developers to trace the root cause of any problem. This is why we often ask users to submit logs when reporting an issue.

Making logs mandatory is not a random or arbitrary decision. It’s a necessary step to efficiently resolve issues, improve the app, and ultimately ensure that users have the best possible experience. When logs are missing, developers have to guess the cause of the issue, often leading to prolonged troubleshooting times, unnecessary back-and-forth communications, and delayed fixes. It’s not just about simplifying our job as developers—it’s about getting to the solution faster for the benefit of the user.

Unfortunately, there are instances where users ignore this requirement or, worse, claim to have uploaded logs when they have not. This creates several problems:

  1. Wasted Time and Effort: Without logs, any work spent trying to replicate or diagnose the issue is largely speculative. Developers may spend hours following false leads, when the logs could have provided an immediate answer. This is inefficient and takes time away from addressing other users’ issues or working on app improvements.
  2. Delayed Solutions for All Users: When a problem isn’t resolved quickly due to missing logs, not only does the user who reported the issue have to wait longer, but other users who might be experiencing the same problem are also left without a solution. In this way, ignoring the log requirement impacts the broader community.
  3. Strains Developer-User Trust: Reporting that logs have been uploaded when they haven’t can damage the trust between developers and users. We rely on transparency and honest communication to fix issues quickly. When this trust is broken, it complicates the process and leads to frustration on both sides.
  4. Disrespect for the Effort Involved: Developing, maintaining, and improving an app like Symfonium requires significant time, expertise, and dedication. When a user disregards the request for logs, it can feel like a lack of respect for the work developers put into making the app better. Providing logs is a simple but crucial contribution users can make to help improve the app they use.

At the end of the day, both developers and users share the same goal: to make the app function as smoothly and efficiently as possible. Logs are a key part of that process, and adhering to the guidelines when reporting issues is a sign of respect for the effort, expertise, and time that goes into app development.

So when we ask for logs, it’s not a formality or an unnecessary hoop to jump through. It’s because they are the most direct and reliable tool we have to fix problems. Ignoring the rule or being dishonest when filling out the issue form isn’t just frustrating for developers—it delays the very solution the user is hoping to get. Please remember that we are all working toward the same goal, and following these rules helps us get there faster.