Let me know if you are interested in more compare / contrast videos and what you'd like to see me do differently next time.
Played series of semi-random intervals and rhythms to hear how different libraries handle legato and sound, back to back. I was looking for the most consistently pleasing sound in my collection, something I can make my "go to" for most projects.
Notes were quantized to 120 bpm 8th notes, and overlapping by 20 ticks to engage legato.
Tweaked each patch a bit to make them similar for compare / contrast. Did not use Spitfire Chamber, NI+AudioBros or others in this example... maybe in a future vid.
Spitfire "won" this challenge for me, it was easiest to dial in quickly, sounded most consistently pleasing, and did not have any "surprises".
Anthology had some strange stereo effects happening, so I narrowed the stereo image ("width") a bit. It also took the most wrangling of controls to dial something in that felt pleasing without any distracting surprises along the way, but the tone and overall sound is quite nice otherwise.
Hollywood had inconsistent volumes on some of the transitions (I go back and play a very noticeable volume jump twice ... tried to smooth this out with finger position and other controls but could never get that one to sound natural). The tone is nice and full and woody in the low range with felt very "viola section" to me.
EastWest Quantum Leap Symphonic has a nasal tone and fairly rudimentary legato. There may have been other patches to experiment with but the Butter Legato has a great name. I like to mix this in with others because the nasal quality can help a string section shine if blended "underneath" a more balanced sound.
Made this compare/contrast for my own purposes but hope others enjoy as well.
Strings Comparison Patch editing Notes
Spitfire Symphonic - Adjusted mics, full vibrato, slowest legato, low dynamics (mod wheel)
8dio Anthology - Narrowed stereo image (“width”) turned up convolution, mf, medium expression, Leg 1, Full vibrato, medium speed
EWQL Hollywood - “Powerful System” Violas, EW Fat Hall LR, mid mics only, “Other” selected
EWQL Symphonic - Portamento is on… with it off the transitions are very quick and the tone is more pleasing, EW Fat Hall LR
You're so right! I'm sorry, my fault. People should watch this demo, which shows how velocity can be used to make a more porto (lower velocities) or less porto (higher velocities) sound. (Dynamics are controlled w/mod wheel, not velocity.) https://www.spitfireaudio.com/info/basics/spitfire-symphonic-strings-performance-legato/
A trigger is a named PL/SQL unit that is stored in the database and executed ( fired ) in response to a specified event that occurs in the database.
Overview of Triggers.
A trigger is a named program unit that is stored in the database and fired (executed) in response to a specified event. The specified event is associated with either a table, a view, a schema, or the database, and it is one of the following:
A database manipulation (DML) statement ( DELETE , INSERT , or UPDATE )
A database definition (DDL) statement ( CREATE , ALTER , or DROP )
A database operation ( SERVERERROR , LOGON , LOGOFF , STARTUP , or SHUTDOWN )
The trigger is said to be defined on the table, view, schema, or database.
A DML trigger is fired by a DML statement, a DDL trigger is fired by a DDL statement, a DELETE trigger is fired by a DELETE statement, and so on.
An INSTEAD OF trigger is a DML trigger that is defined on a view (not a table). The database fires the INSTEAD OF trigger instead of executing the triggering DML statement. For more information, see Modifying Complex Views (INSTEAD OF Triggers).
A system trigger is defined on a schema or the database. A trigger defined on a schema fires for each event associated with the owner of the schema (the current user). A trigger defined on a database fires for each event associated with all users.
A simple trigger can fire at exactly one of the following timing points :
Before the triggering statement executes.
After the triggering statement executes.
Before each row that the triggering statement affects.
After each row that the triggering statement affects.
A compound trigger can fire at more than one timing point. Compound triggers make it easier to program an approach where you want the actions you implement for the various timing points to share common data. For more information, see Compound Triggers.