# \[Csnd\] \[ANN\] apeCsound – Csound 7 live inside your DAW

**URL:** <https://forum.csound.com/t/csnd-ann-apecsound-csound-7-live-inside-your-daw/2596>\
**Category:** The Csound Mailinglist\
**Created:** [October 25, 2026, 9:24am UTC](https://forum.csound.com/t/csnd-ann-apecsound-csound-7-live-inside-your-daw/2596 "2026-10-25T09:24:04Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![apeSoft](https://forum.csound.com/user_avatar/forum.csound.com/apesoft/32/810_2.png) [@apeSoft](https://forum.csound.com/u/apeSoft)\
**Post date:** [October 25, 2026, 9:24am UTC](https://forum.csound.com/t/csnd-ann-apecsound-csound-7-live-inside-your-daw/2596/1 "2026-10-25T09:24:04Z")

</div>

Hi,

I’m happy to announce **apeCsound** , a new apeSoft plugin and app that runs **Csound 7** code live inside your DAW.

Write or load a `.csd` file in the built-in editor, press **Apply** , and the engine recompiles while the track keeps playing. No restarts, no external tools.

**What you get**

- **An audio effect with MIDI input:** process the track audio, or play Csound instruments from MIDI.
- **144 DAW parameters** (Float, Int, Toggle, Menu) mapped to Csound channels, fully automatable.
- **A code editor made for Csound:** syntax highlighting, autocompletion, opcode help for the whole Reference Manual, and errors marked on the line.
- **Graphs** of function tables and signals, and a console with Csound’s messages.
- **Built-in examples** from the Cabbage and CsoundQt collections; their sliders, knobs and menus become parameters when the file is loaded.
- **OSC support** and multichannel tracks (up to 16 channels).

Designed for teaching, experimenting, sound design and electronic music.

**Download**

- **iPad** (AUv3 + app): [App Store](https://apps.apple.com/app/id6821382219)
- **macOS** (AU, VST3, Standalone): [apeCsound.pkg](https://www.apesoft.it/Download/apeCsound.pkg)
- **Windows** (VST3, Standalone): [apeCsound-win.zip](https://www.apesoft.it/Download/apeCsound-win.zip)
- **Linux** (VST3, Standalone): [apeCsound-linux.zip](https://www.apesoft.it/Download/apeCsound-linux.zip)
- **Source code:** [GitHub](https://github.com/alessandropetrolati/apeCsound)

More info: [www.apesoft.it/apecsound](https://www.apesoft.it/apecsound/)

Happy Csounding!

Alessandro Petrolati  
apeSoft

Csound mailing list [Csound@listserv.heanet.ie](mailto:Csound@listserv.heanet.ie) [https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND](https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND) Send bugs reports to [https://github.com/csound/csound/issues](https://github.com/csound/csound/issues) Discussions of bugs and features can be posted here

---

<div class="post-metadata">

**Author:** ![Dr\_Richard\_Boulanger](https://forum.csound.com/letter_avatar_proxy/v4/letter/d/0ea827/32.png) [@Dr\_Richard\_Boulanger](https://forum.csound.com/u/Dr_Richard_Boulanger)\
**Post date:** [October 25, 2026, 11:27am UTC](https://forum.csound.com/t/csnd-ann-apecsound-csound-7-live-inside-your-daw/2596/2 "2026-10-25T11:27:22Z")

</div>

WOW. Can’t wait to check this out and start sharing it with all the Live users at Berklee.

Thanks, Alessandro. Incredible.

---

<div class="post-metadata">

**Author:** ![apeSoft](https://forum.csound.com/user_avatar/forum.csound.com/apesoft/32/810_2.png) [@apeSoft](https://forum.csound.com/u/apeSoft)\
**Post date:** [October 25, 2026, 12:23pm UTC](https://forum.csound.com/t/csnd-ann-apecsound-csound-7-live-inside-your-daw/2596/3 "2026-10-25T12:23:00Z")

</div>

Dear Tarmo,

Thank you so much for your kind words and for taking the time to test it! It really means a lot to me.

I haven’t had the chance to test the Linux and Windows builds myself, as I compiled them using GitHub Actions, so I’m especially happy to hear that everything works well!

Thanks again for your support and encouragement.

A big warm hug!

Csound mailing list [Csound@listserv.heanet.ie](mailto:Csound@listserv.heanet.ie) [https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND](https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND) Send bugs reports to [https://github.com/csound/csound/issues](https://github.com/csound/csound/issues) Discussions of bugs and features can be posted here

---

<div class="post-metadata">

**Author:** ![giovanni\_damiani](https://forum.csound.com/letter_avatar_proxy/v4/letter/g/d2c977/32.png) [@giovanni\_damiani](https://forum.csound.com/u/giovanni_damiani)\
**Post date:** [October 26, 2026, 10:45am UTC](https://forum.csound.com/t/csnd-ann-apecsound-csound-7-live-inside-your-daw/2596/4 "2026-10-26T10:45:30Z")

</div>

Dear Alessandro,

I warmly gratulate for this very precious new frontend and interface with DAW!  
I appreciated and agreed with your keynote speech, and wondered that this new release was there just a modest appendix… very elegant and esthetically responsible attitude, I feel very in sympathetic resonance with this approach.  
And yet, I am enthusiast of this new environment, in Reaper MIDI-in and Audio-in is immediate, I will explore other ways to interact with: e.g. score to MIDIout (to visualize and monitor a score as PianoRoll) and so on. With  
Thanks!  
Giovanni

> Dear Tarmo,
> 
> Thank you so much for your kind words and for taking the time to test it! It really means a lot to me.
> 
> I haven’t had the chance to test the Linux and Windows builds myself, as I compiled them using GitHub Actions, so I’m especially happy to hear that everything works well!
> 
> Thanks again for your support and encouragement.
> 
> A big warm hug!
> 
> Csound mailing list [Csound@listserv.heanet.ie](mailto:Csound@listserv.heanet.ie) [https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND](https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND) Send bugs reports to [https://github.com/csound/csound/issues](https://github.com/csound/csound/issues) Discussions of bugs and features can be posted here

Csound mailing list [Csound@listserv.heanet.ie](mailto:Csound@listserv.heanet.ie) [https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND](https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND) Send bugs reports to [https://github.com/csound/csound/issues](https://github.com/csound/csound/issues) Discussions of bugs and features can be posted here

---

<div class="post-metadata">

**Author:** ![apeSoft](https://forum.csound.com/user_avatar/forum.csound.com/apesoft/32/810_2.png) [@apeSoft](https://forum.csound.com/u/apeSoft)\
**Post date:** [October 26, 2026, 2:39pm UTC](https://forum.csound.com/t/csnd-ann-apecsound-csound-7-live-inside-your-daw/2596/5 "2026-10-26T14:39:43Z")

</div>

Dear Giovanni,

Thank you so much for your kind words and for your appreciation of the new frontend. I’m really happy to hear that you’re already exploring it in Reaper!

It was truly an honour to participate as a keynote speaker at ICSC, and I’m very grateful for the opportunity.

Thanks again, and enjoy exploring!

Warmly,  
Alessandro

> Dear Alessandro,
> 
> I warmly gratulate for this very precious new frontend and interface with DAW!  
> I appreciated and agreed with your keynote speech, and wondered that this new release was there just a modest appendix… very elegant and esthetically responsible attitude, I feel very in sympathetic resonance with this approach.  
> And yet, I am enthusiast of this new environment, in Reaper MIDI-in and Audio-in is immediate, I will explore other ways to interact with: e.g. score to MIDIout (to visualize and monitor a score as PianoRoll) and so on. With  
> Thanks!  
> Giovanni
> 
> > Dear Tarmo,
> > 
> > Thank you so much for your kind words and for taking the time to test it! It really means a lot to me.
> > 
> > I haven’t had the chance to test the Linux and Windows builds myself, as I compiled them using GitHub Actions, so I’m especially happy to hear that everything works well!
> > 
> > Thanks again for your support and encouragement.
> > 
> > A big warm hug!
> > 
> > Csound mailing list [Csound@listserv.heanet.ie](mailto:Csound@listserv.heanet.ie) [https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND](https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND) Send bugs reports to [https://github.com/csound/csound/issues](https://github.com/csound/csound/issues) Discussions of bugs and features can be posted here
> 
> Csound mailing list [Csound@listserv.heanet.ie](mailto:Csound@listserv.heanet.ie) [https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND](https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND) Send bugs reports to [https://github.com/csound/csound/issues](https://github.com/csound/csound/issues) Discussions of bugs and features can be posted here

Csound mailing list [Csound@listserv.heanet.ie](mailto:Csound@listserv.heanet.ie) [https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND](https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND) Send bugs reports to [https://github.com/csound/csound/issues](https://github.com/csound/csound/issues) Discussions of bugs and features can be posted here

---

<div class="post-metadata">

**Author:** ![rory](https://forum.csound.com/user_avatar/forum.csound.com/rory/32/7_2.png) [@rory](https://forum.csound.com/u/rory)\
**Post date:** [October 28, 2026, 2:02pm UTC](https://forum.csound.com/t/csnd-ann-apecsound-csound-7-live-inside-your-daw/2596/6 "2026-10-28T14:02:13Z")

</div>

> What an age we live in though! We can load in csound and pure data via  
> plugdata in DAWs to create whatever we like.

I feel compelled to point out that we have been able to run Csound in a DAW for almost 20 years through Cabbage :rofl

But the more ways we have to do this the better, as far as I am concerned :+1

Csound mailing list [Csound@listserv.heanet.ie](mailto:Csound@listserv.heanet.ie) [https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND](https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND) Send bugs reports to [https://github.com/csound/csound/issues](https://github.com/csound/csound/issues) Discussions of bugs and features can be posted here

---

<div class="post-metadata">

**Author:** ![apeSoft](https://forum.csound.com/user_avatar/forum.csound.com/apesoft/32/810_2.png) [@apeSoft](https://forum.csound.com/u/apeSoft)\
**Post date:** [October 28, 2026, 2:11pm UTC](https://forum.csound.com/t/csnd-ann-apecsound-csound-7-live-inside-your-daw/2596/7 "2026-10-28T14:11:30Z")

</div>

Hello Brandon,  
thank you very much, I’m glad to hear the Linux build just worked: it gets less testing than the others, so that is good news.  
Good timing: apeCsound 1.0.5 was released this morning, and it answers your first question directly.

1. Host tempo. Yes. Since 1.0.5 I’ve released just this morning.

[

| 

[Dev](http://www.apesoft.it/dev)  
[apesoft.it](http://www.apesoft.it/dev)

 | 

[![cropped-cropped-apeSoft-logo-1-1-180x180.png](https://forum.csound.com/uploads/default/original/1X/42c2acd78e7ff2df36e77fe72adb8e5170686a93.png)](http://www.apesoft.it/dev)

 |

](http://www.apesoft.it/dev)

The host transport is available to your code as control channels, with the same names Cabbage uses:

csound  
kbpm chnget “HOST\_BPM”  
kplaying chnget “IS\_PLAYING”  
kppq chnget “HOST\_PPQ\_POS”  
plus IS\_RECORDING, TIME\_IN\_SECONDS, TIME\_IN\_SAMPLES, HOST\_PPQ\_BAR\_START, TIME\_SIG\_NUM, TIME\_SIG\_DENOM.  
They are updated once per block, so a tempo-synced delay is just kdel = 60 / kbpm \* knote.

There is a test file, CSD/Examples/Test/HostTransportTest.csd, and a section in the in-app Guide (Audio, MIDI and channels \> Host transport channels).

1. Instrument vs. effect. apeCsound is a single plug-in declared as an effect that accepts MIDI, because the same .csd can be an instrument, an effect or both, and most hosts accept MIDI into an FX plug-in. A separate “instrument” build is technically easy — it would be the very same binary with a different category flag — but it means shipping two plug-ins that are identical, and in my tests the two-identical-plugins approach is not clean everywhere: some hosts handle it fine, others get confused by two plug-ins sharing code, presets or state, and I can’t guarantee compatibility across all of them. So I haven’t done it yet. The Renoise workaround you mention (mixer effect + MIDI routing) is the intended path for now, and so is “Send all keyboard input”-style MIDI routing in other hosts.

That said, I’m open to it: if enough people hit this, a “apeCsound Instrument” variant (same code, synth category, no audio input) is on the table, and **any idea on how hosts you use behave with such pairs is welcome.**

Here is what changed in 1.0.5:

• VoiceOver support across the whole app: controls, menus, code editor and XY pad.  
• Live coding: Evaluate (Shift+Return) sends the selection, the instr block or the current line to the running engine without recompiling; an Evaluate line for one-liners such as i 2 0 1.  
• Channels panel (Cmd+4): every channel the engine knows, with type, direction, value and who writes it; channels the code reads and nobody writes are flagged, and can be mapped to a parameter in one click.  
• Monitor: values written with chnset shown as meters, sparklines, multi-bar cards and text, with chn\_k attributes (db, spark, int, hidden, group:Name).  
• Graphs: function tables are redrawn live when their content changes.  
• Host transport channels (see above); 64 toggle parameters (176 DAW parameters in all); XY pad cards from ; @xy “X” “Y”; groups from Cabbage containers; Option+click opens or closes all groups.  
• Snapshots menu stays open: tap to recall, pencil to overwrite, rename or delete.  
• Cabbage import: buttons are imported, menu defaults fixed, indicator widgets dropped first when slots run out.  
• Fixes: parameters no longer stay at 0 after Apply, errors are never hidden by the console filter, examples updated for Csound 7, six new test files.

And yes — Csound and Pure Data living inside a DAW, side by side, is a good age to be making sounds in.  
Thanks again, and keep the questions coming.  
Best, Alessandro

> Hello Alessandro,
> 
> I would like to thank you greatly for making this amazing csound plugin/frontend. This is a dream come true for me, as I’ve been really wanting a simple way to get my csound code into my DAWs of choice. Also, I would like to thank you for the great Linux version (it just worked when downloading it and loading it in my DAWs.)
> 
> I have two questions for you after playing around with it a little bit:
> 
> 1. Is there an easy way to get the vst host’s/DAW’s tempo? I would love to make some fun delays that take into account the tempo.
> 
> 2. When loading the plugin up in my beloved renoise, renoise only sees it as an FX plugin (it separates out FX and instruments). There is an easy workaround in renoise, but is there a way you could (or even I could modify something) so that there is also an instrument version? The plugin could literally be the same once loaded, this would allow me to load up the plugin in renoise as an instrument, instead of loading the plugin as a mixer effect and then routing renoise’s control data (midi) to it.
> 
> What an age we live in though! We can load in csound and pure data via plugdata in DAWs to create whatever we like.
> 
> Brandon Hale
> 
> > Hi,  
> > I’m happy to announce _apeCsound_, a new apeSoft plugin and app that runs _Csound 7_code live inside your DAW.  
> > Write or load a |.csd| file in the built-in editor, press _Apply_, and the engine recompiles while the track keeps playing. No restarts, no external tools.  
> > _What you get_
> > 
> > - _An audio effect with MIDI input:_ process the track audio, or play  
> > Csound instruments from MIDI.
> > - _144 DAW parameters_ (Float, Int, Toggle, Menu) mapped to Csound  
> > channels, fully automatable.
> > - _A code editor made for Csound:_ syntax highlighting,  
> > autocompletion, opcode help for the whole Reference Manual, and  
> > errors marked on the line.
> > - _Graphs_ of function tables and signals, and a console with Csound’s  
> > messages.
> > - _Built-in examples_ from the Cabbage and CsoundQt collections; their  
> > sliders, knobs and menus become parameters when the file is loaded.
> > - _OSC support_ and multichannel tracks (up to 16 channels).  
> > Designed for teaching, experimenting, sound design and electronic music.  
> > _Download_
> > - _iPad_ (AUv3 + app): App Store \<[https://apps.apple.com/app/id6821382219](https://apps.apple.com/app/id6821382219)\>
> > - _macOS_ (AU, VST3, Standalone): apeCsound.pkg \<https://  
> > [www.apesoft.it/Download/apeCsound.pkg](http://www.apesoft.it/Download/apeCsound.pkg)\>
> > - _Windows_ (VST3, Standalone): apeCsound-win.zip \<https://  
> > [www.apesoft.it/Download/apeCsound-win.zip](http://www.apesoft.it/Download/apeCsound-win.zip)\>
> > - _Linux_ (VST3, Standalone): apeCsound-linux.zip \<https://  
> > [www.apesoft.it/Download/apeCsound-linux.zip](http://www.apesoft.it/Download/apeCsound-linux.zip)\>
> > - _Source code:_ GitHub \<[https://github.com/alessandropetrolati/apeCsound](https://github.com/alessandropetrolati/apeCsound)\>  
> > More info: [www.apesoft.it/apecsound](http://www.apesoft.it/apecsound) \<[https://www.apesoft.it/apecsound/](https://www.apesoft.it/apecsound/)\>  
> > Happy Csounding!  
> > Alessandro Petrolati  
> > apeSoft  
> > Csound mailing list [Csound@listserv.heanet.ie](mailto:Csound@listserv.heanet.ie) \<[mailto:Csound@listserv.heanet.ie](mailto:Csound@listserv.heanet.ie)\> [https://listserv.heanet.ie/cgi-bin/](https://listserv.heanet.ie/cgi-bin/) wa?A0=CSOUND \<[https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND](https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND)\> Send bugs reports to [https://github.com/csound/csound/issues](https://github.com/csound/csound/issues) \<[https://github.com/ csound/csound/issues](https://github.com/%20csound/csound/issues)\> Discussions of bugs and features can be posted here
> 
> Csound mailing list  
> [Csound@listserv.heanet.ie](mailto:Csound@listserv.heanet.ie)  
> [https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND](https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND)  
> Send bugs reports to  
> [https://github.com/csound/csound/issues](https://github.com/csound/csound/issues)  
> Discussions of bugs and features can be posted here

Csound mailing list [Csound@listserv.heanet.ie](mailto:Csound@listserv.heanet.ie) [https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND](https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND) Send bugs reports to [https://github.com/csound/csound/issues](https://github.com/csound/csound/issues) Discussions of bugs and features can be posted here

---

<div class="post-metadata">

**Author:** ![Victor\_Lazzarini1](https://forum.csound.com/letter_avatar_proxy/v4/letter/v/3d9bf3/32.png) [@Victor\_Lazzarini1](https://forum.csound.com/u/Victor_Lazzarini1)\
**Post date:** [October 28, 2026, 2:32pm UTC](https://forum.csound.com/t/csnd-ann-apecsound-csound-7-live-inside-your-daw/2596/8 "2026-10-28T14:32:59Z")

</div>

For more complex VSTs you should really try Cabbage, cabbageaudio.com  
Prof. Victor Lazzarini  
Maynooth University  
Ireland

> \*Warning\*
> 
> This email originated from outside of Maynooth University's Mail System. Do not reply, click links or open attachments unless you recognise the sender and know the content is safe.
> 
> \> 1. Host tempo. Yes. Since 1.0.5 I’ve released just this morning.  
> Yay, happy to see this!
> 
> \> The Renoise workaround you mention mixer effect \+ MIDI routing is the  
> \> intended path for now, and so is “Send all keyboard input”-style MIDI  
> \> routing in other hosts.
> 
> Fair enough. 🙂 I'll keep doing this then, which doesn't seem like it  
> hurts anything. And as far as making a version with no audio input for  
> synth making: I'd honestly rather just have the full features in the  
> plugin for doing weird stuff, including audio input.
> 
> Luckily, the other DAW I use, reaper (which works great with apeCsound  
> on Linux), doesn't really care so much if something is labeled FX or  
> instrument. I wish all DAWs treated things this way, but not every DAW  
> can be as nice as reaper.
> 
> Lastly, do you think you might make a version or enable a feature to  
> allow for 64 or even 128 channels of audio inputs and outputs for  
> interesting DAW multichannel and high order Ambisonics workflows?
> 
> Brandon Hale
> 
> > Hello Brandon,  
> > thank you very much, I’m glad to hear the Linux build just worked: it  
> > gets less testing than the others, so that is good news.  
> > Good timing: apeCsound 1.0.5 was released this morning, and it answers  
> > your first question directly.
> > 
> > 1. Host tempo. Yes. Since 1.0.5 I’ve released just this morning.
> > 
> > Dev \<[http://www.apesoft.it/dev&gt](http://www.apesoft.it/dev&gt);  
> > apesoft.it \<[http://www.apesoft.it/dev&gt](http://www.apesoft.it/dev&gt);  
> > &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;cropped-cropped-apeSoft-logo-1-1-180x180.png \<[http://www.apesoft.it/dev&gt](http://www.apesoft.it/dev&gt);
> > 
> > \<[http://www.apesoft.it/dev&gt](http://www.apesoft.it/dev&gt);
> > 
> > The host transport is available to your code as control channels, with  
> > the same names Cabbage uses:
> > 
> > csound  
> > kbpm chnget "HOST\_BPM"  
> > kplaying chnget "IS\_PLAYING"  
> > kppq chnget "HOST\_PPQ\_POS"  
> > plus IS\_RECORDING, TIME\_IN\_SECONDS, TIME\_IN\_SAMPLES, HOST\_PPQ\_BAR\_START,  
> > TIME\_SIG\_NUM, TIME\_SIG\_DENOM.  
> > They are updated once per block, so a tempo-synced delay is just kdel =  
> > 60 / kbpm \* knote.
> > 
> > There is a test file, CSD/Examples/Test/HostTransportTest.csd, and a  
> > section in the in-app Guide (Audio, MIDI and channels \> Host transport  
> > channels).
> > 
> > 2. Instrument vs. effect. apeCsound is a single plug-in declared as an  
> > effect that accepts MIDI, because the same .csd can be an instrument, an  
> > effect or both, and most hosts accept MIDI into an FX plug-in. A  
> > separate “instrument” build is technically easy — it would be the very  
> > same binary with a different category flag — but it means shipping two  
> > plug-ins that are identical, and in my tests the two-identical-plugins  
> > approach is not clean everywhere: some hosts handle it fine, others get  
> > confused by two plug-ins sharing code, presets or state, and I can’t  
> > guarantee compatibility across all of them. So I haven’t done it yet.  
> > The Renoise workaround you mention mixer effect \+ MIDI routing is the  
> > intended path for now, and so is “Send all keyboard input”-style MIDI  
> > routing in other hosts.
> > 
> > That said, I’m open to it: if enough people hit this, a “apeCsound  
> > Instrument” variant same code, synth category, no audio input is on  
> > the table, and \*any idea on how hosts you use behave with such pairs is  
> > welcome.\*
> > 
> > Here is what changed in 1.0.5:
> > 
> > • VoiceOver support across the whole app: controls, menus, code editor  
> > and XY pad.  
> > • Live coding: Evaluate Shift\+Return sends the selection, the instr  
> > block or the current line to the running engine without recompiling; an  
> > Evaluate line for one-liners such as i 2 0 1.  
> > • Channels panel Cmd\+4: every channel the engine knows, with type,  
> > direction, value and who writes it; channels the code reads and nobody  
> > writes are flagged, and can be mapped to a parameter in one click.  
> > • Monitor: values written with chnset shown as meters, sparklines,  
> > multi-bar cards and text, with chn\_k attributes (db, spark, int, hidden,  
> > group:Name).  
> > • Graphs: function tables are redrawn live when their content changes.  
> > • Host transport channels see above; 64 toggle parameters (176 DAW  
> > parameters in all); XY pad cards from ; @xy "X" "Y"; groups from Cabbage  
> > containers; Option+click opens or closes all groups.  
> > • Snapshots menu stays open: tap to recall, pencil to overwrite, rename  
> > or delete.  
> > • Cabbage import: buttons are imported, menu defaults fixed, indicator  
> > widgets dropped first when slots run out.  
> > • Fixes: parameters no longer stay at 0 after Apply, errors are never  
> > hidden by the console filter, examples updated for Csound 7, six new  
> > test files.
> > 
> > And yes — Csound and Pure Data living inside a DAW, side by side, is a  
> > good age to be making sounds in.  
> > Thanks again, and keep the questions coming.  
> > Best,
> 
> Alessandro
> 
> > > Hello Alessandro,
> > > 
> > > I would like to thank you greatly for making this amazing csound  
> > > plugin/frontend. This is a dream come true for me, as I've been really  
> > > wanting a simple way to get my csound code into my DAWs of choice.  
> > > Also, I would like to thank you for the great Linux version (it just  
> > > worked when downloading it and loading it in my DAWs.)
> > > 
> > > I have two questions for you after playing around with it a little bit:
> > > 
> > > 1. Is there an easy way to get the vst host's/DAW's tempo? I would  
> > > love to make some fun delays that take into account the tempo.
> > > 
> > > 2. When loading the plugin up in my beloved renoise, renoise only sees  
> > > it as an FX plugin it separates out FX and instruments. There is an  
> > > easy workaround in renoise, but is there a way you could (or even I  
> > > could modify something) so that there is also an instrument version?  
> > > The plugin could literally be the same once loaded, this would allow  
> > > me to load up the plugin in renoise as an instrument, instead of  
> > > loading the plugin as a mixer effect and then routing renoise's  
> > > control data midi to it.
> > > 
> > > What an age we live in though! We can load in csound and pure data via  
> > > plugdata in DAWs to create whatever we like.
> > > 
> > > Brandon Hale
> > > 
> > > > Hi,  
> > > > I’m happy to announce \*apeCsound\*, a new apeSoft plugin and app that  
> > > > runs \*Csound 7\*code live inside your DAW.  
> > > > Write or load a |.csd| file in the built-in editor, press \*Apply\*,  
> > > > and the engine recompiles while the track keeps playing. No restarts,  
> > > > no external tools.  
> > > > \*What you get\*  
> > > > \* \*An audio effect with MIDI input:\* process the track audio, or play  
> > > > &nbsp;&nbsp;Csound instruments from MIDI.  
> > > > \* \*144 DAW parameters\* Float, Int, Toggle, Menu mapped to Csound  
> > > > &nbsp;&nbsp;channels, fully automatable.  
> > > > \* \*A code editor made for Csound:\* syntax highlighting,  
> > > > &nbsp;&nbsp;autocompletion, opcode help for the whole Reference Manual, and  
> > > > &nbsp;&nbsp;errors marked on the line.  
> > > > \* \*Graphs\* of function tables and signals, and a console with Csound’s  
> > > > &nbsp;&nbsp;messages.  
> > > > \* \*Built-in examples\* from the Cabbage and CsoundQt collections; their  
> > > > &nbsp;&nbsp;sliders, knobs and menus become parameters when the file is loaded.  
> > > > \* \*OSC support\* and multichannel tracks up to 16 channels.  
> > > > Designed for teaching, experimenting, sound design and electronic music.  
> > > > \*Download\*  
> > > > \* \*iPad\* AUv3 \+ app: App Store \<[https://apps.apple.com/app/](https://apps.apple.com/app/)  
> > > > id6821382219 \<[https://apps.apple.com/app/id6821382219&gt;&gt](https://apps.apple.com/app/id6821382219&gt;&gt);  
> > > > \* \*macOS\* AU, VST3, Standalone: apeCsound.pkg \<https://  
> > > > [http://www.apesoft.it/Download/apeCsound.pkg](http://www.apesoft.it/Download/apeCsound.pkg) \<[http://www.apesoft.it/](http://www.apesoft.it/)  
> > > > Download/apeCsound.pkg\>\>  
> > > > \* \*Windows\* VST3, Standalone: apeCsound-win.zip \<https://  
> > > > [http://www.apesoft.it/Download/apeCsound-win.zip](http://www.apesoft.it/Download/apeCsound-win.zip) \<[http://www.apesoft.it/](http://www.apesoft.it/)  
> > > > Download/apeCsound-win.zip\>\>  
> > > > \* \*Linux\* VST3, Standalone: apeCsound-linux.zip \<https://  
> > > > [http://www.apesoft.it/Download/apeCsound-linux.zip](http://www.apesoft.it/Download/apeCsound-linux.zip) \<[http://www.apesoft.it/](http://www.apesoft.it/)  
> > > > Download/apeCsound-linux.zip\>\>  
> > > > \* \*Source code:\* GitHub \<[alessandropetrolati (Alessandro Petrolati) · GitHub](https://github.com/alessandropetrolati/)  
> > > > apeCsound \<[https://github.com/alessandropetrolati/apeCsound&gt;&gt](https://github.com/alessandropetrolati/apeCsound&gt;&gt);  
> > > > More info:[apeCsound – Electronic Music Software](http://www.apesoft.it/apecsound) \<[http://www.apesoft.it/](http://www.apesoft.it/)  
> > > > \>\<[apeCsound – Electronic Music Software](https://www.apesoft.it/apecsound/) \<[https://www.apesoft.it/](https://www.apesoft.it/)  
> > > > apecsound/\>\>  
> > > > Happy Csounding!  
> > > > Alessandro Petrolati  
> > > > apeSoft  
> > > > Csound mailing listCsound@listserv.heanet.ie  
> > > > \<mailto:Csound@listserv.heanet.ie\>\<mailto:Csound@listserv.heanet.ie  
> > > > \<mailto:Csound@listserv.heanet.ie\>\>[https://listserv.heanet.ie/cgi-](https://listserv.heanet.ie/cgi-)  
> > > > bin/ \<[https://listserv.heanet.ie/cgi-bin/&gt;wa?A0=CSOUND](https://listserv.heanet.ie/cgi-bin/&gt;wa?A0=CSOUND) \<https://  
> > > > listserv.heanet.ie/cgi-bin/wa?A0=CSOUND \<[https://listserv.heanet.ie/](https://listserv.heanet.ie/)  
> > > > cgi-bin/wa?A0=CSOUND\>\> Send bugs reports tohttps://github.com/csound/  
> > > > csound/issues \<[https://github.com/csound/csound/issues&gt;&lt;https://](https://github.com/csound/csound/issues&gt;&lt;https://)  
> > > > github.com/ csound/csound/issues \<[https://github.com/%20csound/](https://github.com/%20csound/)  
> > > > csound/issues\>\> Discussions of bugs and features can be posted here
> > > 
> > > Csound mailing list  
> > > Csound@listserv.heanet.ie \<mailto:Csound@listserv.heanet.ie\>  
> > > [LISTSERV 16.5 - CSOUND List at LISTSERV.HEANET.IE](https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND) \<https://  
> > > listserv.heanet.ie/cgi-bin/wa?A0=CSOUND\>  
> > > Send bugs reports to  
> > > [Issues · csound/csound · GitHub](https://github.com/csound/csound/issues) \<[Csound · GitHub](https://github.com/csound/)  
> > > csound/issues\>  
> > > Discussions of bugs and features can be posted here
> > 
> > Csound mailing list Csound@listserv.heanet.ie  
> > \<mailto:Csound@listserv.heanet.ie\> [https://listserv.heanet.ie/cgi-bin/](https://listserv.heanet.ie/cgi-bin/)  
> > wa?A0=CSOUND \<[LISTSERV 16.5 - CSOUND List at LISTSERV.HEANET.IE](https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND&gt); Send bugs  
> > reports to [Issues · csound/csound · GitHub](https://github.com/csound/csound/issues) \<[https://github.com/](https://github.com/)  
> > csound/csound/issues\> Discussions of bugs and features can be posted here
> 
> Csound mailing list  
> Csound@listserv.heanet.ie  
> [LISTSERV 16.5 - CSOUND List at LISTSERV.HEANET.IE](https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND)  
> Send bugs reports to  
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[Issues · csound/csound · GitHub](https://github.com/csound/csound/issues)  
> Discussions of bugs and features can be posted here

The information contained in this email may be confidential and privileged. It is intended only for the addressees stated above. If you are not an addressee any use, dissemination, distribution, publication or copying of the information contained in this email is strictly prohibited. If you have received this email in error, please immediately notify us by email at dataprotection@mu.ie\<mailto:dataprotection@mu.ie\> and delete this email from your system.

Please note that Maynooth University is subject to Freedom of Information and Data Protection laws. We may be required to disclose the content of emails under the FOI Act 2014, the Data Protection Act 2018 or GDPR.

Is don seolaí / do na seolaithe thuasluaite amháin an ríomhphost seo. D’fhéadfadh an t-eolas atá ann a bheith rúnda agus faoi phribhléid. Mura seolaí tú, tá cosc iomlán ar aon eolas atá sa ríomhphost seo a úsáid, a scaipeadh, a dháileadh, a fhoilsiú nó a chóipeáil. Má fuair tú an ríomhphost seo trí thimpiste, cuir sin in iúl dúinn láithreach trí ríomhphost a chur chuig dataprotection@mu.ie\<mailto:dataprotection@mu.ie\> agus scrios an ríomhphost seo ó do chóras.

Tabhair faoi deara go bhfuil Ollscoil Mhá Nuad faoi réir dhlíthe um Shaoráil Faisnéise agus um Chosaint Sonraí. D’fhéadfadh ceangal a bheith orainn ábhar ríomhphoist a nochtadh faoin Acht um Shaoráil Faisnéise 2014, faoin Acht um Chosaint Sonraí 2018 nó faoi GDPR.

Registered charity number 20037130

Csound mailing list  
Csound@listserv.heanet.ie

> **[LISTSERV 16.5 - CSOUND List at LISTSERV.HEANET.IE](https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND)**

Send bugs reports to  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[Issues · csound/csound · GitHub](https://github.com/csound/csound/issues)  
Discussions of bugs and features can be posted here

---

<div class="post-metadata">

**Author:** ![Partev\_Sarkissian](https://forum.csound.com/letter_avatar_proxy/v4/letter/p/ce7236/32.png) [@Partev\_Sarkissian](https://forum.csound.com/u/Partev_Sarkissian)\
**Post date:** [November 14, 2026, 11:41pm UTC](https://forum.csound.com/t/csnd-ann-apecsound-csound-7-live-inside-your-daw/2596/9 "2026-11-14T23:41:15Z")

</div>

How well does this work with MOTU’s Digital Performer???  
Using Digital Performer DP11 on a MacBook Pro, Intel processor,  
running 15.8.3 Sequoia OS, in my case.

Thanks you,  
-Partev

> Hello Brandon,  
> thank you very much, I’m glad to hear the Linux build just worked: it gets less testing than the others, so that is good news.  
> Good timing: apeCsound 1.0.5 was released this morning, and it answers your first question directly.
> 
> 1. Host tempo. Yes. Since 1.0.5 I’ve released just this morning.
> 
> [
> 
> | 
> 
> [Dev](http://www.apesoft.it/dev)  
> [apesoft.it](http://www.apesoft.it/dev)
> 
> | 
> 
> [![cropped-cropped-apeSoft-logo-1-1-180x180.png](https://forum.csound.com/uploads/default/original/1X/42c2acd78e7ff2df36e77fe72adb8e5170686a93.png)](http://www.apesoft.it/dev)
> 
> |
> 
> ](http://www.apesoft.it/dev)
> 
> The host transport is available to your code as control channels, with the same names Cabbage uses:
> 
> csound  
> kbpm chnget “HOST\_BPM”  
> kplaying chnget “IS\_PLAYING”  
> kppq chnget “HOST\_PPQ\_POS”  
> plus IS\_RECORDING, TIME\_IN\_SECONDS, TIME\_IN\_SAMPLES, HOST\_PPQ\_BAR\_START, TIME\_SIG\_NUM, TIME\_SIG\_DENOM.  
> They are updated once per block, so a tempo-synced delay is just kdel = 60 / kbpm \* knote.
> 
> There is a test file, CSD/Examples/Test/HostTransportTest.csd, and a section in the in-app Guide (Audio, MIDI and channels \> Host transport channels).
> 
> 1. Instrument vs. effect. apeCsound is a single plug-in declared as an effect that accepts MIDI, because the same .csd can be an instrument, an effect or both, and most hosts accept MIDI into an FX plug-in. A separate “instrument” build is technically easy — it would be the very same binary with a different category flag — but it means shipping two plug-ins that are identical, and in my tests the two-identical-plugins approach is not clean everywhere: some hosts handle it fine, others get confused by two plug-ins sharing code, presets or state, and I can’t guarantee compatibility across all of them. So I haven’t done it yet. The Renoise workaround you mention (mixer effect + MIDI routing) is the intended path for now, and so is “Send all keyboard input”-style MIDI routing in other hosts.
> 
> That said, I’m open to it: if enough people hit this, a “apeCsound Instrument” variant (same code, synth category, no audio input) is on the table, and **any idea on how hosts you use behave with such pairs is welcome.**
> 
> Here is what changed in 1.0.5:
> 
> • VoiceOver support across the whole app: controls, menus, code editor and XY pad.  
> • Live coding: Evaluate (Shift+Return) sends the selection, the instr block or the current line to the running engine without recompiling; an Evaluate line for one-liners such as i 2 0 1.  
> • Channels panel (Cmd+4): every channel the engine knows, with type, direction, value and who writes it; channels the code reads and nobody writes are flagged, and can be mapped to a parameter in one click.  
> • Monitor: values written with chnset shown as meters, sparklines, multi-bar cards and text, with chn\_k attributes (db, spark, int, hidden, group:Name).  
> • Graphs: function tables are redrawn live when their content changes.  
> • Host transport channels (see above); 64 toggle parameters (176 DAW parameters in all); XY pad cards from ; @xy “X” “Y”; groups from Cabbage containers; Option+click opens or closes all groups.  
> • Snapshots menu stays open: tap to recall, pencil to overwrite, rename or delete.  
> • Cabbage import: buttons are imported, menu defaults fixed, indicator widgets dropped first when slots run out.  
> • Fixes: parameters no longer stay at 0 after Apply, errors are never hidden by the console filter, examples updated for Csound 7, six new test files.
> 
> And yes — Csound and Pure Data living inside a DAW, side by side, is a good age to be making sounds in.  
> Thanks again, and keep the questions coming.  
> Best, Alessandro
> 
> > Hello Alessandro,
> > 
> > I would like to thank you greatly for making this amazing csound plugin/frontend. This is a dream come true for me, as I’ve been really wanting a simple way to get my csound code into my DAWs of choice. Also, I would like to thank you for the great Linux version (it just worked when downloading it and loading it in my DAWs.)
> > 
> > I have two questions for you after playing around with it a little bit:
> > 
> > 1. Is there an easy way to get the vst host’s/DAW’s tempo? I would love to make some fun delays that take into account the tempo.
> > 
> > 2. When loading the plugin up in my beloved renoise, renoise only sees it as an FX plugin (it separates out FX and instruments). There is an easy workaround in renoise, but is there a way you could (or even I could modify something) so that there is also an instrument version? The plugin could literally be the same once loaded, this would allow me to load up the plugin in renoise as an instrument, instead of loading the plugin as a mixer effect and then routing renoise’s control data (midi) to it.
> > 
> > What an age we live in though! We can load in csound and pure data via plugdata in DAWs to create whatever we like.
> > 
> > Brandon Hale
> > 
> > > Hi,  
> > > I’m happy to announce _apeCsound_, a new apeSoft plugin and app that runs _Csound 7_code live inside your DAW.  
> > > Write or load a |.csd| file in the built-in editor, press _Apply_, and the engine recompiles while the track keeps playing. No restarts, no external tools.  
> > > _What you get_
> > > 
> > > - _An audio effect with MIDI input:_ process the track audio, or play  
> > > Csound instruments from MIDI.
> > > - _144 DAW parameters_ (Float, Int, Toggle, Menu) mapped to Csound  
> > > channels, fully automatable.
> > > - _A code editor made for Csound:_ syntax highlighting,  
> > > autocompletion, opcode help for the whole Reference Manual, and  
> > > errors marked on the line.
> > > - _Graphs_ of function tables and signals, and a console with Csound’s  
> > > messages.
> > > - _Built-in examples_ from the Cabbage and CsoundQt collections; their  
> > > sliders, knobs and menus become parameters when the file is loaded.
> > > - _OSC support_ and multichannel tracks (up to 16 channels).  
> > > Designed for teaching, experimenting, sound design and electronic music.  
> > > _Download_
> > > - _iPad_ (AUv3 + app): App Store \<[https://apps.apple.com/app/id6821382219](https://apps.apple.com/app/id6821382219)\>
> > > - _macOS_ (AU, VST3, Standalone): apeCsound.pkg \<https://  
> > > [www.apesoft.it/Download/apeCsound.pkg](http://www.apesoft.it/Download/apeCsound.pkg)\>
> > > - _Windows_ (VST3, Standalone): apeCsound-win.zip \<https://  
> > > [www.apesoft.it/Download/apeCsound-win.zip](http://www.apesoft.it/Download/apeCsound-win.zip)\>
> > > - _Linux_ (VST3, Standalone): apeCsound-linux.zip \<https://  
> > > [www.apesoft.it/Download/apeCsound-linux.zip](http://www.apesoft.it/Download/apeCsound-linux.zip)\>
> > > - _Source code:_ GitHub \<[https://github.com/alessandropetrolati/apeCsound](https://github.com/alessandropetrolati/apeCsound)\>  
> > > More info: [www.apesoft.it/apecsound](http://www.apesoft.it/apecsound) \<[https://www.apesoft.it/apecsound/](https://www.apesoft.it/apecsound/)\>  
> > > Happy Csounding!  
> > > Alessandro Petrolati  
> > > apeSoft  
> > > Csound mailing list [Csound@listserv.heanet.ie](mailto:Csound@listserv.heanet.ie) \<[mailto:Csound@listserv.heanet.ie](mailto:Csound@listserv.heanet.ie)\> [https://listserv.heanet.ie/cgi-bin/](https://listserv.heanet.ie/cgi-bin/) wa?A0=CSOUND \<[https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND](https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND)\> Send bugs reports to [https://github.com/csound/csound/issues](https://github.com/csound/csound/issues) \<[https://github.com/ csound/csound/issues](https://github.com/%20csound/csound/issues)\> Discussions of bugs and features can be posted here
> > 
> > Csound mailing list  
> > [Csound@listserv.heanet.ie](mailto:Csound@listserv.heanet.ie)  
> > [https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND](https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND)  
> > Send bugs reports to  
> > [https://github.com/csound/csound/issues](https://github.com/csound/csound/issues)  
> > Discussions of bugs and features can be posted here
> 
> Csound mailing list [Csound@listserv.heanet.ie](mailto:Csound@listserv.heanet.ie) [https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND](https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND) Send bugs reports to [https://github.com/csound/csound/issues](https://github.com/csound/csound/issues) Discussions of bugs and features can be posted here

Csound mailing list [Csound@listserv.heanet.ie](mailto:Csound@listserv.heanet.ie) [https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND](https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND) Send bugs reports to [https://github.com/csound/csound/issues](https://github.com/csound/csound/issues) Discussions of bugs and features can be posted here
