The Logic Off Topic list

[Redirected from LUG to L-OT:]

From: "Marcus Barczak" <mjb@...> 
Date: Fri Apr 5, 2002 2:27am 
Subject: RE: [LUG] RE: [LAM] firewire drive  



> SDII files can be read on a PC by Awave Studio and 
> Quicktime also recognoses them though I don't know 
> if that helps.

Why do people still spout information about process that they have not
tried!  

1)  AWAVE supports SDII files in the guise that it will open in a file
in MOTOROLA binary format you physically CANNOT read the resource fork
of a file on an HFS formatted partition on a PC irrespective of
MacOpener/Conversions Plus or any other "mount a mac disc on a PC" type
utility.  It is up to YOU to specify sample rate, bit-depth and number
of channels.

2)  AWAVE will crash on large files ... sure it's cool for small samples
but give it a 3 minute+ 24-bit/44k1 file and it will barf

3)  Any application that can open RAW audio files and specify then
endian'ness (ie. motorola/intel big/little endian) can open an SDII file
provided you specify the bit depth, sample rate and number of channels -
sound forge 5.0 can now do this since it is now 24 bit, shame they made
batch converter an additional plugin :( boo hiss

Hendrik Jan Veenstra then said:

> The resource fork is a typical Mac invention, and is just an "extra 
> part" of the file, which PC files don't have.  Indeed, as you say, 
> they make 3-letter filetype extensions unnecessary & all, but the 
> disk format has nothing to do with that.

The resource/data fork concept was a great idea aside from it being
incompatible with every other filesystem format under the sun.  Aside
from eliminating the need for file extensions most importantly it
provided a means for mac programmers to extrapolate the raw data from
the information describing the data.  In SDII terms the resource fork
aside from citing the creator and file type also contains pertinant info
such as the bit depth, sample rate, number of channels, time stamp etc
... it's a great idea but not portable unfortunately :(  ProTools (pre
5.1) stored the entire data in a session file entirely in the data fork
making it a right royal pain in the ass to open in a PC ... this
thankfully has been rectified :) in 5.1 onwards :)

nuff of my rant

cheers,
marcus