|
Home
/ FAQ
/ News Classifieds / Events |
Audio Asylum Thread Printer |
Get a view of an entire thread on one page |
65.19.76.104
| '); } else { document.writeln(''); } } else { document.writeln(''); } } else { document.writeln(''); } } // End --> |
In Reply to: RE: Please try out some music I created and tell me what you think (of the recording quality) posted by Christine Tham on July 01, 2009 at 16:38:00
I downloaded the file yesterday and had no trouble playing it with cPlay. However, after reading the thread I ascertained that dBpoweramp and the FLAC front end would not convert the file. And others reported they couldn't play.Here is the situation:
1. Some people are using old FLAC software which can not read the newer format (a problem only with 24 bit data, not 16 bit). They may get part way into the file and then strange things happen. When I try to play the file with SoundForge 9c this is in fact what happens, because SoundForge hasn't updated their FLAC library routines.
2. There was bad metadata, which was put into the file by your software. The effect of this is for the FLAC library to report an error. If you use FLAC frontend you will see the error message, and deduce that it is related to metadata (as some posters did). If you ignore the error you may get a decoded wav file, but in my case it was truncated a bit at the end. However, if you take the time to look at the FLAC Frontend GUI you will see there is a check box to "decode through errors". If you set this, the FLAC front end will simply ignore the bad headers and produce a valid wav file that plays all the way through.
Presumably dBPowerAmp does not set the "decode through errors" option, but cPlay does. This is an appropriate choice, IMO, because with a player you probably want to hear the music such as it is. With a conversion tool you probably want to know about a problem before it's too late.
Oh well. Computers.... :-)
Tony Lauck
"Diversity is the law of nature; no two entities in this universe are uniform." - P.R. Sarkar
Edits: 07/02/09
This problem woke me up to the realization that I haven't updated several of my programs in quite some time. Oopsie! Taking care of this as I write this. :)
Post a Followup: