View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008721 | ardour | features | public | 2021-05-24 09:05 | 2022-04-18 05:23 |
| Reporter | whitewolfmusic | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | N/A |
| Status | new | Resolution | open | ||
| Platform | Apple Macintosh | OS | MacOS | OS Version | 10.12 or later |
| Product Version | 6.7 | ||||
| Summary | 0008721: MIDI workflow improvements for Ardour v7 | ||||
| Description | Original topic with explanations: https://discourse.ardour.org/t/suggestions-to-improve-midi-workflow-in-ardour-v7/105979 Summary of requested changes: ============== Add track dialog: ============== - remember the last selected track type and / or - allow rearranging track types / making MIDI track the default selection ==================== Create new MIDI region: ==================== - double clicking inside a MIDI track creates a new 4-bar MIDI region, starting with the bar that has been double-clicked ================== Editing a MIDI region: ================== After double-clicking a MIDI region to zoom into it: - if the region is empty, automatically switch to drawing mode - if the region contains note data, automatically switch to internal edit mode; but in the settings: - add an option to choose between internal edit mode and drawing mode for this - default note velocity should be 127. - when scrolling with mousewheel to change velocity before drawing a new note, keep this new velocity value for drawing further notes =================================== Something that drives me crazy right now: =================================== When drawing notes within a zoomed region, I want to scroll up and down the octaves. NOT the tracks. To do that, I currently have to move the cursor over this super thin strip of octave selector, which slows me down, is not intuitive and requires too much precision to keep the cursor in that slim region. So: - When zoomed into a MIDI region, make scrolling the mouse wheel scroll up and down ovtaves instead of the track list, while the cursor is over an empty area and no notes are selected. ====================================================== Allow to exit the zoom to MIDI region the same way as entering it: ====================================================== - double-click with the grabbing tool inside a zoomed-in MIDI region goes back to the zoom level before | ||||
| Tags | Ardour, editing, feature request, MIDI region, usability | ||||
|
|
Thanks, that is a nice list of good suggestions! A few comments: > - remember the last selected track type > and / or > - allow rearranging track types / making MIDI track the default selection The latter is not great since GUI should be consistent. However The former has been near the bottom of my ToDo list for at least 10 years. It is low priority since compared to hours and hours of recording, editing and mixing, adding tracks is a non-issue. Preselection shaves off a few seconds. I keep it on a list for someone new to the coding who may want to start contributing to the project. > - when scrolling with mousewheel to change velocity before drawing a new note, keep this new velocity value for drawing further notes Currently Ardour uses velocity of the previous note when you append to a region, and otherwise the average of previous/next note. This should perhaps be more explicit, and this ties in with https://tracker.ardour.org/view.php?id=5608 > - double-click with the grabbing tool inside a zoomed-in MIDI region goes back to the zoom level before We need to be careful to not overload what double-click does. I don't like the double-click to zoom. That was added only as experiment and somehow remained. Double-click usually it activates an action that operates on the current selection (e.g. create regions on selected track). There are some edge-cases with your suggestion. e.g. what happens if you manually resize the track or window after maximizing? Does double-click fill again? explicit "fill" (F) and "visual undo" (Ctrl+shift+Z) operations are preferable. PS. Ardour 7 is mainly about fixing a fundamental issue how ardour represents time internally, major version change is needed since the session format changes. Your suggestions are mostly incremental small changes that can happen later during the 7.x or 8.x minor releases. They're workflow specific and not session-format related. |
|
|
I would add panning note inside pianoroll. |
|
|
> - allow rearranging track types / making MIDI track the default selection @x42: "The latter is not great since GUI should be consistent." That is correct, in hindsight, I would prefer a simple "make default" button or an option in the settings. ----------------------------------------- @x42: "what happens if you manually resize the track or window after maximizing? Does double-click fill again? explicit "fill" (F) and "visual undo" (Ctrl+shift+Z) operations are preferable." Good point. However, I see an urgent need for improvement in this area. Since Ardour does not apply to the typical way of MIDI editing, having a separate window or screen area, my personal experience is that navigating tracks and navigating the piano roll get in each other's way. When I zoom into a MIDI event, I commit to edit only the note content of that event. I want to navigate only the information surrounding this task. That means to me, if I scroll, I want to scroll the octaves, not the tracks. Fully zooming in to a MIDI event equals opening a separate editor window in my mind, so double-clicking to zoom should lock this zoom state until manually exiting it. Zooming into a MIDI region should prevent scrolling tracks and instead scroll octaves inside the piano roll, that would be the best and most logical compromise to me, for not having a separate editing area. |
|
|
as of commit b725b7ddb4, the scrolling behavior has been implemented as follows: - scroll in a MIDI region with no notes selected with adjust the visible note range - with no modifier, it moves by single notes - with the tertiary modifier (shift) it moves by octaves (matches transpose behavior) - with the primary (ctrl on linux/win, cmd on macOS) modifier, it modifies expands the note range rather than scrolling. scroll up will increase the uppermost visible note, scroll down will decrease the lowermost visible note Remember that scroll if there are notes selected is used to adjust note velocity. Thanks for this suggestion. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2021-05-24 09:05 | whitewolfmusic | New Issue | |
| 2021-05-24 09:05 | whitewolfmusic | Tag Attached: Ardour | |
| 2021-05-24 09:05 | whitewolfmusic | Tag Attached: editing | |
| 2021-05-24 09:05 | whitewolfmusic | Tag Attached: feature request | |
| 2021-05-24 09:05 | whitewolfmusic | Tag Attached: MIDI region | |
| 2021-05-24 09:05 | whitewolfmusic | Tag Attached: usability | |
| 2021-05-24 17:20 | x42 | Note Added: 0025886 | |
| 2021-05-24 17:37 | Daniele1971 | Note Added: 0025887 | |
| 2021-05-25 03:08 | whitewolfmusic | Note Added: 0025890 | |
| 2022-04-18 05:23 | paul | Note Added: 0026407 |
