# Demo Songs

**URL:** <https://forum.csound.com/t/demo-songs/2544>\
**Category:** General\
**Created:** [September 12, 2026, 4:51pm UTC](https://forum.csound.com/t/demo-songs/2544 "2026-09-12T16:51:41Z")\
**Posts on this page:** 12\
**Page:** 2

<div class="post-metadata">

**Author:** ![hlolli](https://forum.csound.com/user_avatar/forum.csound.com/hlolli/32/3_2.png) [@hlolli](https://forum.csound.com/u/hlolli)\
**Post date:** [October 9, 2026, 4:46pm UTC](https://forum.csound.com/t/demo-songs/2544/21 "2026-10-09T16:46:08Z")

</div>

thanks @Thomas you’ve fixed a long standing issue with your suggestion. It’s fixed, keep 'em good suggestions coming 🙂

---

<div class="post-metadata">

**Author:** ![Thomas](https://forum.csound.com/letter_avatar_proxy/v4/letter/t/e36b37/32.png) [@Thomas](https://forum.csound.com/u/Thomas)\
**Post date:** [October 9, 2026, 8:45pm UTC](https://forum.csound.com/t/demo-songs/2544/22 "2026-10-09T20:45:01Z")

</div>

You’re welcome, and thanks for fixing. Plays nicely on my iPhone when in silent mode, too now, including my new Guitar Duett 😉  
Speaking of good suggestions: On the starting page in “popular projects”, when I click on one, it opens the project. I’d prefer a play button on the icon similar to the list of projects when opening an artist - directly play when clicking on the icon, open the project when clicking on the name of the project. So I could listen first, and when I like it, see how it was done in detail. More logical from a user experience point of view (for me).  
Good suggestion? 🙂

---

<div class="post-metadata">

**Author:** ![Thomas](https://forum.csound.com/letter_avatar_proxy/v4/letter/t/e36b37/32.png) [@Thomas](https://forum.csound.com/u/Thomas)\
**Post date:** [October 13, 2026, 3:31pm UTC](https://forum.csound.com/t/demo-songs/2544/23 "2026-10-13T15:31:05Z")

</div>

Hi, I have another issue: my new classical song “Sad Cello & Violent Violin” cannot be played, I get “Csound compilation failed. Read the console for details.”, but there are not messages on the console.

Found out it‘s the STKbow opcode that is unsupported on WASM. I just started implementing a WASM STK plugin, curious if Astra nails it 😉

---

<div class="post-metadata">

**Author:** ![hlolli](https://forum.csound.com/user_avatar/forum.csound.com/hlolli/32/3_2.png) [@hlolli](https://forum.csound.com/u/hlolli)\
**Post date:** [October 13, 2026, 4:34pm UTC](https://forum.csound.com/t/demo-songs/2544/24 "2026-10-13T16:34:25Z")

</div>

Your first suggestion I’ve implemented, you’ll see it later today after I merge dev to main.

Your second issue, was hidden because the log level was too low. I remember suggesting the logs were too noisy. The log level settings could be set to allow errors but ignore other logs.

The issue is:  
syntax error, unable to find opcode with name: STKBowed, line 393, columns 18-25 Parsing failed due to syntax errors Stopping on parser failure

The STK family opcodes have been moved over to plugins repo. Maybe good idea to start building and distributing the plugins as wasm binaries and support some of them, including the STK opcodes in the web-ide.

---

<div class="post-metadata">

**Author:** ![Thomas](https://forum.csound.com/letter_avatar_proxy/v4/letter/t/e36b37/32.png) [@Thomas](https://forum.csound.com/u/Thomas)\
**Post date:** [October 13, 2026, 5:17pm UTC](https://forum.csound.com/t/demo-songs/2544/25 "2026-10-13T17:17:27Z")

</div>

Thanks a lot! 🙂  
Oh, and Astra DID nail it: during my train ride from my home to my girlfriend, the WASM STK plugin was created and tested, and it is indeed able to play my new song with the STKbowed opcode.  
Exciting times we live in, a lot will change very soon in software development, that’s for sure…

See: [CsoundWebPlayer/plugins/stk at main · thomassresearch/CsoundWebPlayer · GitHub](https://github.com/thomassresearch/CsoundWebPlayer/tree/main/plugins/stk) for the code and [Csound Web Player · WASM proof of concept](https://thomassresearch.github.io/CsoundWebPlayer/) for the demo

---

<div class="post-metadata">

**Author:** ![hlolli](https://forum.csound.com/user_avatar/forum.csound.com/hlolli/32/3_2.png) [@hlolli](https://forum.csound.com/u/hlolli)\
**Post date:** [October 13, 2026, 5:30pm UTC](https://forum.csound.com/t/demo-songs/2544/26 "2026-10-13T17:30:46Z")

</div>

very nice, I have a todo to make the csound plugins in wasm, so it will arrive to web-ide in next days too

---

<div class="post-metadata">

**Author:** ![hlolli](https://forum.csound.com/user_avatar/forum.csound.com/hlolli/32/3_2.png) [@hlolli](https://forum.csound.com/u/hlolli)\
**Post date:** [October 15, 2026, 6:20am UTC](https://forum.csound.com/t/demo-songs/2544/27 "2026-10-15T06:20:21Z")

</div>

STK opcodes are now available in the web ide

---

<div class="post-metadata">

**Author:** ![Thomas](https://forum.csound.com/letter_avatar_proxy/v4/letter/t/e36b37/32.png) [@Thomas](https://forum.csound.com/u/Thomas)\
**Post date:** [October 15, 2026, 8:00am UTC](https://forum.csound.com/t/demo-songs/2544/28 "2026-10-15T08:00:12Z")

</div>

Wow amazing thanks a lot!

---

<div class="post-metadata">

**Author:** ![tarmo](https://forum.csound.com/letter_avatar_proxy/v4/letter/t/c37758/32.png) [@tarmo](https://forum.csound.com/u/tarmo)\
**Post date:** [October 15, 2026, 11:56am UTC](https://forum.csound.com/t/demo-songs/2544/29 "2026-10-15T11:56:23Z")

</div>

Thr Web IDE has developed a lot recently. Very cool!

Thanks!

Tarmo

N, 15. oktoober 2026 11:10 Huber \<[noreply@forum.csound.com](mailto:noreply@forum.csound.com)\> kirjutas:

---

<div class="post-metadata">

**Author:** ![hlolli](https://forum.csound.com/user_avatar/forum.csound.com/hlolli/32/3_2.png) [@hlolli](https://forum.csound.com/u/hlolli)\
**Post date:** [October 16, 2026, 5:13am UTC](https://forum.csound.com/t/demo-songs/2544/30 "2026-10-16T05:13:27Z")

</div>

thanks 🙏 @tarmo

---

<div class="post-metadata">

**Author:** ![Thomas](https://forum.csound.com/letter_avatar_proxy/v4/letter/t/e36b37/32.png) [@Thomas](https://forum.csound.com/u/Thomas)\
**Post date:** [October 18, 2026, 4:14pm UTC](https://forum.csound.com/t/demo-songs/2544/31 "2026-10-18T16:14:31Z")

</div>

Hi  
I found a bug in the STK plugin: it seems to assume a fixed sampling rate of 44.1kHz, independent of what is set in the CSD.  
Because of that, the pitches of my saxophone are off by 147 cents and sound wrong in my latest song “After Hours” ([Csound Web-IDE](https://ide.csound.com/editor/3UlA250pqrNeholJER81))

Astra says:  
In both STK adapter `init()` methods, call `stk::Stk::setSampleRate(csound->GetSr(csound))` **before constructing the instrument or calling `noteOn()`**. The WASM plugin currently retains 44.1 kHz internally, making saxophone playback at 48 kHz about 147 cents sharp. Rebuild and verify tuning at both sample rates, including successive runs with different rates.

Regards, Thomas

---

<div class="post-metadata">

**Author:** ![hlolli](https://forum.csound.com/user_avatar/forum.csound.com/hlolli/32/3_2.png) [@hlolli](https://forum.csound.com/u/hlolli)\
**Post date:** [October 18, 2026, 4:45pm UTC](https://forum.csound.com/t/demo-songs/2544/32 "2026-10-18T16:45:15Z")

</div>

[fix(stk): use the Csound sample rate in all instrument adapters by hlolli · Pull Request #58 · csound/plugins · GitHub](https://github.com/csound/plugins/pull/58) fix incoming

[Previous page](https://forum.csound.com/t/demo-songs/2544.md?page=1)
