Errant Folder Tagging

[jb76]

When ripping multi-disc CDs, a separate folder is created within the artist folder for each Disc number. This occurs even though I have the "Multi-CD Add Disc to Album" option set to "(never)." I attempted to reinstall the latest dBpoweramp 2025-04-17 version, but to no avail. Please advise on how to stop adding the Disc number to the folder name. Thanks.

[Spoon]

Your naming string will have disc number in it which is not effected by that option.

[jb76]

The naming string initially displayed: Album Artist\Album\Track Num - Title. Nowhere did I see any mention of the words disc or number. It was not until I clicked on the Naming Set button that it presented "Disc" in the string. I removed it, and it seems to have fixed my initial concern.

The problem that I'm noticing now are:

1) The disc numbers are missing from the metadata.
2) There is no confirmation that HDCD was detected after ripping disc even though it is enabled in settings, and the Track Technical column is present.
3) There is no confirmation that Pre-Emphasis was applied after ripping even though it is enabled to do so.

Seems as though this latest version is not working like any of the many previous versions dBpoweramp has released in the past.

Please advise me on how to resolve the new issues above and where can I find all of the changes made to the latest release that warrant my attention.

Thanks.

[Spoon]

2) It has to be a HDCD, you have one to test? the resulting file will be 24 bit.
3) Pre-emphasis has to be detected in the TOC for it to be applied
1) could be tag related, what format ripping to?

[jb76]

With regard to issue #1, I believe this has been resolved by no longer manually entering the disc number / total disc number (ex., 1/3).

Concerning issues 2 and 3, I am ripping an HDCD CD, dBpoweramp detects it as such in the Track Technical column. But the Information window that appears after the last track is ripped no longer confirms this, as evidenced by the screen capture below. And the resulting files are ripped FLAC 44/16, not 44/24.

[jb76]

I have been tinkering around with the CD Ripper app and believe I have solved Issue #2, not ripping detected HDCD discs into 44/24 FLAC file format. FWIW, here are the steps necessary to do so:

1) Enable detection (CD Ripper Options -> Meta Data & ID Tag Options -> Check HDCD option in Write ID Tags list).
2) Add Track Technical column in main track list (Insert disc -> Right click column heading -> Select Track Technical option).
3) Add HDCD to DSP list (Click DSP tab -> Click Add DSP / Action button -> Select HDCD in Add DSP Effect drop-down list -> Click OK button).

I discovered how to do this many years ago on my Windows 7 through Windows 10 PC. Each dBpoweramp version upgrade kept my HDCD settings intact. But I recently had to purchase a new Windows 11 PC and forgot that it takes more than enabling HDCD in the CD Ripper Options. I was missing the DSP addition step.

Concerning Issue #3, the Pre-Emphasis not appearing each time in the after-rip Information window, this may have been an error on my part in the past. I believe I may have added the Audio CD - De-Emphasis DSP Effect option on my old PC. I received a warning not to add this particular option in the CD Ripper app today. But I think that is why I always saw a note that Pre-Emphasis was applied whenever I ripped a disc and considered it a missing feature since I enabled it in the CD Ripper options. My only concern now is whether all of my previous rips with the Pre-Emphasis DSP Effect added had an ill effect on the quality of the sound on these FLAC files?

And my only other concern is still with Issue #1. The latest dBpoweramp CD Ripper app will, by default, enter the disc number as Disc # / Total Disc # (ex., 1/3). If I do not remember to back the Total Disc # out manually, it will create a separate folder for each disc (ex., Voyage, Disc 1; Voyage, Disc 2; Voyage, Disc 3). I prefer to have one folder titled Voyage, for example, that houses files from all three discs ripped, with the appropriate Disc # assigned in the metadata. I do not recall this problem before. Is there a setting I'm missing to avoid this issue?