Carstairs: Difference between revisions
From YM2149.org
Jump to navigationJump to search
No edit summary |
No edit summary |
||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
This project is dead, it will no longer be developed. | [[File:Coffin_spinning.gif]] This project is dead, it will no longer be developed. | ||
== Releases == | == Releases == | ||
Line 15: | Line 15: | ||
* To tell Carstairs where your programs will be, create a config file <code>[[libcarstairs.py]]</code> in the same dir as the <code>.so</code> file | * To tell Carstairs where your programs will be, create a config file <code>[[libcarstairs.py]]</code> in the same dir as the <code>.so</code> file | ||
** Unload and reload the plugin in Renoise to make it read the new config file | ** Unload and reload the plugin in Renoise to make it read the new config file | ||
[[Category:Software]] | [[Category:Software]] |
Latest revision as of 20:22, 17 February 2025
This project is dead, it will no longer be developed.
Releases
Usage
- You need a DSSI host, these instructions assume it's Renoise
- Put the
.so
file in~/.dssi
or add its dir toDSSI_PATH
- Note if
DSSI_PATH
is set then it must include~/.dssi
explicitly if you want Renoise to look there
- Note if
- If you now run Renoise you should see Carstairs in the list of available DSSI plugins
- It's a good idea to run Renoise in a terminal so you can monitor the logging
- The only program (in MIDI parlance) available is the default, which is enough to check that the spectrum of the square wave tails off before Nyquist
- To tell Carstairs where your programs will be, create a config file
libcarstairs.py
in the same dir as the.so
file- Unload and reload the plugin in Renoise to make it read the new config file