Zynaptiq Adaptiverb released

[Sampleconstruct]

I thought this little adaptiverbed piano impro was worth sharing in this thread, what an amazing plugin this is...

https://soundcloud.com/sampleconstruct/ ... adaptiverb

[TabSel]

It is. Indeed! How smooth the reverb tail harmonically blends with the piano, even though the "room" is really huge. No inharmonic smear. This is so fascinating!

[Hez]

Denis, would there be any possibility of adding a glide/portamento setting to the keyboard harmonic filter? Experimenting with some spacey drones this morning and when you're high on resynth/simplify the chord changes can sound quite abrupt. A way of setting the oscillators to gradually glide between snapshots (with variable time and possibly curve ideally) could sound really beautiful I think.

EDIT: And while I'm being a very demanding customer, microtuning support for this would be sick and make it a lovely partner for Kaleidoscope. Ideally implemented in a similar way, i.e. load a scale file and then set the root/centre note on the fly with a drop down, rather than having to continually bounce out .tun files every time you want to change key.

[Sampleconstruct]

I've been observing this for some weeks now and it's starting to nag me: when the UI of Adaptiverb is open, the graphics of all other plugins sort of freeze, get stuck, like it's interfering with something in the graphic card or whatever, this actually happens with all plugins and also with the UI in LogicX. Could be related to my dual monitor setup with a 27" Retina/thunderbolt monitor and a Sharp 4k 31.5" - anybody else experiencing this? I'm on a MacPro (newest model 12 core), OS is El Cap. I hoe this can get fixed soon...

[Sampleconstruct]

Just to add to this, as soon as I close the UI of Adaptiverb, all graphics go back to normal behavior.

[Sampleconstruct]

Here is a quick demo video demonstrating the bug, look at the Padshop Pro interface how the granular stream indicators freeze when the UI of Adaptiverb is opened. It also happens with Kaleidoscope and everything else I tested so far, but it seems that it only occurs if you insert Adaptiverb directly on an instrument track, so then the interface of the processed instrument will freeze/become unresponsive (not the instrument on the next track), will check again what happens when it's inserted on a Bus.

[Sampleconstruct]

That is weird indeed, when I insert Adaptiverb on a bus only the UI of the instrument freezes which is sent to that bus, the graphics of other instruments are no affected, how can that be, voodoo...

[TabSel]

Doesn't happen here...

Cubase 8.5.20 @ MacBook Pro late 2013 el Capitan 10.11.6, Padshop Instrument track fed by Midi, AV insert (checked with both VST and VST3), tried with various random presets for both Padshop and AV. Smooth GUI overall... Strange

[Sampleconstruct]

Doesn't happen here...

Cubase 8.5.20 @ MacBook Pro late 2013 el Capitan 10.11.6, Padshop Instrument track fed by Midi, AV insert (checked with both VST and VST3), tried with various random presets for both Padshop and AV. Smooth GUI overall... Strange

Thanks for checking, must be related to AU/LogicX then. I'll check Cubase 8 tomorrow and see if it also happens there.

[TabSel]

That is weird indeed, when I insert Adaptiverb on a bus only the UI of the instrument freezes which is sent to that bus, the graphics of other instruments are no affected, how can that be, voodoo...

Thread scheduling

Hosts calculate audio processing chains in parallel, using multiple threads, with thread synchronization on sinks. UIs are again different threads.

This is a clear indicator of a threading "issue", possibly logic, but triggered by AV. This will be hard to analyze

Is it just AVs UI influencing other UIs, or is it any (focused, or latest in processing chain) VSTs UI influencing any VSTs UI (unfocused, or earlier in the processing chain?

[Sampleconstruct]

That is weird indeed, when I insert Adaptiverb on a bus only the UI of the instrument freezes which is sent to that bus, the graphics of other instruments are no affected, how can that be, voodoo...

Thread scheduling

Hosts calculate audio processing chains in parallel, using multiple threads, with thread synchronization on sinks. UIs are again different threads.

This is a clear indicator of a threading "issue", possibly logic, but triggered by AV. This will be hard to analyze

Is it just AVs UI influencing other UIs, or is it any (focused, or latest in processing chain) VSTs UI influencing any VSTs UI (unfocused, or earlier in the processing chain?

It only happens with AV, I've never encountered this before, especially not this voodoo type of interference when sending a signal to a bus, that the plugin inserted on the bus (AV) messes up the graphics of the plugin which is generating the send signal, totally weird.

[TabSel]

do you have other plugins that are build using BlueCatAudios KITTY 2.0 framework? Like BlueCatAudio plugins? If so, could you test with replacing AV with these and see if the same happens?

If so, it might be a thread locking issue in the KITTY framework and Zynaptic has to consult BlueCatAudio, and they have some work to do and companies which licensed and use their KITTY might recompile with the possibly updated framework.

Nothing that will be fixed in the short run, I suspect...

[Sampleconstruct]

I don't have blue cats, never heard of them before actually.

[zynaptiq]

We'll have a look at the rendering thing.

It could be the CAIRO framework that we use for cross-platform 2D rendering – it generally wraps OS native stuff but who knows, maybe it's calling deprecated OS features or something like that.

At any rate: indeed not something that we can just sit down and fix because our part of the total code of the plugin doesn't do any drawing itself.

[zynaptiq]

I thought this little adaptiverbed piano impro was worth sharing in this thread, what an amazing plugin this is...

https://soundcloud.com/sampleconstruct/ ... adaptiverb

Lovely, man, really cool, thanks for sharing!