Bug 481383

Summary:	Opus files metadata/collection support
Product:	[Applications] amarok	Reporter:	Michael <junkmailsink>
Component:	general	Assignee:	Amarok Bugs <amarok-bugs-null>
Status:	REPORTED ---
Severity:	minor	CC:	amarok-bugs-null, bugs.kde.org, martin, mrypsilons, tuomas
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	kf5
Platform:	unspecified
OS:	Microsoft Windows
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Bug Depends on:	312905
Bug Blocks:

Description Michael 2024-02-15 21:38:16 UTC

+++ This bug was initially created as a clone of Bug #312905 +++


SUMMARY
Bug #312905 is still going strong. Amarok 2.8.0 for Windows (which is the current version, although it's not available to be selected in the bug tracker as the affected version: https://community.kde.org/Amarok/GettingStarted/Download/Windows ) will not add opus files to the collection when they are scanned, and will not read their metadata if they are manually played.

Steps to Reproduce:
1. Put an opus file into the collection folder (.opus / .ogg)
2. refresh collection
3. open the file directly
Actual Results:  
1-2: Amarok doesn't add the opus files to the collection
3: Amarok isn't able to read the metadata of the file

Expected Results:  
1-2: Opus files should added to the collection with metadata
3: Metadata should be determined


SOFTWARE/OS VERSIONS
Windows: 10 Home 22H2
(available in About System)

"KDE Platform Version 4.11.00"

KDE Plasma Version: might or might not be 4.11.00?
KDE Frameworks Version: might or might not be 4.11.00
Qt Version: 4.8.5

ADDITIONAL INFORMATION
Amarok can neither import Ogg-Opus files into the collection nor read their metadata if you directly add the file to a playlist.

Amarok plays the file itself fine. It's only the metadata which is not detected.

Comment 1 Tuomas Nurmi 2024-04-16 15:51:53 UTC

Amarok 2.8 was released in 2013. As far as I know, that is the latest Windows version in existence. I assume this bug would be fixed if someone built a new Windows version (with a TagLib version > 1.9). I am not aware of anyone planning on doing that, but I guess it is not impossible that someone might do that after 3.0 release. (No idea how much fine-tuning the codebase would need to get the Qt5/KF5 changes since 2018 compile & run on Windows, possibly not too much)