# The "pulsar/atom plugin" thread

**URL:** https://uzu.lurk.org/t/the-pulsar-atom-plugin-thread/2244
**Category:** TidalCycles
**Tags:** questions
**Created:** [3 October 2020 14:15 UTC](https://uzu.lurk.org/t/the-pulsar-atom-plugin-thread/2244 "2020-10-03T14:15:59Z")
**Posts on this page:** 20
**Page:** 4

<div class="post-metadata">

### Author: ![ndr\_brt](https://uzu.lurk.org/user_avatar/uzu.lurk.org/ndr_brt/32/396_2.png) [@ndr\_brt](https://uzu.lurk.org/u/ndr_brt)
#### Post date: [26 February 2021 07:28 UTC](https://uzu.lurk.org/t/the-pulsar-atom-plugin-thread/2244/61 "2021-02-26T07:28:00Z")

</div>

That was my thought, but also in atom plugin could be implemented... maybe an "osc controlled mute/unmute", like the "osc eval" implemented by @mrreason.  
The midi to osc conversion could be leaved to sc.

I opened an issue on the tidal repository, but maybe it could be implemented also on atom plugin at this point 🙂

---

<div class="post-metadata">

### Author: ![cleary](https://uzu.lurk.org/user_avatar/uzu.lurk.org/cleary/32/177_2.png) [@cleary](https://uzu.lurk.org/u/cleary)
#### Post date: [26 February 2021 08:28 UTC](https://uzu.lurk.org/t/the-pulsar-atom-plugin-thread/2244/62 "2021-02-26T08:28:09Z")

</div>

Aha I get it now, sorry I didn't join the dots before 🙂

---

<div class="post-metadata">

### Author: ![mrreason](https://uzu.lurk.org/user_avatar/uzu.lurk.org/mrreason/32/3203_2.png) [@mrreason](https://uzu.lurk.org/u/mrreason)
#### Post date: [26 February 2021 11:05 UTC](https://uzu.lurk.org/t/the-pulsar-atom-plugin-thread/2244/63 "2021-02-26T11:05:40Z")

</div>

@cleary the idea of using MIDI here is great! I see my configuration growing 😃

As @ndr_brt said I think it would make more sense to use OSC for it and just to transform MIDI to OSC. Maybe we should think about a scalable format for handling OSC messages in the atom plugin?

---

<div class="post-metadata">

### Author: ![tedthetrumpet](https://uzu.lurk.org/user_avatar/uzu.lurk.org/tedthetrumpet/32/39_2.png) [@tedthetrumpet](https://uzu.lurk.org/u/tedthetrumpet)
#### Post date: [27 February 2021 11:23 UTC](https://uzu.lurk.org/t/the-pulsar-atom-plugin-thread/2244/64 "2021-02-27T11:23:34Z")

</div>

Just updated SC, Atom plugin and Tidal to latest everything… I'm getting `Variable not in scope: unmuteAll` when I try to do ctrl+0 to unmute all. This is on the Mac. Any ideas?

---

<div class="post-metadata">

### Author: ![ndr\_brt](https://uzu.lurk.org/user_avatar/uzu.lurk.org/ndr_brt/32/396_2.png) [@ndr\_brt](https://uzu.lurk.org/u/ndr_brt)
#### Post date: [27 February 2021 14:59 UTC](https://uzu.lurk.org/t/the-pulsar-atom-plugin-thread/2244/65 "2021-02-27T14:59:42Z")

</div>

Checkout the loaded BootTidal.hs file loaded... contains the unmuteAll definition like the one contained in the tidal codebase? ([https://github.com/tidalcycles/Tidal/blob/main/BootTidal.hs](https://github.com/tidalcycles/Tidal/blob/main/BootTidal.hs))

---

<div class="post-metadata">

### Author: ![tedthetrumpet](https://uzu.lurk.org/user_avatar/uzu.lurk.org/tedthetrumpet/32/39_2.png) [@tedthetrumpet](https://uzu.lurk.org/u/tedthetrumpet)
#### Post date: [27 February 2021 17:22 UTC](https://uzu.lurk.org/t/the-pulsar-atom-plugin-thread/2244/66 "2021-02-27T17:22:49Z")

</div>

Ah, right, I see, or at least I think I see. I had a custom BootTidal.hs based on the default fallback file in the plugin, but it looks like that one is a bit out of date. Now based my custom file on the one you linked to, all good!

---

<div class="post-metadata">

### Author: ![ndr\_brt](https://uzu.lurk.org/user_avatar/uzu.lurk.org/ndr_brt/32/396_2.png) [@ndr\_brt](https://uzu.lurk.org/u/ndr_brt)
#### Post date: [2 July 2021 17:32 UTC](https://uzu.lurk.org/t/the-pulsar-atom-plugin-thread/2244/67 "2021-07-02T17:32:34Z")

</div>

New release in town!  
The most interesting change is the introduction of [tidal-listener](https://github.com/tidalcycles/tidal-listener), is an "advanced feature" far from usable but is a good start.  
As always, any feedback is welcome

> **[Release v3.16.8 · tidalcycles/atom-tidalcycles](https://github.com/tidalcycles/atom-tidalcycles/releases/tag/v3.16.8)**
>
> Fix syntax highlighting for d10, d11, d12... #154
> Introduce new tidal-listener interpreter. #157

---

<div class="post-metadata">

### Author: ![hellocatfood](https://uzu.lurk.org/user_avatar/uzu.lurk.org/hellocatfood/32/42_2.png) [@hellocatfood](https://uzu.lurk.org/u/hellocatfood)
#### Post date: [5 July 2021 10:27 UTC](https://uzu.lurk.org/t/the-pulsar-atom-plugin-thread/2244/68 "2021-07-05T10:27:36Z")

</div>

Is there a way to have the code have a different background to the rest of the editor? e.g. as in the below screenshot?

 ![Screenshot from 2021-07-05 11-23-07](https://club.tidalcycles.org/uploads/default/original/2X/7/765c0cc8b595e8438680c2dddc5ef04ad9e2ab2b.png)

Currently I've been editing atom's stylesheet (Edit \> Stylesheet) and adding this code

```haskell
atom-text-editor span {
  background-color: #FFFFDD;
}

```

However, this means I can't see when code is highlighted (the highlight colour goes behind the text background colour). Is background colour for the code something that can be added to the atom plugin or is more of a case of perfecting the atom stylesheet?

---

<div class="post-metadata">

### Author: ![ndr\_brt](https://uzu.lurk.org/user_avatar/uzu.lurk.org/ndr_brt/32/396_2.png) [@ndr\_brt](https://uzu.lurk.org/u/ndr_brt)
#### Post date: [5 July 2021 12:00 UTC](https://uzu.lurk.org/t/the-pulsar-atom-plugin-thread/2244/69 "2021-07-05T12:00:07Z")

</div>

I'm always a little torn on what to do with stylesheet custom.  
Maybe the cleanest option is to leave this customizations into the atom stylesheet.

To keep it usable with selection maybe you could use a more soft color, like

```haskell
atom-text-editor span {
  background-color: @background-color-highlight
}

```

---

<div class="post-metadata">

### Author: ![ndr\_brt](https://uzu.lurk.org/user_avatar/uzu.lurk.org/ndr_brt/32/396_2.png) [@ndr\_brt](https://uzu.lurk.org/u/ndr_brt)
#### Post date: [12 July 2021 11:41 UTC](https://uzu.lurk.org/t/the-pulsar-atom-plugin-thread/2244/70 "2021-07-12T11:41:09Z")

</div>

New interesting feature for the newcomers: since v3.16.10 SuperDirt will be launched inside atom automatically. More info on the readme: [GitHub - tidalcycles/atom-tidalcycles: Atom package for TidalCycles](https://github.com/tidalcycles/atom-tidalcycles#superdirt)

> **[Release v3.16.10 · tidalcycles/atom-tidalcycles](https://github.com/tidalcycles/atom-tidalcycles/releases/tag/v3.16.10)**
>
> Launch SuperDirt automatically inside Atom

edit: new release that set superdirt autostart false by default:

> **[Release v3.16.11 · tidalcycles/atom-tidalcycles](https://github.com/tidalcycles/atom-tidalcycles/releases/tag/v3.16.11)**
>
> Set superdirt autostart to false by default

---

<div class="post-metadata">

### Author: ![Elefou](https://uzu.lurk.org/user_avatar/uzu.lurk.org/elefou/32/1495_2.png) [@Elefou](https://uzu.lurk.org/u/Elefou)
#### Post date: [12 July 2021 17:48 UTC](https://uzu.lurk.org/t/the-pulsar-atom-plugin-thread/2244/71 "2021-07-12T17:48:19Z")

</div>

I just tried the superdirt autostart both with and without superdirt\_startup.scd file in the folder where my .tidal file is but I get this error: "'sclang' could not be spawned. Is it installed and on your path? If so please open an issue on the package spawning the process." Should the startup file be somewhere else? What could be wrong?

---

<div class="post-metadata">

### Author: ![ndr\_brt](https://uzu.lurk.org/user_avatar/uzu.lurk.org/ndr_brt/32/396_2.png) [@ndr\_brt](https://uzu.lurk.org/u/ndr_brt)
#### Post date: [12 July 2021 18:47 UTC](https://uzu.lurk.org/t/the-pulsar-atom-plugin-thread/2244/72 "2021-07-12T18:47:22Z")

</div>

Is supercollider installed correctly? Why if you open a terminal and execute `sclang`?

---

<div class="post-metadata">

### Author: ![Elefou](https://uzu.lurk.org/user_avatar/uzu.lurk.org/elefou/32/1495_2.png) [@Elefou](https://uzu.lurk.org/u/Elefou)
#### Post date: [12 July 2021 19:06 UTC](https://uzu.lurk.org/t/the-pulsar-atom-plugin-thread/2244/73 "2021-07-12T19:06:53Z")

</div>

Yes, when I run supercollider with my startup file and then atom everything works fine. When I execute "sclang" on terminal I get: "-bash: sclang: command not found" (I'm on Mac if that helps).

---

<div class="post-metadata">

### Author: ![ndr\_brt](https://uzu.lurk.org/user_avatar/uzu.lurk.org/ndr_brt/32/396_2.png) [@ndr\_brt](https://uzu.lurk.org/u/ndr_brt)
#### Post date: [12 July 2021 22:13 UTC](https://uzu.lurk.org/t/the-pulsar-atom-plugin-thread/2244/74 "2021-07-12T22:13:21Z")

</div>

Uhm... I thought that supercollider would put the executables link into the $PATH also on mac os x, on linux that works out of the box.

---

<div class="post-metadata">

### Author: ![ndr\_brt](https://uzu.lurk.org/user_avatar/uzu.lurk.org/ndr_brt/32/396_2.png) [@ndr\_brt](https://uzu.lurk.org/u/ndr_brt)
#### Post date: [13 July 2021 15:42 UTC](https://uzu.lurk.org/t/the-pulsar-atom-plugin-thread/2244/75 "2021-07-13T15:42:12Z")

</div>

Maybe a new beginning, introduced the first version of code highlight using `tidal-listener` as interpreter.

![Peek 2021-07-13 17-32](https://club.tidalcycles.org/uploads/default/original/2X/1/165f9e205505c8262a9ec417eb35a76e9dbead82.gif)

Feedbacks welcome!

> **[Release v3.16.12 · tidalcycles/atom-tidalcycles](https://github.com/tidalcycles/atom-tidalcycles/releases/tag/v3.16.12)**
>
> Introduced first version of code highlight with tidal-listener

---

<div class="post-metadata">

### Author: ![igormpc](https://uzu.lurk.org/user_avatar/uzu.lurk.org/igormpc/32/2963_2.png) [@igormpc](https://uzu.lurk.org/u/igormpc)
#### Post date: [13 July 2021 20:32 UTC](https://uzu.lurk.org/t/the-pulsar-atom-plugin-thread/2244/76 "2021-07-13T20:32:38Z")

</div>

great news, thx ndr\_brt! 😃

how can i install & use tidal-listener? and how i enable code highlight on atom? i didnt find an example or help file...

---

<div class="post-metadata">

### Author: ![ndr\_brt](https://uzu.lurk.org/user_avatar/uzu.lurk.org/ndr_brt/32/396_2.png) [@ndr\_brt](https://uzu.lurk.org/u/ndr_brt)
#### Post date: [13 July 2021 21:54 UTC](https://uzu.lurk.org/t/the-pulsar-atom-plugin-thread/2244/77 "2021-07-13T21:54:07Z")

</div>

On linux you have to clone`tidal-listener` and execute `cabal install`  
There should be a way to install it on windows/Mac but I don't know how.  
To enable it select `tidal-listener` as interpreter into the atom-tidalcycles plugin configuration.  
Everything is still work in progress, so don't expect to perform live with this feature 😃

---

<div class="post-metadata">

### Author: ![ndr\_brt](https://uzu.lurk.org/user_avatar/uzu.lurk.org/ndr_brt/32/396_2.png) [@ndr\_brt](https://uzu.lurk.org/u/ndr_brt)
#### Post date: [14 July 2021 11:54 UTC](https://uzu.lurk.org/t/the-pulsar-atom-plugin-thread/2244/78 "2021-07-14T11:54:37Z")

</div>

Another progress on the use of `tidal-listener`, now pattern highlight works really well, only for a single pattern executed on the first line (we have to wait some improvements on `tidal-listener` itself to make it work for multiple patterns)

![Peek 2021-07-14 09-35](https://club.tidalcycles.org/uploads/default/original/2X/a/af0ff681170541785b3edf010c78c27d73479cc6.gif)

> **[Release v3.16.13 · tidalcycles/atom-tidalcycles](https://github.com/tidalcycles/atom-tidalcycles/releases/tag/v3.16.13)**
>
> Improve tidal-listener highlight visualization

---

<div class="post-metadata">

### Author: ![ndr\_brt](https://uzu.lurk.org/user_avatar/uzu.lurk.org/ndr_brt/32/396_2.png) [@ndr\_brt](https://uzu.lurk.org/u/ndr_brt)
#### Post date: [25 July 2021 10:03 UTC](https://uzu.lurk.org/t/the-pulsar-atom-plugin-thread/2244/79 "2021-07-25T10:03:00Z")

</div>

New version released, now with tidal-listener it's possibile to use multiple patterns, I used this feature in a live performance thursday and it worked pretty well!  
 ![Peek 2021-07-25 12-01](https://club.tidalcycles.org/uploads/default/original/2X/b/b9be6cdc68093a0b37f6cdc5db96431b10e109ea.gif)

> **[Release v3.16.14 · tidalcycles/atom-tidalcycles](https://github.com/tidalcycles/atom-tidalcycles/releases/tag/v3.16.14)**
>
> Handle multi pattern highlight visualization on tidal listener
> Add detailed logs on ghc and BootTidal file loading

---

<div class="post-metadata">

### Author: ![mrreason](https://uzu.lurk.org/user_avatar/uzu.lurk.org/mrreason/32/3203_2.png) [@mrreason](https://uzu.lurk.org/u/mrreason)
#### Post date: [25 July 2021 15:47 UTC](https://uzu.lurk.org/t/the-pulsar-atom-plugin-thread/2244/80 "2021-07-25T15:47:47Z")

</div>

Great job first! I tried to experiment with it but I got this error in Atom:

```haskell
t> Didn't typecheck GhcError {errMsg = ":1:1: error:\n \8226 Variable not in scope: d1 :: ControlPattern -> t\n \8226 Perhaps you meant \8216dt\8217 (imported from Sound.Tidal.Context)"}
error: GhcError {errMsg = ":1:1: error:\n \8226 Variable not in scope: d1 :: ControlPattern -> t\n \8226 Perhaps you meant \8216dt\8217 (imported from Sound.Tidal.Context)"}

```

I installed the `tidal-listener` with `cabal install tidal-listener.cabal` and the installation process looked fine. I switched from `Default` interpreter to `tidal-listener` in Atom and got the mentioned error. Do you have any idea what the problem could be?  
Many thanks in advance!

[Previous page](https://uzu.lurk.org/t/the-pulsar-atom-plugin-thread/2244.md?page=3)

[Next page](https://uzu.lurk.org/t/the-pulsar-atom-plugin-thread/2244.md?page=5)
