# Control feedback

**URL:** <https://forum.toplap.org/t/control-feedback/1155>\
**Category:** TidalCycles\
**Created:** [9 March 2020 23:43 UTC](https://forum.toplap.org/t/control-feedback/1155 "2020-03-09T23:43:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![victor-shepardson](https://forum.toplap.org/user_avatar/forum.toplap.org/victor-shepardson/32/633_2.png) [@victor-shepardson](https://forum.toplap.org/u/victor-shepardson)\
**Post date:** [9 March 2020 23:43 UTC](https://forum.toplap.org/t/control-feedback/1155/1 "2020-03-09T23:43:47Z")

</div>

it is possible to do this in BootTidal.hs:

```haskell
tidal <- startMulti [OSCTarget {oName = "Tidal", oAddress = "127.0.0.1", oPort = 6010, oPath = "/ctrl", oShape = Just [("phasor", Nothing)], oLatency = 0.02, oPreamble = [toDatum $ VS "phasor"], oTimestamp = BundleStamp}, (superdirtTarget {oLatency = 0.1, oAddress = "127.0.0.1", oPort = 57120})] (defaultConfig {cFrameTimespan = 1/20})

```

and then:

```haskell
p 1 $ pF "phasor" $ "1*64" |> (pi/32 + cF 0 "phasor") -- increments "phasor" every 1/64th cycle
p 2 $ s "bd*16" # speed (rangex 0.5 2 $ sin (cF 0 "phasor")) -- stateful LFO

```

feels like it should be possible to do something like this without the mild absurdity of making tidal send OSC to itself. But is it? Would there need to be special logic in onTick, like for cps patterning?

related: [How does trigger's implementation work? (Is it possible to have patterns react to each other?)](https://forum.toplap.org/t/how-does-triggers-implementation-work-is-it-possible-to-have-patterns-react-to-each-other/492)

---

<div class="post-metadata">

**Author:** ![victor-shepardson](https://forum.toplap.org/user_avatar/forum.toplap.org/victor-shepardson/32/633_2.png) [@victor-shepardson](https://forum.toplap.org/u/victor-shepardson)\
**Post date:** [15 March 2020 15:17 UTC](https://forum.toplap.org/t/control-feedback/1155/2 "2020-03-15T15:17:37Z")

</div>

also related: [https://github.com/tidalcycles/Tidal/issues/483](https://github.com/tidalcycles/Tidal/issues/483)