1. Summary/Title
Automation doesn’t work correctly with Beepstreet Dagger
2. Description
When I create an automation lane for a parameter in Dagger by recording it with RW enabled, I can’t edit it the way other lanes can be edited. It’s stepped, there are no lines that aren’t strictly horizontal or vertical. It’s not possible to create an angled line between two points. Also, the “Reduce” button doesn’t work, it only removes one of the selected points, then stops doing anything.
3. Expected Results
Adding two automation points connects them with one rising/declining line.
4. Actual Results
Adding two automation points connects them with one horizontal and one vertical line, creating a step.
5. Environment
iPad Pro 11” 2020 A12Z, latest versions of iPad OS and Cubasis.
As far as I know Cubasis doesn’t support using lines or curves when editing AUv3 automation. This affects all AUv3’s and is not isolated to Dagger.
Hopefully this situation will change someday but only @LSlowak knows if/when that will happen…
That’s what I thought at first, but I tried automating Magma effect, and it works well, the lines are present.
I primarily use LogicPro for iPad when I’m on the iPad and have no issues automating both of them?!
There’s also a slight difference in Cubasis when it comes to automating Effects vs Instruments for some odd reason?!
Just tested with Bleass Monolit. Automation works just as well, so I guess Cubasis handles automation well for AUv3 instruments, except Dagger.
Send Beepstreet a message about it and I’m quite sure He’ll fix it in due time…
…but I also know that Cubasis ‘cheats’ the AUv3 standard by ignoring touch & release-events which are part of the AUv3 standard so it might even get fixed when Cubasis finally adds ‘by the book’ support for AUv3 automation…
(Monolit also doesn’t fully support touch & release events so it’s a shaky situation).
I’m quite sure you’ll find plenty of other plug-ins with similar issues when used with Cubasis 
