Full Instrument Expansions - how, what where....

[Lindon]

Well Im sure I will have a truck load more questions but lets start with this....

I have a Player project that will load the Full Expansion, now how do I get that full Expansion project to show up in a specific location in my player (so where the red X is ):

[David Healey]

@Lindon What do you mean by "show up"?

[Lindon]

@David-Healey said in Full Instrument Expansions - how, what where....:

@Lindon What do you mean by "show up"?

well its a full instrument - so it has its own User Interface, I mean the user interface to appear in this spot...

[David Healey]

@Lindon Ah ok I understand. When you load a full instrument expansion it completely replaces the entire plugin UI, it doesn't load within it. It's like you're launching a completely different plugin.

You might find this video informative: https://www.youtube.com/watch?v=x4b8WlStG40

[Lindon]

@David-Healey okay, watched that...

Nooooooooooooooooooooooooooo!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Surely to God its more sophisticated than this???

Now I have to duplicate all my Library(expansion) management display and functionality in every Full Instrument I ship......God help me.

[David Healey]

@Lindon Yes if it's a custom preset/expansion manager and you want it in all of them then you need to duplicate it. Or you can do like Rhapsody and have a button that unloads the current expansion and returns you to a dashboard type page where you select your expansion.

I think maybe the regular expansion system might be more suitable in your case.

[Lindon]

@David-Healey said in Full Instrument Expansions - how, what where....:

I think maybe the regular expansion system might be more suitable in your case.

In what way? I need each expansion to have its own UI, its own widget set, its own samples and its own functionality. I cant see how I get there with anything other than a Full Expansion approach

[David Healey]

@Lindon Yeah if each UI is totally unique then yes the full expansion is probably the better option.

What I do for shared stuff that is reused across all my expansions is I put it into a set of scripts that are loaded at the beginning.

[Lindon]

@David-Healey yes that will have to be my approach....luckily this compartmentalising of functionality has been my std. approach for some time.