Stupid live limitation [solved!]

[haydxn]

haydxn...you CAN do this...at least it works here in Live 5.2.

It's not exactly straight forward if you haven't done it, but...

First choose a track for your MIDI plugin...Then choose another track to send this MIDI data to, and after you select the Track # that has your MIDI plugin in the "MIDI From" drop down(you are clearly getting to this point)....you will notice right below where it says "Track out" now has a little drop down arrow next to it...click and change this from "Track out" to the MIDI plugin. Now you should be recieving the MIDI data from your MIDI plugin instead of the Tracks MIDI.

This is what I was reffering to, and it is how I get Chordspace to work. kodama implied that most plug-ins don't work this way.

-Shehryar

i can see that now it was clear that if it was possible to get chordspace to do it, then ALL plugins would work (no offence to nuffink but there's nothing special about chordspace you know what i mean ). shame you didn't explain how to do it! thanks to all for your help.

[kodama]

Well I can get some to work in Live, but many midi plugs don't work for me at all without using EXT and NicFit NFOut with Midi Yoke.

I wish more midi plug authors could figure out why Chordspace (written in SE) will work but so many others (even ones written in SE) won't?

There seem to be these levels of compatibility:

- WOrks from track to track without having to use MidiYoke.

- Works from track to midiyoke to track.

- Works only within another environment (EXT with NFOut) to midiyoke to the track.

[tamahome]

I couldn't get tobybear's microtuner from the midibag to work with that method. I saw a post somewhere that ableton won't support midi effect vst's because it's not part of the vst standard.

[haydxn]

well if a vst outputs MIDI i see no reason why it shouldn't work. this thread has proved that it is possible to get the midi out of a plugin routed to a track.

i can't think what might be 'broken' about those plugs that causes them not to work...

[nuffink]

Well I can get some to work in Live, but many midi plugs don't work for me at all without using EXT and NicFit NFOut with Midi Yoke.

I wish more midi plug authors could figure out why Chordspace (written in SE) will work but so many others (even ones written in SE) won't?

Beats me. It's not hard.

If anyone wants a visual guide to routing any midi-out vsti (not just ChordSpace) in Live 5, there's one here... http://www.chordspace.com/Playa/Live5Install.htm

[tamahome]

I am sorry, but there are no MIDI plug-ins in the VST standard. Some people misuse the standard to implement something like that, but this doesn't fit into the way Live handles plug-ins. VST effects are all audio based.
If you would be able to insert an audio effect with MIDI functions before the instrument, what shall happen to the audio? And in addition there is no way to detect how a plug-in should be used. We decided not to remove usability for a few plugs that misuse a standard.

Frank
_________________
Frank Hoffmann
hoffmann@ableton.com

http://www.ableton.com/forum/viewtopic. ... t=midi+vst

[nuffink]

I am sorry, but there are no MIDI plug-ins in the VST standard. Some people misuse the standard to implement something like that, but this doesn't fit into the way Live handles plug-ins. VST effects are all audio based.
If you would be able to insert an audio effect with MIDI functions before the instrument, what shall happen to the audio? And in addition there is no way to detect how a plug-in should be used. We decided not to remove usability for a few plugs that misuse a standard.

Frank
_________________
Frank Hoffmann
hoffmann@ableton.com

http://www.ableton.com/forum/viewtopic. ... t=midi+vst

Frankly, Frank's wrong.

[haydxn]

yes. wrong as a... well, he's wrong.

[pdxindy]

I am sorry, but there are no MIDI plug-ins in the VST standard. Some people misuse the standard to implement something like that, but this doesn't fit into the way Live handles plug-ins. VST effects are all audio based.
If you would be able to insert an audio effect with MIDI functions before the instrument, what shall happen to the audio? And in addition there is no way to detect how a plug-in should be used. We decided not to remove usability for a few plugs that misuse a standard.

Frank
_________________
Frank Hoffmann
hoffmann@ableton.com

http://www.ableton.com/forum/viewtopic. ... t=midi+vst

People don't misuse the standard, they provide tools that musicians want. The users are more important than the standard!

[shamann]

The VST Module Architecture SDK is part of the standard, no? Published by Steinberg, they say it is there for the making of MIDI plugins.

[haydxn]

well, that's not really VST tho, that's like, special pretty-much-steinberg-only VST with extra knobs on.

[Polite Company]

People don't misuse the standard

To be fair people do 'misuse' the standard because they are creating tools with it that are outside of the intended scope of the standard. Its like in web design, you can choose to make something that looks good in Internet Explorer (which isn't standards complient) but you can't complain when it looks like crap in Firefox.

Now I'm not saying people should not make whatever plug-ins people want or are useful to people all I'm saying is that when you are working outside the bounds of the standard you should not complain when it does not work right with every host. Either that or campaign to get MIDI plugs inplimeted as part of the VST standard.

[pdxindy]

People don't misuse the standard

To be fair people do 'misuse' the standard because they are creating tools with it that are outside of the intended scope of the standard. Its like in web design, you can choose to make something that looks good in Internet Explorer (which isn't standards complient) but you can't complain when it looks like crap in Firefox.

Now I'm not saying people should not make whatever plug-ins people want or are useful to people all I'm saying is that when you are working outside the bounds of the standard you should not complain when it does not work right with every host. Either that or campaign to get MIDI plugs inplimeted as part of the VST standard.

hehehe

that is not misuse of the standard, that is creatively overcoming a stupid limitation of the standard... it is really the standard which is misusing the people, who are then doing something about it.

same with governments, if they are misusing the people, the people need to go around it or replace it, by whatever means are needed

[MotorsKill23]

Well I can get some to work in Live, but many midi plugs don't work for me at all without using EXT and NicFit NFOut with Midi Yoke.

I wish more midi plug authors could figure out why Chordspace (written in SE) will work but so many others (even ones written in SE) won't?

There seem to be these levels of compatibility:

- WOrks from track to track without having to use MidiYoke.

- Works from track to midiyoke to track.

- Works only within another environment (EXT with NFOut) to midiyoke to the track.

The reason some SE plugins work in Live and some, such as mine do not....is because there is no audio output. If you want to use these plugins in Live, get XT....end of

[nuffink]

The reason some SE plugins work in Live and some, such as mine do not....is because there is no audio output. If you want to use these plugins in Live, get XT....end of

Nope. Mine has no audio output and it works fine in Live.