View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000078 | OpenMPT | Plugins / VST | public | 2011-02-27 18:20 | 2012-03-07 18:58 |
Reporter | Saga Musix | Assigned To | Saga Musix | ||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | resolved | Resolution | fixed | ||
Target Version | OpenMPT 1.20.01.00 (upgrade first) | Fixed in Version | OpenMPT 1.20.01.00 (upgrade first) | ||
Summary | 0000078: MIDI routing for VST plugins | ||||
Description | It should be possible to route MIDI events (f.e. notes) between VST plugins. There's no concept for this yet, but one idea is to simply use the current "output to" mechanism for selecting the target plugin. | ||||
Tags | No tags attached. | ||||
Has the bug occurred in previous versions? | |||||
Tested code revision (in case you know it) | |||||
Yes, I was thinking about the same. How about in the mix mode you can make a selection called: "Midi note only" and then output to the vst you want. |
|
Could you not just utilize different instruments to do this? FE say you have an instrument which is assigned to use a VSTi (no samples in the map) and you want to route its output to multiple VST effects; a particular effect for this part of the pattern, another effect for a later portion of the pattern. You could easilly accomplish this by setting up an instrument~VSTi which was chained to output to the first VST, and duplicate said instrument and then change the VST the dupe outputs to. Then in the pattern, select the appropriate instrument(s) at the appropriate time(s). Interestingly, I just made use of this suggestion in the song I most recently released.. ^_^ ... unless I'm missing something or didn't fully understand the idea... |
|
I think this misses the point. The problem is that VST plugins can send MIDI data, but this MIDI data is currently not treated by OpenMPT, and can thus not be routed to other plugins (which is the whole idea of the concept). |
|
Ahhhhh... indeed, I had misread (or perhaps poorly interpreted..) the original report.. And true it is, if one wishes to consider OMPT a true host; that MIDI data should indeed flow between plugins if/when desired. One could do so already though; perhaps with creative routing via Midi Yoke or Maple.. and/or VST2MID if wanting to also allow MIDI from the tracker.. so... shrug ;) |
|
Revision 1206 introduces a simple routing mechanism for VST events: If there is a follow-up plugin specified through the "Output to" field, they are routed to that plugin. In the future, more fancy mechanisms like recording MIDI events to the pattern could be introduced (but should not be enabled by default, so that users won't wonder where those strange notes in their pattern come from...). |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2011-02-27 18:20 | Saga Musix | New Issue | |
2011-02-28 16:30 | rakib | Note Added: 0000073 | |
2011-06-17 09:59 | christofori | Note Added: 0000214 | |
2011-06-17 11:30 | Saga Musix | Note Added: 0000216 | |
2011-06-17 16:26 | christofori | Note Added: 0000217 | |
2012-03-07 18:50 | Saga Musix | Assigned To | => Saga Musix |
2012-03-07 18:50 | Saga Musix | Status | new => assigned |
2012-03-07 18:58 | Saga Musix | Note Added: 0000620 | |
2012-03-07 18:58 | Saga Musix | Status | assigned => resolved |
2012-03-07 18:58 | Saga Musix | Resolution | open => fixed |
2012-03-07 18:58 | Saga Musix | Fixed in Version | => OpenMPT 1.20.00.* (old testing) |
2012-03-07 18:58 | Saga Musix | Target Version | => OpenMPT 1.20.01.00 (upgrade first) |
2016-11-20 17:48 | Saga Musix | Category | VST => Plugins (VST) |
2016-11-20 17:48 | Saga Musix | Category | Plugins (VST) => Plugins / VST |