Vienna Symphonic Library Forum
Forum Statistics

180,783 users have contributed to 42,141 threads and 254,364 posts.

In the past 24 hours, we have 1 new thread(s), 11 new post(s) and 66 new user(s).

  • Vi 1.1 and Logic : Show window : 30s : Is this normal?

    Thnx to VSL for the update. YEY Really..


    Just one question I always wanted to ask.


    After having switches screenset
    or
    Upon opening a track's VI AU - server interface (Grey & white float window)
    ->
    When I click 'Show Window' in the VI AU - server interface, I systematicly have to wait for +- 30 seconds before I can edit/access the Vienna Instrument parameters... (I'm on a G5 Quad here)

    The blue VI plug-in window's position is always 'reset' to default position...

    Generally this means using screensets in Logic, while editing a few Vi's, will make you wait for serious amounts of time...
    I would actually say that the VI implementation makes the use of screensets a little 'useless' if you want to work in a fluid manner...

    I may have overlooked something here.. but is it 'reasonable'? I'm puzzles.
    Consider the following basic scenario..

    1 song with 8 VI's loaded
    Screenset A : All Vi's open and visually layed out for editing
    Screen set B : Any other screenset in your setup.

    You want to do basic screenset switching between 2 Screenset
    You go from A to B : for whatever reason it matters not.
    Then you want to return to A to go back to VI editing.

    What happens then : you have to reclick 'show window' 8 times and wait for 4 minutes before the VI's appear.. And all those windows are stacked on one another at default position... So you need to lay them out again.

    I hope I missed something and that one of you is gonna show me my mistake...


    Basically wouldn't it be more healthy if the VSL server was a 'viewable' and selectable application like others in the finder. With a 'rack of VI's' stacked in some kind of way?
    Always accessible with one click. No waiting.
    having the VSL server as active front window in OSX wouldn't stop Logic from running midi anyways... Clicking in Logic on the 'show window' would simply set VSL server to foreground in OSX... and corresponding VI would be higligted in some way..

    True, there is the issue of playback orders to Logic when VSL server would be foreground ap... Midi can do that, any controller will do the job...

    Any thoughts..

    BTW : I'm trying to figure if I'm wrong here. I wanna be constructive. This is no ranting..

  • Yes everytime you swap a screenset in Logic the VI's windows are lost in the original screenset. This action is a nuisance (no other plug-ins I have do this). and when you do reopen them they do all stack in a default position rather than their last position.

    However re-opening the plug-in should only take about 5 seconds per plug (30-40 seconds to re-open 8 instances)

    If you want to have 8 VI's open frequent screenset changes are going to stifle your productivity (and creativity) So I'm hoping it will be on the "fix list" for the next update!

    Julian

  • Thanx for confirming you're having the same issue.

    I am very surprised that plug reopens in 5 seconds in your setup...
    That is good news...

    But why the hell is it taking 30 seconds here....

    I have A G5 quad...

    Do you think it's processor related or more 'licence' related... (usb dongle)?
    Could someone from VSL give me a hint on what issues I should look into..

    Does the program checl licence dongle upon simply reopening plug in...?
    I have fairly complexe screenset setups. Could that be an issue?

    What are other people's waiting time just for the plug window to reopen... Thanx

  • Hi Charl,

    I'm running the VIs on a G5 Quad also but can't really point to your problem. I can confirm that only the 'Show Window' dialogues are displayed when returning to a screenset containing VIs but mine are opening in around half a second!

    I've tried this in my current project with fairly substantial patches loaded but I'm only using the four instruments of the Chamber Strings in this one, so I can't say if the duration escalates with more VIs open.

    Sorry, but at least there is perhaps some confirmation of a problem within your setup. I'm also running 6.5Gb RAM if that's any indication. [*-)]

  • Thanx a million...
    Very kind of you.

    At least I know it shouldn't be like this...
    I'll try to test with a very basic song template.
    And maybe with minimum usb stuff connected..

  • Tested with most basic Logic setup -> same results
    Tested with minimal VI collections loaded via instr Dir Manager -> same results.
    Tried moving dongle to mac usb instead of having it on hub.. -> same results.

    So, I've looked in greater detail at what happens exactly.

    It seems that Plug-in opens in a flash (that's good)
    But the window is blocked (timer ticking) and there is no content in the browser.
    After those 30 seconds, content appears in browser window. Content is 'Document' folder from the user folder.
    It's as though it takes 30 seconds for the VI to update the browser content...

    Is this normal?

    I'd really like someone from VSL to comment on what's supposed to be happening at that point in time.

    Recap : What does the VI application do when the user has just clicked on "show window" button, and plug-in has appeared with no content in browser window on right.. And the OSX ball is spinning for +- 30 s untill content apears on the right.

    Isn't there a way to avoid this? Or to set another browsing destination than 'documents'folder in the user folder..


    Please chime in VSL. Thanx

  • not sure now if i'm interpreting your description correctly and maya could guess better, but it seems you have set the custom folder (in directory manager) to your home-directory and so the VI has to scan the probably hundreds of files (unrelasted to VI) there ...
    if i'm right i'd recommend to create a seperate folder somewhere (actually within your userfolder) keeping it free of other stuff.
    of course you had to re-attach the paths in the directory manager after doing so
    christian

    and remember: only a CRAY can run an endless loop in just three seconds.
  • CM and the others,

    Thanx Thanx Thanx Thanx Thanx Thanx Thanx Thanx Thanx and thanx again


    I totally missed/skiped the 'custom folder' when I checked the directory manager..

    AND I also missed this in the manual...

    Go figure what made me miss such an obvious thing.. At two levels of my investigation.

    All is now how it always should've been.. Quick

    Goodness...

    This makes me feel good : )