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.
- Host tempo. Yes. Since 1.0.5 I’ve released just this morning.
[
](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).
- 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:
-
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.
-
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
- 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
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