Vienna Symphonic Library Forum
Forum Statistics

199,039 users have contributed to 43,151 threads and 258,882 posts.

In the past 24 hours, we have 6 new thread(s), 14 new post(s) and 63 new user(s).

  • Special Edition articulations?

    The website doesn't list the woodwind articulations that come with the Special Edition (standard): sustained, perf-leg, stacc, sfz, like the strings? Also: are the perf-leg in the strings and the woods generally the mV (vibrato) versions, perhaps except the brass?

    Thanks

    Dom


  • Here is the complete list for both standard and extended.  Just look at the green check mark to see if what you're looking at is standard or extended library.

    http://vsl.co.at/en/211/261/314/1607/1625/604.htm

    Maestro2be


  • Thanks for this. This lists the Special Edition bundle's articulations. Which woodwind articulations are included with the Special Edition (not the bundle)?


  • I think this is what you were looking for.

    http://vsl.co.at/en/211/261/314/1605/1613/409.htm

    Maestro2be


  • Yeah I saw this list, but it only lists the articulations for the extended edition, but not the standard woodwind articulations - with the strings it's clear. 


  • Hi Dom,

    all instruments in the Standard Library contain the same articulations as the instruments in the Extended Library [:)]

    Best,

    Paul


    Paul Kopf Head of Product Marketing, Social Media and Support
  • Excellent, thanks.

    It's strange, but I have the Pro Ed, Symphonic cube, Appas, etc etc, but I think the SE standard is just about all I need![H] But I'll see, I am setting up a "B" rig for programming with SE. I'll miss the trills probably.


  • What format are your old libraries in?  You could always launch them within VE Pro, unless they are EXS24.  That way you could keep all the ones you need from the old libraries.

    Maestro2be


  • Thanks for the suggestion! I have Giga, EXS as well as the new V.I. versions, but as I am looking to more or less duplicate the set up (which is all VI), working with V.I is best. The more refined response as and control, particularly the keyswitching and velocity crossfade, is difficult to achieve with the old Pro Edition libraries.

    The difficulty with this project is that when opening a Logic project on another rig is that VE Pro will keep searching forever for an unavailable server, rather than giving the option to connect to a differently named server, or simply leaving it disconnected. But this time-out issue will get addressed in the next VE Pro version apparently.


  • What I have found is that whenever I use VE Pro all on the same machine that will happen to me (extremely long load time if I don't have the server runing).  However, if I setup a slave machine and connect to it, then save the project it loads instantly.  It's almost as if it KNOWS that the connection point was EXTERNAL and not "in the box".  I can open all my projects within seconds because I save all my projects using VE Pro on slaves.  When I go from home to the office, I can load my project on macbook pro, then connect to my slave pc.  Then go back home, fire up my slave and do the same.

    If I however, open the server locally and connect to it and then save it, I get the long load times the next time I launch the project and don't have the local server running.

    Maestro2be


  • Interesting. Both of my rigs will have external slaves.

    So if I understand correctly you have one slave at the office and one slave at home (who also does your hoovering).  But what happens when you load your project from the office at home? Will the VE plugin within Logic not try to connect to a differently named computer. Or do you have identical IDs and IP addresses for both of your slaves?


  • So it looks like this:

    1.  I open project at home.  It's blazing fast.  I open the VE Pro channel strip plug and connect to the slave.  Done.

    2.  At work.  I open the project and it's just as fast (does not try to connect to anything).  I open the channel strip and click connect and it shows my slave at the office.

    However, if I open the project and then connect to my LOCAL machine and do it all on one box, the NEXT time I open the file it will be slower than hell.  So say I go on the road and work all in one box on my macbook pro and save the changes etc.  When I get home and launch the application, it will take forever to load (because it's looking locally for the service I used last time and no isn't running).  After I go and connect to a slave and hit save it will open fast for me everytime after that.  For me it's only when my projects are saved using the VE Pro server locally all on the same box.

    Make sense?

    Maestro2be


  • Makes sense. So after your step 1 do you save and close your project with the server still connected, or do you disconnect first? 

    What I found is that if a project is saved with the server still connected and then opened again with the server unavailable (ie switched off or not connected) the project hangs for 15 minutes. 


  • I never disconnect, decouple or preserve.  When I am done with my project and say going to bed or whatever I just close Logic entirely and it closes all my VE Pro sessions for me.

    When I want to change songs I do a file, close project.  Then file open and grab the project I want to work on.  VE Pro closes my other sessions and launches my new ones automatically.  I don't use 30GB templates and projects so it takes about 1-3 minutes for it to load all the VE Pro instances for my project but I don't care, it's not bad.  And the actual project itself opens instantly, I just wait for VE Pro to get done loading my vframes.

    When I am done I close Logic entirely and VE Pro automatically closes all of the open sessions.  I wake up the next day and have absolutely no issues opening the project at instant speed, no matter where (home or office) as long as the last VE Pro server I connected to was a slave and not my local machine.

    Maestro2be


  • Ok, I think the difference is that I connect to preserved instances, decoupled, as the template is 20GB, spread over 11 instances. This may explain the different behaviour: If VE Pro wants to connect to a preserved instance that doesn't exist at the moment, it hangs.


  • Yes because if you saved your project, with preserved instances, that information is being saved in the actual project.  It's also important to keep the preserved instance names the exact same (all of this is on pages 14-15 in the manual).

    Maestro2be


  • Cgernaey, sorry that my description was unclear - but this was the issue I was talking about: 

    http://community.vsl.co.at/forums/t/25249.aspx

    and as mentioned, it's being looked into.


  • No problem.  I read that link you put there and it will be so nice to see them finally fix this once and for all.  It has been a long time annoyance.

    Maestro2be