Kaizen DSP Choroboros (Public Beta)

[KaizenDSP]

..

KVR service has been pretty intermittent for me here, been waiting days to post this haha:"oh and did i forget to mention i ran a linux build? https://github.com/EsotericShadow/choro ... -x64.1.zip

need someone to test it out and see if it loads on their distro!"

cheers
Gabriel
Kaizen DSP

[FrettedSynth]

Running on MXLinux 23.2 xfce working great, wonderful sounding chorus thank you

[audiojunkie]

..

KVR service has been pretty intermittent for me here, been waiting days to post this haha:"oh and did i forget to mention i ran a linux build? https://github.com/EsotericShadow/choro ... -x64.1.zip

need someone to test it out and see if it loads on their distro!"

cheers
Gabriel
Kaizen DSP

Nice!!!

[audiojunkie]

Running on MXLinux 23.2 xfce working great, wonderful sounding chorus thank you

Awesome!!

[audiojunkie]

What's the difference between the paid version and the open source version?

[KaizenDSP]

What's the difference between the paid version and the open source version?

Great question! And glad to hear Linux is working well for you guys! thanks for the kind words.

The beta (open-source) version ships with 5 engines, 10 DSP cores, and the Dev Panel, so you can tweak, modify, and set things up just how you like within the limits of those 10 cores.

The commercial version, which I've already forked and done alot of work on, takes that a lot further. The Dev Panel is being reworked to include:

Custom Engine Builder: design your own engines with ease from scratch

Custom Asset Upload Pipeline: bring in your own visual assets for the UI(KnobForge, the 3D asset creator I made will be released free and open source along side the commercial Choroboros) as well as instructions and requirements for best practices regarding the assets.

Proprietary ".kzn" file format: cryptographically signed engine packages that bundle everything together

The vision is that anyone with the commercial version will be able to fully configure their own engines and DSP cores, then share them as a signed .kzn file and asset folder. Inside the plugin, you'll be able to upload a .kzn file to instantly port another user's custom engine into your Choroboros.

For example, say someone builds an engine that sounds really close to a C4, almost identical, and designs some assets to match the look. They export it from Choroboros, share it in a forum like this one, and anyone can download it, load it into their Choroboros, and instantly have that sound.

The .kzn files are cryptographically signed for two important reasons:

Provenance: if you make a unique creation and share it with the world, no one can take it and claim they made it. It's signed and timestamped, and if it's tampered with, it will no longer open in Choroboros.

Security: since the files are tamper-proof, bad actors can't inject malicious code through your plugin.

We're also planning to design additional DSP cores over time, which will extend the Engine Builder's capabilities even further. Some of these new cores won't ship with a factory engine, they'll be left open for the community to decide how to use. The goal is to propagate a creator economy around Choroboros, where people are building, sharing, and discovering engines made by other users.


love to know what thoughts on that are!

[KaizenDSP]

Running on MXLinux 23.2 xfce working great, wonderful sounding chorus thank you

glad its working on linux, i pushed that build out completely blind using github actions.

i have yet to run a linux vm and test it, windows(cubase specifically) and mac(logic is wierd) are keeping me really busy haha

[FrettedSynth]

Sounds amazing, found the developer panel wow. Running great so far, again thank you

[audiojunkie]

What's the difference between the paid version and the open source version?

Great question! And glad to hear Linux is working well for you guys! thanks for the kind words.

The beta (open-source) version ships with 5 engines, 10 DSP cores, and the Dev Panel, so you can tweak, modify, and set things up just how you like within the limits of those 10 cores.

The commercial version, which I've already forked and done alot of work on, takes that a lot further. The Dev Panel is being reworked to include:

Custom Engine Builder: design your own engines with ease from scratch

Custom Asset Upload Pipeline: bring in your own visual assets for the UI(KnobForge, the 3D asset creator I made will be released free and open source along side the commercial Choroboros) as well as instructions and requirements for best practices regarding the assets.

Proprietary ".kzn" file format: cryptographically signed engine packages that bundle everything together

The vision is that anyone with the commercial version will be able to fully configure their own engines and DSP cores, then share them as a signed .kzn file and asset folder. Inside the plugin, you'll be able to upload a .kzn file to instantly port another user's custom engine into your Choroboros.

For example, say someone builds an engine that sounds really close to a C4, almost identical, and designs some assets to match the look. They export it from Choroboros, share it in a forum like this one, and anyone can download it, load it into their Choroboros, and instantly have that sound.

The .kzn files are cryptographically signed for two important reasons:

Provenance: if you make a unique creation and share it with the world, no one can take it and claim they made it. It's signed and timestamped, and if it's tampered with, it will no longer open in Choroboros.

Security: since the files are tamper-proof, bad actors can't inject malicious code through your plugin.

We're also planning to design additional DSP cores over time, which will extend the Engine Builder's capabilities even further. Some of these new cores won't ship with a factory engine, they'll be left open for the community to decide how to use. The goal is to propagate a creator economy around Choroboros, where people are building, sharing, and discovering engines made by other users.


love to know what thoughts on that are!

Very interesting! So, these engines are all just chorus variations? Or are these engines (or DSP cores--not sure on the terminology) do different effects like delays, reverbs, etc?

[KaizenDSP]

right now the 10 DSP cores are all Chorus/modulation-focused, but they each take a fundamentally different approach. Some are cleaner and more transparent, others get into territory that sounds more like a flanger or a detune, and a couple go pretty experimental. So even within the chorus/modulation space, there's a huge range of tonal character depending on which core you use and how you configure it.

The new cores we design down the road will also be modulation cores. Choroboros is a chorus/modulation effect at its heart, and that's what it'll stay. But within that domain there's still a ton of unexplored territory, and the Engine Builder will let the community combine and configure those cores in ways we haven't even thought of yet.

For other effect types like reverb and delay, those will be their own dedicated tools built on the same philosophy, creator economy, and .kzn sharing, just purpose-built for their respective domains.

[pekbro]

I got my founders (or whatever) thing done.

[KaizenDSP]

I saw your feedback! also was looking into the issue you brought up about the info text not showing, but was unable to reproduce it in my environment.

if you can think of any other details, doesnt matter if its unrelated or not, please let me know!

[pekbro]

Ok, I will see what I can do over the weekend

[FrettedSynth]

Two small things on the graphics! The display beneath the knob sets about 14px too high, it's not centered on the box. The slider does not go the full length, it does go from 0-100% but not the length of the slider graphics.

[KaizenDSP]

Two small things on the graphics! The display beneath the knob sets about 14px too high, it's not centered on the box. The slider does not go the full length, it does go from 0-100% but not the length of the slider graphics.

on which? the main plugin interface? which colour? all of them?

youre on linux right?

thanks for letting me know! definitely something id like to get sorted before commercial launch

Cheers!