View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001685 | ardour | bugs | public | 2007-05-17 09:43 | 2020-04-19 20:12 |
Reporter | SaBer | Assigned To | SaBer | ||
Priority | normal | Severity | major | Reproducibility | random |
Status | closed | Resolution | fixed | ||
Product Version | 2.0 | ||||
Summary | 0001685: An audible click (noise) is produced at end of loop range | ||||
Description | An audible click is produced at end of loop range even in normal playback mode. This doesn't always happen, but once you get it to happen in a session, it will be reproducible until you close the session.Only happens if there is a sound playing at that point (i.e. if everything is quiet, you won't get a click). | ||||
Tags | No tags attached. | ||||
2007-05-21 20:36
|
|
|
I uploaded a session file for duplicating this (drums5.ardour) Steps to duplicate: 1. open session 2. move loop end marker to a position with sound 3. play across the marker The quality of the click depends completely on the underlying audio. In quiet places the click is soft and quiet and in loud places sharp and loud. |
|
Can't open your drums5.ardour, don't know if that's normal: ardour: [ERROR]: Unable to create all required ports I can't seem to reproduce this unless I add plugins to a track. In particular, if I add CAPS JVRev (Stanford reverb), it produces a huge pop at the end of the loop range, and due to the reverb it's much easier to notice it. Can you reproduce the bug with all plugins disabled? If not, a plugin might be trying to do 'control parameter smoothing' but using uninitialised values on the first run each loop (does anyone know if that's right?). |
|
OUCH!! Ever wondered what 600dB sounds like through headphones? Obviously my sound card wasn't quite be able to produce a sound that loud, but it sure as hell tried. The sound it put out was so loud that after clicking stop I continued to hear an unexplained grinding/droning noise at full volume for several seconds afterward... I really thought my mixer (or my head) was going to blow up. This bug hit me just now, I didn't notice anything until I'd added a lot of plugins. But now after being able to reproduce it, I tried disabling, and then entirely removing the plugins from all channels and it continues to produce an incredibly loud pop each loop around, of about 609.6 to 618.3dB on any channel with its fader set above -inf. The exception to this is, I am looping some a pre-recorded audio (not captured during this session) on a stereo track, and that's completely unaffected by this. If I delete the captured audio from any of the affected channels, the pop stops happening on that channel. If I create any new, blank mono tracks, they do not pop. If I drag regions from one of the popping tracks to this new track, the audio plays without a pop, and the original track (now empty) no longer pops. If I drag it back, the original track starts popping again. |
|
same here. i have this issue with fons' REV plugin (which creates a very audible reverb tail from the original pop). i tried putting a dc offset remover and a lowpass before it (sprinkling some fairy dust to rule out denormal issues), but the problem stays. weird thing is i can mute every single channel that feeds my reverb bus, and it still happens. quite a showstopper for me atm. i'm using 2.4.1 and updating to current svn as i'm typing this. |
|
btw, i suggest raising this issue to at least "major". |
|
i've just upgraded to current svn (3518). at the same time, i've also upgraded to a new rt kernel and to current jackmp svn (used to use jackd-1 before). so far, i could not reproduce the problem. UPDATE: it's back. but now that i know it's related to the loop marker, i can work around the issue by setting the loop start and end points to the start and end of the session, so that the noise is outside of the audio material... |
|
I did some debugging, and the diagnose is that plugins do not get processed for some time after the loop end. e.g. adding an amplifier with zero gain to the track and recording the track output reveals some of the signal getting through to the track being recorded on. |
|
Resolved in 4979 (which probably introduced other bugs) |
|
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. |
Date Modified | Username | Field | Change |
---|---|---|---|
2007-05-17 09:43 | SaBer | New Issue | |
2007-05-21 20:36 | SaBer | File Added: drums5.ardour | |
2007-05-21 20:40 | SaBer | Note Added: 0004007 | |
2007-07-28 13:52 | StevenChamberlain | Note Added: 0004201 | |
2007-07-28 16:32 | StevenChamberlain | Note Added: 0004202 | |
2008-07-07 20:11 | nettings | Note Added: 0005093 | |
2008-07-07 20:12 | nettings | Note Added: 0005094 | |
2008-07-09 12:05 | nettings | Note Added: 0005103 | |
2008-07-10 12:26 | nettings | Note Edited: 0005103 | |
2009-04-10 08:33 | SaBer | cost | => 0.00 |
2009-04-10 08:33 | SaBer | Severity | minor => major |
2009-04-10 09:29 | SaBer | Note Added: 0005878 | |
2009-04-27 20:31 | SaBer | Note Added: 0005913 | |
2009-04-27 20:31 | SaBer | Status | new => resolved |
2009-04-27 20:31 | SaBer | Resolution | open => fixed |
2009-04-27 20:31 | SaBer | Assigned To | => SaBer |
2020-04-19 20:12 | system | Note Added: 0021523 | |
2020-04-19 20:12 | system | Status | resolved => closed |