score guys-Midi automation tips,.please
Moderator: James Steele
Forum rules
This forum is for most discussion related to the use and optimization of Digital Performer [MacOS] and plug-ins as well as tips and techniques. It is NOT for troubleshooting technical issues, complaints, feature requests, or "Comparative DAW 101."
This forum is for most discussion related to the use and optimization of Digital Performer [MacOS] and plug-ins as well as tips and techniques. It is NOT for troubleshooting technical issues, complaints, feature requests, or "Comparative DAW 101."
score guys-Midi automation tips,.please
Hi Guys,
working on a piece and needed to take a 12 bar section down to pianissimo.
What I did was,.go to the start and take a snapshot to set initial levels.
Then, the section I needed to bring down,..
I grouped the tracks in the mixer via "W" and used "trim latch"
it kind of worked, but made a mess of all the other tracks. They were not in the mix or list,...
so, a question,...guys who do orchestration,...what method do you use for this stuff?
thx in advance
working on a piece and needed to take a 12 bar section down to pianissimo.
What I did was,.go to the start and take a snapshot to set initial levels.
Then, the section I needed to bring down,..
I grouped the tracks in the mixer via "W" and used "trim latch"
it kind of worked, but made a mess of all the other tracks. They were not in the mix or list,...
so, a question,...guys who do orchestration,...what method do you use for this stuff?
thx in advance
Mac Pro Quad 2.66|9GB|Macbook Pro dual core 2.4|4GB|
OS 10.6.4|DP 7.21|Apogee Ensemble & Duet|
OS 10.6.4|DP 7.21|Apogee Ensemble & Duet|
- Mr_Clifford
- Posts: 2430
- Joined: Mon Apr 17, 2006 5:56 pm
- Primary DAW OS: MacOS
- Location: Sunshine Coast, QLD, Australia
- Contact:
Re: score guys-MIDI automation tips,.please
Write p instead of f.minimoog wrote:Hi Guys,
working on a piece and needed to take a 12 bar section down to pianissimo.
so, a question,...guys who do orchestration,...what method do you use for this stuff?
thx in advance
DP 9.52 Mac Pro 10.14.6 RME fireface800. Sibelius. Dorico 4
- MIDI Life Crisis
- Posts: 26277
- Joined: Wed May 18, 2005 10:01 pm
- Primary DAW OS: MacOS
- Contact:
Re: score guys-MIDI automation tips,.please
I generally use either velocity or ctl #7 (vol) depending on the VI or synth response to velovity. In some instances it will switch to a different sample with a better result, but if not then cc#7 will do it as well. I wouldn't mess with latch and stuff especially if you want to export to notation or SMF. My method will allow export that data, latching, etc., um, ...not so much.
2013 Mac Pro 2TB/32GB RAM
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
Instagram
Facebook
MIDI LIFE CRISIS
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
MIDI LIFE CRISIS
Re: score guys-MIDI automation tips,.please
I usually start by loading in a part of a mastered track as a reference for dynamic range and balance. Doing this enables me to leave the faders alone until later. This helps me a lot to maintain a dynamic home base, so to speak. It's one thing to see the master fader topping out at -6dB, for example, but I found it important to understand where a single instrument or any group of instruments register at any given dynamic from softest to loudest and how the aggregate dynamic may result in a well balanced -6dB or whatever your personal "safe peak level" might be.
I'll proceed by going through the MIDI velocities to make sure they transition smoothly or contrast properly from one note to the next. If a sample has velocity layers, I try to make sure that what goes on at the velocity splits or crossover points (where different samples are triggered) are behaving properly.
After that I'll work with CC#11 for more detailed dynamics and fine tuning balances between similar instrumental sections. If all goes well by this point, I'll either group them or bus them to an aux (or auxes) as needed. This minimizes the number of faders to be automated with CC#7. Since there will be no automation on my reference track, it helps me not to have the faders all over the place too early on the mixing process. Thus, my reference track remains almost as relevant at the end of the project as it was at the beginning.
I'll proceed by going through the MIDI velocities to make sure they transition smoothly or contrast properly from one note to the next. If a sample has velocity layers, I try to make sure that what goes on at the velocity splits or crossover points (where different samples are triggered) are behaving properly.
After that I'll work with CC#11 for more detailed dynamics and fine tuning balances between similar instrumental sections. If all goes well by this point, I'll either group them or bus them to an aux (or auxes) as needed. This minimizes the number of faders to be automated with CC#7. Since there will be no automation on my reference track, it helps me not to have the faders all over the place too early on the mixing process. Thus, my reference track remains almost as relevant at the end of the project as it was at the beginning.
6,1 MacPro, 96GB RAM, macOS Monterey 12.7.6, DP 11.33
Re: score guys-MIDI automation tips,.please
thanks for the input guys,..I'm findng that a balance of V scale and "create continuos" (cc7) works well
Mac Pro Quad 2.66|9GB|Macbook Pro dual core 2.4|4GB|
OS 10.6.4|DP 7.21|Apogee Ensemble & Duet|
OS 10.6.4|DP 7.21|Apogee Ensemble & Duet|
Re: score guys-MIDI automation tips,.please
I had the 'W' key do that to me long long ago, and haven't used it since.minimoog wrote:
I grouped the tracks in the mixer via "W" and used "trim latch"
it kind of worked, but made a mess of all the other tracks. They were not in the mix or list,...
I find it safer to use the 'T' key for temporary grouping. There is the added step of selecting tracks to be grouped, but that's no big deal.