Survey Time!

[machinesworking]

Yeah I think of CC for performance type controls, mod, expression, MPE etc. and immediate control. But! the elephant in the room is plenty of DAWs can access host automation and map it in a preset permanently to Macros for instance. On top of that Kontrol Mk3 access's host automation outside of the NKS/Komplete Kontrol world. For plugins like Falcon for instance you get clear slots for a few hundred parameters if you wanted, that map perfectly to the Kontrol endless encoders. This would be true of any control surface using the Mackie protocol I believe. So IMO the obvious solution was always 8 macro cc's and or automation slots. 4 and 4 would do. then you can use either your host DAW that supports it like Live or Bitwig to assign permanent automation for the plugin, or preset in the plugin, and cc gets regulated to performance controllers and quick project assignments.

I'm sure all of that is much harder than I make it out to be.

[Gamma-UT]

I use both host and CC automation equally. It depends on the plugin, if it does not offer up CC controls I use host and visa versa. So I'm forced to say host automation because I don't think the survey answer of Host would have you skip CCs but the opposite might be true.

Unfortunately, I think you've got that backwards. A bunch of synths are automation-only because the devs think the DAW should do all that stuff (and is IMO a bit of a PITA). I think the question was intended to find out who is using CC rather than automation where available, though it could have been phrased better or at least provided the option to say both.

[Urs]

It's more like, to get a feel for the importance. Some people keep saying that MIDI was not necessary for plug-ins... so we wanna find out...

(I'm old school that way, I've been using MIDI since 1985, I don't know why an one would want anything else, and to me it's all natural... but if it turns out it's dead, then sure, I'll cope with that and work around it)

[Urs]

Also, our original first draft had like 80 questions, and we needed to get it down to 30 or so. So it's a bit "boiled down". If we see something in this curve that we think we need more detailed answers on, we'll simply do another survey.

[audiojunkie]

Can you please release the results of the survey when it is complete? I'd be really interested in seeing the results.

[audiojunkie]

It's more like, to get a feel for the importance. Some people keep saying that MIDI was not necessary for plug-ins... so we wanna find out...

(I'm old school that way, I've been using MIDI since 1985, I don't know why an one would want anything else, and to me it's all natural... but if it turns out it's dead, then sure, I'll cope with that and work around it)

Same here. MIDI is essential.

[Quasipro]

Thanks for the direct opportunity for feedback. Filled one out for Arturia too, regarding controllers. Seems everyone is seeking the Grand Unified Theory of soft/firm/hardware unification. Unfortunately, system OS is always changing…. So, 42!

[Urs]

Can you please release the results of the survey when it is complete? I'd be really interested in seeing the results.

We might post a summary, but the individual questions are not necessarily saying much.

For instance, we have published software for nearly 25 years. So many of our customers who have bought stuff when they were in their twenties, are in their forties now. Therefore, the average age of our user base naturally skews older than that of younger companies. Correlating the age question with the age and number of the products and the "how long have you..." question gives a more differentiated picture than "oh, looks like u-he have a really old user base". But if we post the plain results, you'll simply see just latter.

Plus, we have additional data (revenue, total number of licenses per product etc.), which help us "unskew" the survey.

[Chris-S]

Done!

[audiojunkie]

Can you please release the results of the survey when it is complete? I'd be really interested in seeing the results.

We might post a summary, but the individual questions are not necessarily saying much.

For instance, we have published software for nearly 25 years. So many of our customers who have bought stuff when they were in their twenties, are in their forties now. Therefore, the average age of our user base naturally skews older than that of younger companies. Correlating the age question with the age and number of the products and the "how long have you..." question gives a more differentiated picture than "oh, looks like u-he have a really old user base". But if we post the plain results, you'll simply see just latter.

Plus, we have additional data (revenue, total number of licenses per product etc.), which help us "unskew" the survey.

Oh, a summary is what I was referring to as well.