Very impressive! Thanks for creating this. Was curious about csound, but never got around to exploring it.
simply paste a csd will not work as the communication with VCVRack must be done. the Csound module is also more designed to act as module what means that it should focus on one thing. in csd a complete “orchestra” can be programmed but in the Csound module i recommend to only use one one instrument (instr 1) and use multiple Csound modules in the patch if needed.
Definitely, thanks for the pointer. First test was with the simple VCO instrument running through the chorus by Ian McCurdy, no problems so far on a Mini M1. @docB This is great work !
Best regards,
dp
Gave it a whirl with the exciter from the csound docs with little prior csound experience.
Looking forward to giving it a more thorough go but a good start, thanks for adding it to Rack.
Here are some fixes, mainly the factory presets and pasting text on windows should work now
1 Like
Btw, if anyone is looking for a way into Csound I highly recommend Jim Aikin’s excellent Csound Power. It is indeed a comprehensive and very well-written guide into the environment.
Alas, it’s apparently out of print and now overpriced (on Amazon at least), but still definitely worth looking for.
1 Like
vcvRack 2.2.2 - win11?x64 CsoundModulePoly 2.0.3:
Hi, this is a beautiful module, MANY THANKS!!! When right click on CsoundModulePoly module, shows the Presets/Open options that refer to this path: C:\Users\USER\Documents\Rack2\presets\dbRackCsound\CsoundModule16 BUT the right presets are placed in one diverse path: C:\Users\USER\Documents\Rack2\plugins\dbRackCsound\presets\CsoundModule
When one preset is opened, Rack crashed;
Do you planned to add others pfield knobs/inputs for someother signal control?
thanks again, cheers
Restoring two posts which belong to this thread:
Hi,
another reference to Csound
https://flossmanual.csound.com/
greetings…
And:
I’ve been using its examples to create new presets. Also from here:
https://csound.com/docs/manual/index.html
Lots of cool things from Ian McCurdy:
1 Like
Hello thanks for finding these links and all the sounds, fxs from Iain McCurdy. So easiest way to use these is to put the Csound file in the correct folder of the docb module? That right?
no, currently there are normal presets in these folders and the csound code is stored as text in the preset. Csound code from other resources must be adapted anyway, as you want to communicate with other vcv rack modules via inputs and outputs and parameters. so a mix of looking at the current presets and the examples of McCurdy would be the best way to get it work.
Thanks, I’ll have a look at the presets and McCurdy as well, see if I can get my head around them.
Hi, thanks for this beautiful module! I ask you some things I have confusion as to what you mean by the 4 knobs P1, p2, p3, p4. I’ll explain myself better
when I compose a piece that will be rendered by csound, I use a score, and in this score the “P-Field 1” OR P1, inform which instrument will be played, P2 tells csound WHEN to PLAY the note and the “P-Field 3” OR P3 tells csound HOW LONG IT SHOULD PLAY.
dBRackCsound is a real-time module. Pitch and Note-on Time is managed via MIDI in the case of the instrument. In the GUI you indicate P1, P2 and P3 as inputs for what?
Have you considered adding more P-type inputs?
In your opinion, is it possible to create a module that allows you to add widgets that allow you to change the values in real time through reserved channels? for example
right click on the form /add/slider or /knob or /input jack or else
the added slider will be renamed “volume1” and then the “reserved channel” to receive the values of this slider in csound will be “volume1”
thanks again 4all
hi,
the module has a simple model regarding the csound p parameters:
p1=1, p2=0, p3=-1 and p4 is the polyphonic channel for which the instrument is activated so it can be used directly for that (see factory examples). All other parameters must be passed as k rate channel parameters via the P1-P4 knobs or the 4 polyphonic inputs.
As we are in a modular environment this module is not designed for making a full orchestra with hundreds of parameters - instead the idea is that complex csound code can be devided into multiple Csound module instances. (see e.g. video in the manual section).
If several users would like to have more than 4 knobs and inputs there would be place on the module for that. But i decided to wait for corresponding github issues.
I do not plan to make any special instruments using csound, as i would implement them vcvrack native.
I also do not plan to make a generic ui interface because of too much effort and i can make it with the current Csound module and MindMeld PatchMaster.
Thanks again for all and also for your quick response… 
Regards
Perhaps an expander module would be more appropriate ?
yes and no. i really want to engage users to do small things with a csound module and use then more of them. as i mentioned i could provide e.g. 4 more knobs and at least two more inputs on the existing module.
I have a feature request for your Chords module … its almost perfect , better then many others with its auto channels and auto reorder … perfect for feeding into arpeggiator but there is one missing piece ,an option to choose the ordering\time offset between the notes to get better control of an arpeggiator that can order notes as they were played.
maybe something simple like color coding via spectrum colors (red to purple) where the first note chosen is the first.
have you tried the Squinkronix arpeggiator? I think it’s pretty nice.
hi so you mean in this case
where the auto order is turned off, and the notes are played in the order as they were selected, then there could be a visual support via colors indication the order. I will look into that for the next version. (Btw: this thread is the dbRackCsound thread, Chords belong to dbRackSequencer …)
1 Like