cfg files useless, you'll find this useful. With all the CC7 values set to the same value, the raw mockup may become useless.If your stage music is too low in volume and like me, you find the volume settings in the. I personally like to start listening to a raw mockup after having applied a playback template, and only after that going on fine-balancing the orchestra. ![]() While I understand (and agree) that having a startup CC7 value for each track is good hygiene, this is not always the fastest way to work. When the instruments are as many as the ones in a full orchestra, reprogramming all of them to balance the orchestra becomes a huge work. Resetting the main MIDI Volume may be harmless when dealing with a single instrument. Paul, just to not let you think you are doing a lot of work for nothing, let me please explain why sometimes this CC7 ‘reset to default’ message can be problematic.Īs you explain, instrument presets in virtual instruments are already programmed, so that they have an internal balance between all the different volume stages. There isn’t the ability to suppress sending of MIDI CCs for volume and pan at the moment, but it’s something we’ll consider for the future. ![]() ![]() So generally it’s better to ensure Kontakt and other plugins are set up with a separate audio output for each MIDI channel, and then use the Dorico audio mixer. So if you change the instrument fader inside Kontakt then any changes will be overwritten by any host (most of them) that send CC7. Meanwhile, Kontakt has a fader on each instrument, but despite looking like an audio fader (it’s labelled in dB), it actually responds to the MIDI CC7. This can also be automated by editing the CC7 profile in Play Mode. Pretty much all plugins respond to the CC7 volume control, so Dorico’s MIDI fader sends this when you start playback or move the fader. So in the case that a plugin has multiple input MIDI channels but only one output, Dorico also needs to have a MIDI fader (eg this is essential for NotePerformer). By default in Kontakt everything is routed to the same audio output, but Dorico doesn’t know whether you have changed that. It assumes MIDI channel 1 => audio output 1. In the case of Kontakt, there are (at least) 4 different faders that affect the level of each instrument:įirstly, Dorico has no way of knowing which MIDI channel is connected to which audio output inside the plugin. ![]() I know Paul normally chimes in on these sort of topics…do you have any insights Paul? This seems strange…firstly that it is different on my slave computers rather than locally, and then the fact that the version history says that if there is explicit data in the CC7 lane of PLAY mode, then this should not happen…and it seems like it still is… This was not what happened in 3.0.10, where the same thing occurred as you experience…Midi reset on CC7 was always sent. However, I also use two slave computers running VSL VIPro players within VEpro Instances…For these slave computers, the CC7 data does not go through anymore and the CC7 Fader stays in whatever state it was left in. I have done some more checking and this is what I have found: Using Dorico 3.1 and VEPro on the same machine, I am finding the same behavior as before, even when there is is explicit CC7 data in the Play lane. I remember your post about Kontakt and it also came up when I searched the forum for CC7.
0 Comments
Leave a Reply. |