View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000708 | ardour | bugs | public | 2004-09-06 00:14 | 2008-11-20 23:38 |
| Reporter | dharper | Assigned To | paul | ||
| Priority | urgent | Severity | crash | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0000708: Sends don't work and sometimes crashes | ||||
| Description | Using Ardour 0.9beta19 ardour/gtk: 0.531.1 libardour: 0.830.0 When I try to create a send in the post fader section of a track to a bus, in various places in this process I've crashed Ardour. If I am successful in setting it up, the send doesn't work, there is no signal going to the bus even though the routing is setup correctly. | ||||
| Tags | No tags attached. | ||||
|
|
is this limited to the post-fader section? |
|
|
No, the same behaviour occurs if the send is post or pre fader. I tested it again with the latest CVS over the weekend and had the same problems as before. |
|
|
I've also never managed to get sends working. I setup what I was sure should have worked, but also got no signal. Ardour did also crash sometimes when attempting (send creation worked but enabling the send killed Ardour). I'll try to put some reproducible instructions down later, that way I can verify that I'm doing things correctly, if nothing else. |
|
|
my sends work perfectly now. |
|
|
It seems the problem I was having with sends was a combination of user error and a bug in ardour. The user error part consists of my initial confusion with the send output dialog; I assumed that I should choose the track wishing to send data as an output, and then select the send output in the input dialog of the bus or track wishing to receive the send data. Obviously this is not correct, and given a little thought, doesn't make any sense! The send infers implicitly what the input is, by the bus or track it is inserted in (pre or post fader). I didn't notice that the send automatically adds itself to the inputs of the track or bus selected in the send output dialog. However, an ardour-crashing bug still exists from the send that feeds its output back into itself. This bug still exists in CVS from 9th Nov 2004. To reproduce: 1. Create a new session 2. Create a mono track, and name it 'sendtrack' 3. In the pre-fader section, create a send: set the output to sendtrack/1 4. Enable the send 5. Create a new mono track or bus At the point of attempting to create the new track/bus, Ardour should crash. |
|
|
i replicated the bug, and fixed it in my code. we should not check for a route feeding itself. even though routes can do this, it causes an endless recursion when computing the execution order of routes. CVS commit later today. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2004-09-06 00:14 | dharper | New Issue | |
| 2004-09-06 00:14 | dharper | => tech@danharper.org | |
| 2004-09-06 00:14 | dharper | Name | => Dan Harper |
| 2004-10-13 00:20 | paul | Note Added: 0001491 | |
| 2004-10-25 00:01 | dharper | Note Added: 0001537 | |
| 2004-10-26 14:54 | ericsean | Note Added: 0001538 | |
| 2004-11-08 23:03 | ericsean | Note Added: 0001576 | |
| 2004-11-10 14:48 | ericsean | Note Added: 0001587 | |
| 2004-11-16 11:59 | paul | Status | new => resolved |
| 2004-11-16 11:59 | paul | Resolution | open => fixed |
| 2004-11-16 11:59 | paul | Assigned To | => paul |
| 2004-11-16 11:59 | paul | Note Added: 0001612 | |
| 2008-11-20 23:38 | seablade | Status | resolved => closed |
