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

Hi,

I’m happy to announce apeCsound, a new apeSoft plugin and app that runs Csound 7code 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

More info: www.apesoft.it/apecsound

Happy Csounding!

Alessandro Petrolati
apeSoft

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

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

Thanks, Alessandro. Incredible.

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 https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

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 https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

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

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 https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

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

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

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 https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

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
apesoft.it

cropped-cropped-apeSoft-logo-1-1-180x180.png

](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 7code 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

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

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

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. :slight_smile: 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;
apesoft.it <http://www.apesoft.it/dev&gt;
     cropped-cropped-apeSoft-logo-1-1-180x180.png <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
  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&gt;&gt;
* *macOS* AU, VST3, Standalone: apeCsound.pkg <https://
http://www.apesoft.it/Download/apeCsound.pkg <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>>
* *Linux* VST3, Standalone: apeCsound-linux.zip <https://
http://www.apesoft.it/Download/apeCsound-linux.zip <http://www.apesoft.it/
Download/apeCsound-linux.zip>>
* *Source code:* GitHub <alessandropetrolati (Alessandro Petrolati) · GitHub
apeCsound <https://github.com/alessandropetrolati/apeCsound&gt;&gt;
More info:apeCsound – Electronic Music Software <http://www.apesoft.it/
><apeCsound – Electronic Music Software <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-
bin/ <https://listserv.heanet.ie/cgi-bin/&gt;wa?A0=CSOUND <https://
listserv.heanet.ie/cgi-bin/wa?A0=CSOUND <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://
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>
LISTSERV 16.5 - CSOUND List at LISTSERV.HEANET.IE <https://
listserv.heanet.ie/cgi-bin/wa?A0=CSOUND>
Send bugs reports to
Issues · csound/csound · GitHub <Csound · GitHub
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 <LISTSERV 16.5 - CSOUND List at LISTSERV.HEANET.IE; Send bugs
reports to Issues · csound/csound · GitHub <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
Send bugs reports to
      Issues · csound/csound · GitHub
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

Send bugs reports to
        Issues · csound/csound · GitHub
Discussions of bugs and features can be posted here

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
apesoft.it

cropped-cropped-apeSoft-logo-1-1-180x180.png

](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 7code 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

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

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

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