Stephen Barncard wrote: > ...What's needed to make a usable audio file is just to provide the > appropriate > header info, which obviously missing. The binary data with no or special > headers is stored in the stack as an audioclip. Are there hidden properties > of the individual audioclip object ( such as sample rate ) that can be found > before export?...
Isn't there a reference to "standard" headers for the various sound file formats- the way there is for MIDI files? For instance, for AIFF: http://uweb.txstate.edu/~me02/tutorials/sound_file_formats/aifc/docs/aifc.htm -and- http://uweb.txstate.edu/~me02/tutorials/sound_file_formats/aiff/common.htm and for WAVE: http://www-mmsp.ece.mcgill.ca/Documents/AudioFormats/WAVE/WAVE.html I'm presuming here that in the case of, for example AIFF, the length of the raw binary sound data could be read by LiveCode so as to be able to define cksize and other chunk components. This could then be added to create the required header. Am I mistaken? Or would this be too much to bother with? Perhaps the length of audio data, as opposed to MIDI data, makes this method impractical? Of course, best would be for this to be a built-in function. -Kurt _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
