Snappy Snap _plugin Host for live creative Jams with VST/AUs / Has: morph, preset switching, randomisation, sideChain

[Funky40]

I´ve also installed now the full trial. ( same download / you get a 7 days license)

The plugin load process is here completely different than it is in the free LE. Looks good.


- The "show plugin" button is here also not CC mappable. ( i effectivly use this and do map this to HW controls)
- The GUI of the loaded plugin is not closing. Even not when i switch the "patch" in GP (host). Even when i delete the Snappy instance, iirc, or replace the plugin inside snappy, iirc......( i had to check again. I made this noon a long post, but entered preview rather than send, and closed then the forum / lost my post)
These points would me my feature requests


Some more observations:
- dealing with ZL3 (zebralette3) yesterday, it did show me the changes of the parameters while morphing.
- today not.
I was doing something different when i mapped to Snap1 and 2. I need to have there a closer look again.

It´s interesting, using such a plugin like Snappy brings things into ones focus that you´∂ just not be aware of.
In my case: i know now, i definitly want to have that visual feedback from the plugin, seeing how parameters chnage, and seeing which values are active. This makes a difference to me.


Seems that this is working with some plugins, while with others not.
I would guess that this is not in the hands of Snappy or its dev ? ...rather than beeing a thing of the used plugins itself ?

- Absynth6 did not give me a visual feeback.
- ZL3 did yesterday, today with the new patch with snappy-full, it did not.
- GRM Atelier FX did not ( this one is a major case for me / i wanted to get to have the old GRM Tools superslider functionality back. I thought Snappy couild be it here / but re. this usecase the visual feedback would be crucial for me )

Also, i started to understand that for some usecases i had in mind, i finally also want to be able to have contrtol "from outside" to some parameters individually. Like lets say with a WT Synth like Microwave1, morph between presets, but have the "WAve" parameter accessible independently at the same time. This is not possible.

I wonder here @inkie if there are restrictions for you as a Dev you just can´t work around, or is it in theory possible to gain access to the used plugins parameters twice ?
- have access for your morph control
- but have a 2nd access for a individual CC mapping. ( direct or by appling a makro control)
This last point is a crucial point for me.

My pirmary idea waht for i´d want to use Snappy was/is to create EQ morphs.
I´ve not tested this out so far.
There for example could i live with that (2nd access) restriction.
But i need to check if my EQ gives back vidual feedback or not.


I would say there are some small details re. the Snappy plugin that could make for one user a difference, but not for another. Our wishes and usecases differ !......it´s definitly usecase and "specific plugin" sensible.
I would say with this plugin is it a good idea to check some things for yourself, and invest some time into some testings.

It´s clear that several things depend on the loaded plugins, rather than Snappy itself.

[inkie]

Ah, learn mode for macro knobs is just to expose parameters from your loaded plugin to DAW.

And learn mode above the snapshot is for exclusive randomization.

It is two different features. I recommend to look at users manual to see the logic behind them.

[inkie]

"Like lets say with a WT Synth like Microwave1, morph between presets, but have the "WAve" parameter accessible independently at the same time. This is not possible."

For this one you should use macro knobs they are exactly for this scenario, and they auto excluded from morphing, I demo it on the video.

[aMUSEd]

Looks like the closest thing to the late lamented NI Kore 2 - as long as it is as stable

[Thymos]

It would be great if there would be mouseover effects, which blend in a short description about what button xyz does.

[Uncle E]

Really liking the morphing. Needs to be able to exclude parameters.
Didn't get good results from the Randomizer.
Getting stuck notes.
Needs a minimum of 16 macro controls to match most midi controllers.
It would be awesome if it could load multiple plugins and morph between them.

[Funky40]

Ah, learn mode for macro knobs is just to expose parameters from your loaded plugin to DAW.

"Like lets say with a WT Synth like Microwave1, morph between presets, but have the "WAve" parameter accessible independently at the same time. This is not possible."

For this one you should use macro knobs they are exactly for this scenario, and they auto excluded from morphing, I demo it on the video.

Ahh, i understand.....
But there is this:
i use GigPerformer as my host.
ANY CC mapping i do is based on using the "daw automation" context.




This is how GP works !
GP would not hinder me to CC map directly to a plugin. BUT: to CC map things out the way GP works has some crucial advantages ! You are into live play stuff, ...looping...and such. Maybe you should look into GP ?

I explain you quickly the CC mapping in GP:
in GP there is a inbetween layer called "Widgets". These are virtual Faders, Knobs, bottons, etc.
With those do we create a graphical "control surface". For example can we mirror our own HW control setup ( yes, it´s work to do so / but the recommended approach). Now: We do map "these Widgets" to the plugins !.....which is based on using "DAW automation". Then: we map our midi HW controls => to these Widgets.

Looks tedious and unnecessary overcomplicate at first. BUT: it is the key for several things that makes GP so so SO SO great ! (at least re. my usages / other folks like it more based on other things)



Inkie, you could try to ask David for a NFR license. offer him the value equivalent of yours
I would guess it "could be" very useful for your own personal uses.

It´s imho by far the most powerful "live-play" host around. (it´s a node based host. quasi a modular patch environment for the use with plugins) ( we can accomplish there insane things)
....quasi all live-play folks who use GP say: ".......then i found GP, and never looked back"
( and that´s exactly how it is )

[Funky40]

ahh wait, my quote was to some degree wrong:

"Like lets say with a WT Synth like Microwave1, morph between presets, but have the "WAve" parameter accessible independently at the same time. This is not possible."

For this one you should use macro knobs they are exactly for this scenario, and they auto excluded from morphing, I demo it on the video.

i exactly "don´t want" to have the Wave knob auto exclouded from the morphing in this case !
i do use right now the macro knob, as you say.

my wish would be to be able to have both at the same time:
- Snappys morph incloudes said Wave knob
- but i ´d want to be able to CC map another individual HW control to said Wave knob as well ( by using host automation)

- since i have to use the makro knob to do so,...based on using host automation.....is the auto exclusion working against my goals.

The question is:
- is it even possible for you -as the dev-. to access the "loaded plugins" parameters two times ?
- 1x from the Snap-Morph side of things
- 1x from the makro knob side of things

each would then be able to override the other one, vs. the set value. ( The control applyed last would set the value)


i mean, even cooler would be if a makro knob "could be set" to act as an offset re. the snap-morph value

[Funky40]

Needs to be able to exclude parameters.

You can do re. the snap-morphs: map the parameter you want to excloude to a makro knob
i thought we can also exloude re. randomisation. I thought gthere is a setting.

Needs a minimum of 16 macro controls to match most midi controllers.

+1. Would be very welcome

It would be awesome if it could load multiple plugins and morph between them.

Now that would be something ! Ohh boy ( while it could open a rattail of new wishes at same time)

[Funky40]

The full version (demo) creates problems here vs. GP-host.

unfortunately i just lost a very long post describing everything.
i made many tests, work, etc...quite a bit to tell.....

i´l repost next week, hopefully.
I´d say, versus Gigperformer would some testing be due.
Has to do with the GUI it seems.
One problem was definitivly the GUI....Snappy creeping out and changing the GUI into something simple ( see screenshot/cancel: not loading....)

the other problem led to startup problems with GP. I´ve never seen such a problem bevore re. GP.
Could be that this was GUI related too. Or a communictation problem within Snappy re. its loaded plugin ?
Looks to me like there are several things to watch out for vs. debugging or optimisation. At least re. GP.
(ohh ok, can´t add my new screenshot either / says file too big....wtf ....it´s not big)

[inkie]

Really liking the morphing. Needs to be able to exclude parameters.
Didn't get good results from the Randomizer.
Getting stuck notes.
Needs a minimum of 16 macro controls to match most midi controllers.
It would be awesome if it could load multiple plugins and morph between them.

Great feedback!

But in terms of multiple plugins, there is a Link-Lead mode, i demonstrated it in the video.
Load snappysnap1 with 'reverb'>enable Link and Lead.
Load snappysnap2 with 'distortion'>enable Link only.

After that Everything you do on snappysnap1 will be replicated on snappysnap2. So you can add then snappysnap3 with Link enabled, and you will have one master snappysnap controlling other two. Just be careful, morphing 3 plugins with 500+ parameters can hit your CPU hard.

[Funky40]

Just be careful, morphing 3 plugins with 500+ parameters can hit your CPU hard.

thats what happened here in GP. That was without link enabled btw..

I start to understand some observations i was running into.
I did not think about that you effectivly would morph all parameters. Respectivly have to "back and forth communicate" with each parameter.



i finally started yesterday to create some EQ morphing. Probably my main usage i had in mind.
- This was not working out well with the Kirchhoff EQ. It slows down the GUI, And the oscilloscope.
- i did work out well with the FF pro-Q4


i´d like to see a lite version for something like $19.
- take the free LE, add one or two makro controls, add the plugin browser. I´d be fine with that.
Well, i would also want to see a visual feedback vs. if a "save to snap" command was properly taken or not. I have there quite some fails. which makes the overall handling for me cumbersome.
( no clue who this works on other systems)

The big Snappy, should probably get a mode where we can select or deselect parameters per the single plugins re. beeing inclouded or explouded vs. all the under the hood communication dialog that has to take place.
Imho, It "then" had to be saveable per plugin. and had to remember that state.
thinking this further, probably with several slots, to save different such states per plugin.


This plugin looks useful in regards to many things.
For others it looks too fresh, underdeveloped out in regards to that whole underlying idea.


As is now it´s not a buy, use,....whatever you want to do plugin.
I think it would be a good idea to make a clear commication in regards to that.
The available videos leave that point out for my taste. ( not saing it´s the fault of the plugin / it´s part of the nature of the situation)


i had so far great fun dealing with Zebralette3. That alone could be worth the asking price. But: i lost there visual feedback now too. No clue why it was working first. Then nolonger.

Any of my problems started after installing the full version (demo license)
Especially when i started to load more than one snappy instance into a patch in GP.

( still: can´t add my screenshot vs. the screwed GUI i got)


sorry, if many of these things do sound negative. I´m in fact very positiv to the plugin itself.
Just, there are some things.......part of the nature of the situation....that might require some further thinking ?

[aMUSEd]

What’s the difference between the lite and full versions?

[biomechanoid]

What’s the difference between the lite and full versions?

Detailed in the FAQs: https://electricsmudge.com/faq

[aMUSEd]

What’s the difference between the lite and full versions?

Detailed in the FAQs: https://electricsmudge.com/faq

Thanks Col

Looks like I need the full version to do what I want