Audition saved wav file can't be played in Android device

Auditions internal format is always actually 32 bit Floating Point and unless instructed otherwise will generally save .wav files in this format. It could therefore be a 32 bit file that the Android device is having problems interpreting.

To make sure that you save the correct .wav type use Save As to save your file and make sure that the Sample Type is set to 44100Hz Stereo 16 bit. If it isn't click the Change button to set it correctly using one of the Presets.

I don't own an Android but I'll wager that ryclark is right that your device is set up to handle CD standard wave files (16 bit, 44,100 Hz sampling) since that is what you'd get if you simply ripped a CD like most users.

Audtition can handle a wide range of different sample rates and bit depths since many production users require higher settings--as ryclark says, Audition works internally at 32 bit floating point.

Ryclarks method is exactly right for any future files but, if you want to fix the present non-standard one, go to Edit/Convert Sample Type and just change the settings to 16 bit/44,100 sampling then save.

BendyLin wrote:

 

 

Audition works internally at 32 bits floating point, but my windows OS is Win7 64bits, is it possible caused any change to the header or the body of wav file when saving?

Doesn't make any difference at all - that's not what is causing your problem...

Can you help explain what does hdr.fmt_sz 18 mean?

This, on the other hand, does indicate why you are having difficulty playing the file. When it says hdr.frmt_sz 16 it's indicating that you have a 'normal' pcm wave file, which the android should play fine. hdr_frmt.sz 18 though indicates that it's used some sort of compressed format (although I can't figure out exactly which one 18 is at present). So what you have is a file that looks like a wav file, but actually has some form of compressed data in it -  in other words, the file is acting as a carrier for something else. This is perfectly allowable in the format, but the chances of getting an android to decode it are slim. That's why the android says that it's not PCM data. So when you make files to play this way, you have to make sure that you've saved them as PCM wav files, and not a compressed sub-format.

Weird and probably wrong thought, but could you (or whoever saved your file) have typed in the .wav suffix rather than leaving it to Audition?  This is one way I know of to get a confused file type.

I don't know of any setting for wave file type in Preferences...the only adjustments I know are in the various drop down boxes on the Save As menu...hopefully others will correct me if I'm wrong.

I find MediaInfo very useful in type of situation. If you drop the file into MediaInfo it may tell you more details about the exact format of your file.

http://mediaarea.net/en/MediaInfo

You didn't use Libsndfile's .wav option to save the file, by any chance? That gives you endian options, and has all sorts of other possibilities for wav files. That could cause all sorts of problems!

Use the Windows PCM option at the bottom of the list only - that's almost certainly the only one that's going to work properly.

BendyLin wrote:

 

This make sense now, I change the format to save as Libsndfile's .wav, format setting: libsndfile: Waveform Audio 16-bit PCM Little-Endian(Intel Byte Order), and then the Androud device can play it normally.

 

My Audition is default to wave PCM format, setting: Wave Uncompressed 16-bit Integer.

These two should amount to the same thing...

I think the reason may related to the format encode. If possible, you could have a try to do the conversion before you transfer to your devices. I am using the Pavtube video converter and the conversion effect is good. You can download the free version to have a try. Hope this may helpful to you.

cherryhunter wrote:

 

I think the reason may related to the format encode. If possible, you could have a try to do the conversion before you transfer to your devices. I am using the Pavtube video converter and the conversion effect is good. You can download the free version to have a try. Hope this may helpful to you.

I think you'll find that the issue has been resolved without recourse to any other software - which is as it should be.

Hello!
I also drew attention to this problem - two extra bytes in the header. Some software refuses to accept such files. I could not find the answer on this forum.
Did you manage to solve the problem by setting up Au?

alexeya13543593  wrote

 

I also drew attention to this problem - two extra bytes in the header. Some software refuses to accept such files. I could not find the answer on this forum. Did you manage to solve the problem by setting up Au?

The answer is the one marked as 'correct' in this thread! Don't use Libsndfile, use Windows PCM.

You should have tried re-saving the original, not the copy...

Re-saving without change is impossible.

The first thing you did was change the save format to Multiple Data Chunks - the legacy format. For a start, I'm not sure why you did this, but never mind. Then you re-saved the file you'd created (look at the top of the screen at the file name - it's a bit of a giveaway) and tried to revert that back to RF64, and got the same extra two bytes as a result. I'd say that was hardly surprising...

You should have re-opened the original file and saved it as RF64 if you were trying to prove something - what you did proves nothing, I'm afraid.

I saved original at two variants.

Look at img. On top is original. Bottom is copy from AU. They was open in Notepad. Is headers. Try save any .wav in AU like on top.

If you succed - let me know.