Hello. I’m new to Csound and very familiar with sound design. Starting off was more difficult than it should be due to the way information is presented. The opcode examples in the Csound reference manual are quite confusing to an educated beginner that has no coding experience. The way the examples are presented are quite a bit different from the way I write code. I can look at examples now with a good understanding of how to code Csound and still get confused by the examples.
I learned to write Csound in about two weeks and started cranking out plug ins. Ten finished so far in less than 60 days. Not basic plug ins either. Some are 1000 lines of code and have more than 50 controls. I’m going to keep going until I run out of ideas for plug ins.
At some point, I might write up a “How to Learn Csound the Fast Way” tutorial someday. It would be only one page long and would make it a lot easier for people to learn Csound.
One noob DSP tragedy to note. A cpu spike occurred while running Cabbage. The cpu spike was due to a coding error that produced too much compute demand. The end result is it fried my RME pci card the first time I tried to use the RME interface with Cabbage. That was an expensive lesson to learn. Ouch.
Then I tried to use a Native Instruments audio interface after fixing the cpu spike issue. ASIO did not work. The Windows basic tier driver did not work. A new Behringer interface works with the basic Windows driver. Do any ASIO drivers function with Windows and Cabbage?
Awesome! Sounds like you’ve been very productive. Note that the examples in the reference manual are for reference only. The Csound FLOSS manual is a better place to go to learn how to use Csound.
Which version of Cabbage have you been using? Version 2 has had ASIO support for quite a long time. What version are you using?
I’m sorry to hear you lost your RME interface, but a CPU spike was almost certainly not the reason this happened. This sounds like a hardware issue, most likely a fauly PSU
The RME interface had no issues. Then I tried to use it with Cabbage and it broke immediately. The power supply is fine. The breakout box is fine. The PCI card that communicates with the interface is blown.
I continue to use the RME interface with a laptop that has a different PCI card bus. According to RME, corrupt data streams can harm the PCI card. Or maybe Cabbage had nothing to do with it and this was just an unfortunate coincidence. I don’t think anyone can say for sure.
A modern Native instruments audio interface worked but produced flawed audio at any setting and any driver. So Cabbage is not communicating flawlessly with every windows audio interface. I don’t need ASIO for Cabbage. I just need something that works. The cheap Behringer interface works with Cabbage and the basic windows driver. Good enough for me.
The Behringer ASIO driver does not work with Cabbage. Unable to open device error. But the basic windows audio driver works. Windows exclusive mode driver does not work. Didn’t try the Windows low latency driver.
Correction. Windows exclusive mode driver actually does work. I made an error. Windows low latency driver also works. Direct Sound does not work. ASIO does not work. I will use exclusive mode.
Spoke too soon. Exclusive mode works IF you select it while Cabbage is open. But the app crashes in this mode after restarting the app then hitting play. I have to use the basic windows audio driver. Didn’t test the low latency mode after a restart.
I’m okay using the basic Windows driver. It sounds good enough for development. It’s not easy to tell the difference in sound quality using ASIO with other apps. ASIO is really only neccessary for DAW work. Thanks.
