0:12 - Celli Staccatissimo
1:20 - Celli Leg. Slur
2:16 - Violins Runs
2:50 - Violins Pizzicato
3:45 - Violins Spiccato
5:03 - Violins Leg. Port
6:44 - Violas NV NV NV VB
8:34 - Full Strings (1st Violin Leg.)
All melodies are played directly by me on a MIDI keyboard, and are all improvised. Thus, there was no mixing, quantizing or other changes made to the performance heard. Any similar rhythms to other songs are unintentional. The video is for demonstrative purposes only.
If you'd like to see more from this library, you can comment on the video and I can create an additional video showing more from the library. The instruments I chose to feature in this video are among my favorite and most used, and also what I feel best represents the library.
For more information on the product, visit this link:
Hollywood Strings was produced by Doug Rogers, Nick Phoenix, and Thomas Bergersen, with Shawn Murphy as a sound engineer.
"HOLLYWOOD STRINGS has many groundbreaking features not found in any other collection. Finger position is, for the first time, controllable by the user, so you can play as far up the strings as you want, and get a fuller more romantic Hollywood sound. Vibrato intensity and extensive dynamics are controllable by the user. Extensive multi-dynamic true legato has been sampled for all sections in three different categories: slurred, portamento, and bow change. This results in unsurpassed legato performance that has never been available. HOLLYWOOD STRINGS has five user-controllable mic positions, including main pickup (Decca tree), mid pickup, close pickup, surround pickup, and an alternate vintage circa 1945 RCA ribbon room pickup."
Check out some of my original compositions on my channel to hear Hollywood Strings in action.
If I were to export midi from say Guitar Pro 6, does it sound just as good? I've got that problem with EzDrummer that their midi maps that are included sound way better that if I were to export mine from GP6 and adjusting the velocities... Highly considering buying it since it's 50% off atm!
It's quite difficult to sample legato and portamento in a room with natural reverb. Sometimes companies have to make decisions to avoid the expressive articulations for realism reasons. Besides, nothing can beat a real musician's live portamento. The day sample libraries can replace performers is the day we are all doomed haha
Ive just bought CCC2, from east west. Its a huge library. I'm a beginner really, but have high passion and aspiration. I am wondering if you could point me to tutorials on how to use EAST West Hollywood strings, brass, in fact all of them.....Something step by step...which not only shows you how to use it, but for what.
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.