-
1. Re: Audition saved wav file can't be played in Android device
ryclark Jan 7, 2014 4:47 AM (in response to BendyLin)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.
-
2. Re: Audition saved wav file can't be played in Android device
Bob Howes Jan 7, 2014 5:13 AM (in response to ryclark)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.
-
3. Re: Audition saved wav file can't be played in Android device
BendyLin Jan 9, 2014 10:56 PM (in response to ryclark)thanks ryclark for your reply, I did that try as you mentioned, save the wav file in Wave PCM format, 44100Hz Stereo, 16-bit(Wave Uncompressed 16-bit Integer), and uncheck the option Include markers and other metadata, but the wav file still can't be played by the my android device, same feedback via ADB log.
-
4. Re: Audition saved wav file can't be played in Android device
BendyLin Jan 9, 2014 11:06 PM (in response to Bob Howes)Hi Bob Howes, thanks for following up this topic.
Actually, my wav file is the simple sine wave tone that is purposed to test, and it is indeed 16bit 44100Hz sampling.
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?
Can you help explain what does hdr.fmt_sz 18 mean?
-
5. Re: Audition saved wav file can't be played in Android device
SteveG(AudioMasters) Jan 10, 2014 1:40 AM (in response to BendyLin)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.
-
6. Re: Audition saved wav file can't be played in Android device
BendyLin Jan 10, 2014 3:15 AM (in response to SteveG(AudioMasters))Hi SteveG, appreciate for your explanation.
I think you are right and catching the right point now. I compared the two wav files in HEX format, found that the bad one adds some additional info in the header and the good one doesn't show it. I tried to re-install the Audition and try again in default setting, still can't play it. Then I tried to change the setting in Audition(I don't really understand what the setting mean) Edit->Preferences, unfortunately, I can't find the correct one. So I post a question here to see if anyone have the same issue and fix it already.
-
7. Re: Audition saved wav file can't be played in Android device
Bob Howes Jan 10, 2014 3:23 AM (in response to BendyLin)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.
-
8. Re: Audition saved wav file can't be played in Android device
ryclark Jan 10, 2014 3:39 AM (in response to Bob Howes)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.
-
9. Re: Audition saved wav file can't be played in Android device
BendyLin Jan 10, 2014 4:21 AM (in response to ryclark)I compare the two wav files again, find that it is only a little bit difference, I show the Hex data here of the comparison for you, maybe it helps for you to find the right approach.
good one:
52 49 46 46 A4 D5 01 00 57 41 56 45 66 6D 74 20
10 00 00 00 01 00 02 00 44 AC 00 00 10 B1 02 00
04 00 10 00 64 61 74 16 ...
bad one:
52 49 46 46 A6 D5 01 00 57 41 56 45 66 6D 74 20
12 00 00 00 01 00 02 00 44 AC 00 00 10 B1 02 00
04 00 10 00 00 00 64 61 74 16 ...
As you can see, the bad one(saved by Audition) add two bytes to the original one, and change the info of the header. Fortunately, I use the HEX editor to remove these two bytes and change the header info back to same as previous one, save, then my android device can play. So I am sure it is the Audition saving the header with some info that makes the android device can't decode it. Is there any setting in Audition to remove this info?
-
10. Re: Audition saved wav file can't be played in Android device
SteveG(AudioMasters) Jan 10, 2014 9:38 AM (in response to BendyLin)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.
-
11. Re: Audition saved wav file can't be played in Android device
BendyLin Jan 11, 2014 7:52 PM (in response to SteveG(AudioMasters))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. I also try Big-Endian(PowerPC Byte Order), can't play. I compare the HEX again, finding that only some bytes in Body is differ, i believe it is the PCM coding accuracy issue. Header format is exactly the same.
My Audition is default to wave PCM format, setting: Wave Uncompressed 16-bit Integer.
-
12. Re: Audition saved wav file can't be played in Android device
SteveG(AudioMasters) Jan 12, 2014 2:33 AM (in response to BendyLin)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...
-
13. Re: Audition saved wav file can't be played in Android device
cherryhunter Feb 12, 2014 5:05 PM (in response to BendyLin)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.
-
14. Re: Audition saved wav file can't be played in Android device
SteveG(AudioMasters) Feb 13, 2014 2:11 AM (in response to cherryhunter)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.
-
15. Re: Audition saved wav file can't be played in Android device
alexeya13543593 Apr 3, 2018 7:46 PM (in response to BendyLin)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? -
16. Re: Audition saved wav file can't be played in Android device
SteveG(AudioMasters) Apr 4, 2018 2:12 AM (in response to alexeya13543593)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.
-
18. Re: Audition saved wav file can't be played in Android device
SteveG(AudioMasters) Apr 4, 2018 4:08 AM (in response to alexeya13543593)You should have tried re-saving the original, not the copy...
-
19. Re: Audition saved wav file can't be played in Android device
alexeya13543593 Apr 4, 2018 4:18 AM (in response to SteveG(AudioMasters))Re-saving without change is impossible.
-
20. Re: Audition saved wav file can't be played in Android device
SteveG(AudioMasters) Apr 4, 2018 10:19 AM (in response to alexeya13543593)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.