I find the Triton to be an impressive workstation, but, more specifically, very initially impressive and less and less impressive the more I learn about it and use it. If the XP-80 had a sampler, I'm sure I'd prefer it to the Triton. I like the Expansion Board sounds, keyboard, sequencer, value dial/wheel, omnipresent 16 track buttons, waveforms, filters, outcome of sound editing, and disk drive of the XP80 better than that which compares to those things on the Triton. I like the Triton's Touch Screen (makes OS navigation incredibly intuitive), but I still seem to have to scroll through as many menus/screens as I do on my XP80 to get to where I want to be. I can push a button just as easily as I can a screen. I do like the realtime controllers on the Triton better (mainly because there are RTCs for the arpeggiator and because most RTCs are knobs instead of sliders) as I do the effects (although I'm quite happy with the XP80 effects - quality moreso than routing). Also, as a standalone workstation, having SCSI capability, sampling, and the MOSS upgrade option make the Triton very appealing.

I have not decided if I will return the Triton or not yet (I have until this weekend). When I weigh what else I could buy for $2800 (=61 key Triton with SCSI and MOSS board) - like an XP-30 + Yamaha A3000 + Waldorf Microwave XT...or used XP60 + Yamaha A3000 + Nord Micromodular or Waldorf Microwave II - returning it seems like more of a reality...

Korgasm's complaints re: the Triton above are pretty much my exact complaints and it is very good that most of these are addressable by OS upgrades (need time-stretch, crossfade looping, and one-touch UNDO/REDO function pronto!). One other question I have has to do with sampling: when I sample an audio signal, the resulting sample is not velocity-sensitive when played on the keyboard...is there some setting I can change to make this so? This is my first real sit-down with a sampler (and even I can see why crossfade looping and time-stretch are so essential) and my endless searching through the manuals has shown me nothing to correct this. I guess I could sample the same sound at different (vol.) levels and create a combination that would play the layered sound (levels) according to keystroke velocity, but I feel like there should be a way for a multisample-turned-into-program to be velocity sensitive. I had brief exposure to Kurzweil sampling and, if I remember correctly, some kind of velocity map was applied to the samples automatically. Anyone know if the Triton can do like the Kurzweils? If so, please share! Thanks!