Re: Old question...

[marc@cxr_rs6000.med.ge.com (Marc Wolfgram)]

Bill Logsdon writes:
>I have since tried using the sound cedv that came with sys 6, and used
>rsound to do conversions.... to no avail....

The System 6 Sound CDEV won't play if the sound tools are already running
(started by some other app, da, init or finder extension) so I'd check to
see what's installed on your system in those catagories that _might_ be
affecting this.

>can someone provide better instructions/recommendations for converting
>stuff to rsounds, and getting the sys to recognize em?

There are plenty of different ways to move existing digitized sounds into
rSound resources.  The Sound CDEV looks in every file it finds in the
*/system/sounds folder for _named_ rSound resources.  This means that you
could even put HyperCard IIGS stacks with sonds in this folder and they
would be recognized.  The rSound resource format is described fully in
the IIGS Tech Note 76 (I believe).

Ways to create rSound resources are (not all inclusive):
- The rSounder program (there was a problem with it not naming the
  resources properly in an early version - I don't know if it's fixed)
- SoundConvert (from Mike Nuzzi at Triad Ventures)
- The Digitizer NDA (also from Triad)
- The SoundREM (again from Triad) for Foundation (not too blatant a plug -
  from Lunar Productions :)
- I know there's at least one more but my memory fails me - I'd look into
  utilities written more specifically for some of the sound cards.

The Sound CDEV ignores resources that are _not_ named, so make sure that
whatever tool you use to create the rSound resource will let you add a
rResourceName resource to the file as well.

Marc Wolfgram
AOL: M Wolfgram   GEnie: M.WOLFGRAM2   inet: marc@cxr_rs6000.med.ge.com
There are two ways to write bug-free code and only the third one works!