I take it that means that "the more capable Soundedit 16" is ARTA-compatible.
Not in my experience using SoundEdit 16; i think that statement is more talking about the fact that SoundEdit Pro was less fancy in other ways... but I may be wrong.
Someone here (paging?) got 24 tracks out of an 8100/G3
That'd be me! I got about a dozen realtime effects out of it, too. It took *lots* of config-tweaking to get it there, but it sure did it! It actually could do more like 28-30 tracks, but at those levels it would occasionally hiccup and skip. 24 tracks was steady enough I felt OK about giving it to my father-in-law and forgetting about it.
Up to 16 tracks was really fun... I set the 10,000RPM drive's mode pages to statically segment the cache into 16 segments, and then set Deck's cache to 1/32 the disk cache, so each cache segment was twice the Deck cache size. With such a small cache, there was almost no lag-time between pressing 'play' and getting playback, but the playback was still smooth and reliable because the hard drive firmware's read-ahead kept the buffers full quite efficiently. I was really banging on the access time of the disk, which was great because a fast drive, even on a JackHammer, still doesn't have that great of a sustained data rate (9-14MB/s). While working on this method, I discovered a bug in Deck II that causes it to loop audio and crash if you set it's cache size too low (like, way way below the default, which they encourage you to _raise_ for increased track counts)
Once I moved beyond 16 tracks (the limit of the drive's cache segmentation) this method quit working and I had to go back to the standard method of "use a big buffer in Deck" which works, but results in much-increased latency on the play-button. For example, if you have a 256k buffer, a file with 24 tracks will have to grab 6MB from disk before it can even begin playing: this translates into a 1-2 second latency. This kind of configuration does *not* make the old 8100 shine, because it stresses raw transfer speed much more than access time.
I suspect that with a modern 15,000RPM drive that has a 32MB buffer that can be segmented into 32 or more segments, 32 usable tracks in Deck II on the 8100/G3 would be a reality, using the "tiny RAM buffer and let the disk do all the read-ahead optimizations" strategy. I mean, SCSI works a lot faster when
everything you ever ask for is already in the drive's cache memory...
the DSP control panel showed both the set of DSPs on my Thunder/24 with GX addon and a seperate Nubus DSP card
Were you using the Thunder/24 GX and a ThunderStorm board together? I think that configuration is supported, because they're both SuperMac DSP Photoshop cards... Were the 4 DSPs (two on the GX, two on the ThunderStorm) substantially faster than 2?
I think a Thunder IV GX and a PhotoEngine together can load-balance, too, but I'm not *sure*. I can't say that I'd mind using Photoshop on an overclocked IIfx with a fast SCSI subsystem, 8 DSPs, and that NewerTech ramdisk NuBus card for a scratch disk. }
Are you using upgraded GWorld memory on that Thunder/24? If so, does it make scrolling in Photoshop as much faster as I think it should? I've always been really excited to get a Thunder/24 + GX or a RasterOps Horizon24 setup to try out Photoshop on GWorld memory...