-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sparta Binuralizer crashes in adobe audition 2020. #81
Comments
I have found that it does work in Reaper fine. |
Hey, thanks for letting me know! I've now made sure that the host samplerate has a default value. This is not an issue for e.g. REAPER, due to the order in which the functions are called, but perhaps other hosts might call things differently, which I can see causing issues... This (potential) fix will be in the next release. |
I have an answer for the samplerate support query here: #67 (comment) |
The OS is windows 10, I don't know if anybody would seriously call Adobe Audition a DAW, I'll try to find the crash logs. Mostly I just want to play around with some of my old multichannel audio recordings at this point see how the specialization sounds. |
Ok. I'm not sure if this is just because I'm still running a Trial of reaper (it inserts silence at the beginning of mixdown), but the samples I generated are definitely low passed for 48kHz info. I don't know if that's baked into the 48kHz Head Transfer Function? |
I have a bunch of old multichannel audio recordings I would like to try to listen to using some of the more modern stereo headphone spatializer techniques.
When I try loading the binuralizer plugin says Resampling the HRIR's. Shows middling cpu activity on a few of my cores then eventually crashes. This is pretty odd behavior for a VST plugin.
I thought it might be because I was trying to load it on 88kHz sample rate wav files, but I also tried it on 48Khz wav files to the same result.
Any idea if there is a fix, the entire program is essentially non responsive as soon as I load the plugin.
Also why not support higher sample rates?
The text was updated successfully, but these errors were encountered: