That link yields a "page not found" error this morning.

Am familiar with the velociraptor drive, though.

For those recording multiple input soundcards, it may be an edge as to track count possibilites, if set up properly to do so with their host recording software.

As for RealTracks/Realdrums generation times, one has to realize what happens when a track is generated in order to figure out how to use faster drives. Storing the base Realtracks files on the faster drive is one thing, but it will hit a bottlenectk whenever generating a Realtrack to playback because BIAB/RB use the C:\Temp drive to store the generated tracks for playback. RB allows us to specify a new drive route for that, but then you will have the same drive reading and then writing to itself at the same time, another possible bottleneck.

A machine that has TWO velociraptors in it, one on the C: drive and a second one for RealTracks storage, should be able to load and generate Realtracks a bit faster, but after that point there is likely little to gain. THREE velociraptor drives, one for C: and system, one for storage of RealTracks and the third's first logical partition for the RealBand host would be interesting.

Band in a Box, however, is a different story entirely. We don't have any setting to route the Temp file to somewhere else, it will always be C:\Temp at this stage of the game. Installing a Velociraptor as your C: drive may speed things up a bit when a set of Realtracks is generating. The amount of time saved may or may not be significant, though. A little bit wider bandwidth with about the same read/write time going on. I think that the read/write cycle is taking the majority of time here.


--Mac