AudioMasters
 
  User Info & Key Stats   
Welcome, Guest. Please login or register.

Login with username, password and session length
November 10, 2007, 07:55:40 AM
62065 Posts in 6138 Topics by 2106 Members
Latest Member: RayH
News:   | Forum Rules
+  AudioMasters
|-+  Audio Software
| |-+  Adobe Audition 2.0 & 3.0
| | |-+  Adobe Audition 2.0
| | | |-+  ASCII Text Export Data
  « previous next »
Pages: [1] Print
Author
Topic: ASCII Text Export Data  (Read 494 times)
« on: October 12, 2007, 10:38:25 PM »
KronoWR Offline
Member
*****
Posts: 3



Hi there,

I've recently discovered the ability to export music as ASCII text data. It's a neat feature and I'd like to play with the values somehow. The problem is that I don't understand how the data is formatted.

If I were to guess, I'd guess that I'm seeing left and right channel information and that the values are intensity. I can see that 0,0 is silence, but aside from that I'm completely lost.

Does anyone know how this information is actually outputted? Is there a set value for notes, pitch, tempo, or any other specific aural data? What determines when a value is recorded? Is each line a millisecond?

I'm hoping to use the information to do some mathematical equations, so I'd like to know exactly what each entry means.


Thanks!
Logged
Reply #1
« on: October 15, 2007, 05:48:54 AM »
younglove Offline
Member
*****
Posts: 28



The ASCII text file format represents PCM audio data, just like wave files, but the sample values are in text form.
Each line of values represents digital sample(s) in time--one value on a line for mono, two for stereo.
The options for this filetype include whether the data should be normalized or not, and whether to include
a format header.  When normalized, the sample values range from -1 to 1.  When unnormalized, they
range from -32768 to 32767.  The format header, when present, includes lines at the beginning of the
file indicating the number of samples in the file, the bit depth, the number of channels, the sample rate,
and whether the data is normalized or not.  The values are strictly sample values; no values for pitch, tempo, notes, etc.

The resolution of the data is very good:  approximately 22-23 bits of floating point precision.

This filetype is useful for having a computer program read audio data as ASCII text when you don't have a
wave file parser.  Files of this filetype are significantly larger than corresponding wave files.
Logged
Reply #2
« on: October 16, 2007, 12:03:07 AM »
KronoWR Offline
Member
*****
Posts: 3



Hello younglove,

Thanks for your reply. That explains quite a bit about what I'm looking at.

Since the values are strictly numeric, what is telling audition to make various noises? If I have a trumpet, piano, and guitar all playing the same song, what would change in the data to illustrate the differences between the instruments? I'm afraid I don't know anything about PCM audio data or wave parsers. I am most certainly *not* an audio guy. Smiley
Logged
Reply #3
« on: October 16, 2007, 05:58:57 AM »
younglove Offline
Member
*****
Posts: 28



Try these links:

http://en.wikipedia.org/wiki/Pulse-code_modulation

http://en.wikipedia.org/wiki/Digital_audio

http://en.wikipedia.org/wiki/Midi
Logged
Reply #4
« on: October 16, 2007, 04:33:55 PM »
MusicConductor Offline
Member
*****
Posts: 1274



Nice to see Mr. Younglove lurking about here -- and thanks for an interesting read.
Logged
Reply #5
« on: October 17, 2007, 01:54:04 AM »
KronoWR Offline
Member
*****
Posts: 3



Thanks again, Younglove. I'll give those a read and see if I can get my equations to work. Smiley
Logged
Reply #6
« on: October 20, 2007, 08:27:02 PM »
Ericson Offline
Member
*****
Posts: 2



...When unnormalized, they range from -32768 to 32767.

Can there be decimals, or is the bit depth 16 only?

Bert
Logged
Reply #7
« on: October 20, 2007, 09:08:04 PM »
SteveG Offline
Administrator
Member
*****
Posts: 8243



Can there be decimals, or is the bit depth 16 only?
Binary Digit

Rather says it all... digits are whole numbers!

It's only the normalised values that would have the equivalent of decimal places. Normalised values for a 24-bit sample would also extend from -1 to 1, but the amount of decimal places needed would be greater, because in a 24-bit sample the integer values have to go from -8388608 to 8388607.

The numbers are relatively easy to arrive at - 2^16 = 65536, so dividing that by 2 (+ve and -ve) gives the 32767/8 value, and 2^24 etc gives the 24-bit result similarly.
Logged

Reply #8
« on: October 21, 2007, 03:16:48 PM »
younglove Offline
Member
*****
Posts: 28



The values are not integers (example -4104.632 (unnormalized) or -0.1252634 (normalized)).  Subtracting the text values from an original wave float gives a difference of about -166 dB, i.e., very little loss.
Logged
Reply #9
« on: October 21, 2007, 05:27:10 PM »
SteveG Offline
Administrator
Member
*****
Posts: 8243



The values are not integers (example -4104.632 (unnormalized) or -0.1252634 (normalized)).  Subtracting the text values from an original wave float gives a difference of about -166 dB, i.e., very little loss.

I'm sure that this is true for the text values, but not for Bits. Bits are, by definition, what the acronym says they are.
Logged

Reply #10
« on: October 21, 2007, 06:04:11 PM »
Ericson Offline
Member
*****
Posts: 2



The values are not integers (example -4104.632 (unnormalized)...

Thanks,
That was just what I wanted to know, and the obvious reason for my question.
Bert
Logged
Pages: [1] Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP Valid XHTML 1.0! Valid CSS! Ig-Oh Theme by koni.