Vienna Symphonic Library Forum
Forum Statistics

200,448 users have contributed to 43,198 threads and 259,084 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. VI Pro Beginning to feel like an early Beta release

  • VI Pro Beginning to feel like an early Beta release

    D
    D

    Well, I'm certainly not criticizing VSL's general work, or samples at all.

    I'm having too many issues with it, so I've stopped working with it for the time being.  I paid $148.00 for it, and I expected VI Pro to just work for my money.

    Here are some of the issues I've had (everything is the lates version):

    1.  Yesterday, I loaded VI Pro Instruments (10) into Logic Pro 9.1.1.  The last one was my Bassoon (DL version).  It made a horrible noise, and wouldn't play afterward.  I looked, and the Bassoon looked loaded correctly, but no sound would come.  I deleted the samples, and reloaded them.  No luck.  Finally, I deleted that instrument from VE Pro, then added the 10th instrument again, loading the Bassoon (DL) again.  This time, it worked fine.

    2.  Sometimes, when I save a setup of just a few (6-10) VI Pro instruments, the setup will load, but the Samples aren't loaded into each VI Pro instrument.  It's not necessarily repeatable, but this does happen now and then.

    3.  Also, there are times when some of the articulations will not play.

    There's more, but I have gone back to using VE Pro, 64 bit, without VI Pro, just the original VIs.

    I would love to use VI Pro for my Vienna Instruments, but right now I really can't trust it.  Things are very stable with VE Pro.
  • R
    R

    I unfortunately agree.  I posted a message as well.  I will wait until the bugs are ironed out.  VI Pro is a great idea but I think it is not quite ready for prime time.
  • marnixM
    VSL Team
    marnixM

    Hi Dayadon,

     

    I am sorry to hear you had such a bumpy start with VI Pro and I really wonder what could actually cause this, since none of the issues you describe have been reported during our Betatesting phase.

     

    It is really hard to find problems, when they are not reliably reproduceable - can anybody here on the forum confirm all or some of the behaviour of VI Pro you are referring to?

     

    Please give it a try and repair permissions to your system drive with Disk Utility - this seems to have resolved quite some issues other VSL users had in the past!

     

    Does that perhaps already make a difference?

     

    Best, Marnix
  • D
    D

    Hi, Marnix.

    I can see how it's hard to fix consistently unreproduceable issues.  That's really why I'm not going to consistently use VI Pro for now.  It is hard to reproduce the things that occur for me while using it.  I will try to reproduce some of the issues for you, but things are working so well with VE Pro without VI Pro (for me) that I'll stick with that for now.
  • T
    T

    I had similar issues using VI Pro (with Logic 9). I had a logic song with several instances of VI (normal version). After adding some tracks with VI Pro there was a terrible noise during playback. I had to delete the tracks and recreate them with the "normal" VI  to get it play normally again.

    Perhaps the problem is caused by using VI and VI pro inside the same song?

    Anton
  • J
    J
    last edited
    last edited

    @marnix said:

    It is really hard to find problems, when they are not reliably reproduceable - can anybody here on the forum confirm all or some of the behaviour of VI Pro you are referring to?

    I can confirm occasional issues with loading patches...   and only a reload will solve it.

    Issues such as:  From nowhere, 1 note will play the wrong sample or a noise - but only at certain velocities (typically use velxfade to a controller).

    A reload always solves this.

    Unfortunately there is no rhyme or reason. I can work for 2 10-hour days loading dozens of patches, but then one day I will experience this issue 2 or 3 times. Then 2 or 3 days without any issues.

    This only happens on my macbook Pro which is one of my VE Pro servers. My Winxp server has not surprised me with these "phantom" samples.

    A reload always fixes this.

    Yes, I am religious about drive maintenance. This is not a prefs or permissions issue. This NEVER EVER happened prior to VI Pro.

    Of course, there is nothing to report, since I can't reproduce it. But since the topic is here (and you asked) I thought I'd add a "me too" to this issue -- 

    FInal thought -- some users build large templates and leave them loaded all day. I typically load what I need for a song, and I frequently go on fishing trips (where I'm not sure the exact combination of patches to build my matrix), and this is when I get the surprise. And then, the only way to fix things is to restart, since the mac likes to cache samples now and then... If I had an actual bug report, I would have done it by now. SO now it's simply anecdotal. A way to try to recreate this would be to load many patches on a mac 32-bit server and then go fishing for sounds... build matrices, stack cells. Enable/disable cell xfade. Move your controllers. Use velxfade and play various velocities using the controller. Eventually over a day or 3, something will surprise you. then it will be fine for a day or 3 following a restart.

    Not much help, I know!
  • PaulP
    VSL Team
    PaulP

    Hi,

    we´re already looking into this. Should be fixed with the next build [:)]

    Best,

    Paul

    Paul Kopf Head of Product Marketing, Social Media and Support
  • RaymondeR
    RaymondeR
    last edited
    last edited

    @marnix said:

    It is really hard to find problems, when they are not reliably reproduceable - can anybody here on the forum confirm all or some of the behaviour of VI Pro you are referring to?

    Please give it a try and repair permissions to your system drive with Disk Utility - this seems to have resolved quite some issues other VSL users had in the past!

    I am surprised no one has noticed the issue with the patches not loading and or playing inconsistently because that has happened with me also and I posted on it

    Also, in VE Pro, the memory usage box that VI is reporting shows the memory total for the last loaded matrix, and reports the same Number-no matter whether the preset I select  and look into is one cell or 30!

    Other anomolies have crept up but I failed to note them-please, everyone, let's keep up on reporting the errors-myself included in that plea[:^)]

    Ray Phenicie

    Southfield, MI

    USA

    System

    MIDI USB connection Mark Of the Unicorn Microlite 5-in/5-out MIDI interface Driver Date 7/12/2010, Driver Version 4.0.4.2114 64 bit version

    Cubase 4.5.2 Built September 2008

    StudioLogic Fatar SL 88 key midi controller

    Processor      Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz, 2667 Mhz, 4 Core(s), 8 Logical Processor(s)      BIOS Version/Date      American Megatrends Inc. 0209, 11/11/2009  

    Installed Physical Memory (RAM)      12.0 GB     Total Physical Memory      12.0 GB     Available Physical Memory      9.72 GB   
     Total Virtual Memory      23.9 GB     Available Virtual Memory            21.7 GB Audio Card  Name   M-Audio ProFire 2626

  • M
    M

     Finding myself agreeing here and will hope for a swift resolution of such bugs / instability issues. I have the following:

    - Projects with multiple (10+) VIP instead of VI instances seem to load with difficulty. Sometimes new VIP instances cannot be added (adding instance in Cubase 4.5, window popping up, but without graphical content). At project startup, i am amazed at how quickly everything might load, and does indeed play (whilst loading), yet usually i can't see the loading bar (nor any instance's graphics).

    And while you're at it:

    - It's pretty annoying in the basic view that one can't see what patches there are in the matrix... the patch info shows stuff from the browser, not the actual matrix (although this is shown in the advanced view). Or did i miss something?

    - Hope to see VE (non-pro) integration soon!

    Cheers,

    M.

    (PS: otherwise brilliant piece of software!)

    (Win7 32 bit, AMD64, 3 GB, Cubase Studio 4.5)
  • RaymondeR
    RaymondeR
    last edited
    last edited

    @mspape said:

    And while you're at it:

    - It's pretty annoying in the basic view that one can't see what patches there are in the matrix... the patch info shows stuff from the browser, not the actual matrix (although this is shown in the advanced view). Or did i miss something?

    - Hope to see VE (non-pro) integration soon!

    Cheers,

    M.

    (PS: otherwise brilliant piece of software!)

    (Win7 32 bit, AMD64, 3 GB, Cubase Studio 4.5)

    Agreed with all you say, however, just to be clear, VI has never had a listing of what patches are in the matrix and thanks for pointing that out because I would think a screen listing showing what patches were loaded in the matrix would be a good thing. Afterall, a word processor shows you what styles you have available and lets you select one or the other from a drop down box.

    I know this is not a word processor, and I love my VSL experience, but I'd like the work flows to be a bit less cumbersome, and if the computer knows what patches are loaded, why can't I? As things stand now, I have to write down what patches are in each cell.

    Not so good. [8-)]

    Ray Phenicie

    Southfield, MI

    USA

    System

    MIDI USB connection Mark Of the Unicorn Microlite 5-in/5-out MIDI interface Driver Date 7/12/2010, Driver Version 4.0.4.2114 64 bit version

    Cubase 4.5.2 Built September 2008

    StudioLogic Fatar SL 88 key midi controller

    Processor      Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz, 2667 Mhz, 4 Core(s), 8 Logical Processor(s)      BIOS Version/Date      American Megatrends Inc. 0209, 11/11/2009  

    Installed Physical Memory (RAM)      12.0 GB     Total Physical Memory      12.0 GB     Available Physical Memory      9.72 GB   
     Total Virtual Memory      23.9 GB     Available Virtual Memory            21.7 GB Audio Card  Name   M-Audio ProFire 2626