Luis Humanoide
New member
- Genre
- Soundtrack
- Instruments
- Kontakt:
Brass:
♦ Infinite Brass & Beaufort brass from Orchestral Tools
♦ Trailer Brass
♦ Pacific Brass, JunkieXL brass, Fortissimo brass (Free library by Jasper Blunk) [Fortissimo has very nice legato]
♦ Cinematic Studio Brass for a solo trumpet
Strings:
Main strings:
♦ Pacific Ensemble Strings for Spiccato and marcato, and sometimes legato
♦ Performance Sample Vista for the legato string section
♦ Soaring Strings for supporting Vista Strings
♦ Orchestral Strings Runs from Orchestral Tools for the running string part of the end
Woodwinds:
♦ Infinite woodwinds for all woodwinds [It has very nice playability and was very easy to adapt, very good for the runs]
♦ Cinematic Studio Woodwinds for the main flute and piccolo flute [It sounds even more natural]
(I had to bounce to waveform the woodwinds part because my CPU was suffering)
Percussion:
♦ X3M Orchestral percussion for almost everything
♦ True Strike, Metropolis Ark 3 for extra timpani
♦ Cineperc for melodic percussion
Harp:
♦ Orchestral Harp from Project Sam
- Effects
- Valhalla room, Pro-Q
- Released when
- 2024
I'm sharing this cover of the Star Wars theme that I made back in 2024.
My workflow when I made this mockup was:
-Download the MIDI file
-Separate the short and long notes
-Load patches for each type of note
-Add an extra layer of patches, but bounce them to audio so as not to overload the CPU. (I did that in Aaron Venture's Infinite Woodwinds, which don't use much RAM but do use a lot of CPU, causing live performance to freeze.)
Where I took advantage here was in Studio One's ease of bouncing or dragging a MIDI track to an audio track, which allows me to avoid saturating the RAM, especially in a cover with so many instruments.
However, there are things that could have been improved in my workflow, such as the use of Sound Variations and the use of the piano roll with multiple tracks where I could have separated some notes and sent them to another track.
At that time, I loaded Kontakt instances for around 3-4 instruments, when I could have done much more, and assigning multiple outputs.
I put reverb effects on each track, increasing CPU usage. Now I could have sent to multiple FX channels.
My workflow when I made this mockup was:
-Download the MIDI file
-Separate the short and long notes
-Load patches for each type of note
-Add an extra layer of patches, but bounce them to audio so as not to overload the CPU. (I did that in Aaron Venture's Infinite Woodwinds, which don't use much RAM but do use a lot of CPU, causing live performance to freeze.)
Where I took advantage here was in Studio One's ease of bouncing or dragging a MIDI track to an audio track, which allows me to avoid saturating the RAM, especially in a cover with so many instruments.
However, there are things that could have been improved in my workflow, such as the use of Sound Variations and the use of the piano roll with multiple tracks where I could have separated some notes and sent them to another track.
At that time, I loaded Kontakt instances for around 3-4 instruments, when I could have done much more, and assigning multiple outputs.
I put reverb effects on each track, increasing CPU usage. Now I could have sent to multiple FX channels.