View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009647 | ardour | features | public | 2024-02-27 19:47 | 2024-02-27 22:01 |
| Reporter | Attila S. | Assigned To | |||
| Priority | normal | Severity | tweak | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | GNU | OS | Linux | OS Version | (any) |
| Product Version | 8.4 | ||||
| Summary | 0009647: Allow inserting bus into another bus without feedback loop problem indication | ||||
| Description | First, to make it clear, this report is about inserting a bus into another bus, and NOT about inserting a bus into a track. So allow inserting bus into another bus without feedback loop problem indication. - Because it seems to work correctly. - Because it is a most useful thing: for example I can set up an elaborated multiband compression or broadcast processor scheme in a bus (used as a plugin chainer) and I can insert it to my main bus as a single and easily bypassable "plugin". - Because it is not the case of "an audio signal chain is plugged back to its input" as the user manual describes what the Feedback indicator really shows: "Feedback - Blinks when Ardour detects a feedback loop, which happens when the output of an audio signal chain is plugged back to its input. This is probably not wanted and can be dangerous for the hardware and the listener." | ||||
| Tags | No tags attached. | ||||
|
|
> First, to make it clear, this report is about inserting a bus into another bus, and NOT about inserting a bus into a track. Same things. Tracks are really just busses with a disk-reader. (We call those "Routes") When it comes to processing, the smallest unit is a Route, which is monolithic. You cannot insert a Route to be processed inside a route. Sorry. Feedback indicates that the process graph is not acyclic. Or In other words: there is a cyclic dependency. Route A depends on route B, and Route B depends on Route A. A feedback loop (unrelated but correlated to audible feedback). |
|
|
"You cannot insert a Route to be processed inside a route. Sorry." Right. At the same time why can I do it in Ardour and why is it working? And if I insert an intermediate Jack passthrough then how is that different? Is that different or correct? Because then the feedback indicator does no blinking. |
|
|
Ardour allows you to temporarily create feedback. e.g. connect first (feedback) then disconnect (feedback resolved). This was motivated for for live mixing where you don't want to interrupt signal flow. During the intermediate state the old process graph and process order is used. Ardour switches to the new graph once the feedback is resolved. > And if I insert an intermediate Jack passthrough then how is that different? It is delayed by 2 process cycles. Ardour's route runs: reads data in jack's input. and writes data for jack client to process next cycle. Ardour finishes processing. jack client wakes up, processes data and writes it to the port for Ardour to use. |
|
|
I see. Thank you Robin for informing me. One more question: Should/could I create future request for a plugin chainer? The current plugins section from a bus would be good as a single plugin. |
|
|
future request = feature request :) |
