# Plugin feedback DAW automation

**URL:** <https://forum.cabbageaudio.com/t/plugin-feedback-daw-automation/2012>\
**Category:** Cabbage Stew\
**Created:** [28 June 2020 10:06 UTC](https://forum.cabbageaudio.com/t/plugin-feedback-daw-automation/2012 "2020-06-28T10:06:11Z")\
**Posts on this page:** 1\
**Showing post:** 26

<div class="post-metadata">

**Author:** ![Samo](https://forum.cabbageaudio.com/letter_avatar_proxy/v4/letter/s/71c47a/32.png) [@Samo](https://forum.cabbageaudio.com/u/Samo)\
**Post date:** [4 April 2021 08:22 UTC](https://forum.cabbageaudio.com/t/plugin-feedback-daw-automation/2012/26 "2021-04-04T08:22:13Z")

</div>

Hi!

I just wanted to mention that apart from the particularities of my setup, the feedback issue is illustrated also by other Cabbage plugins, as described [recently](https://forum-next.cabbageaudio.com/t/midi-controllable-custom-presets-csound-to-daw-feedback/2341). Rory introduced the reserved channel `CHNSET_GESTURES` to resolve this.

Now we can either have DAW automation playback working while internal parameter changes (by `chnset`) are not broadcast to the host (default, `chnset 0, "CHNSET_GESTURES"`) or we can broadcast changes, e.g. triggered by a preset change, but no automation playback enabled (`chnset 1, "CHNSET_GESTURES"`). Perhaps one could refer to the two states as the automation playback and record/performance modes. For me, this works fine since I don’t need playback and record/performance modes simultaneously. I’d refer you to this Rory’s example: [AutoTest.csd](https://forum-next.cabbageaudio.com/uploads/short-url/fpCaJ60EKD93kDUXwyGlmv6WlvD.csd) (889 Bytes)

I have some issues with AUs (which might be particular to my setup) but it works perfectly with VSTs.

---

_[View the full topic](https://forum.cabbageaudio.com/t/plugin-feedback-daw-automation/2012)._
