View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005332 | ardour | features | public | 2013-02-07 17:02 | 2020-04-19 20:16 |
| Reporter | Alex Stone | Assigned To | x42 | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Summary | 0005332: new tab in editor list "instruments" | ||||
| Description | This is a proposal for a tab that shows a tree view for all the banks and patches in a midnam, associated with a track. (If no midnam assigned to the track, then generalmidi as a default) Use case. When adding a new midi track, or opening a "blank" project from a template, the only way to initialize a patch (to hear it) is to add a region, and assign a patch, then run playback over it. So for example, i open a new project with my "kitchen sink" template, and get no sound untill i go through the manual process described above. Proposed improvement. A new tab in the editor list called "instruments." This tab shows the entire patch list for a selected track's assigned midnam file, in tree form, for banks and patches. Confronted with a blank track (no regions yet), the user selects a patch from the instruments tab, and that patch is loaded, (for a designated channel. If all channels are still active, it defaults to Mcha 1) The user now has a sound to work with. If that particular patch is not the one he wants, he simply selects another patch from the instrument list, and that is loaded, wash, rinse, repeat. When the user has decided he has the patch he wants, he hits a keybinding, or an icon in the patch list, and that patch is added as a program change to the track, at the chosen edit point. If no region is present, a new 1 bar default region is added, but if a region is already present, under the edit point, then the patch is added to the existing region. I'm trying to think this stuff out around the current design of Ardour, and the editor list, imho, offers a good opportunity for better midi patch and/or data management. This should work in conjunction with the program change tab feature request. There's a lot of daws with some sort of active/engageable "directory" window these days, or some derivative, and we already have such a option in place, with the editor list. | ||||
| Tags | No tags attached. | ||||
|
|
The MIDI Patch-Selector should provide the improvements and fulfill the requirements outlined in this feature request. |
|
|
Issue has been closed automatically, by Trigger Close Plugin. Feel free to re-open with additional information if you think the issue is not resolved. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2013-02-07 17:02 | Alex Stone | New Issue | |
| 2020-04-15 02:10 | x42 | Assigned To | => x42 |
| 2020-04-15 02:10 | x42 | Status | new => resolved |
| 2020-04-15 02:10 | x42 | Resolution | open => fixed |
| 2020-04-15 02:10 | x42 | Note Added: 0021354 | |
| 2020-04-19 20:16 | system | Note Added: 0023191 | |
| 2020-04-19 20:16 | system | Status | resolved => closed |
