View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006367 | ardour | bugs | public | 2015-06-07 16:37 | 2015-08-15 02:12 |
| Reporter | ovenwerks | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | won't fix | ||
| Product Version | 4.X git (version in description) | ||||
| Summary | 0006367: Monitor Section should not be session specific. | ||||
| Description | Right now the presence of the monitor track/route is decided per session. However, the use of the monitor session is more likely to be studio specific than session specific as it may rely on the audio interface or outboard equipment. For example: Joe has a two I/O studio and uses master as his monitoring output. He records several tracks and sends it to his friend Steve to mix down. Steve has a better setup with 8 i/o and uses the monitor section for his control room, master for client listening and a bus (or three) for talent monitors. Steve has to change the session just to start using it and if he sends it back to Joe, Joe is confused by the extra window. Problem two: Many of the monitor sections functions are mappable as key binding and/or control surface buttons. Any of these binding that are set during a monitor on session do not show up in either the keybinding window or the mackie profile editor in a non-monitor section session, but the bindings are still active in that they prevent those keys/buttons from working and in fact look like they are set to default. | ||||
| Tags | No tags attached. | ||||
