It would need to encompass a completely detached model and heirachy of objects. How would a layer collection behave in the engines or sound fonts weren’t available? What about different zynth builds 3a versus 4? I don’t see these as insurmountable problems indeed I m keen with a rig of 5 or so zynths to see a decoupling of this sort.
Reducing the number of clicks required to perform operations of this sort will increase the usage. We have done good work with capture and ogg files in this regard but if a tool like audacity can require less operations to cross fertilise then that has to be a good thing and plays well to the Swiss army knife approach.
I see it like @wyleu.
Maybe a link Dropbox over the Zynthian Logo in the webconf.
But what if we have multiple engines for the same suffix? I see more issues than gain.
Ceterum censeo we should not concentrate on too many things simultaneously. Now the stepseq has prio with a lot of open issues regarding integration.