![]() ![]() But many times the resulting ‘bounce’ file contains errors. What this means is that if you have a 2 minute sequence, and you bounce to disk, it takes less than 2 minutes to create that bounce audio file. In Digital Performer, this ‘bounce’ process occurs offline, and usually happens faster than real time. ![]() Posted by chasapple on in mixing | 11 commentsĪll DAW programs have a ‘bounce’ feature available to create a stereo or multi-channel mix of your current multi-track project. ![]() Using real-time mixdown instead of Bounce That track is essentially an audio monitoring track, which happens to be the place where the instance. Notice that nothing needed to be done with the actual Instrument track containing Kontakt 3.5. Sometimes just turning on the Automation Play button is enough to make all the proper settings occur behind the scenes. You might never experience this issue as you work with midi VI’s. Just choose Volume in the above settings windows. Notice how the pan knob correctly shows pan left, corresponding directly to the cc#10 data in the track: Some other things to consider: Volume works in exactly the same fashion as Pan was described here. Next click on the Automation Play button in the mixer channel strip for the midi clave track so that it turns green: Now when you playback the track, the pan knob for the midi clave track correctly responds to the incoming cc#10 pan data. Go ahead and select midi pan and close that window. Click and hold in the white rectangle above the pan pot which currently reads ‘latch’ and at the bottom of the resulting menu choose ‘Setup’ : A box opens up showing that global midi automation for Volume/Pan is currently disabled. It’s stuck at the center position: To fix this, we need to check the Automation setup for the clave midi track. CC 10 Pan data is present at the wiper position of Bar 4, but the Pan knob is not responding. The other is a midi track assigned to a Clave instrument on channel 5 of the Kontakt instance. One is the Instrument Track which has Kontakt 3.5 inserted. In this simple example, I have a DP7 project with only 2 active tracks. And this is managed from the Mixing Board for the tracks involved. But if you’re not careful in DP, you may notice that the track does NOT respond to the CC7 and CC10 data you have entered in the Midi Editor or Sequencer Editor window! What causes this? In DP midi tracks, the midi CC data for pan, volume and track mute is still referred to as ‘automation’ data, the same way that ‘automation’ classically refers to things like audio track volume/pan/send levels. In order to send volume and pan changes to your midi VI track, you need to send CC7 for volume and CC10 for pan. Posted by chasapple on automating volume and pan on a midi VI track ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |