I would love to be able to open a blank metaframe and simply drag v-frames from the VSL Custon Data folder into it.
I would also love to be able to change the order of the v-frame loading within a metaframe in the server interface.
196,669 users have contributed to 43,022 threads and 258,418 posts.
In the past 24 hours, we have 1 new thread(s), 2 new post(s) and 99 new user(s).
I would love to be able to open a blank metaframe and simply drag v-frames from the VSL Custon Data folder into it.
I would also love to be able to change the order of the v-frame loading within a metaframe in the server interface.
neither is a big deal so that I'd lobby for them. the first one isn't more convenient to me the way I think of things.
the second one I would use because I name the instances according to their slot number in VST instruments and have metaframes that read '[project name] "3,1,2"]' so my sort of anal tendency would appreciate that.
what I want is the viframe to recall the positioning and sizing of the automation map.
So none of you like to create variants of your existing m-frame templates, which would certainly be easier by simply dragging v-frames into them? I guess people work differently than i do.
I have all sorts of variants of a given metaframe, I just don't have 'finder' open. <open 'finder', drag and drop [close finder]> vs <command/O, arrow down, enter>? kind of a wash to me.
@Ashermusic said:
So none of you like to create variants of your existing m-frame templates, which would certainly be easier by simply dragging v-frames into them? I guess people work differently than i do.
My template is my template. There is no reason to alter it mid-project. If I want any extras, I load them as and when I need them in another instance, coupled but not preserved. That way the project recalls it when it is opened, but closes it when it is closed.
DG
I never work coupled.Causes more potential issues than it solves IMHO. Horses for courses.
Oh well, I planted the thought but if no one else cares, then so be it.