Vienna Symphonic Library Forum
Forum Statistics

194,142 users have contributed to 42,912 threads and 257,924 posts.

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

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. I just have to ask...

  • I just have to ask...

    P
    P
    When is VI going to support Open Multi Document Interface with Shared Window Focus? Currently usage is very combersome having to switch focus back and forth between Logic and VI. Any update or timeframe whould be appreciated.

    Best regards,

    B
  • P
    P
    Allow me to rephrase my question.

    Is the VI GUI window going to become like other plugins in that when you cursor over it, you have direct access to it without having to click on it first, as if it was a separate application. In other plugs, cursoring between the plug and the host are seemless, leaving qwerty keyboard control where it belongs, in the sequencer. Working with VI now, anytime I want to access a different articulation I have to click on the VI window to choose it, than I lose control of my sequencer so I can't start playback or trigger a note in the matrix, so I have to click the Arrange window to access Logic, but then I lose the VI window behind the Arrange window. So now that I have access to my matrix and playback and want to select a different articulation I have to click on the VI window again, once again losing control of playback. This goes on and on....kind of like this post. Anyway it is very cumbersome and unintuitve. Even the most inexpensive Plugins and Virtual Instruments support "Shared Window Focus".
    There is no other product on the market today that can touch the VI in it's ability to faithfully realise orchestral instrument performance, however I believe this serious workflow problem needs to be addressed. Any comments would be appreciated.

    Best Regards,

    Barry
  • P
    P
    Any Comments?
  • D
    D
    The program actually runs outside the host sequencer so hence you have that behavior. VSL already fixed a couple of similar issues with the window. A benefit however, is ram usage as the host sequencer is not burdened by sharing ram resources with VI (which is great really.) I don't know if it can be made to behave like it's running withng the program or not.
  • P
    P
    Thank you Dave for your reply and insight. I am curious however, what the official(VSL) stance is on this issue. Is this possible to fix?
  • D
    D
    I am curious as well. I will say that the initial problems were rather annoying but are completely gone now. I really haven't been bothered by the current behavior because I'm using a seperate screen for displaying the GUI which seems to be the way to go.

    VSL will chime in here at some point I expect.
  • P
    P
    [VSL will chime in here at some point I expect.]

    Appearently Not.....
  • P
    P
    HI guys! Anyone from VSL?
  • D
    D
    Barry

    You can rely on the fact that they will solve various bugs and problems as fast as possible. They can't always predict when so the answer to most issues is "we're working on it." These guys are real sharp and professional. The next update will probably include more GUI adjustments.
  • P
    P
    A week and still no reply! I would think that my support for VSL by purchasing virtually every product they make would warrant at least a couple of words from someone in the company....
  • JBacalJ
    JBacalJ
    I know that Herb is on a well-deserved vaction. Perhaps he will comment when he returns.

    Best,
    Jay
  • G
    G
    (..chiming in ..)

    Well, we are aware of this behaviour and we investigate into it.
    Basically there is a peculiar property in OSX that prevents making
    the PlugIn behave like on Windows.
    Technically it is a separate app with all properties of an app.

    We had the choice of delaying (completely rewriting) the OSX
    version for a year or so or to make this solution which brings
    along some minor disadvantges to the user.
    We thought you might be rather interested in working with VI
    as is than wait for a "perfect" plug.

    Version 1.1 will adress further issues but won't solve this particular
    thing on OSX.

    We are currently adding resources to the development team and
    we will adress this issue fully in version 2.0 ( along with other major improvements of course)

    Thanks

    Christian Teuscher
    Deveopment
  • J
    J
    Christian,

    Thanks for the reply. I had commented on another thread about this very thing, so I've watched this thread closely to see if any resolve would come.

    Certainly, the way the Vienna Instrument behaves in OSX is far from debilitating, but it it is destructive to a smooth work flow.

    I'm encouraged to read that the Vienna team is aware of it however, and am pleased to read that it will be addressed at some point.

    I, for one, am very pleased that you didn't wait to release the product based on this alone! Now, if I could only type a response to a forum, like this one, without the Vienna Instrument interupting my ability to type, as it loads... [:D]
  • C
    C
    last edited
    last edited

    @golem said:


    ....We are currently adding resources to the development team and
    we will adress this issue fully in version 2.0 ( along with other major improvements of course)...


    oooooooooooohhhhhhhhhh [H]

    Maybe even new features? [:)]
  • D
    D
    last edited
    last edited

    @golem said:

    Technically it is a separate app with all properties of an app.


    Christian,

    I think this fact may be causing other major issues. For example when I bounce to disk in Digital Performer (OSX) all the instances (5 Strings I+II + 1 Appassionata) disappear forever - even if I don't save. Only the 'Show Window' remains.

    Thought I would catch you while you're in the neighborhood. [:)]
  • P
    P
    Christian,

    Thank you for your reply. It's good to hear that this will be addressed, even if it is a bit of a wait. And, yes I too am glad that you released the VI "as is", instead of waiting for the OSX total rewright. From a user stand point however it's hard to know what the intention of the software developer is, i.e., it's good enough as it is, stop wining, you don't like it, too bad-you bought it etc., without some kind of communication. Which is why to me, your response is very much appreciated!

    Thanks again and best regards,

    Barry [:)]