Kushview Element plugin host

[VariKusBrainZ]

I presume VST and midi control of plugins hosted in the plugin is a feature to be added as unless a plugin is a synth they only present audio input and outputs

fyi I bought a licence

[Kalamata Kid]

I have Bidule.
https://www.plogue.com/products/bidule/

Is there a god reason to get Element?

What I would like additional in either:
a native 32-64 bit bridge.
Multi-touch keyboard.
Something similar to VSTforx https://www.vstforx.de/ but Multi-touch
Partial control of modules without having to open the GUI.
Assignable Multi-touch midi controller.
To be able to host MFX (cakewalk)

[VariKusBrainZ]

I have Bidule.
https://www.plogue.com/products/bidule/

Is there a god reason to get Element?

What I would like additional in either:
a native 32-64 bit bridge.
Multi-touch keyboard.
Something similar to VSTforx https://www.vstforx.de/ but Multi-touch
Partial control of modules without having to open the GUI.
Assignable Multi-touch midi controller.
To be able to host MFX (cakewalk)

MFX to VST wrapper

http://www.kvraudio.com/forum/viewtopic.php?t=177538

I bought Element because of the inro price and hope, ie I hope some interesting features are implemented

I dont currently see why it would merit $99 price tage based on the future festures hinted at but who knows

I have all the other modular vsts so in its current state Element brings nothing to the party. You might as well use IL Minihost as its currently more feature rich and useful.

[Kalamata Kid]

I have Bidule.
https://www.plogue.com/products/bidule/

Is there a god reason to get Element?

What I would like additional in either:
a native 32-64 bit bridge.
Multi-touch keyboard.
Something similar to VSTforx https://www.vstforx.de/ but Multi-touch
Partial control of modules without having to open the GUI.
Assignable Multi-touch midi controller.
To be able to host MFX (cakewalk)

MFX to VST wrapper

http://www.kvraudio.com/forum/viewtopic.php?t=177538

I bought Element because of the inro price and hope, ie I hope some interesting features are implemented

I dont currently see why it would merit $99 price tage based on the future festures hinted at but who knows

I have all the other modular vsts so in its current state Element brings nothing to the party. You might as well use IL Minihost as its currently more feature rich and useful.

Years ago I tried the MFX to VST wrapper with little success. I spent a lot of time and finally gave up.

Thanks for confirming that "Element brings nothing to the party."

I am looking forward to Audulus 4. Might be released this summer.
http://audulus.com/
viewtopic.php?f=1&t=452425
http://forum.audulus.com/discussion/157 ... r-input/p1

[VariKusBrainZ]

Years ago I tried the MFX to VST wrapper with little success. I spent a lot of time and finally gave up.

It worked with all the ones I tried which included those bundled with Sonar, NTONYX MFX Kit 1 and Kit 2 and a few others I cant remember.

[Kalamata Kid]

Years ago I tried the MFX to VST wrapper with little success. I spent a lot of time and finally gave up.

It worked with all the ones I tried which included those bundled with Sonar, NTONYX MFX Kit 1 and Kit 2 and a few others I cant remember.

I am glad you got it working. If I ever become desperate enough for some MFX plugins I will re-read the wrapper threads a lot more carefully. But knowing it is doable is very helpful.

[XComposer]

I am considering Element as a possible additional purchase. Complex elaborations of audio samples, also non-live, are a priority for me (like spectral transformations, sidechain-based morphing or vocoding and the like), much more than using synths or VSTi live.

I'm currently using Metaplugin and I am very happy with it: it can run 32-bit VST on my 64-bit AU-based Mac (with Logic Pro X), showing correctly even complex interfaces like, just for example, that of the old Cameleon synth (the one by the former company Camel Audio, now closed) and can save and recall very complex patches with multiple kinds of plug-ins inside.

Anyway, I'm always looking for modular chainers that allow to build one's own complex patches; it's almost like building your own instruments or your own complex plug-ins, so to speak.

So, just to understand better: could those who already use it please explain to me what would be the advantage of having also Element (over Metaplugin) and what are its main strong advantages, especially in my situation (AU, Mac) and with my priorities (complex audio elaborations, much more than using live synths)? And can the developers confirm that Kushview is really going to introduce a 32-bits to 64-bits bridging within Element, too, in a near future?

[bmcclure]

Element is awesome! I just got it today after searching around for the best solution to use as a plugin host inside my DAW that allows me to create and save plugin routing configuration. Another option would have been Bidule, but it was out of my current price-range for my use case.

I was a little bit frustrated with how using Midi FX works in Studio One--you have to put them on a separate track with the MIDI, and then route that to the input of an instrument track, which then has to always have Monitoring enabled for you to be able to hear anything.

I might have been able to find a better way in the DAW, but I preferred something I could configure different templates for and insert them as a single plugin in my DAW easily. Element has so far worked flawlessly for this purpose. I can route Element's MIDI in to Cream or Cthulhu, and route the MIDI out to any instrument(s) I choose, and then route the output of those instrument(s) to Element's outputs.

Element is capable of much more powerful things, but that simple use case makes the plugin more than worth it in my opinion, especially considering the introductory price (plus current Fall 2018 discount bringing the price down to like $20, it's a steal).

There are a few things that I hope will be improved, such as:
- Allowing to hide plugins which will then not show up next time you scan for plugins
- Allowing to recategorize plugins or fix plugins that don't have categories
- Add some sort of multi-tagging system for plugins to browse for them more easily
- Allow configuring Element and scanning for plugins when using it as a plugin inside another DAW, instead of requiring you to load it separately to do that
- There are several plugins that Element couldn't load when scanning, but it doesn't tell me what's wrong. Even just allowing me to rescan broken plugins only instead of all plugins would be helpful when troubleshooting these issues.

But none of these affect its usefulness or the ability for this to be used in production right now. I haven't run into any bugs that I could find, and would recommend this to anyone looking for a feature rich plugin host to use inside or outside their DAW that will surely only get better as it gets closer to final release.

[xbitz]

just a played a bit with the trial, but can't see how the different node values can be automated from outside the vst plugin, so seems the automation doesn't work under Studio One

[ReverendLove]

It doesn't work at all.
You can apply midi ccs and pcs only.
For me it’s a big disadvantage keeping me away from using it. Although I bought it a year ago. Still waiting and using metaplugin instead.Sadly an essentialfeature is missing.

[kushview]

just a played a bit with the trial, but can't see how the different node values can be automated from outside the vst plugin, so seems the automation doesn't work under Studio One

I'm currently working on a concept of "Performance Parameters" which will allow host automation in the plugin versions of Element. This far nobody has requested this feature, but after finding this post I've decided to start work on it.

[kushview]

It doesn't work at all.
You can apply midi ccs and pcs only.
For me it’s a big disadvantage keeping me away from using it. Although I bought it a year ago. Still waiting and using metaplugin instead.Sadly an essentialfeature is missing.

See my previous message about automation. As for MIDI mapping, I encourage you to go to https://kushview.net/feedback and let me know specifically what you need in the MIDI mapping department. Thanks!

[BeeDog]

I bought Element while on sale previously, and have to say I'm really happy at the rate of updates, awesome job. Wish more people would take a hint from you in that department

[ReverendLove]

It doesn't work at all.
You can apply midi ccs and pcs only.
For me it’s a big disadvantage keeping me away from using it. Although I bought it a year ago. Still waiting and using metaplugin instead.Sadly an essentialfeature is missing.

See my previous message about automation. As for MIDI mapping, I encourage you to go to https://kushview.net/feedback and let me know specifically what you need in the MIDI mapping department. Thanks!

I'm fine with the midi implementation. The "only" was referring to the lack of automation.
Iirc I sent a feature request for automation and modulation of plugin parameters after buying elements.
Your performance parameters are a good idea.

[kushview]

It doesn't work at all.
You can apply midi ccs and pcs only.
For me it’s a big disadvantage keeping me away from using it. Although I bought it a year ago. Still waiting and using metaplugin instead.Sadly an essentialfeature is missing.

See my previous message about automation. As for MIDI mapping, I encourage you to go to https://kushview.net/feedback and let me know specifically what you need in the MIDI mapping department. Thanks!

I'm fine with the midi implementation. The "only" was referring to the lack of automation.
Iirc I sent a feature request for automation and modulation of plugin parameters after buying elements.
Your performance parameters are a good idea.

Ok, I see. That one must've slipped through the cracks then. Apologies on that. In any case, I'm working on it now. Trying to get it done by this Friday. If not then, then the next release will have it!