ssp wrote:actually the comparison is sound, it relates to a single failure or fault being able to lose functionality of the whole.
as i stated, if a client came into my studio and specifically asked me for bpm to be used only for me to explain i cannot use it because one function does not work the client would look at me like an idiot.
As someone who just bought BPM 1.5 a couple of weeks ago, and only recently realized this major
crippling bug in it, I have to respectably agree with M-Goldie and disagree with mr
ssp. The comparison that a multi-channel mixer has one broken channel is nowhere near comparable. You CAN go around that, just don't
use that broken channel - but here, you just simply can NOT slice samples. Period. It just doesn't work. There
isn't a "workaround". Other than doing it in Ableton, which kind of defeats the purpose of an "all-around beat production machine" BPM is supposed to be, now doesn't it?
Also, who says we've STOPPED using BPM in general because of this? I don't think anyone did? I certainly didn't. In fact, I bought it firsthand as a beat-making tool for drums, because I love the workflow. The sample slicing "in the box" was a sweet, added bonus. The point is, that a major feature in the software has been rendered unusable because of this bug (in an update for which most paid for...), and the fact that it's been, what, at least half a year and still not a peep from MOTU...? You would think that fixing this would be top priority, before focusing on developing additional software and hardware...or at least addressing the issue.
M-Goldie (or ssp, for that matter) have you gotten a valid response from MOTU regarding the matter that they're actually even -working- on it? My "TechLinks" remain in "Unread" state...