Description of problem: A significant part of my audio tracks seems to be not visible, or not recognized by Clementine, even with a full library scan. In my case the classical 'update songs set unavailable=0' workaround (https://github.com/clementine-player/clementine/issues/2746) is not efficient. They are visible, readable and playable with other players. Version-Release number of selected component (if applicable): V1.4.0 R.0.rc1.423.1.mga8 How reproducible: Always(even by uninstalling completely Clementine and suppressing by-hand its .config/Clementine folder and reinstalling it). Steps to Reproduce: 1. Find that music tracks are missing from Clementine's library 2. Launch a library rescan 3. Find that you get no result.
The problem is solved, at least at my level : it comes from the CD extraction tool of Clementine which doesn't recover properly the metadata of tracks and albums. When I use Sound Juicer to extract music from CDs, everything works well and Clementine finds back the tracks without any problem. That's a bit strange that it is not able to use correctly its own extraction tool !
Just in case... I was astonished to find that Clementine has no Help. I found this: https://livingthelinuxlifestyle.wordpress.com/2020/02/28/clementine-music-player-tutorial/ which is rather good. I imagine you know it. Searching the page for 'scan' found useful things like: "To update the library, click Tools and Update Changed Library Folders. To rescan the library, click Tools and Do a Full Library Rescan. When you add a new folder, Clementine will scan the folder and add the contents to your library. [It lookss like this is what is not working for you] *** It’s helpful to check Update the Library When Clementine Starts and Monitor the Library for Changes, as this will automatically update your library To rescan the library, click Tools and Do a Full Library Rescan." Can you confirm that you have tried these things - in vain? This page on its site: https://www.clementine-player.org/participate offers: "IRC Come chat with us at the #clementine channel on Freenode. Please remember to stick around after asking a question - we might be in a different timezone so won't see your question right away." "Forum Clementine uses Google Groups for its forum/mailing list/general discussion group. Support and discussion group:" http://groups.google.com/group/clementine-player Can you please try these options to explore whether your problem is known, or that Mageia's packaging might be at fault.
CC: (none) => lewyssmithStatus: NEW => NEEDINFO
Hi Lewis, I have been using Clementine and the options you mention for a lot of time. There is no tuning in the application which solves this problem. It's a fact that the embedded extractor function has never worked properly. Until a recent date, I did not success at all to extract my music tracks in format OGG and I'm not so astonished that despite some improvements, it's still unreliable. Clementine has a file manager which enables to see the extracted files, but they cannot be moved and on the contrary of regular files, metadata cannot be accessed and modified. Something seems wrong in the format of extracted files. The only solution is to use an alternative tool : Sound Juicer is perfect for that, and to inform Clementine's team but sorry, I really get no time for that.
(In reply to Michel AUTEM from comment #3) > The only solution is to use an alternative tool : Sound Juicer is perfect > for that, and to inform Clementine's team but sorry, I really get no time > for that. Hélas, neither have we! We cannot enrol on every application forum when something like this crops up; it is much better that the end user does so. If you do get round to it, cite this bug URL in your post so that you do not have to repeat the whole story. Do other Linux users see the same problem? If I am closing this 'wontfix', that really means 'cannotfix'. At least until Clementine replies with either an explanation (Mageia's fault), workaround, or fixed new version. You can re-open this bug for the first & last; or just add a comment for the 'workaround' case even though the bug is closed, to help other users.
Keywords: (none) => UPSTREAMResolution: (none) => WONTFIXStatus: NEEDINFO => RESOLVED