View Issue Details

IDProjectCategoryView StatusLast Update
0001131ardourbugspublic2020-04-19 20:12
Reportermarukqs Assigned Toseablade  
PrioritynormalSeveritymajorReproducibilitysometimes
Status closedResolutionfixed 
Product Version0.99 
Summary0001131: No sound after opening
DescriptionSometimes there is no sound in ardour. It appears just after opening the song. Auditioning in regionlist works well - so the problem is not the soundcard's, but in the mixer signal handling.

To temporary resolve this problem (to make ardour play the song) sometimes it is needed to find which LADSPA plugin 'kills' the output by disabling all the LADSPA plugins in the song step-by-step and putting playback cursor to various places of the song and clicking PLAY and STOP buttons multiple times until the sound appears. When the song is opened the next time the problem can be with another random track and LADSPA plugin. Changing parameters of the 'faulty' LADSPA plugin does not help - the plugin needs to be deleted and then inserted again.

This behaviour was detected with various plugins: TAP Reverberator, Multivoice chorus, TAP Equalizer, TAP Dynamics and Simple Compressor. It is possible that "digital overload" of the amplitude on a single mixer stripe can disable the sound on entire ardour's master output for all the playback time, until this 'digital overload' is not killed.

This behaviour was not detected in previous versions of ardour.
This problem appears in the songs created in ardour 0.99.
TagsNo tags attached.

Relationships

duplicate of 0001129 closedseablade LADSPA plugins break outputs 

Activities

perkins

2005-11-29 01:58

reporter   ~0002389

As per a note I just added to 1129, suggest you try adding a plugin, then removing it, and see if that helps it to make some noise...?

seablade

2008-12-03 20:10

manager   ~0005483

As per the duplicate bug, this appears to be fixed in the 2.x branch of Ardour and as the last comment there was one indicating resolution, and there has been no activity on either report in years, I am going to go ahead and resolve this bug.

     Seablade

system

2020-04-19 20:12

developer   ~0021471

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
2005-10-22 07:17 marukqs New Issue
2005-11-20 20:44 v2 Relationship added duplicate of 0001129
2005-11-29 01:58 perkins Note Added: 0002389
2008-12-03 20:10 seablade cost => 0.00
2008-12-03 20:10 seablade Status new => resolved
2008-12-03 20:10 seablade Resolution open => fixed
2008-12-03 20:10 seablade Assigned To => seablade
2008-12-03 20:10 seablade Note Added: 0005483
2020-04-19 20:12 system Note Added: 0021471
2020-04-19 20:12 system Status resolved => closed