Taking their sweet time

Thank you Dr Washington but I don’t think you see the problem for whatever reason so allow me to explain.

The problem with sample rates has nothing to do with any one specific feature, it is due to audio management in Windows generally (don’t know about mac) so Steinies view would be to release the program, otherwise wait 6 months, when there were already people banging the door down just to have a play.

You need to remember that not all musicians are “poor”. Some can actually afford to test new versions on the side with a machine that is not necessarily their main workstation and thank God for them. Also your logic about the updates ie .01, .02 etc doesn’t mean that is what will occur, even if it seems convenient from the users point of view because we don’t have the internal schedule and don’t know what fixes and/or updates to expect or when.

Bug report?


If programmers are anything like most artists/craftspersons, their best work is done when working at their own pace.

Beating the paid for slaves to pick more cotton served to only slow them down.

But there may have been a measure of venting or maybe even fun in it for the beater.

And let’s not (or shall we) talk about the time in between the Great Wars.

Precisely. (interbellum).


Yes curteye. There was a guy in the UAD forum who knew all this stuff like you maybe you know him :slight_smile:

Anyway, since Dr Washington has stated they have issues with C5, maybe they could help our friendly devs (who participate too I might add) and outline any issues in the correct forum.

Timestretching existed before C6 I understand and it’s quite adequate so it’s not as urgent as the howling heading would suppose.
Sorry, but oldies actually know (as advised by nilsemil) that first versions are to be treated with kid gloves. We’ve long ago given up ranting for the first six months of product release.
Bit like pointing over an artists shoulder as he’s painting and saying “You’ve missed a bit, mate.”
The paint is still wet. Let it dry first. But don’t waste time watching it dry and poking it to see if it is. :slight_smile:

Writing as a general consumer, rather than a Cubase user:

In the “real world”, if a company releases a new product and touts its new features all over the place, the new features are expected to work. If they don’t, there’s generally a perception of incompetence at least, or even possibly deception, and the company generally gets crucified by consumers and the media.

It’s always interesting in these cases to read the reviews in SOS, etc. … “Fine product!!! If I had to niggle I’d point out that the hugely important feature maybe doesn’t work at all, butCompany X should really be commended for the awesome concept development …”.


I’m arguing that this paradigm ought to change. I’ve been using this software long enough to be considered an “oldie”, and I’m no more comfortable with major broken features with “*.0” versions. There should be public beta testing so these things are caught. More and more companies are doing this, and it’s certainly possible for Steinberg to follow suit.

Dr Washington,

As much as I’d like to agree, I think you are being rather disingenuous to say that the feature (time stretch) is “broken” when the reality it half works.

As I have stated to you a number of times now were Steinberg to provide a complete working feature set, we would most likely have to wait at least 6 months anyway and this is likely counter to the commercial aspirations of the company notwithstanding the development schedule, which is obviously well on track by virtue of the 5.53 update.

Cheers & shalom

There is absolutely nothing wrong with this statement. Couldn’t agree more.

As a matter of fact, Steinberg once released a “beta”, but they called it a hotfix. Anybody remember C4.0.3? It fixed some serious interim problems, came with a warning that it wasn’t an official release and the world didn’t end. No reason why they can’t do this more often.

You wouldn’t do it for a whole numbered version though would you, which is what seems to be the central argument of this thread.

Two things: first, the major version numbers should be publicly beta tested at least enough to catch the more glaring issues–this 48/96k bug would’ve been caught before release if they did so.

Second, when bugs do slip through, as a few always will, there is nothing wrong with ‘unofficial’ releases or ‘hotfixes’ that fix these errors. We can choose to skip them if not affected. A hotfix could also, of course, fix major bugs like this until an ‘official’, stable release is ready.

Or, they could just do like C.O.C.K.O.S. does, and update very often.

Either way, no, I wasn’t being disingenuous. I’ve said from the beginning that this works at 44.1kHz. It doesn’t for me, as I never track at that rate. Therefore, me saying “it is broken” is perfectly true from my perspective. :unamused:

In any case, I think it’s time for a change. Things are pretty good now, but they could be remarkably good. Cubase is a mature product now, which was not so much the case during the SX phase. It could be the standard DAW if Steinberg would just push that much harder and work to craft a masterpiece. We’re almost there, and I’m cheering them on. : :mrgreen:

I just don’t want to see big features like this not work for me right out of the gate anymore. I was really, really looking forward to elastique. It’s just a bit of a let-down.

Dr Washington, you seem to be avoiding the fact that so called “broken time stretch” is not really a bug parse, it is simply an incomplete feature so there is nothing at all to catch, but the real “catch” though is this: if there did exist this holy grail of internal bug testing that you talk about, then we’d most probably not have newer versions so quickly and sales on the whole would be down, which is not in the interests of users alike otherwise how would older versions be upgraded?

you should have quit while you were ahead, now you are wrong too.

It’s definitely a bug.

It’s obvious to me that either you never use time stretching, or you don’t do serious audio work with timestretching. If you did, you’d know that timestretching in C5 and before was completely unusable. It was my biggest gripe . Warbles, glitches, just terrible. I’m looking forward to C6’s superior time stretching, and I do use 44.1k, so Dr Washington’s gripe is not mine. That said, I completely understand it and fail to see the logic behind your argument.

Addditionally, you look a bit Sanctimonious.


+1 - 5.5 and C6 can run on the same machine

To sell something knowing that it doesn’t work fully, but not disclosing that, is not a business practice that is generally accepted anywhere in any situation. There are even penalties often associated with such behavior, ranging from negative word-of-mouth/decreased sales, to criminal sanctions. Not sure why people think these normal conventions don’t apply in the case of DAWs!

I think a lot more goodwill (which ultimately may = increased sales?) would be generated by a company instead saying something like, “Look, we’re releasing this completely awesome DAW today, and it can currently do A,B,C better than anyone else’s. AND, on such and such a date in the very near future, we will be releasing an upgrade that will enable features X, Y, Z - features that will blow your socks off, and make our DAW far and away the best in the universe. BTW - until then, you can play with features X,Y,Z - just remember they won’t be fully functional until then …”.

Is that so hard to say? Am I completely off base, or is that a better business practice than the one being discussed?

Awesome that thread disappear to the lounge without trace.

Loving this forum even more! :laughing: