Another popular VSTi adds microtonal support

www.wusik.com

Wusikstation v2 now supports .tun files.

Pasport197,

{you wrote...}
>www.wusik.com
>
>Wusikstation v2 now supports .tun files.

Yeah, everybody beware though! I bought this instrument, and I like it a lot, but as I just posted on their KVR forum yesterday, the microtuning is seriously broken: I haven't done exhaustive testing but many of the tunings simply don't work correctly, and it may be more of that "if it is more or less than 12 notes per octave it doesn't calculate correctly" syndrome. I told WilliamK, the dev, that I would document it better and send him info after I finish my current composing/recording project.

I imagine it *can* be fixed, but I'm not sure. This is the second or third instrument that has come about this way, and there may be a .tun format / microtuning block of source code that people are using without really understanding microtonal implementations. I'll try and help them get it sorted out, and when/if it starts working correctly I'll report back. Until then, it is still a very interesting instrument, and the current purchase gives you tons of sounds and presets, and it is pretty light on the CPU cycles.

Cheers,
Jon

Jon, you wrote:

> the microtuning is seriously broken [...]
> and it may be more of that "if it is more or less than
> 12 notes per octave it doesn't calculate correctly" syndrome.

I've seen that syndrome in other synths; e.g. a pre-alpha version of one
synth I was testing gave different timbres from the same settings,
depending on the tuning... Successfully fixed, of course.

> there may be a .tun format / microtuning block of source code
> that people are using without really understanding microtonal
> implementations

I'm not sure. The only sharable .tun code I know of is the Anamark code,
which in itself isn't broken. I would guess that probably some other subtle
12-tone assumptions are being made in oscillators, filters, and relations
between parameters. Probably some hard-coded goop that just needs to be
weeded out.

Rick

Rick,

{you wrote...}
>I've seen that syndrome in other synths; e.g. a pre-alpha version of one >synth I was testing gave different timbres from the same settings, >depending on the tuning... Successfully fixed, of course.

Glad it got sussed out. At first I thought it was more prone in instruments that were sample-based (for instance, VSampler is still unusable, and *that* dev doesn't even know the meaning of tech support), but the recent CronoX3 synth continues good implementation of sample usage with .tun compatability.

>I'm not sure. The only sharable .tun code I know of is the Anamark code, >which in itself isn't broken. I would guess that probably some other >subtle 12-tone assumptions are being made in oscillators, filters, and >relations between parameters. Probably some hard-coded goop that just >needs to be weeded out.

Hope so. I'm going to offer a handful of .tun files, mention which work and which don't, and burn some mp3s of both the broken tunings as well as correct tunings rendered with other instruments (in case they don't know what, say, 19tet should sound like!). I'm kind of bummed, as I was going to do my current dance project in a tuning or two, but some of the sounds came from non-micro sources. However, this is a work-in-progress, and by the next performance I may be able to get things back into intonations I'd like to mess with.

As to the synth in question - Wusikstation - the developer seems *very* responsive, so there is a good chance. I always figure that carping about microtonal support is coming from such a small niche that one can't _assume_ it will be prioritized, but you never know these days...

Cheers,
Jon