Bjorn Elfstrom wrote about bouncing: >although it's >not really logical as to how it works. I can't share that thought, I find it kinda logical... >it still crashes my machine if I >attempt to bounce all tracks at once, don't know if this is normal. It never crashes here, it did sometimes with 4.0.4, that's why I used 4.0.0 before 4.1.1 was available. Upgrading to the latter is defenitely recommended. >I thought that the point of bouncing is that you relieve the computer from >the real-time stress which means it could process *everything* in one >go. well, apparently not; but this is good enough. Well, if you knew the story about VSTs "offline" mixdown feature you'd also know that it was a middle catastrophe. It took Steinberg almost two years to make it work as supposed. I second the point that it'd be great to have such a feature, but I really wouldn't want to trade it for stability. There even are some applications doing an offline mixdown pretty well, I saw it with Sonic Foundry's ACID on a friends machine, seemed to work pretty nice (and wow, it was extremely fast too!), but for now everything is ok with me as there even is some advantage of a realtime mixdown with a listen-while-bounce function (something 4.1.1 offers): You could simultaneously do a copy to tape or DAT or whatever, defenitely some kinda time saviour if you run a studio as most artists usually want to have some immediate copy of the things they just did. Even in my little home setup it's of certain use. When I finish something and bounce it down I usually copy it to some tape and give it a go in the kitchen ghetto blaster. A working offline mixdown however would be cool for things such as freeing up your CPU via intermediate mixdowns (bounce > reimport) but for me it should be optional. Sascha