Convolution Reverb glitch/timing Bug.

[lalalandsynth]

Using the convolution reverb in Reaper.
When I start playback right at the start of a sound I get an artifact , some kind of glitch that is not there when I start playback a bit farther back and before the sound starts.

Also, my reverb seems to start before the actual sound ? EDIT: That seems to have changed in my last test , see bottom of post.

For reference here is the piano sound used
Dry:[audio/6EnBBW46vpVNpHjbE93qghFv.wav]

Played from start of sound and includes glitch:[audio/9z6hkoQKo3cN6r07HgvVz6at.wav]

Played at least 170 ms from start of sound and sounds fine.[audio/ZMUaobmhX21PSWflnXVfrJci.wav]:

Probably related....

For testing purposes I placed a small file "46ms" and played that through the reverb.
If I place the cursor right at the beginning of the item and start playback there is no reverb, I have to place the cursor about 170ms earlier to hear it go through the reverb. Any earlier than that and its like the Reverb does not "catch it"

My assumption is that for some reason the Convolution is ahead of the daw by at least 170 ms or something , therefore causing all issues.

1. Glitch when starting at start of sound.
2. Not catching a sound if playback starts close then 170 ms.
3. Audio/Reverb is ahead of the audio.

EDIT: I did another test and now the audio/reverb is not ahead of the sound but the glitch is there ?

[lalalandsynth]

Another test , using the Convolution module (rather then the scriptnode) as it seems to me that they have the same issues. That is, when play cursor is placed close to the audio and playback starts, the convolution seems to miss the initial portion of the audio.

When using the new DAW style timeline in HISE, placing a tiny audio snippet on the timeline, placing the playback cursor at the start of audio and starting playback, there is no issue.

To test in a DAW ( using the provided dll)
Make a tiny snippet of audio, place it on the timeline, start playback at the start of audio.
The convolution reverb will not "catch" the audio.

Then move your playback cursor at least 170ms before the sound starts and start playback.
Now the sound goes through the convolution reverb.

So the result seems to me like when you have a normal sound "vocal/pad" and start playback ,the initial sound comes out dry (or something ?)and then the reverb starts working. I might be wrong on the specifics of what is failing but that is what it sounds like.

Here is an Win dll for testing, click to download

Here is the snippet , super simple convolution.

HiseSnippet 1235.3oc2X0saaTDEd1DuPSJT0VUp3x8BtHUpDYSSKn1KhS7OIFxOV1tMsRQpZxtGaOjcmYY1YSpEBtlGCdTr3I.ItkGh7F.mYW+yrgMAioMjhuHRyYlyNemuyuSZJEtPTjPRrVpyfPfX8Q1sGvU8qzmx3jFU0BpPUt8cTPjhr4fPZTD3QrrVbK8IrVp.I42YquI0mxcgohHjWHXtvNr.lZpzlk+FluecpGzgEXb50J2vUvqH7EwHZVztHIj5dLsGrGUerErIVePMOlRHaqnHXHVE1T3Mncewo7zy+BVD6HePunDoM9gREWW36oQrVJoReluWywVcDgXY2bJGrXJGbO6cYdrIxmxE2NYCmoZXxGVKjEdKlAdkLgWQC3kCjrLfTgTHcG61tRVnZ5NZ7bS6FbEH6RQZ2DJomkXMzth.O.WsZ.8XntDWLQgUdRwhOzA+yCdV2XtqhI3NB9dBErOekGr72u7RK+CK6b9s51M28zWiT36Cxb2V6okWlhqviCNBjOz4DpeLL4fn4mkSsuXN0zk6lZ0FGTvavYp8CA9EEHPFQUZ9eDpvHNUB6+IiX+Mh8XhCnm.cEx.BC456m2NkHIlgYlfGUQIVOyt9SOrEL33uEOo7Hmud6scVyPvgIel5LeH5vhO5.gv6TF2a2UOkdBQR48.jGjne01R+MSjTi6oW+6+HdUOuQU80Lx.PaAsuPPpXZpypJbBlMlFNsjcUH5XkHL4rAgBt1xs9v4zbeyTSsS4ASWzn7oLOU+IBFdZ49.qW+okCFdT4vwNgFd5qFg9IB+3j3iVflUPu0eMg.SEEdw9TU17ScQoQafefLIE5HedDSMvrn0asj1YEh2wtICKmlOFWHGLhty2EXbTotO1tV2tfqZJ.KXW+kuipqsfw8eiIsaXAg9vViu9aMRfiVRoKpgyO+KO9oCqB9zLD0AYB1HupbNsjZvwPJUSgOUddZdwY1NKc41YgYNVPaRNWqiWuqcBMecGjIt9q2f711Mo+W4raIvBp7d6RURFVr1du3f13bVt.BONG70sVsVP2DLccww8XZCbujE+A9azlkzqsFsYowaZRC2cbwEih4IbP9k2MIhpxAYGr7UCO.Tlo93HHC2AIDtalz2FAgw9QvN.umYQfyVeDtZvCiUlxedDrINgYOoHl60ouDndleulRv67EX1lUw3a7S+V4pzfPjWMOS85cF0icjn6UV2POcJ1+MC.DnofTuR.8Mia56KDgYlJPKvXnf2ZU0tpigtUJKdSre.GRdSRRDz8SV6nm8vYKfCRcRVoK4gI+5r9vjvY9gI66pvquCN+UTnHJyGtMDv5fSSEYJDizpKguqkNs2TdEAUl6VmsdczHyUm1TUrLo9wFAXfq5x5fUX170+MOPpv0tGH8dv3fYdC2RiwX5nM0vQP7wAymzesKM1WMVZ1X4cEbQXeAm4Z5naAXNXudfzD64ZPanTXMNyhQs.efZFz9Yk2AC1nRjmf4jKJ8O98r45u9T6T35nS.cd+cL9E+e8X7WIMBtJti.pqT7Z2z25qiSuQhDzt4IMqWxdW8ZmIOm21t3pEw9vdrW65po3OuDgjuNewbnyilCcVaNz4wygNOYNz4KmCc9pKUGcykMhUhfzTNTPyZI+KOrrpwoXzaRjN4OADPVNR.

[lalalandsynth]

Any chance of addressing this or verify, although I am 99% sure this is a bug.

[Dan Korneff]

@lalalandsynth I'm using a test file that is 8 samples long.

In Cubase, I'm not seeing any issues using online or offline rendering.

In Reaper, I see an unexpected result when using offline rendering, but online rendering works properly.

[Dan Korneff]

With larger files, it seems to render completely, but offline rendering contains a little glitch at the beginning.

This only affect audio when the rendering start point is directly at the beginning of an audio source. Starting offline bouncing a couple ms before audio will export properly.

[ustk]

@Dan-Korneff @lalalandsynth If audio is spitted out prior it comes in, it looks like a buffer is somehow not emptied properly in the DSP...
This might also explain that a pre-roll cleans the buffer in time before audio is coming again...
@Christoph-Hart ?

[lalalandsynth]

Any chance of getting this fixed, would rather not release a plugin with this issue.

[rzrsharpeprod]

@lalalandsynth did you ever resolve this as I am encountering this issue at the moment.
It is quite noticeable in DAW (FL in this case) and puts me off using the reverb which is a shame as it is a flexible option to have.

[lalalandsynth]

@rzrsharpeprod No, sorry.
I am assuming this has to be fixed, have not found a workaround.

[paper_lung]

Was this ever fixed?

[Adam_G]

bump bump :D