Audio glitches on IRs (Hise 2.0)
-
@Christoph-Hart Same thing. Also Projucer app bundled is not opening, I just used 5.4.3 build 22 Mar 2019
- pulled changes
- opened project with projucer 5.4.3
- Save and open IDE
- Build Failed
-
@Christoph-Hart WAIT!!! Just trashed the git folder and downloaded a fresh .zip and is compiling.... updating in minutes
-
Opened Hise and played a bunch of notes on a sinewave with mouse, and got hanging notes. Also Midi is not working. I see keys being pressed on onscreen keyboard but no sound. changed hise output a couple of times, but same thing.
-
Hmm, I got no hanging notes - can you do something to reproduce it consistently? MIDI is also working - and if the keys on the screen are pressed if you play notes on your hardware keyboard, MIDI is working, but the sound generation isn't.
-
@Christoph-Hart will record a video as soon as I get home. I just pressed down the mouse a moved left and right over the onscreen kb from C0 to C7 aprox, like 3 or 4 times. Just a sinewave there. Then start the hanging
-
@Christoph-Hart here you go
https://youtu.be/KgOGjcZ-suAOn MacOs 10.11.8
Compiling nicely on Hise 2.0 from 7 Feb 2019 -
Btw a nice post about how to create IRs
-
BTW, I got the hanging notes also with the 2.0.0 version but I thought it was just a glitch on my macbook. It happens only in the optimised build though, in the Debug build it doesn't produce hanging notes. This is fun.
-
@Christoph-Hart on 2.0.0 same test and no hanging notes :0 im a bit confused.
Keep in mind I'm on a 2009 Macbook pro. I think I will try a not ipp hise to see what's happen regarding IRs
-
Alright, please try again, there was a uninitialised value that caused both issues.
-
@Christoph-Hart awesome!!!! Thanks. Will try it this afternoon!
-
@Christoph-Hart Everything is working!!!!!!!!!!!!!!! Standalone Hise 2.1.0 ompiled OK, switched to Ooura and artifacts are gone!!!! (Apple optimized generates artifacts also)
What can I say..... you are a genius!
-
Ahh, good to know. I think the error is how the different FFT algorithms expect the data to be formatted, and they all expect a different first number in the array as the "zero frequency bin", which might explain why this happened only for very low frequencies.
If I have a few minutes to spare, I'll take a look whether this can be fixed properly, but for now we're good then :)
-
@Christoph-Hart Maybe is not noticeable on sample-based sounds. I'm doing some extreme things like stacking 100+ sinewaves and maybe that made it more obvious. But it's there!
Let me know if you need me to run some other test or whatever.
-
@Christoph-Hart almost finished!
