[Solved] Where's my reverb?

[ustk]

Hey guys,
I don't know what happened, I surely made a mistake sometimes, somewhere...

My Convolution reverb doesn't work anymore in some Hise built I've made.
I still have one version that is working (unfortunately it is a modified version so I can't use it for all the projects...)

It is just that I don't hear any reverb... But if I load the project in another built, it works!

I don't think the problem is Hise, because I've made two builds of the same commit, where one is working (the customized one), and the other doesn't (the standard built)...

So maybe a flag I disabled by mistake? any other idea?

[dustbro]

I've had the same thing happen. Haven't had a chance to investigate

[ustk]

@dustbro Thanks, is it working for you now?
I just built today's commit, same issue... That's weird, because the jucer project should be set by default...
Or is it computer-related?

[dustbro]

In my situation, it was working just fine on a compiled plugin.. and then after a week it stopped making sound. I just compiled a new version when that happened and it worked again. Waiting for the new version to fail again so I can troubleshoot.

[ustk]

@dustbro Woww that is even stranger... Let me compile so I can see if it does the same here...

[ustk]

Well, it doesn't work either when exported
@Christoph-Hart any idea on this hair-pulling issue?

[dustbro]

@ustk Do you have "embed audio files" selected in your HISE project settings?

[ustk]

Yep it is ticked, but since the problem happens directly in Hise, I'm not sure the audio file is related to the issue. The audio passes through the reverb module (the dry knob works) but is not treated by the IR

[d.healey]

@ustk Snippet...

[ustk]

@d-healey I'm not sure a snippet will help, I am just testing with a sine generator and a convolution module, so there's no code because I manually insert an IR for testing purpose.
This preset will work or not depending on the Hise build I open

What I could do is provide you with two Hise builds (a good and a bad one) so you can test them on a mac?

[d.healey]

@ustk I see. What is the difference between the two builds? No need to share them with me, without knowing the source code each came from I wouldn't be able to do much.

[ustk]

Ok, after some investigations, the only commit that works is the commit from the 19th July, all the commits I possess after this date don't work (28th, 2nd, and today's commit).
Does someone have one of these to test the convolution reverb, please?

[d.healey]

I don't see a commit from the 19th

[ustk]

What??? @Christoph-Hart didn't work on the 19th???

@d-healey oh sorry then, it is the 18th actually...
I have made many tests for hours, apparently, there had been several updates related to convolution in the source files since then
So I just need to know if it works for you guys after the 18th, so 23rd till today, so I'll be fixed if it is on my end or a bug in Hise

[ustk]

Side question: How do you download a previous commit? I tried but had an error instantly when building...

[d.healey]

[ustk]

Thanks, that's what I did back then, but it didn't work. Anyway, I just succeed in building a commit from 4th of July with the convolution working, so I think it is a recent bug in Hise... A commit from the 26th shows modifications of the convolution...
@Christoph-Hart Are you aware of that?

[Christoph Hart]

I rewrote the module so that I could reuse the convolution reverb as node in scriptnode but it might be possible that something old broke. What are the steps to reproduce? Just load any IR into it and play a sine wave through, and the wet signal is silent?

[ustk]

@Christoph-Hart Yep just load an IR with with any sound module, the signal is not affected by the IR
The dry signal is passing through

[Christoph Hart]

Here's your reverb

https://github.com/christophhart/HISE/commit/a17b1074ef59bc9fd8d08e629537b226505dbde2