The reason that the loop point were persisted is that SD2 files have the wave3data in the datafork, and the loop info in the resource fork. When they were zipped, the data fork was put in, but not the resource fork. So the SD2 files were simply raw data. The EXS is rather nice - it simply needs a reference to a file, and just uses the data. On import, though, it wants to write into the Zones the loop info etc. On the Mac, when the EXS was ready to read the CD2 resource fork, it could and imported the settings in nicely. But when it's taken away.... The EXS file submitted had the loops from the SD2 in there. But once we redid it, at least I lost them. Garth Hjelte Sampler User
Message
Re: [exs] Sharing a confusing string Instrument
2002-02-11 by Rubber Chicken Software Co.