View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003625 | ardour | features | public | 2010-12-24 15:14 | 2020-04-19 20:15 |
| Reporter | danboid | Assigned To | cth103 | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Target Version | 3.0-beta1 | ||||
| Summary | 0003625: Proposed changes to inserting PCs | ||||
| Description | As discussed yesterday, when inserting a program change it should inherit the channel(s?) from the channel selector of the currently selected track hence the "Add Program Change" window will only ask for a program number. Might be worth renaming that window to "Insert Program Change" because.. Insering a PC is a bit tedious atm having to go to Region -> MIDI -> Program Change - it would be much more convenient being able to select "Insert Program Change" from the context menu of a region (same goes for Bank changes of course). | ||||
| Tags | No tags attached. | ||||
|
|
As for accessing the program change option, its not quite as bad as I first thought as I forgot that the region menu is available as the top item when you RMB on a region but still it would be better if everything under Region -> MIDI was was available in the top level of the context menu for MIDI regions regardless. |
|
|
I'm not entirely sure how this is supposed to work now in 8357. Now, instead of having a flag for PC and a MIDI auto track for BC we have 'Insert Patch Change' under the MIDI region menu. This window asks for both a Program and a bank number so does each patch change always entail changing/ entering both? Most of the time I will only ever be changing a program or a bank and I'm not entirely sure if all synths like doing both simultaneously- I'm under the impression that the safe way to change to a patch in a new bank is to send the bank change first and then the program change although I can't say I've had this as a problem yet and I don't have any hw synths I can test this with. My second problem with the patch change feature now is that the marker flags it creates only ever show the program number you had selected at insertion and there doesn't seem to be any way to view or edit the bank number. I'd say its prob best to separate PC and BC back out into separate markers that function the same but have unique colours. |
|
|
No, PC and BS messages are "special" in the MIDI spec. It is required that if you need to send both (i.e. to change to a different bank & program) that they be sent with no possible gap between them. As a user you need to think in terms of the following 3 operations: 1) I'm changing to a new program in the same bank 2) I'm changing to a new program in a different bank 3) I'm changing to the same program in a different bank Ardour will ensure that the PC and/or BS messages are delivered as required to accomplish whichever goal you had in mind. I would guess that (3) is likely to be rare. |
|
|
btw, i agree that the bank number needs to be visible. |
|
|
OK Paul- that sounds fine to me then. I've never read the MIDI spec so I was only guessing. I've just discovered that patch change markers are editable exactly like notes are ie you CTRL-RMB click them when in note edit mode to view and edit its properties so its just a case of the marker needing to show both PC and BS (yes BS- much better than BC which was wrong anyway). I think I'd prefer the PC number on the left of the marker and the BC on the right rather than having them aligned vertically which would likely be PC on top and BS below. |
|
|
The bank number is in the verbose cursor; it could be 5 digits long so it might take up quite a lot of space, but it could go there somewhere. |
|
|
Bank number is now displayed in the patch `flag', so this should all be fixed. Please re-open if not. |
|
|
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 |
|---|---|---|---|
| 2010-12-24 15:14 | danboid | New Issue | |
| 2010-12-26 02:12 | cth103 | cost | => 0.00 |
| 2010-12-26 02:12 | cth103 | Target Version | => 3.0-beta1 |
| 2010-12-26 16:45 | danboid | Note Added: 0009708 | |
| 2010-12-26 16:45 | danboid | Note Edited: 0009708 | |
| 2010-12-29 08:52 | danboid | Note Added: 0009728 | |
| 2010-12-29 13:44 | paul | Note Added: 0009729 | |
| 2010-12-29 13:49 | paul | Note Added: 0009730 | |
| 2010-12-29 14:33 | danboid | Note Added: 0009731 | |
| 2011-01-01 17:56 | cth103 | Note Added: 0009772 | |
| 2011-01-30 13:06 | cth103 | Note Added: 0009999 | |
| 2011-01-30 13:06 | cth103 | Status | new => resolved |
| 2011-01-30 13:06 | cth103 | Resolution | open => fixed |
| 2011-01-30 13:06 | cth103 | Assigned To | => cth103 |
| 2020-04-19 20:15 | system | Note Added: 0022318 | |
| 2020-04-19 20:15 | system | Status | resolved => closed |
