Hi everyone, We’ve published an overview of the upcoming introduction of optional diagnostic and usage data collection in selected Steinberg products. You can find all the details here: Diagnostic and Usage Data in Steinberg Products We’ve created this thread as a place to discuss the announcemen…

When will it be introduced? And where can we turn it off?

The timeframe is mentioned on the website – aiming for later this year. It will be controllable from your Steinberg ID account.

Does diagnostic and usage data collection affect performance? No. The system is designed to run efficiently in the background with minimal impact on performance. I wouldn’t mind the collection of my data to help Steinberg as described, but with an old computer that i feel is always on the edge of …

The way the system is designed is to write usage data events to disk for upload by another process separately as a low-priority activity. That way, the main application is not slowed down in any way by networking connections. The impact should be negligible.

That’s entirely your choice and is completely fine!

Why does Steinberg product management direct valuable development time at a feature nobody asked for instead of improving the product?

The idea is that having insights into how users actually use our products will help us prioritise our valuable development time.

I think this is a good idea. Keep in mind however that if you use this data for developing enhanced or new functionality that you’re going to have users that aren’t using some functions because they aren’t working properly or are incomplete. Take VCAs for example; I use them within certain boundari…

How is this different from the already optional data collection in Cubase? Is it now different in scope? Is it across all Steinberg products, on the account level rather than the product level?

Steinberg Forums

Upcoming: Optional Diagnostic and Usage Data Collection

Steinberg Lounge

announcement

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled