I used to use SoundForge to downsample to CD quality for CDbaby releases. When my Windows machine died, so I got dbPowerApp music converter for my Mac. Appears to have been a mistake. All of the files converted from 96k 24bit to CD Quality with the app were rejected by CDbaby (multiple attempts). The output was set to Wave 16bit, 44.1k, Stereo. So...This passed CDbaby's "CD quality check" but the company would send me "we can't process these audio files" messages. Unfortunately no further explanation was provided, even when asked. So, I installed Windows and SoundForge on an older Intel Mac, converted the files to CD quality there, and those were accepted and released. Lost 2-3 weeks of Spotify placement opportunities as a result. Any idea why the files were unusable? Release 2024-05-30 (6)
CDbaby Rejects Downsampled Files Created by Music Converter
Collapse
X
-
Use the DSP effect 'ID Tag Processing' set to delete all ID Tags
It is likely CD Baby cannot read any wave files with ID Tags -
All the files I render are 32-float or 24-bit @ 96kHz - Music Converter has been my exclusive output converter for a few years. I've never had a rejection from CD Baby or any of the major distributors or major platforms. I'm on PC and often have full metadata in the files.
TL:DR - something is wrong with your configuration in Music Converter, or Windows is Windows-ing on you. This shouldn't have happened.
Have to ask.- After conversion, did you open them in other applications to confirm everything was ok with the output? Same with the Sound Forge 24/96 output on the PC. Were those files clean and usable?
- How did you lose 2-3 weeks on this? You should have come here right away. This forum is very responsive. Don't let that happen to you again. Speak up.
- Can you post the configuration you used in Music Converter for the group to see? There is a good chance something went wrong there. (It is VERY easy to do. Ask me how I know).
- It sounds like you are the artist, producer, engineer, mixing engineer, and mastering engineer. That's fine, but this issue should have landed on the mastering engineer's shoulders, not yours. There's a reason every commercial release goes through a professional mastering engineer. Find someone just starting their career; they'll know enough and charge next to nothing. Plus they know some secrets to getting your streaming tracks to sound great across platforms.
Comment
Comment