EastWest Academy 3: Orchestration Part 1

[@tuttib1902]

All recent Ryan/EW scoring/academy videos have been brilliant. Well done. Can't wait for Fantasy Orchestrator🎉

[@matthewfritz]

Ryan, I learn more from you than my ACTUAL orchestration books. Just watching you demonstrate everything with the EW products is an experience on its own. Not just that, but your musical passages are genuinely interesting and engaging and make me want to hear more and learn further about what each part is doing and how they combine to form the full picture.

[@MahmoudNader]

Ryan is a whole new level ❤

[@jawnsolo0]

Ryan is the alpha giga chad of composers for these epic tutorials 🫡🤘🤘

[@alfonsofdez74]

Fantastic content!! You're great! Please, continue with the Academy Series.

[@zhongzheng2450]

This video is awesome. From shooting to production and explanation, everyone is very attentive. Thanks to the creators for their hard work. I'm slowly learning...

[@erikjohnson2976]

Excellent! I was starting to lose faith the EW and Ryan were going to continue with this super-educational series. Bravo! Please keep this going. And, yes, these videos are definitely generating interest in the EW product suite -- I just recently started my Composer Cloud subscription based upon these videos. Please. Keep. This. Going.

[@dutonic]

You're so talented dude. The classes are great as always, but you bring a magic and adventurous feeling in this song that almost made me cry from how awesome and epic it sounded. Great stuff

[@tdcmusicnow5312]

Eastwest always comes through this is PURE brilliance 😎

[@Tanguy_Follio]

Bravo Rayan for your talents as a composer, orchestrator, and of course, teacher ;-) Your videos are really rich and useful for young composers.

[@studioraymondvanmelzen]

I love this series. It's very helpful and you make it all look and sound so easy. That gives me the courage to keep trying.

[@jloiben12]

These videos aren’t the easiest to make but this is the best type of content you can make. How to videos are very good marketing tools

[@rotarydragon6834]

Excellent information in an easy and quick format

[@41Fingers]

What a Great Video!, Impressive music demo!

[@shane_taylor]

A great continuation of one of the best Orchestration tutorials I've seen. Great work Ryan and EW. Thanks for providing these. They are such an educational treasure.

[@akcel1211]

Love this tutorial series, thanks so much !

[@mattwallis1893]

Excellent

[@tdcmusicnow5312]

This stuff is breathtaking what dreams are made of

[@exodusstudioprod]

Excellent work. Great explanation

[@NowCopland]

Once again, that's excellent!

[@Dragan_Drazic]

Wonderful demonstration and explanation, thank you.

[@gobeyondchannel]

Superb video, let's just appreciate how talented Ryan is. John Williams would be proud.

[@paulferber2118]

As with everything East/West, outstanding, clear and helpful. Keep them coming.

[@misterdeity]

Great piece!!!

[@MusicNation-TV]

Wow, outstanding piece!

[@BenMartinBox]

Thank you for sharing. Nice tips and very good piece of composition /orchestration.

[@spokansas]

Yay! I was awaiting Class #3

[@adrian.joker1338]

you guys are awesome for this amazingly educational series, Ryan, you're a beast! such a great teacher!

[@Zoomfilm1]

So nice and delicate piece of music and a great inspiration

[@superkaboose1066]

Can't wait for the next part! Especially when you get into the mixing of things, easy to get messy!

[@MsTessG]

Great stuff! Thanks!

[@Bashanvibe]

Always a learning experience!!! Respect 👊🏾

[@CJCalvertMusic]

Great video Ryan - excellent orchestration tips!

[@MihaiSorohan]

Awesome music.

[@franklp2183]

These videos are absolutely awesome! Ryan is a great composer/programmer, and I'm grateful to him for sharing his wonderful tips and techniques in composing, orchestration and utilization of EastWest's powerful library!

[@calvin_choi]

Thank you!! I got a lot of musical inspiration from this video.

[@BenjaminOziel]

Thank you Ryan ! You are among the great composers ! And a very good teacher too :)

[@CathlynDeBurga]

I love it!!!! cant wait to use it by myself

[@SebastianAmmerlynd]

Great series so far! Very inspirational!

[@1000buffalos]

I work up an idea and get a few good ideas out. Ryan makes a demonstration piece, and he whole thing is brilliant!

[@DopaLink]

Very informative video! Thanks!

[@EWQLTutorials]

Glad you enjoyed it!

[@alexngm]

You are truly an amazing composer! I have all these sounds, and I wish I could make mine sound this incredible. Well done!

[@ObsessiveCostumingDude]

Fantastic demo piece - thanks for sharing and discussing it with us! :)

[@marcotronic]

Excellent video! Looking forward to the next part already!

[@Ohleysmokes]

Amazing writing and amazing product

[@VannKrakenGaming]

Glad to see the return of the series!!

[@ilidan257]

Pleasure to watch. Its so helpful 🎉

[@thebarrylurveshow5530]

This is great, so well explained

[@turtlefeet7722]

Thanks, I really have to learn to use the Opus thoroughly.

[@GaryEskow]

You are fantastic! Gary Eskow

[@donferrone9679]

Great presentation. Your knowledge and artistic ability blows sky mind. Thank You

[@j.j.hagelsieb]

Love it, guys!!!

[@ghfjfghjasdfasdf]

Outstanding explanation 🤟

[@erichurt9001]

absolutely incredible...love these videos!

[@CybreSmee]

Hey Ryan, amazing. Any chance you could release the MIDI arrangement for that? I'd love to study it closer.

[@NikosDimogiannis]

excellent writing!!!

[@AlexisPerezIndal]

Very insightful as always. And really inspiring! I’ve been composing and producing rock and "contemporary" music. Working with orchestra has always been a side thing. The Composer Cloud allows me to have the full orchestra under my fingers with a very coherent sound thanks to your library, as I use your sounds almost exclusively. I’ve been studying orchestration for months now and it feels great to feel like a student again :) these videos really help! Thanks guys

[@Hugosanches594]

Pleasee keep with this series release the part 2 with fantasy orchestrator, and thanks for all

[@novaray3405]

Awesome

[@musicjazzvez]

Great video and instruction, make me want to do better in my compositions! Thank you for sharing!

[@brickfactor]

Thanks ! Great tutorial as always. Will you share one of your sequencer project one day ? It would be great to be able to study it in details.

[@studioryde]

Hi Ryan. This project is out of this world. It sounds like real orchestral performance, no doubt. All my congratulations ! I have EWSOQL, Diamond, Hollywood and Fantasy, along with the candy libraries. So I would LOVE to have the MIDI project for trying it out. Thanks a million for these tutorials, keep them up !

[@KaceyBakerFilms]

Wouldn’t we all 😂

[@prodbysgbeatz2]

looking forward to the next episode.... just don't make us wait half a year again :))

[@stevenvillacis1163]

I have re watched it at least 3 times now, always learn something new! I copied your template but my computer seems to barely hadnle it, I'd love to see any tips on how to manage such a large session so that your computer doesn't explodes! Bravo, amazing video!

[@EWQLTutorials]

RAM ALLOCATION / TEMPLATE CONSOLIDATION SUGGESTIONS: RAM allocation is all based on your session size and equates to your system’s available memory resources for that session. While using an SSD can certainly assist with the performance of your samples and your DAW, it cannot allow you to load up more instances or allocate more RAM than you were able to before or that you have available to you with your system specs. Please refer to the chart below to see what is the approximate recommended template size(s) for your system’s corresponding RAM based on a calculation of 2GB each for DAW and OS, and 250-330MB per instrument. The new OPUS Engine is a lot more economical in RAM consumption. Please see performance improvements specific for Opus a bit further below. This allows for roughly 1.5 - 2x the instrument count with the same available RAM. TEMPLATE SESSION SIZES CHART PER RAM COUNT: 8 GB of RAM / 10 to 15 tracks session size [Not recommended for Opus Edition libraries] 16 GB of RAM / 15-25 tracks maximum usually. 32 GB of RAM / 50-70 tracks session size (with being economical, up to 100) 64 GB of RAM / 100-150 tracks session sizes 128 GB of RAM / 150+ tracks approximately We recommend either consolidating your session’s template size through the following tips below or upgrading your RAM to allow for more Memory resources in your sessions - DAW TIPS & TRICKS for IMPROVING PERFORMANCE: Bouncing certain sections of the ensemble to audio / aux tracks - e.g. String libraries use a ton of RAM, so if you are writing string heavy ensembles that have high track counts that can eat up your RAM quickly. Freezing tracks of sections you aren’t actively working on, which would allow for more available RAM. This one is a bit less likely, but GPU/GUI resources, such as Channel FX strip plugins - Reverb, EQ, compressors, or mastering plugins (watch for these inside of the libraries themselves too! If a lot of those are turned on, that will steeply affect RAM and CPU performance). Many composers do their mixing & mastering at the end with the bounced audio stems, but it’s these little things to look out for, particularly with Microphone placements and other added effects. Lastly, the most optimal way to go about it is consolidating your session by minimizing your track counts/ sample sizes to account for your current RAM. Ways you can do this are the following: Creating multis or keyswitches/articulation maps with only the articulations you need or bouncing out to audio any samples that serve as doublings. While Play currently doesn’t allow for any custom keyswitches in it’s current version, depending on your DAW, you could create/design a custom expression map or articulation map for the instruments you would like to load up in your session and be able to swap between articulations more efficiently. PLAY Engine only: Settings > Streaming > Streaming Settings > Voices Limit: This feature determines how many voices can be streamed simultaneously. The Sample Cache feature (page 23) allows you to determine how many of the samples are loaded directly into RAM or are streamed from the drive. Test out different levels to see what works best for you. media.soundsonline.com/manuals/EW-Play-6-User-Manual.pdf#page=28 Sample Purging (page 65) on larger samples that aren’t inherently active / similar to freezing tracks.media.soundsonline.com/manuals/EW-Play-6-User-Manual.pdf#page=70 Thinking about the sample sizes (Actual listed RAM sizes, which you can see on the bottom when the samples are loaded in the Play engine Browser/Player window.) OPUS Engine only: The Opus engine allows for custom keyswitches through the "Perform" > "Zones" section. Go to Settings > Performance > Audio Engine and Audio Drives and make sure that the "Default Preload Size" is set to whatever drives you have installed. Make sure that "Never Preload" is turned off. Use the Purge control (the horizontal red / yellow / green buttons) to purge all samples. Purging the samples, then playing your MIDI line, will only reload the required samples, and not the entire patch. Turn off all background programs such as security etc. Depending on your security settings, these might actually be scanning the samples prior to them loading / playing. Only open your DAW. Check how many programs are automatically run upon startup. -Instead of loading up the full samples for a given library collection, you can reduce the stress on your project’s template and your machine by loading up the LITE resources instrument samples. Use these to your advantage to reduce the amount of RAM consumption during your sessions. Sort through your instrumentation/palette and try to find ways to cut corners for your particular setup. It’s exactly like budgeting where the little stuff can really add up.

[@stevenvillacis1163]

@@EWQLTutorials This is amazing, thanks guys! You're the best!

[@HealingNews]

It is simply amazing what EastWest has done with instruments and vocals, while taking orchestration to the level of Opus, opening up this tech to anyone interested in excelling, and whoa, what an opportunity this makes for all of us! We, I specifically - wish to have more time to learn even more, seems like the more diversity we have the farther we can go, any more comments or suggestions?

[@rolandv-piano]

Ryan is the best! When will part 2 be uploaded?

[@komsfon]

Great! Thank you!

[@enzodigiuseppe.]

Hi, thank you so much for sharing your skill. Compliments !! it would be wonderful to also have a midi session to be able to see all the joints better. it would be possible? Thank you very much :-)

[@Kraflyn]

is there a limiter at the output?

[@Infamore]

Interesting. He pretty much teaches you how to compose music.

[@cguzelli1]

Wonderful and extremely educational. May I ask what DAW you are using?

[@EWQLTutorials]

Logic, though you can use any DAW.

[@BlkvlvtEnt]

Eastwest sound is 🔥🔥🔥 never disappoint with the out come 💯

[@Karabanka]

Thank you sooo much for this video. Can you make this using Kontakt :D?

[@datooch]

What MIDI controller is that? These videos are awesome! Thank you for sharing your knowledge! You are very talented.

[@OceanViewStudioArts]

Watched all three in one go. Chapeau Ryan! As a newbie to EW, I would like to get into more depth of you using Reverb in the Orchestration, hence how do you decide how much you send each section or individual Instruments to the send FX bus reverb of your choice. As for articulations, key switches puzzle me to be honest. Switching while playing seems awkward to me, I tried it a few times now, perhaps you get used to it, but I guess the only alternative is to edit the recording and apply articulations afterwards. Anyways, keep them Academy videos coming, much appreciated.

[@TheFjMartinmusic]

Please update hollywood with solo viola

[@musicformediagr]

Thank you Ryan 😍✌️Can i ask if you do any volume balancing between patches? Or just expression and modulation??

[@TheAtheistworld]

Where is part 2 ??????

[@AlexisPerezIndal]

What articulation are you using on your violin run at the beginning? I’m struggling to make it work…

[@david_musicisdivine5541]

Thanks for the tips! Anyway may I know how reliable is the Nektar LX88+ ? Is it a good midi controller keyboard ? I mean can it cope up with the current updates ?

[@froogs165]

When buying a new mac for Logic, which is more important: RAM or CPU?

[@EWQLTutorials]

... Yes? Both definitely play a part in how large of a project you can run before you start either having issues with the processing or RAM overload. RAM ALLOCATION / TEMPLATE CONSOLIDATION SUGGESTIONS: RAM allocation is all based on your session size and equates to your system’s available memory resources for that session. While using an SSD can certainly assist with the performance of your samples and your DAW, it cannot allow you to load up more instances or allocate more RAM than you were able to before or that you have available to you with your system specs. Please refer to the chart below to see what is the approximate recommended template size(s) for your system’s corresponding RAM based on a calculation of 2GB each for DAW and OS, and 250-330MB per instrument. The new OPUS Engine is a lot more economical in RAM consumption. Please see performance improvements specific for Opus a bit further below. This allows for roughly 1.5 - 2x the instrument count with the same available RAM. TEMPLATE SESSION SIZES CHART PER RAM COUNT: 8 GB of RAM / 10 to 15 tracks session size [Not recommended for Opus Edition libraries] 16 GB of RAM / 15-25 tracks maximum usually. 32 GB of RAM / 50-70 tracks session size (with being economical, up to 100) 64 GB of RAM / 100-150 tracks session sizes 128 GB of RAM / 150+ tracks approximately We recommend either consolidating your session’s template size through the following tips below or upgrading your RAM to allow for more Memory resources in your sessions - DAW TIPS & TRICKS for IMPROVING PERFORMANCE: 1. Bouncing certain sections of the ensemble to audio / aux tracks - e.g. String libraries use a ton of RAM, so if you are writing string heavy ensembles that have high track counts that can eat up your RAM quickly. 2. Freezing tracks of sections you aren’t actively working on, which would allow for more available RAM. 3. This one is a bit less likely, but GPU/GUI resources, such as Channel FX strip plugins - Reverb, EQ, compressors, or mastering plugins (watch for these inside of the libraries themselves too! If a lot of those are turned on, that will steeply affect RAM and CPU performance). Many composers do their mixing & mastering at the end with the bounced audio stems, but it’s these little things to look out for, particularly with Microphone placements and other added effects. 4. Lastly, the most optimal way to go about it is consolidating your session by minimizing your track counts/ sample sizes to account for your current RAM. Ways you can do this are the following: - Creating multis or keyswitches/articulation maps with only the articulations you need or bouncing out to audio any samples that serve as doublings. While Play currently doesn’t allow for any custom keyswitches in it’s current version, depending on your DAW, you could create/design a custom expression map or articulation map for the instruments you would like to load up in your session and be able to swap between articulations more efficiently. PLAY Engine only: - Settings > Streaming > Streaming Settings > Voices Limit: This feature determines how many voices can be streamed simultaneously. - The Sample Cache feature (page 23) allows you to determine how many of the samples are loaded directly into RAM or are streamed from the drive. Test out different levels to see what works best for you. media.soundsonline.com/manuals/EW-Play-6-User-Manual.pdf#page=28 - Sample Purging (page 65) on larger samples that aren’t inherently active / similar to freezing tracks.media.soundsonline.com/manuals/EW-Play-6-User-Manual.pdf#page=70 - Thinking about the sample sizes (Actual listed RAM sizes, which you can see on the bottom when the samples are loaded in the Play engine Browser/Player window.) OPUS Engine only: - The Opus engine allows for custom keyswitches through the "Perform" > "Zones" section. - Go to Settings > Performance > Audio Engine and Audio Drives and make sure that the "Default Preload Size" is set to whatever drives you have installed. - Make sure that "Never Preload" is turned off. - Use the Purge control (the horizontal red / yellow / green buttons) to purge all samples. Purging the samples, then playing your MIDI line, will only reload the required samples, and not the entire patch. - Turn off all background programs such as security etc. Depending on your security settings, these might actually be scanning the samples prior to them loading / playing. - Only open your DAW. Check how many programs are automatically run upon startup. -Instead of loading up the full samples for a given library collection, you can reduce the stress on your project’s template and your machine by loading up the LITE resources instrument samples. Use these to your advantage to reduce the amount of RAM consumption during your sessions. But even if you account for RAM by having the samples set to never preload, the libraries streaming from an SSD, etc. you could still get stymied by having not enough CPU for the number of tracks/processes you're running at once

[@froogs165]

Thank you so much for this robust, detailed response! @@EWQLTutorials

[@craigreeves5465]

Can we have Ryan's talent included in the next upgrade as an add-on?

[@wagnerbertolino2]

Isn't anybody gonna say anything about these seven-headed monster Chord Progressions on his theme??? It is in the key of C-C#-D-D#-E-F-Gb-G-Ab-A-Bb-B!!!! Nuts!!!

[@larssterberg7340]

I can hear some choir? But it's not mentioned... otherwise very nice😊