ReaFir transient smearing issue
|
06-13-2009 02:05 PM
|
Human being with feelings
|
|
ReaFir transient smearing issue
The issue from http://forum.cockos.com/showthread.php?t=25258 was fixed sometime ago. But obviously ReaFir is still "eating" transients in the following case:
1. You have more than 1 instance of ReaFir on the same track
AND
2. The track is record-armed
Example: (44.0kB)
-> load it
-> playback
=> Smeared transient on playback start
-> stop playback
-> remove two ReaFir instances OR un-arm the track
-> playback
=> Fine
|
|
Issue Details
|
Project
Deprecated REAPER issue tracker
Category Plugins
Status Not a Reaper Bug
Priority 10 - Lowest
Affected Version 3.02
Closed Version (none)
Yes votes
0
No votes
0
Assigned Users
(none)
Tags
(none)
|
|
06-13-2009 09:55 PM
|
|
Administrator
|
|
|
I've downloading your project and duplicated what you found (I hear the smearing).
HOWEVER, this is not a problem in ReaFIR. What's happening:
Since the multiple ReaFir instances requires a fair amount of initial rendering, and because the track is record armed (preventing any anticipative render-ahead from happening), there's a slight audio dropout (possibly right after the first frame plays -- I haven't tested this to determine exactly when it is). So basically the audio system is disrupted for a quick bit.
If you try setting a higher ASIO blocksize, or (to rule out blocksize-specific bugs) KS with 32 128-sample buffers, you'll find the playback plays correctly. You'll also find that if you put that sample on a different track it will get disrupted..
(other tests I did included doing inversion against the sample on another non-reafir track, as well as saving live output to disk and watching that come through perfect).
Anyway, this could probably be handled better (I know that a non-monitoring track should someday allow anticipative rendering, too), but this bug isn't a bug...
|
|
All times are GMT -7. The time now is 12:03 PM.