flactag Activity
Brought to you by:
adhawkins
Activity for flactag
-
Andrew Hawkins committed [e1fa64] on Git
Fix missing include
-
Add missing source files for progress bars test
-
Reduce number of queries to MusicBrainz server
-
Handle exceptions when requesting Amazon cover art
-
Add more info about selected album
-
Use iconv to create filesystem values from tags. Removes dependency on unac
-
Enable all compiler warnings and treat them as errors
-
Determine Magick++ compile definitions automatically
-
Handle PNGs retrieved from cover art archive
-
Split changelog into separate file
-
Restore ALBUMARTIST tag
-
Update copyright notice
-
Add copyright notice
-
Add StandardiseArtists option to standardise artist names
-
Add option to include album name disambiguation
-
Pass config file to MusicBrainzInfo class for future modifications
-
Add enum to define config file entries
-
Activate C++11
-
Combine MusicBrainzInfo constructors
-
Fake user agent as Amazon seem to block the flactag one
-
Use CoverArtArchive in preference to Amazon for coverart
-
Convert build to CMake
-
Patch to support discid_read_sparse
-
brainchild posted a comment on ticket #5
If you wanted a format for representing the associations between file names and metadata, then it would be a cumbersome addition to the application. For single-album invocations of the application, the need is removed to associate various metadata with particular files in the input format. An easier way may be available, however, even for the bulk case. It is unlikely that all available values for barcode or another field in a collection intersect with multiple possible values for any file. Thus,...
-
It's possible that there was a migration of forum software when the Slimdevices brand was taken over by Logitech many years ago. I'm afraid it's a long time ago so I can't really remember! I've just done a quick search for all my posts, and it looks like I announced flactag in 2006. My memory is that I got the tag format from the forums around that time, but the search doesn't seem to be finding it. I did find some similar discussion here, which recommends the scheme I'm using: https://forums.slimdevices.com/showthread.php?9184-FLAC-Cue-Sheet-Support&p=23555&viewfull=1#post23555...
-
I searched the forum for posts made using your handle, and found a good number of hits, but noticed none that address this particular topic. I did find your announcements of the release of the software. Do you suppose the earlier discussions may have been lost in some system-wide event, such as migration to new forum software? Otherwise, do you think you might misremember the forum in which you discussed the specific topic, since you obviously have given the LMS forum quite a bit of contributions?...
-
Hi, I had had some success with other software players using the scheme that Flactag uses. I think that foobar works, although I wouldn't be 100% sure. As far as documentation goes, I think I got that scheme through a discussion on the LMS forums. It might be worth a search on there to see if you can find any of the posts I made and their responses. My username is 'adhawkins' on there. I had a quick look and couldn't see it, but I didn't spend that much time on it I'm afraid.
-
At the moment, flactag seems to be the only utility that reads TOC or cue data, computes a MusicBrainz Disc ID, fetches releases data, and applies them to an audio file that captures a full disc. MusicBrainz has developed its own tagging tool, Picard, which is tightly integrated with the design of the service, but the only current support in the project for whole-disc files so far has been as a vaguely-specified item on a long list of possible future features. I have casually tested the tags generated...
-
Well, the straightforward answer, though it may seem evasive, is that given a choice between two data sets, the minimum necessary information for resolving the choice is at least some of the differences. At the moment, the application displays a static set of fields for each option, such that, in many cases, all fields are identical across the multiple matching releases. A truly complete solution would allow the user to explore the differences. Although such a solution may be more complicated, for...
-
That's a fair point about adding additional information like barcode etc. I'll consider that. I keep saying I'll get back to flactag to make some much needed additions, but never seem to find the time. Regarding the tagging, I think I asked on the forums all those years ago, and that's the advice I was given.
-
Well, the straightforward answer, though it may seem evasive, is that given a choice between two data sets, the minimum necessary information for resolving the choice is at least some of differences. At the moment, the application displays a static set of fields for each option, such that, in many cases, all fields are identical across the multiple matching releases. A truly complete solution would allow the user to explore the differences. Although such a solution may be more complicated, for both...
-
What extra information do you think is necessary to be able to make the decision as to which release to choose? The interactive interface for flactag is quite 'busy', so I tried to keep the information in there to the minimum. Regarding the formatting of track information, this scheme is (I believe) fairly standard. The music server I use (Logitech Media Server) uses this scheme, and it's what flactag's scheme was based on. It certainly wasn't something I invented myself.
-
The use case I am considering is attaching a set of basic metadata, needed for selecting an asset from others in a library, to the file that contains the related music. The relevant question is less about viewing the full record from MusicBrainz, and more about having a way to select the best match from a list. If this use case is important, then it may be useful to consider how feasible it is for a user to make this choice manually, based on the way the interactive interface presently is arranged....
-
All good points. At the end of the day, flactag isn't really supposed to be a MusicBrainz data or tag viewer. All of the information is visible on the MusicBrainz web site given the album ID. Glad you're finding the app useful. It's definitely in need of some updates.
-
I understand your response. A number of small issues come to mind, in case you are considering further enhancements at some time. Consider the following: The error messages are confusing. No method is offered to express rules for automatic resolution, such as country preferences. Often, the information displayed in the interactive session lacks the fields needed to make the correct choice. For example, text would often be the same, or differ only slightly, whereas the important difference would be...
-
I understand your response. A number of small issues come to mind. Consider the following: The error messages are confusing. No method is offered to express rules for automatic resolution, such as country preferences. Often, the information displayed in the interactive session lacks the fields needed to make the correct choice. For example, text would often be the same, or differ only slightly, whereas the important difference would be country, catalog number, or barcode. Further, small differences...
-
Hi, Essentially, you need to run in interactive mode, and choose one of the offered releases, writing its tags to the file. The MusicBrainz Album ID is listed in the tags to be written if you copy it to the bottom window, along with all of the other tags for that release on MusicBrainz. You need to examine these tags (which will include things like barcode etc.) to determine which of the offered releases matches the one you actually own. Once these tags have been written, future 'batch' sessions...
-
confusing handling for multiple releases
-
Fooby posted a comment on ticket #4
OK, I successfully imported the CUE file–metaflac --import-cuesheet-from=<file> and now flactag works. You could implement this I think. You could first test for an embedded CUE.
-
OK. Thanks. Just because nobody has expressed a desire for this feature doesn't mean they wouldn't appreciate it once they knew about it. They just don't know that yet. ;)
-
The CUE sheet is read from the FLAC file using libflac, the library that is part of the FLAC suite. Generating a CUE sheet from the data in the FLAC file is a lot simpler than attempting to parse one from text format. As I said, thus far nobody else has expressed a strong desire to have flactag handle external CUE sheets. However, I will consider it as a future enhancement.
-
Which library? It doesn't have the ability to work with an external CUE sheet? I see that flactag has an option to create a CUE sheet file. I think your tool would have much more universal appeal if it could operate on CUE sheet files if an imbedded CUE sheet were not found.
-
I'll look into it, but that would involve parsing the CUE sheets directly, rather than using the FLAC representation of them via the library that is available. One thing I will say, is that in all the time since I wrote flactag, you're the first person that has raised the lack of support for external CUE sheets as an issue...
-
Well, first of all, I installed it via homebrew, so I didn't have any way of knowing. Second, I think you are severely limiting your potential user base. It seems fairly obvious to me that most album flacs come with a separate CUE sheet so that would constitute a much larger audience. How hard could it be to add this feature?
-
Hi, The description of the software on the Sourceforge site is: "flactag is a tagger for whole-album FLAC file with embedded CUE sheets, that retrieves data from the MusicBrainz service." I think that's fairly clear. I will try to remember to update the man page also to make this more obvious. The ripflac script that comes with flactag shows how to embed an existing CUE sheet into a FLAC file. Andy
-
A search of the man page reveals one reference to the word embedded in the context of ripping. What about the many cases of an already ripped CD with an external CUE sheet, which is the norm? A simple error message indicating that an embedded CUE is required would have eliminated this whole thread. It's not like this is a common experience.
-
A search of the man page reveals one reference to the word embedded in the context of ripping. What about the many cases of an already ripped CD with an external CUE sheet, which is the norm?
-
A search of the man page reveals one reference to the word embedded in the context of ripping. What about the many cases of an already ripped CD with an external CUE sheet, which is the norm?
-
No CUESHEET found for 'whatever flac file I try.flac'
-
The man page does make reference to embedded CUE sheets. The 'ripflac' script that comes with flactag shows how to create a whole album FLAC file with an embedded CUE sheet. Andy
-
Well, first of all, what is an embedded cue file? I've ever only seen external ones. Second why such an extreme limitation? And why no mention of this limitation in the help, such as it is?
-
That's your issue. flactag works with embedded CUE files, not seperate ones. Andy
-
Way too big! It doesn't matter which file I try. cue sheet has same name as flac file and is in same directory. BTW, shnsplit and cuetag.sh work just fine with all files.
-
Way too big! It doesn't matter which file I try. cue sheet has same name as flac file and is in same directory.
-
Please provide a FLAC file that exhibits this problem. Thanks Andy
-
No CUESHEET found for 'whatever flac file I try.flac'
-
Daniel Pocock committed [346d0a]
checkflac: make script more resilient for filen...
-
Larry Gilbert posted a comment on ticket #2
One more detail: I discovered this error when attempting to build against version...
-
Patch for compilation error in CoverArt.cc (boolean vs. bool)
-
Daniel Pocock committed [827399]
discid: exit non-zero on error
-
Daniel Pocock committed [cd14b5]
Default to /dev/cdrom, allow override
-
Daniel Pocock committed [264512]
checkflac: exit non-zero on error or mismatch
1
