2CAudio Kaleidoscope

VST, AU, AAX, CLAP, etc. Plugin Virtual Effects Discussion
RELATED
PRODUCTS

Post

psynical wrote: Sat Mar 20, 2021 5:28 pm There's a 185 page thread about this plugin...

viewtopic.php?f=6&t=429862&p=8052937&hi ... e#p8052937
thanks - I will search through that as well

Post

not working in Studio One (resourcing issues) fine in Bitwig, fine in Reaper

Post

basically abandonware, Im afraid.
An idiot on Set Theory:
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."

Post

whyterabbyt wrote: Sun Mar 21, 2021 3:02 pm basically abandonware, Im afraid.
Feature set is fine for me so as long as it is maintained for stability on Windows and with my DAWs that is fine

Post

An attempt to answer some of your questions:

Images have to be in a certain format (PNG 24 or 48 bit with no transparancy channel, 1024 x 1024 pixels) and placed in the correct folder designated for user images. I don't find it a lot of hassle, though one can always wish for a more streamlined experience. It's a pretty unique piece of software so I'll just deal with this way of doing things.

It can sound quite different with different settings and different material, but you have to have a certain idea what you're doing and it takes time to get to know this program. It can have things turn out quite smooth textures, or rough and complicated rhythms and polyrhythms (polyrhythms through using 2 pictures that give rhythmic results and having suitably different timing for each of them), or ever morphing delays controlled by the image(s) loaded etc etc.

The control over resonators comes from the picture in combination with selecting scale etc, but the settings don't offer any detailed control over thinning out certain resonators while leaving others unaffected. You'd have to know how to edit the picture in question, and trying to thin out a select few resonators that way might be quite a challenge.

Post

Gone soft wrote: Mon Mar 22, 2021 12:09 am An attempt to answer some of your questions:

Images have to be in a certain format (PNG 24 or 48 bit with no transparancy channel, 1024 x 1024 pixels) and placed in the correct folder designated for user images. I don't find it a lot of hassle, though one can always wish for a more streamlined experience. It's a pretty unique piece of software so I'll just deal with this way of doing things.

It can sound quite different with different settings and different material, but you have to have a certain idea what you're doing and it takes time to get to know this program. It can have things turn out quite smooth textures, or rough and complicated rhythms and polyrhythms (polyrhythms through using 2 pictures that give rhythmic results and having suitably different timing for each of them), or ever morphing delays controlled by the image(s) loaded etc etc.

The control over resonators comes from the picture in combination with selecting scale etc, but the settings don't offer any detailed control over thinning out certain resonators while leaving others unaffected. You'd have to know how to edit the picture in question, and trying to thin out a select few resonators that way might be quite a challenge.
thanks, that is good info - I am going to try editing tuning tables today - that would be very quick and I want to see what happens when I have just one or two ratios.
And I dont have a feel for the wavetable tuning yet at all - looking at the red dot representation I intuitively imagine them as gated frequencies - but they aren't so I am not sure what if anything the shape of the wave is representing audibly

Post

Kudos for throwing yourself into editing tuning files. I got totally confused trying to work that out.

When you write "wavetable tuning" I assume you mean using wav files for tuning. There's no gating involved in the tuning (at least not as I see it and as I think of gating), it's just a different way to get a tuning. Any gating comes from the parts of the image you're using that are completely black. Black pixels should = silence. The red dots when loading a wav for tuning as far as I know represent frequencies, but they do indeed seem a bit all over the place and I'm not really sure what to expect until I just try it out. And only every fourth sample of the wav file is used so that might make it even more challenging to get predictable results. It's kind of mysterious to me, and I've only used it for more experimental and mostly metallic textures and for rhythmic results with the right pictures. As I'm using wav files created my me for tuning I feel it's a way to give me more personal results, though offcourse that can be debated. For detailed predictable control of tuning I reckon editing text files might be the way to go, and I'd suggest just have a more intuitive approach to wav files for tuning for now unless someone who actually has made complete sense of this can help you out.

Post

psynical wrote: Sat Mar 20, 2021 5:28 pm There's a 185 page thread about this plugin...

viewtopic.php?f=6&t=429862&p=8052937&hi ... e#p8052937
yes, there is. It's basically like reading a short story but fairly useless (to me) because of the signal/noise/advertising. i do not understand the "let's keep it to one thread" mentality.
i had the demo of Kaleidoscope, i found it quite fascinating but also extremely involved for programming with so so results. i determined that if i spent a looong time on it i would get some good results but didn't think it was worth it ( time and money).
gadgets an gizmos..make noise~crystalawareness.bandcamp.com/ soundcloud.com/crystalawareness Restocked: 7/2026
if this post is edited -it was for punctuation, grammar, or to make it coherent (or make me seem coherent).

Post

@Gone soft - I have worked through the tuning text file problems I was having - basically I did not need to import the files, they just appeared in the database. So I tested some some personal very sparse tunings and the results were stunning - as is, this is easily worth the money for me.
@CrystalWizard - yeah that is a very long thread - I used "search within results" to trim it down to something usable -and it was very usable then. The way I have attacked the editing is to feed it field recordings I have made and use very sparse text tuning files - just 12 values at the moment but I will do some that are only 2 or 3. I can understand the audible result much easier

Post Reply

Return to “Effects”