Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
[...] The only thing really differentiating it from a CD rip is that the tracknumber field is filled with "A#" or "B#" depending on the side of the record. [...]For some reason I've never thought of that, I've juts been adding the LP side to the comments, I'm gonna retag'em all now.
I'm not sure what the standard Album List component would be doing to make that work. But you can use one of the functions to make that work:
Perfect, thank you
- Playlist formats: .xspf format full compatibility (read, edit and create). Follows the complete specification: items not found don't break playlist loading (it continues with next item). If an item is not found at the set the path, it also tries to find matches on library by query using fuzzy matching according to the playlist metadata (Title + Artist + Album + Track number or a combination of those). By default, if lock flag is not set on file, it's loaded as a locked file. Note fuzzy matching by queries may take a great amount of time on large libraries or when a lot of items are missing.
- Blank lines: new entry to check for blank lines on playlists, although they may be allowed in some formats, some players may behave incorrectly with such playlists (for ex. with .strm files)
- When retrieving paths from M3U files, lines are trimmed (blank spaces). In other words, blank lines are simply skipped for any purpose. Other formats don't allow these "errors".
- Editing metadata on playlists not created by the manager no longer fails neither warns about requiring loading/saving to update the format; now the playlist header is automatically rewritten and then the new metadata added. This change allows to edit metadata for almost any format while not having to rewrite playlists to the currently default format (i.e. allowing .xspf playlists to remain in their format even if the default one is .m3u8).
- While reading Playlist files, they are now split by lines using any of the possible escape sequence combinations and not only windows ones (\r\n). This should allow to correctly read any playlist file created in any SO (no longer limited to Windows ecosystem).
- Crash after manual refreshing a playlist with less items than the number of rows.
.xspf (XML Shareable Playlist Format ): https://en.wikipedia.org/wiki/XML_Shareable_Playlist_Format
Traditionally playlists have been composed of file paths that pointed to individual titles. This allowed a playlist to be played locally on one machine or shared if the listed file paths were URLs accessible to more than one machine (e.g., on the Web). XSPF's meta-data rich open format has permitted a new kind of playlist sharing called content resolution.In other words, query matching... so playlists may be shared as is among different users and libraries and still find matches (no matter the physical media structure). Note this is different to autoplaylists, since the latter looks for any track satisfying an arbitrary condition (GENRE IS ROCK), while the former specifically looks for tracks (U2 - One) which may be present or not on the library. An XSPF playlist will never output more tracks than those written on the playlist (contrary to an autoplaylist which allows duplicates and has no fixed size). (*)
A simple form of content resolution is the localisation of a playlist based on metadata. An XSPF-compliant content resolver will open XSPF playlists and search a catalog for every title with <creator>, <album> and <title> tags, then localise the playlist to reference the available matching tracks
There is an example playlist on the repo, attached here too. Put it on the playlist tracked folder and load it, it will try to find matches on your library. It's a collection of 800 tracks from the 90s so it should easily find at least some of them.
(*) Someone may notice I have explicitly disabled XSPF to be used as 'saving' format, such playlists need to be created manually first with a text editor or another player. Then items can be added with SHIFT+L. Button, metatada edited, etc.. I will change this after enough testing.
(**) This is obviosly similar to 'Import track list' tool at Playlist-Tools-SMP, but XSPF being an XML playlist also allows metadata and paths to work as an standard playlist too. It's also universally supported by other players (mostly Unix).
I've written an audio player for myself in Java (I know, I know - far not the best choice for desktop software, but - it works).
It's called Sonivm and can be downloaded from here: https://github.com/mvmn/sonivm/releases
Requires Java 8+ to be installed.
The actual playback part is based on platform-native FFMPEG (thanks to FFSampledSP library), so that should work fine because FFMPEG is quite mature.
Features that are already there:
- LastFM support
- CUE-sheets support (with gapeless playback for consequent CUE tracks)
- FLAC, OGG, MP3, M4A support etc (thanks to FFMPEG again)
- Smarter repeat (repeat playlist, single track, consequent tracks from same artist or same album)
- Smarter shuffle (shuffle in whole playlist, or for same artist, or for same album, or for same genre)
- Convenient search in play queue
- Drag&drop files into play queue (as you'd expect, but not supported by some players written in Java like JLGUI for example)
Features planned for the future:
- Music library support (scan folders for audio files, filter by artist/album/year range/genre etc)
- Rating and tagging of tracks/albums/artists
- Smart party shuffle (specify filter for year ranges, artists, genres, tags, track rating etc)
- Gapeless playback for individual files
- And if I manage to pull it off: WinAmp classic skins support
Feedback is welcome
It seemed to work for me but the particular WAV I tried didn't have embedded artwork so I don't know if that would be preserved.
Tagging for WAV files is not well-standardized or widely supported and there may be some differences with ID3 tags.
...MP3Tag is pretty convenient because you can select a whole album and fill-in all of the common information at once before adding/editing the title & track number and anything else unique to each tracks.
thx @kode54 but setting up the settings for foo_vgm is a bit too complicated... sry..