I have about 2000 EAC 1.0 beta 3 and 1.3 full disc rip logs and accompanying .cue files as well.
These logs have lots of information and I am wondering for those who have dealt with them what sort of information can/should be pulled out and into musicbrainz and how (all manual entry?).
2 Likes
Look up musicbrainz disc id and freedb id from EAC/XLD log might be helpful if you’re trying to match folders to specific releases
They can be used to generate discids (as briaguya said). I think you can also identify enhanced CDs with them. Really weird accuraterip results from early 2000s CDs are often evidence of CCCDs.
.cue files, if you have those, can be used to find ISRCs and barcodes.
I am not sure how I generate the Disc ID. I put a log into the search she linked and it gave me a bogus result. Turns out the disc wasn’t in the database at all, but it is concerning it gave me a random result.
1 Like
The only part of the EAC log that needs to be pasted into that page is the TOC. A disc ID is then generated from that. Be aware that this is not perfect, but usually a good hit rate of getting the correct release.
Track | Start | Length | Start sector | End sector
---------------------------------------------------------
1 | 0:00.00 | 4:44.30 | 0 | 21329
2 | 4:44.30 | 6:23.37 | 21330 | 50091
3 | 11:07.67 | 4:27.53 | 50092 | 70169
4 | 15:35.45 | 4:24.60 | 70170 | 90029
5 | 20:00.30 | 4:59.20 | 90030 | 112474
6 | 24:59.50 | 4:21.47 | 112475 | 132096
7 | 29:21.22 | 1:57.25 | 132097 | 140896
8 | 31:18.47 | 3:50.48 | 140897 | 158194
9 | 35:09.20 | 4:45.15 | 158195 | 179584
10 | 39:54.35 | 3:48.40 | 179585 | 196724
11 | 43:43.00 | 4:19.47 | 196725 | 216196
12 | 48:02.47 | 5:24.40 | 216197 | 240536
How random is the result? A totally different artist?
Yes absolutely. Same number of tracks but completely different everything else.
It’s possible for two completely different releases to have the same discid, but that’s pretty rare. I’m guessing somebody made a mistake when submitting discIDs in the past.
As explained it can be used to identify your releases but to submit data from them you need to know the release source. Do you also have the covers?
Yes I have full scans of them, about 8k images to upload. I am more so looking to see if I should be pasting the TOC into a submission form or if there is a way to extract the ISRCs from a .cue without manual entry?
1 Like
In this case you can add the TOC indeed, what is important is to trace back to the proper release. In other words, if you are unsure to which one it belongs, better not to add it.
For ISRC not aware of an automatic extract tool from cue but you have some scripts to help: https://magicisrc.kepstin.ca/ or if the ISRCs match the digital versions you can use this https://d.ontun.es/
3 Likes
You can copy the entire cue file and paste it into magicisrc using jesus2099’s MASS ISRC script.
4 Likes
Thank you for gathering this data, and for thinking about how to contribute it to MusicBrainz.
I agree with the comment that scans of the physical releases are valuable to keep as part of the data set. It is very helpful to have the scans correlated with the log files and .cue files.
I see lots of people suggesting somewhat-automated, mostly manual tools for getting the data entered. That sounds to me like a good place to start. Once you have a workflow established, and you have a good idea which steps are repeatable and not very error-prone, you might start to wish for more automation. That may be where I can help. I am (and others here also are) good at writing simple Python programs to automate extraction of text from files, and calling MusicBrainz APIs. But trying the steps manually is an important preceding step, because that exploration tells you what the automation needs to do.
I would love to see these data added to MusicBrainz in a high-quality way, so I am enthusiastic for this effort to succeed.
2 Likes
Thanks for the support. My username on musicbrainz is also Soliloquy. I have just manually been adding a few images & releases over the last few days. Most of what I have seems to not be in the database, but that is O-K, just more work.
All of my folders also have a manually typed .info sheet which I have been using for tracklist adding. For example the last album I just added has this as it’s info sheet.
If there was a cat no or label that would be added to the info as well, but that is about it.
Info
A Pocketful Of Deng - Boxed In (2006) [FLAC] {Self-Released}
Performer: A Pocketful Of Deng
Release Year: 2006
UPC: 7 50532 96862 9Track List:
01 - Such Magic Potion
02 - Nebuchadnezzar
03 - Trixie
04 - Fungee
05 - Industry
06 - Super Bubbles
07 - EPARipped with EAC 1.0 beta 3 (log included). Scans are 600 DPI JPEG.
But that same tracklist info (+more) is on the log file:
Log
Exact Audio Copy V1.0 beta 3 from 29. August 2011
EAC extraction logfile from 30. October 2016, 2:46
A Pocketful of Deng / Boxed In
Used drive : TSSTcorpCDDVDW TS-H653N Adapter: 0 ID: 0
Read mode : Secure
Utilize accurate stream : Yes
Defeat audio cache : Yes
Make use of C2 pointers : NoRead offset correction : 6
Overread into Lead-In and Lead-Out : No
Fill up missing offset samples with silence : Yes
Delete leading and trailing silent blocks : No
Null samples used in CRC calculations : Yes
Used interface : Native Win32 interface for Win NT & 2000
Gap handling : Appended to previous trackUsed output format : User Defined Encoder
Selected bitrate : 1024 kBit/s
Quality : High
Add ID3 tag : No
Command line compressor : C:\Program Files (x86)\Exact Audio Copy\Flac\flac.exe
Additional command line options : -8 -e -V -T “ARTIST=%artist%” -T “TITLE=%title%” -T “ALBUM=%albumtitle%” -T “DATE=%year%” -T “TRACKNUMBER=%tracknr%” -T “GENRE=%genre%” -T “PERFORMER=%albuminterpret%” -T “COMPOSER=%composer%” %haslyrics%–tag-from-file=LYRICS=“%lyricsfile%”%haslyrics% -T “ALBUMARTIST=%albumartist%” -T “DISCNUMBER=%cdnumber%” -T “TOTALDISCS=%totalcds%” -T “TOTALTRACKS=%numtracks%” -T “COMMENT=%comment%” %source% -o %dest%TOC of the extracted CD
Track | Start | Length | Start sector | End sector --------------------------------------------------------- 1 | 0:00.00 | 3:45.48 | 0 | 16922 2 | 3:45.48 | 4:15.12 | 16923 | 36059 3 | 8:00.60 | 4:57.55 | 36060 | 58389 4 | 12:58.40 | 3:45.08 | 58390 | 75272 5 | 16:43.48 | 4:21.12 | 75273 | 94859 6 | 21:04.60 | 4:17.51 | 94860 | 114185 7 | 25:22.36 | 4:43.40 | 114186 | 135450Track 1
Filename G:\Station Music\A Pocketful Of Deng - Boxed In (2006) [FLAC]\01. Such Magic Potion.wav Pre-gap length 0:00:02.00 Peak level 96.6 % Extraction speed 1.7 X Track quality 100.0 % Test CRC 035B9175 Copy CRC 035B9175 Accurately ripped (confidence 1) [9E5AE85B] (AR v2) Copy OKTrack 2
Filename G:\Station Music\A Pocketful Of Deng - Boxed In (2006) [FLAC]\02. Nebuchadnezzar.wav Peak level 89.1 % Extraction speed 1.9 X Track quality 100.0 % Test CRC 06686E81 Copy CRC 06686E81 Accurately ripped (confidence 1) [6A91DE75] (AR v2) Copy OKTrack 3
Filename G:\Station Music\A Pocketful Of Deng - Boxed In (2006) [FLAC]\03. Trixie.wav Peak level 98.8 % Extraction speed 2.1 X Track quality 100.0 % Test CRC 5D407E2A Copy CRC 5D407E2A Accurately ripped (confidence 1) [434D3D65] (AR v2) Copy OKTrack 4
Filename G:\Station Music\A Pocketful Of Deng - Boxed In (2006) [FLAC]\04. Fungee.wav Peak level 98.8 % Extraction speed 1.9 X Track quality 99.9 % Test CRC DDD33ACE Copy CRC DDD33ACE Accurately ripped (confidence 1) [58B71048] (AR v2) Copy OKTrack 5
Filename G:\Station Music\A Pocketful Of Deng - Boxed In (2006) [FLAC]\05. Industry.wav Peak level 96.6 % Extraction speed 2.4 X Track quality 100.0 % Test CRC CCA131AC Copy CRC CCA131AC Accurately ripped (confidence 1) [8791AFF6] (AR v2) Copy OKTrack 6
Filename G:\Station Music\A Pocketful Of Deng - Boxed In (2006) [FLAC]\06. Super Bubbles.wav Peak level 95.5 % Extraction speed 2.6 X Track quality 100.0 % Test CRC C11DC916 Copy CRC C11DC916 Accurately ripped (confidence 1) [D7CAF643] (AR v2) Copy OKTrack 7
Filename G:\Station Music\A Pocketful Of Deng - Boxed In (2006) [FLAC]\07. EPA.wav Peak level 96.6 % Extraction speed 2.3 X Track quality 99.9 % Test CRC B607A392 Copy CRC B607A392 Accurately ripped (confidence 1) [840F8491] (AR v2) Copy OKAll tracks accurately ripped
No errors occurred
End of status report
---- CUETools DB Plugin V2.1.3
[CTDB TOCID: WELVsY49Me5zplNFm0FiLMU8uN8-] found, Submit result: WELVsY49Me5zplNFm0FiLMU8uN8- has been confirmed
[822be7e9] (1/1) Accurately ripped==== Log checksum 27E57F249E3E0C2308A70F737DF8F0DE178FAEF28D9CAE0E8052CC8630AB5500 ====
or cue file:
Cue
REM GENRE Rock
REM DATE 2006
REM DISCID 4B070E07
REM COMMENT “ExactAudioCopy v1.0b3”
PERFORMER “A Pocketful Of Deng”
TITLE “Boxed In”
FILE “01 - Such Magic Potion.wav” WAVE
TRACK 01 AUDIO
TITLE “Such Magic Potion”
PERFORMER “A Pocketful Of Deng”
ISRC H2=K>0600001
INDEX 01 00:00:00
FILE “02 - Nebuchadnezzar.wav” WAVE
TRACK 02 AUDIO
TITLE “Nebuchadnezzar”
PERFORMER “A Pocketful Of Deng”
ISRC H2=K>0600002
INDEX 01 00:00:00
FILE “03 - Trixie.wav” WAVE
TRACK 03 AUDIO
TITLE “Trixie”
PERFORMER “A Pocketful Of Deng”
ISRC H2=K>0600003
INDEX 01 00:00:00
FILE “04 - Fungee.wav” WAVE
TRACK 04 AUDIO
TITLE “Fungee”
PERFORMER “A Pocketful Of Deng”
ISRC H2=K>0600004
INDEX 01 00:00:00
FILE “05 - Industry.wav” WAVE
TRACK 05 AUDIO
TITLE “Industry”
PERFORMER “A Pocketful Of Deng”
ISRC H2=K>0600005
INDEX 01 00:00:00
FILE “06 - Super Bubbles.wav” WAVE
TRACK 06 AUDIO
TITLE “Super Bubbles”
PERFORMER “A Pocketful Of Deng”
ISRC H2=K>0600006
INDEX 01 00:00:00
FILE “07 - EPA.wav” WAVE
TRACK 07 AUDIO
TITLE “EPA”
PERFORMER “A Pocketful Of Deng”
ISRC H2=K>0600007
INDEX 01 00:00:00
So if anything could be automated purely by reading those file(s), it’d be amazing.
2 Likes
Cool! What are these files named? What are the corresponding names of the files with scans? Is there a pattern to the filenames, such that if you see the name of one of these files, you can derive the names of the other files?
2 Likes
Yeah I have lots of patterns, ha.
Let me break down the filenaming starting with folder
folder is always
Artist - Release Title (Original Year) [Format] {Edition Information, Catalog Number Or Label}
So the end bracket has a lot of variability. If it is a CD-R that goes in. If it has a re-release year different than original that would be in.And then always the catalog number or if there is no catalog number then the label and if there is neither a Self-Released is included.
The files are all ## - Track Title (ft. Guest Artist, Guest Artist).flac
Seems like the best thing would be to look at the tags and properties of *.flac files within a selected folder and import data from that.It would make the tool more broadly useable, but a checksum’d .log could be used to verify the data comes from a disc as well to decrease false imports or user compilations.
1 Like
What are the filename patterns of the log, cue, and info files, and of the scan files?
We were talking about log, cue, info, and scan files before. Adding FLAC files to the mix makes it more complicated. I guess it brings up the question of, what kind of data do you think these files could provide to MusicBrainz?
Where there are existing Release entries, and we can establish that a particular set of log, cue, info and scan files definitely correspond to an existing Release entry, then we could perhaps add CD TOC, ISRC, and cover art to the Release entry.
Where we can establish that no existing Release entry corresponds to a particular set of log, cue, info and scan files, then the obvious contribution is to add the Release entry. But in my experience, the time-consuming part of adding a Release entry is adding the Artist entries needed to make the Release entry — the album artists, the composers, and the performers.
Posting a file listing all the file names with all their directory paths would be helpful.
And as I said before, the first step in automation is to do the task manually. Take a couple of the entries as pathfinders. Manually look for existing Release entries. Write down what steps you take to search. Write down the criteria you use to determine that Release entries do or do not match. Is it possible to do the task manually? If not, then automation is likely fruitless. If so, then those notes provide the starting point for the automation.
1 Like