Vienna Symphonic Library Forum
Forum Statistics

182,328 users have contributed to 42,218 threads and 254,755 posts.

In the past 24 hours, we have 2 new thread(s), 9 new post(s) and 52 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Vi-frames vs meta

  • Vi-frames vs meta

    T
    T

    When MetaF's are saved vi-frames are saved WITH them correct?
  • K
    K

    Yes, the data that would be saved with a .viframe is saved for every instance contained in the .mframe.
  • T
    T

    Thats what we thought. Most likely user error on our parts here. We must have made changes to a different M-frame and couldnt figure out why it didnt stick.  

    thnaks again for the quick reply. 
  • C
    C

      - if you have saved as viframes themselves, saving the metaframes does not affect the .viframe itself, but the viframe as exists in the metaframe container; to call up the viframe where the changes saved were only done at the metaframe level, you must call up the metaframe, unless you have saved the viframe separately.
  • T
    T

    thnx- so if i dont create a vi frame but instead open a blank Meta and randomly create vi frames without saving them, if I needed to access JUST the vi frames later what would they be called?  Or do they ONLY exist as part of a MetaF?
  • C
    C

    those only exist as part of the metaframe. you won't be able to access those unless you save project as. ie., .viframe.

    then in a metaframe when you want a particular viframe, eg., to replace one of the viframes you have up, you open a project.

    so, I save most of my vi frames with descriptive names like sub-templates, which could populate metaframes in future.

    I have a more or less consistent method, the instances are simply named 1, 2 etc corresponding with vsti slots; and once up in the metaframe also with the same project name as the DAW project, where [slot] 1 is pitched and aux. pcs, 2 is drums, 3 is ww/brass etc. And then the vi frames tend to have detailed names of their content.  EG: instance name = "3"; viframe name = Spaced "3" [picc,fl,altofl,tpt,trbns,Pbass]; metaframe name = Spaced "1,2,3".
  • T
    T

    Consistency is key and a method needs to be developed and adhered to or one will surely go insane working on several projects at once.

    You have a good system there that works for you.  I wonder if something cant be streamlined a bit within the meta itself. For e.g. when you create a metaF and inside that you have a vi.F and you name it but dont save it- it would 'seem' to be a good idea to have the name you give it become the default SAVE name if you should save it at some time later.

    Regardless: So that I understand what your saying: If I have a metaF open and I load a vi.F project into the MetaF then LATER open that MetaF with that ViF and I change say the Reverb on a WW section. Then when I exit the session i DON'T save the ViF but I DO save the MetaF.  I am guessing in this example that the ViF itself does not change (in other words the ViF as originally created has the same reverb setting I created back some time ago)  

    However in the instance where I CHANGED the reverb - that change still exists but ONLY within the ViF within the MetaF?
  • C
    C

    yes, you have it right.

    as far as naming it not saving it: you are naming the instance, not the project there. naming the project/viframe involves saving as. which is why I indicated ["3"], vis a vis ["3" [instrumentation description]]. In the metaframe "3" is always "3" but [instrumentation description] vanishes when the metaframe is exited. I would like the name of the project/viframe to appear in the metaframe, which is not true until we save again. so no matter what the project is, "3" is ww/brass-based here, at least.

    another thing I do is save channels and channel sets
  • T
    T
    last edited
    last edited

    @civilization 3 said:

     I would like the name of the project/viframe to appear in the metaframe, which is not true until we save again. so no matter what the project is, "3" is ww/brass-based here, at least.

    Yes-that would help in organizing/keeping track of.