I have CD Architect 5.2d, the release notes for 5.2c claims:
"Notable changes in 5.2c
Support has been added for FLAC."
Why can't I read/import FLAC files into my projects. I have tried a couple of different bit rates and Hz settings, but not all. My FLAC files are rendered using ACID Pro 7.
Question is whether CD Architect has a problem, or ACID Pro ?
Reason I ask is that CD Architect opens FLAC files made by SoundForgePro10 or VegasPro10 perfectly; so does SoundForge (or Vegas) open your FLAC files made by ACID? (I don't have ACID to test that).....
Sorry about taking so long to reply. If you know how I can fix this, my forum settings are set so you can email me, if that would help.
SoundForge will open the flac files, Windows Media Player & Foobar2000 will also play them. I will try using SoundForge first and see if CDA will read the SF flac files.
I saved a flac file through SF10 default format of 96,000 Hz, 32 bit default format and 88,000 Hz, 24 Bit default fromat; and CDA still can't load them. The files show up, but when I click on them the following error code comes up, and then CDA Crashes.
Is there a specific bit and resample for CDA? Here is the error code. I copied & saved the .dll file that is mentioned below from SF10 to CDA, after that, CDA stopped crashing. That was a couple of weeks ago, I have since reinstalled CDA 5.2d build 240.
The following is the error screen right before it crashes.
An error occurred during the current operation
An exception has occurred
Here I have same versions of those applications.
In your original post you weren't very specific about FLAC files, so I assumed ALL FLAC files were causing you grief. :-)
here 96kHz/24b FLAC files import into CD Architect and Play fine.
(SF10e won't make 96kHz/32bit, only 96kHz/24bit)
and 196kHz/24b FLAC files cause exception error & crash (same as your report) if I just click on them in CD Architect's Explorer Tab.... I figure CDArchitect does not support them.
BTW why are you saving as FLAC files in ACID, in preference to uncompressed WAV format?
I tried saving through SFP10 and AP7 in the 96Hz/24bit format. CDA will not crash on compression levels 0-2, compression levels 3-8 and it crashes, I was using 5. The problem with 0-2 is that when I add the track to the track list, there is a blank song on the track; no wave forms, nor will sound come from them.
Could you let me know the settings you are using in SF10, I see the 96/24, but what is your compression setting? What might also help is, what is the original file version ,i.e. are you using a WAV or mp3 and then, save as, to FLAC file? If you could give me the process that you are using, from the original file version to each step in SFP, and I will see if I can get CDA to work on my end. I'm missing a step, a setting, something...
as for FLAC vs Wav
The reason I'm using FLAC, is that the FLAC files are 62% smaller than Wav, plus dealing with Wav's inablity to write metadata to the file. Downside, Win7 won't read the metadata in FLAC files using Explorer. At least Foobar can. I currently have just above 30,000 songs, ALL of them are legally purchased or composed by me. A 62% compression rate adds up really fast!
I would LOVE to render from AP7 and then make my CD with CDA. Right now, I'm rendering in FLAC for storage, metadata, and play. Then rendering a 2nd file, Wav, so I can use CDA as my burner. Now I have two versions, while using a tremendous amount of disc space. The optimum way would be to use AP7 to burn the CD. It can, but it can't burn text, as in... the name of the song.
I used to only use Wav files when I used Win Media Player for my player. Until, one day, my computer crashed (trojan) and I lost all of my metadata for all of my Wav files. WMP writes WAV metadata to a separate file. I couldn't move Wav files with WMP, and I couldn't use my external HD on other computers, because the Wav metadata was written to the file on the orig. computer. There is metadata on a Wav file, but it's the data that was written to the file when the file was originally made.
After that disaster with the Wav files, I started using FLAC files and Foobar2000 as my player. Up until now, I've been using another CD burner for the FLAC files. However, the other day I read that in release 5.2c FLAC files could be used. I just haven't figured out how... although with your help I am getting closer... I at least have a file showing on the track... it's just blank.
I'm also going to start buying 24bit music, and they are in the FLAC format. I haven't bought any as yet, so I don't know if CDA will be able to, or not be able to, read them.
I REALLY appreciate your time and knowledge. AND I REALLY appreciate how you don't answer in a condescending way, like several people on this site do.
Trust me, I'm no expert with FLAC files - it was just that in the past someone had brought a bunch of files, including FLAC, for me to 're-master' into a series of CDs, which had all worked fine in CD Architect, so I was surprised to see your post; in my recent quick look at this matter again, I just accepted the default FLAC settings, including the compression level, in SoundForge and suchlike.
I normally will only deal with uncompressed formats in my day-to-day work, delivery to clients, and archiving..... normally if they arrive with a compressed format I insist on getting the original uncompressed master.
So I had another look at this just now, and indeed there are some very weird things going on in CD Architect with FLAC files; in the time I had available I determined CDA has no particular problems with any compression setting for 44.1kHz/16bit FLAC - however at higher samplerates is where the trouble begins - 48kHz/24bit FLAC files sometimes worked, sometimes didn't according to different compression levels; the behaviour was weird and erratic to say the least....
I also found SoundForge10e occasionally generated corrupt FLAC files.
BTW there seemed only small differences in actual saved filesize between the 9 different compression settings within FLAC.
I think you should start a support ticket with SCS regarding CDArchitect's FLAC support (or lack of it), as it does not make sense that some SCS products can generate files that are unreadable by other in-house products, or indeed, cause crashes.