Studio One does support midi plugins, in round about way. I have used the Sonar MIDI plugins and kirnu cream(http://www.kirnuarp.com) but in it's own track.

The way to do it is load the plugin to it's own track(drag it to an open space) then in the track with the instrument you want it control set the input to the track with the plugin track. When you monitor make sure both tracks are active and the keyboard is set on the plugin track and any events are recorded to that track. You can automate both tracks so there is that benefit at least. Kinda like Sonar in reverse two tracks however the MIDi is on both if you make the input set the same.

It's really not too complicated. There is a way of doing a track to accept both the instrument and the plugin but it only works if the plugin is audio such as the old Revalver plugin(which I set up) by creating an instrument track than dropping the plugin on it,removing the instrument than dragging back to browser then dragging it back in on an audio track then Revalver will work.

There are ways to work around the handicaps within Studio One but it would be nice if they come up with a sensible way of doing MIDI plugins.

WallyG

batsbrew
there doesn't seem to be ANY trouble with studio one and midi............?!

I've looked high and low and I can't find any problems with MIDI in Studio One. In fact, I like it better than Sonar's implementation, especially the way they do Continuous Controller change lanes.
 
Walt

It is not that there is anything wrong with what is there. It is functional. It is just that it is not enough for some users. The graphic CC change display is useful for some purposes. For I others, it is a hot, fiddly mess, and a simple midi event list would be a far more effective tool.

anydmusic

tenfoot

soens
A bit expensive ($149, $249, or $349) if you just want patch name capability, which Sonar already does.
 
I know it does a lot more but I already have a FREE patch/sequence editor for my rig.

...
 
Correct me if I'm wrong, but isn't the idea of this as a replacement for Instrument definitions a bit misleading? For one thing, it seems that this is in fact desgined to streamline the process of setting up definitions (patch name export), not replace it.
 
...

I certainly don't see Midi Quest as a replacement for good instrument definitions, I like that it makes managing them easy in Sonar but the fact that the process is convoluted in Cubase to the point where keeping them updated will require a bit more manual effort is not going to stop me using them and start having Midi Quest active when I don't need to.
 
I use Instrument Definitions to help me quickly find a sound that I can use that is already loaded in one of the modules that I have.
 
I use Midi Quest to edit the sounds and manage what is loaded in the modules.
 
If I have understood correctly Jeff is advocating a different workflow where sound selection is handled outside of the DAW using an Editor accessed by switching programs. Even though using Midi Quest I would only need one Editor that approach would not work for me.
 
I have Midi Quest version  11.0.3 which is the latest and is dated 2013 so a few years since the last update. I would agree that the website looks dated.

 
Makes perfect sense Graham. If they ever have a sale I will give it a run. I guess given that this software is really geared towards older hardware the lack of updates isnt that surprising. If it aint broke....:)
 

In this day and age, why do people still assume midi is only used to control synths?
 
Rhetorical question. Software is never improved by defending its limitations.

I am not being able to drive external MIDI instrument.
 
 
I hae a Roland A800 and Yamaha Motif Rack connected to my DAW PC
I have tested with MIDI-OX. I can play the Motif From A800.
In SO3 -I have taken an Instrument Track
Input A800. Output Motif.
MIDI part got recorded from A800 without routing to Motif, thus no sound.
While playback the same.
 
I am not being able to configure, I think.
Any help please.
 
Regards
Snehankur

A little input here from someone who is working with no external instruments except my drum brain, which happens to be a Pearl Mimic Pro at the moment (coming from Rolad TD-20).  I never found Instrument Definitions to be terribly useful, but only really ever had one "external" synth, which was ironically on a card inside the computer and  used an editor for it, which was WAY better.  In that case, it was XGEdit for an old SW1000XG card and it worked so much better than any of the instrument definitions or Sonar control panels (can't even remember what they were called, but we ugly and clunky at best).
 
All that said, I will truly miss the Cakewalk drum maps.  I used them for every recording for the midi data I recorded from my Drums.  In Studio One (which I am adapting to), there are maps to a degree - you can map the notes to names and a few basic things, but the parts I see most missing are:
 
Notes that have no "length".  Drum notes don't have duration and don't need to be shown as such.
Velocity tags ON the note instead of just in the controller pane at the bottom are very useful for quick and accurate adjustments.
BIG: Limiting the notes shown in the midi view to ONLY those that are mapped is a HUGE help in looking at a drum track rather than having to see all of the in between notes that will never be used/recorded.
 
I didn't really use the IN to OUT mapping to change one note to another to control different sample libraries or instruments, though I'm sure that those were useful to others.
 
I will try to put in a FR over at Presonus, but it doesn't seem likely that I'll get a lot of ground there since there is an overwhelming amount of Sonar Whining over there as it is and I've had issues even getting Sonar folks to adopt the Drum Maps.  I even created tutorial videos on how to use the feature, how to set it up, etc, but lots of people still stuck to the old Split Notes to Tracks CAL, which is far inferior in my opinion.

Jeff.... Nice workarounds for parts of the drum map concept. Please check out the video on my web site for the way that an older version through current of sonar handles drums maps.

The main things I am looking for are listed above and I found that there is actually already a fr for it asking for similar things with 250 or so votes.

Amicus717
 
...For what it is worth, though, SO3's midi implementation is an exercise in concise brilliance when compared to Samplitude's. I own Samplitude, and have used it enough to develop a good basic understanding of it, so I figured it might be worth trying as a primary replacement for Sonar. So I've been really digging into the program this week. Tonight, I spent an hour trying to figure out how to set up a multitimbral instance of Kontakt, and I thought at one point I was going to have an aneurism. The GUI designers at Samplitude put extra effort into making the process as unintuitive as possible without actually breaking the software. 
 

Whoah! Here's a TIP worth applying: 
If there is any Samplitude feature you don't know how to use, spend the first 10 minutes searching for and then watching a Kraznet video where he explains how to do it. Then spend the rest of your hour using the feature and enjoying Samplitude (instead of banging your head). 
For Multi-Outs using Kontakt, see this: 
https://www.youtube.com/watch?v=DXQrHfiOpH8
 
And then get back to work!
:^)