Pedantic nerd point: your beziers are not beziers days, are they? Looks like Catmull-Rom - they'll that doesn't quite make such a good brand-name.
I'm not trying to degrade your product, which, again, looks great, but you just targeted an area that is handled quite well in most DAWs already.
Have you considered turning this into a mobile app? Having this run on an iPad next to my keyboard with immediate access may be a better use case than alt-tabbing between my DAW and Bezie. And of course there are countless iOS DAWs that could make use of your advanced automations.
OP, have you looked at BitWig's midi controller API? I wonder if something could be done with that. I use BitWig.
I'd suggest showing this working with Traktor or Serato - Ableton can functionally do something like this already (with Max/MSP) in which case you're competing on UI. This sort of thing is basically impossible in Traktor, last I checked, so you're bringing a much bigger improvement to those users. The live DJ market also benefits much more from improvements to their MIDI controls. If you make a demo video like Ean Golden does with the Midi Fighter [1] or NI does with Traktor [2] I think you'd see significant interest.
Do you think using Bezie with FL studio would give the user a finer control over automation curve?
[1]: https://www.youtube.com/watch?v=DBM5gAm83ao&feature=youtu.be...
I've lost count of the number of times I've had to create an automation 'curve' using points to approximate a curve (particularly for filter cutoff frequency for fairly obvious reasons), so if I can find a way to integrate this well enough to make it work for me during sessions then it will be hugely appreciated. FWIW I'll give it a review on my (tiny) YT channel.
The sad thing about this is that these kind of facilities have been asked for for -years- by users of Cubase, and they haven't made it in to the feature set, despite the clear advantages they would give in creativity. I'm not a programmer (IANAP?), so I'm not sure how many man-years went into creating this, but surely it's not beyond the ken of people who have created something like Cubase to do this, or is it that there's something lurking in the code already that makes it much more difficult to do than if you do it from scratch? (Is this technical debt? I see the term sometimes)
If you're automating level and panning you need assorted log/lin/exp curves, not Beziers. You also need to be able to see the waveform you're automating, which is something Bezie fails to offer.
Parameters automation works better with standard ease in/out curves and keyframing. Beziers are a special case of a more general problem.
This looks very nice, but I'm not sure how useful it's going to be to most users in practice.
https://gamedev.stackexchange.com/questions/10277/equation-f...