Skip to main content

Notice

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.
Topic: CD Subcode & TOC Reader Software (Read 4235 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

CD Subcode & TOC Reader Software

I would like to find a tool that allows me to read the subcode and TOC on an audio CD. Does such a tool exist? If not, then does anyone know why? (e.g., Are there legal issues?)

I am looking to check things like pre-emphasis, HDCD, etc. on a track-by-track basis.

I have heard CUETools might have this functionality, but I cannot seem to find a guide/how-to.

Anyone heard of ISRCViewer?

Re: CD Subcode & TOC Reader Software

Reply #1
The CueRipper part of CUETools does. Simply start ripping the CD and watch the status bar. Once it's done analyzing, I abort the rip (chances are, I've already ripped it with dbpoweramp or foobar, so I don't need to do it over). Even though you abort the rip, it's created the cue sheet for you which will show pre-emphasis flags.

Re: CD Subcode & TOC Reader Software

Reply #2
Does the cue sheet tell you what data is coming from the TOC vs the subcode?

Does it show all TOC and subcode data, or only certain items?

Re: CD Subcode & TOC Reader Software

Reply #3
Does the cue sheet tell you what data is coming from the TOC vs the subcode?

Does it show all TOC and subcode data?
No and no.

AFAIK, in contrast to pre-emphasis, HDCD encoding is nothing to be found in a CD's subcode, but only in the audio data part.

Re: CD Subcode & TOC Reader Software

Reply #4
HDCD on a track-by-track basis can cause lots of issues, some if you use software and some if you use a physical CD player:

You are vulnerable against jumping to tracks. If your DAC has received HDCD packets, it will decode HDCD for some (ten?) seconds after the last one. A non-HDCD track after a HDCD track could be decoded wrongly. This is a problem with compilation CDs thoughtlessly put together from HDCD and non-HDCD sources, but also if you in software switch between tracks from different CDs (you won't do that quick enough with a physical player!). However, software decoding should know what you are doing, even though a physical DAC cannot.

You are vulnerable against misplaced track boundaries. Case: a compilation again, but the trackmark is set a bit too early, so it starts with what should have been the last split second of the previous song - which has HDCD. Then HDCD will be on for some ten seconds. foo_hdcd has the option to put a "no" in the HDCD tag.

And you are vulnerable against jumping to tracks that were intended to be decoded as HDCD, but does not have HDCD flags for the first few seconds (while in continuous playback, the HDCD flag would still be on).

Re: CD Subcode & TOC Reader Software

Reply #5
It really surprises me that there is not a tool that reads *all* subcode, TOC and audio data. I have heard of tools like hdcd.exe, CUETools, etc., but I would think easy to use apps like dBPowerAmp would have a button or log to show all subcode, one for TOC and one for audio data.

Is this just too hard? (obviously I am not a programmer)

Are there legal issues that prevent apps like dBPowerAmp from implementing such features?

Re: CD Subcode & TOC Reader Software

Reply #6
I just remembered (flashback) once wanted to have some info about the pre-emphasis on an old cd and used a tool named icedax under linux.
https://hydrogenaud.io/index.php/topic,76265.msg668270.html#msg668270
Is troll-adiposity coming from feederism?
With 24bit music you can listen to silence much louder!

Re: CD Subcode & TOC Reader Software

Reply #7
Zorlac:  I agree that e.g. CUETools could easily produce a filename.subcode.cue and a filename.TOC.cue if they disagree. Now, IIRC:

* EAC removed some features out of fear of legal issues: http://wiki.hydrogenaud.io/index.php?title=Exact_Audio_Copy#cite_note-1

* I once asked about storing index points in the CUETools database, to which (deleloper) Gregory replied that detection isn't always reliable. Dunno what that means apart from the above defective-by-design thingies. Maybe it was because EAC is likely a way larger contributor to the CUETools database than CUERipper is.
(And, for all that I know: it need not be the CD. It could be the drive.)

* André (EAC developer) also points out that some subcode information is often wrong: https://groups.yahoo.com/neo/groups/EAC/conversations/messages/7463
(Again: for all that I know, it could be the drive.)

* cdda2wav has a feature to check both TOC and subcode and tell you inconsistencies. There are some. Some have wondered if cdda2wav's method is any good: https://hydrogenaud.io/index.php/topic,114278.0.html
(And for all that I know ... again. And it could even be doing things "technically correct but mostly useless" in the sense that when it matters, the errors are so that you will not get much help from the information.)

* CDs with inconsistencies for the Pre-emphasis flag include certain pressings of Pink Floyd's Dark Side of the Moon. IOW, it isn't limited to backyard pressing plants.

* HDCD and hdcd.exe has no place in this discussion. The HDCD flag is part of the signal itself, hidden in the dither. Thus, as long as you rip the CD to a lossless format, you can always retro-scan for HDCD.

Re: CD Subcode & TOC Reader Software

Reply #8
I vaguely remeber CD ripping software named PerfectRip which had something about subcodes, TOC and stuff like that... haven't used it, though, may be worth checking it out.
Error 404; signature server not available.


Re: CD Subcode & TOC Reader Software

Reply #10
I am hoping we can get a comment from the devs of EAC, dBPowerAmp, etc.
I messaged them (thru their official channels), so we shall see.

Re: CD Subcode & TOC Reader Software

Reply #11
Zorlac:
I don't think André posts much here anymore, but he has indeed clarified why already.
From my experience here and at the dBpoweramp forum, Spoon will answer "how" dBp does it (though, that is already known, so you do not need more clarification?) - but not so much why he chose this or that solution.