Question

Hi,

I would love to see something like this for the work with Orchestra and Hybrid templates with a huge variety of instruments.

A) allow value to set playable range of virtual instruments independently (midi track basis; e. g. C0-G2). Both visually (colored keys in the key editor) and as a state for later commands.

B) allow specifying common octave for instruments (when copied to another track in which octave should the part be played?) e. g. Violin C4

C) when something is copied or moved to another track, the part is automatically put in the favored octave of the instrument.

D) with modifiers/or different commands: 1) auto placement of octave is disabled 2) ghost copy to selected track and transposed to favored octave 3) shared copy to selected track and transposed to favored octave

*D: 2+3 These are macros that copy the transposed part to specific instruments (defined in the macro file)

Cheers guys ;)

Answer 1

You’ve got my vote! I’ve also got a feature request that I need your vote on: https://answers.presonus.com/76617/midi-notation-mute-automation-request

My request is designed to simplify the process of editing the notation used for VST instrument arrangements. Once implemented, there would be no need for manual splitting of MIDI events or note-by-note muting of MIDI notation on the piano roll. This feature is especially handy for repetitive music like EDM, rap, and other electronica, but can be used in any genre where VST instruments are used.

Instead of being limited to manually splitting MIDI events and/or having to go into the piano roll of each individual instrument track to edit MIDI notation, users will have the additional option to automate the “MIDI Mute” Button that already exists on each VST Instrument Track: https://drive.google.com/file/d/1fC7Bktj8XS3--Ys8jNHb9U1w6Irej14M/view?usp=sharing

I put together a short video of me attempting to mimic what the process would look like in real time. Please share the above short and simple video with anyone else you know that would like to get Studio One to work faster and better. Bear in mind, we are all currently unable to recall or save ANY of the MIDI Mute button activity shown in this example…because the “MIDI Mute” button is currently not automatable for whatever reason:

After watching this video, think about how much time it would save to be able to automate “MIDI Mute” compared to having to manually split and mute MIDI events and/or notation from the piano roll to accomplish this same task! Even if you don’t see yourself using this feature, it deserves your vote by virtue of it being a button in a DAW that can’t be automated!?! This is a DAW… all buttons should be automatable, right!?!

The first part of the video also highlights the audible difference between “MIDI Mute” and “Audio Mute”, as the two parameters serve entirely different functions. “MIDI Mute” controls the reading of VST Instrument notation, while “Audio Mute” is effectively a sound man, turning your microphone on and off.

In summary, the current workflow of having to manually split and mute MIDI events parts and/or notation just doesn’t feel natural and takes forever. Having the option to automate the VST Instrument Track “MIDI Mute” button to bring different parts in and out in one take on-the-fly for multiple instrument parts simultaneously will not only be more intuitive, it will also be an exponential time saver!

Add your vote for this exponentially time saving feature on the Presonus feature request page:

https://answers.presonus.com/76617/midi-notation-mute-automation-request