View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009344 | ardour | features | public | 2023-05-22 23:45 | 2023-05-31 23:46 |
| Reporter | wargreen | Assigned To | x42 | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | resolved | Resolution | fixed | ||
| Product Version | 7.4 | ||||
| Summary | 0009344: Routing by audio device | ||||
| Description | In the case of a session created with lot of external I/O is open, edited and saved with another device with less I/O, we just lost the routing for the original device. Example : a live recording session used for a virtual souncheck, we do some edit on the internal soundcard in the train... Or : a session with many live clips tracks routed to different outputs, we need to mix it better without the big soundcard... I imagine a workflow as this (but maybe some are better) : Save the external (to hardware) routing by audio device If the device is changed AND the current routing will change something to the routing for this device : a popup with "The audio device changed, what to do ?" "Load original routing" / "Stay with current routing" And maybe is it a way to merge the two routings ? Only load the previous routing for a track if the current routing is not to an hardware port ? | ||||
| Tags | No tags attached. | ||||
| Users sponsoring this issue | ||
| Sponsors List |
Total Sponsorship = US$ 20 2023-05-22 23:54: wargreen (US$ 20) |
|
|---|---|---|
|
|
Since Ardour 7.4-146 external connections are unconditionally remembered per device. So no popup dialog is needed. One exception is made for the master and monitor output busses. The first time a new device is used, and if Preferences > Signal Flow > Auto-connect main output is enabled, mains-out is connected. |
|
|
I think it's preferable to not try to be smart, and not attempt to "merge" existing external connections from different interfaces. But rather maintain a consistent set of connections for each setup. -- Internal connections are not affected. Please test and let me know if the issue can be closed. |
|
|
The external routing by device work perfectly, thank you for this work ! I understand the choice to not touch the internal connection but it leads to an issue : If a port is connected to an external output with device 1, then we switch to device 2, this port is now auto-connected to the master (or manually to a bus...). Switch back to the device 1 leads to an unexpected double signal path : external + master (that is connected to external). I think that should be avoided (think to a live situation with PA), and in this case the signal path is not consistent for each setup. Maybe somebody have a better idea, but mine : If a port should be connected to external by switching device _this port_ should be connected as saved, internal connection included. So, RFC open ! |
|
|
> If a port is connected to an external output with device 1, then we switch to device 2, this port is now auto-connected to the master (or manually to a bus...). That is not the case, there are no internal auto-connections made when switching backends. Please check again. |
|
|
Internal connections are entirely separate independent from the device used and will remain so. Hence it is not possible to have it disconnected to master or connected to master depending on the backend in use. |
|
|
IIUC you want to toggle between two modes 1. each track has is a pass-trhu in -> no panner -> out 2. each track is connected to master with a panner My first suggestion would be to simply ignore the additional master-bus connection in case of (1), and simply disconnect the master output (which will be remembered). But in case of (1) that would also mean removing an extra output for each mono track (assuming a stereo master). You could add external sends (pre-panner) to each track instead. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-05-22 23:45 | wargreen | New Issue | |
| 2023-05-22 23:54 | wargreen | Sponsorship Added | wargreen: US$ 20 |
| 2023-05-22 23:54 | wargreen | Sponsorship Total | 0 => 20 |
| 2023-05-26 22:21 | x42 | Note Added: 0027684 | |
| 2023-05-26 22:25 | x42 | Assigned To | => x42 |
| 2023-05-26 22:25 | x42 | Status | new => resolved |
| 2023-05-26 22:25 | x42 | Resolution | open => fixed |
| 2023-05-26 22:25 | x42 | Note Added: 0027685 | |
| 2023-05-31 22:33 | wargreen | Note Added: 0027696 | |
| 2023-05-31 23:33 | x42 | Note Added: 0027697 | |
| 2023-05-31 23:35 | x42 | Note Added: 0027698 | |
| 2023-05-31 23:46 | x42 | Note Added: 0027699 |
