Rev audio clips

[stephen barncard]

Assuming that Rev stores audio file data sequentially in the first place,
one would have to search for a pattern of binary data AFTER the headers,
which would not be stored in the stack.  Check for where the headers end and
where your test data starts and just use a small sample to search for, like
the first 50 bytes..  Use a tiny sound for tests.

http://www.sonicspot.com/guide/wavefiles.html

http://www-mmsp.ece.mcgill.ca/Documents/AudioFormats/AIFF/AIFF.html


On 18 May 2010 13:02, Richmond Mathewson <richmondmathewson at gmail.com>wrote:

>  On 18/05/2010 22:17, Alejandro Tejada wrote:
>
>> Hi all,
>>
>> After learning about the binary string produced
>> by compress(), i am curious to know if one of
>> the professional audio experts in this platform
>> have examined the converted audio clips
>> that Rev uses internally, after importing an
>> audio file.
>>
>> By trial and error, you could isolate the audio
>> binary string from a saved stack.
>>
>
> Oh Yuck!
>
> I made a new stack "ZOUND" and imported an AIFF
> sound "ZND.aiff" into it.
>
> I then cracked both the stack and the sound file open with
> HexEdit:
>
> http://hexedit.sourceforge.net/
>
> and could NOT find the 'audio binary string' in the
> stack.
>
> Maybe I went about things the wrong way . . .  :)
>
>
>   Then, analize
>> and compare with the original imported audio clip,
>> saved in different audio formats.
>>
>>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>



-- 
-------------------------
Stephen Barncard
Back home in SF