Vienna Symphonic Library Forum
Forum Statistics

199,020 users have contributed to 43,150 threads and 258,877 posts.

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

  • Anyone Own Both Appassionata and Hollywood Strings?

    I have VSL SE and SE+ (the older, larger special editions purchased about 18 months ago). I bought Hollywoods Strings but am very disappointed. VSL's matrix system makes it much easier to set up and load articulations, and even though I have a very powerful PC, Hollywood stresses the CPU. Without going into detail, I will say that it is harder to use from a player/arranger standpoint. It also does not work well from a spinning drive and really requires a large SSD. When I am arranging HS, notes drop out constantly, like a synth running out of voices. I have to freeze/record/bounce the tracks to hear what they sound like The sound is good when you get past all the issues, but almost not worth it. (HS also offers its own reverb which I do not use, and various mic positions which I use rarely.) I am wondering if anyone here has both Hollywood and Appassionata and can compare experiences before I buy Appassionata. (The SE/SE+ has a sample of Appassionata—just 2 or 3 articulations). I am defintiely impressed with VSL overall and will be adding more instruments, although the old SE and SE+ offer most of what I need.

  • I'm halfway between the worlds of Play, VSL, and LASS, and in my personal opinion Play libraries are always the most intense to run on a computer. I don't happen to own HS--I tried the ten day demo and only used it on day 1 because I need software that can run on my laptop, and that just couldn't. This should come as no surprise, though--Appassionata takes up 12GB (18 uncompressed)and Hollywood Strings takes up over 300. The sounds are fantastic, but pre-mixed for a more specific niche than Appassionata. Personally HS's sound is more pleasing to my ear than Appassionata, but that's all down to personal opinion. I think VSL's strings are well-suited for orchestral scores, but their focus is on versatility--you can do anything with it. HS probably wouldn't work quite as well in an orchestral setting as it would in a film score setting because of its specific sound and style. I'd suggest not using Play's built-in reverb, but rather using either the one Vienna offers or Spaces or Altiverb or whatever your preference. Play's reverb drastically increases CPU use in my experience. You get some of those same reverb locations in Spaces, which is somehow much easier on resources, plus you can channel many tracks through one instance, and they don't have to be Play instruments.

  • Casiquire, Thank you for taking time to respond and share all the information.

  • Out of curiousity, have you tried some of the older pre-AP strings techniques?  If not, try layering the SE orchestra strings with the SE chamber strings (and even the SE solo strings if you want).  Try detuning the chamber strings layer slightly from the orchestra strings (1 or 2 cents). 

    That likely will give you a thicker more lush sound and also provide an easy way to write divisi.  For me, the design of Play is far too awkward to easily work with, and while LASS was intriguing, the lack of articulations compared to VSL was a major issue - note that I also am more interested in traditional orchestral/chamber music, as compared to epic Hollywood.

    <edit> Note that I do not own HS as Play didn't play nice with me (EWQLSO).  Likewise, I do not own LASS, for the above mentioned reason.


  • I'm more into orchestral music as well and that's why I'm not into Hollywood Strings. LASS's articulations are so ready to be customized that I never really feel like I need any more articulations, so I think the big difference between VSL and LASS is just down to whichever sound you prefer. They're both extremely good quality and very versatile.

    bhartman--one of the other benefits of the combining technique Noldar mentioned is that you get instant natural divisi capabilities. Plus the sound of slightly different ensembles reacting to the modwheel slightly differently really improves the realism of the whole piece. You already have Solo Strings articulations as well as Orchestral, so you could probably improve your results even more by layering in the Solo Strings to get a little bit of added expression.

  • last edited
    last edited

     

    @bhartmann said:

    When I am arranging HS, notes drop out constantly, like a synth running out of voices.

    I like the East West samples in general, and admire that company a lot, but have to say that the VSL Appassionata are the best overall string sound available, and have become my normal strings in all arrangements. 

    The reason is, that although you can throw out a lot of gigabytes and "features" and so on, the basic string sound is what really matters.  In my experience, there is nothing that can approach the Appassionata violins, violas and cellos in the basic, instant, beautiful rich string tonality.  And it is fairly low in CPU demand.  That is because the playing and recording was tweaked to be a deep and rich string sound that composers usually want.  You can record a million samples of something that doesn't have that, then brag about how big it is, but it still will just cause a lot of problems. 

    Also, what you bring up with the interface is what I've noticed many times - the VSL software using Vienna Ensemble is so logical and useable, that I no longer want to use Kontakt or other proprietary sample players and in fact am becoming very choosy about them.  Because none of them are as good as Vienna Ensemble.  It is so easy and musically logical to load, select and play, that I no longer want to deal with the "All samples in your lap and you figure out how to use them" approach of other players.

    I should emphasize that probably no one will ever regret getting the Appassionata strings.  I am doing a new recording that uses a lot of strings, and though I have done a huge amount of Appassionata recordings,  I was still freshly amazed by the instantantaneous beauty of the sound using them.  It is astounding how authentic the sound is using the simple combo of:  legato 4-velocity, sustain, detache and staccato.   Four articulations!  And they cover almost everything you could ever compose. 

    One other thing - they are tweaked in general so that the most needed, useable sounds are all right there, instead of being  buried within a lot of unnecessary patches.    But if you want something less usual, you can always supplement with more App articulations, such as tremolo or sforzando/dynamics,  or the other strings that VSL offers, and they fit perfectly into the workflow.  Including the divisi effects possible with Orchestral or Chamber/Solo, as well as adding Solo on top of Appassionata for more "texture" effects of espressivo in doubling violin, viola or cello lines.  


  • Hi William,

    I don't mean to butt in, but I am at a point where I am seriously considering either going more into VSL or over to LASS. I do a LOT of divisis and I am quite impressed by how LASS handles this... but that's not my question. :D

    I completely agree with your comments about the inital beauty of a sample lib. I liken this to my guitar students, many of whom spend THOUSANDS on guitars that... on paper... are fantastic, and yet sincerely struggle to get a 'sound'. And for whatever reason, I stumbled upon a $175 stratocaster 30 years ago that just rocks. There's a LOT to be said for hitting a note and just -feeling- a good sound and I'm glad that Appasionata does it for you... but that's not my question. :D

    My question is: why do you like the VSL -interface- so much? Especially since you work so much with your own presets. In fact, that's been my main gripe with VSL. I wish it -was- more like Kontakt. Part of it is because VEP is an external app so it's not really -inside- Cubase so I often lose track of articulations because it's hard to 'follow' the MIDI in Cubase along with the articulation changes in VI. But almost everything... like the nomenclature (matrices, presets, etc.)... feel like they went out of their way to come up with their own vocabulary. Did you experience this at first? If so, was their an 'epiphany' moment or some other insight you could give me? I -really- struggle with this. I love the sound of VSL Chamber Strings, but I find the -mechanics- so tedious vs. the sonically inferior EW (sorry guys, it's true, makes everything sound like some Video Game) that I can never -relax- and just -write-. Always so much 'twiddling'. Any thoughts?

    ---JC


  • Thanks everyone for all the great responses. I personally find the VSL interface 100 times easier to use than Play because you can just load a matrix and then use a keyswitch or controller to pick the proper articulations as needed. That is much easier than working through hundreds of seemingly similar samples in the Hollywood library and trying to guess which ones you need, assign then to separate MIDI channels, etc. With Hollywood you may have five 1st violin patches loaded and all five may react in different ways to controllers, velocities, etc. That is extremely confusing. Example: some patches use CC 1 to control vibrato; some use CC7 to control both volume and vibrato; some are velocity sensitive; some are not, etc.

  •  Hi Suntower,

    Well, I started with the earlier player, which was more basic.  This is still accessible in the basic VE player.  I still like that interface the best actually, though it can't do everything that the Pro version can do.  But it is very elegant which I value more. 

    The thing I like is how the instruments are all present, right there on the line of patches, and you can see how they are switched instantly.  Also, there is no excess of controls - just the basics.  But they are musically important basics, like the perform control for release time, or the controls for what controller is assigned.  It is very straightforward.  So I got used to that basic player.  I admit that I nowadays will often create an orchestral setup in the basic player, and then, only after it is all made and most of the music finished, convert it to Pro version.  Then it can be tweaked further if needed.


  • Thanks so much for taking the time. If I may trouble you a bit more:

    On a daily basis, what features of VI Pro do you find indispensable? I had a demo (which timed out) and the only thing I found immediately helpful was the time-stretching on bowings with a lot of 'sawing' (timing the bow lengths to the tempi). What do -you- find particularly useful about VI Pro? Maybe I'm just not 'advanced' enough yet to even know what I'm missing.

    ---JC


  • last edited
    last edited

    Hi Suntower,

    the Video Tutorials are focussing on all aspects of VI PRO, step by step [:)]

    A few key-words are hidden on the product page as well.

    Best,

    Paul


    Paul Kopf Head of Product Marketing, Social Media and Support
  • I hate Kontact :) haha. VSL is much better to use in my experience, and I love having VEP seperate. If Cubase crashes under a large project load, often the file is corrupted, and you may have to go back a generation in your backups. I may do quite a lot of work in a half hour saved into that project file - that is then lost. That was always my problem with Cubase. With VEP and Cubase it's kind of a layer of redundancy. I keep a save of both versions and that goes a long way to protecting against corrupted projects. The VEPro module inside Cubase is not very memory intensive and when you freeze an instance you basically put aside a whole bunch of channels EQ's and so on and just have a neat stereo pair left. It's really the perfect way to work (for me). ;) I just need a faster machine so I can run more instances at once. ;)

    Why I hate Kontact: compared to VI Pro it's just so utterly un-intuitive and madenning. I have some Native Instruments stuff which I use for various projects, drums, other instruments, not a lot but I do use it, and whenver I do and I wnat to adjust things like Reverb or eq or do various routing, say especially with multi channel drum instruments I find it so hard. If I want to do the same thing in VEPro and route things through Cubase it's extremely easy and intuitive. But, all this is just me.


  • No it's also me.  I feel the same way about Kontakt, and use it for some few things that VSL doesn't yet have but dislike having to. As I said elsewhere, Kontakt is just dump all the samples in your lap and you sort them out.  No elegance, actually almost no organization at all.  Certainly nothing for orchestral musical use. When you use Kontakt, you are using something that is for sampling helicopter landing sound FX as much as it is for orchestral performance.    But maybe I've been spoiled by how elegant the Vienna Ensemble interface is. 


  • last edited
    last edited

     

    @Suntower said:

    Thanks so much for taking the time. If I may trouble you a bit more:

    On a daily basis, what features of VI Pro do you find indispensable? I had a demo (which timed out) and the only thing I found immediately helpful was the time-stretching on bowings with a lot of 'sawing' (timing the bow lengths to the tempi). What do -you- find particularly useful about VI Pro? Maybe I'm just not 'advanced' enough yet to even know what I'm missing.

    ---JC

    The main thing that is indispensable is MIR.  It is absolutely essential to anyone using sampled orchestral sound to use this.  It addresses everything that composers doing MIDI have always needed but never had until now.


  • Thanks William.

    I started a new topic on this in the software section. If you have a moment, please reply there. Appreciate the feedback.

    ---JC