Issue with Grainspace 2 in FL20
-
- KVRer
- Topic Starter
- 3 posts since 10 Oct, 2018
The plugin manager keeps classifying Grainspace as a synth instrument and not as an effect, so when I try to use it in my mixer, it loads into a channel rack instead, I get error an message, and the plugin's unable to receive audio. I've tried several solutions suggested by Image Line's sources to no avail, but I intend to get around to sending them a more detailed message the about this issue.
In the meantime, I'd appreciate any help you can offer.
In the meantime, I'd appreciate any help you can offer.
- KVRian
- 1337 posts since 15 Nov, 2005 from Italy
Hi,
GrainSpace is built as an effect and it's very strange FL Studio is loading it as an instrument. What GrainSpace version are you running?
Thanks,
Luca
GrainSpace is built as an effect and it's very strange FL Studio is loading it as an instrument. What GrainSpace version are you running?
Thanks,
Luca
-
- KVRer
- Topic Starter
- 3 posts since 10 Oct, 2018
An update:
The issue has something to do with the vst3 file; I removed it, rescanned with fl20's plugin manager, and now the 64 bit vst file works as it should
The issue has something to do with the vst3 file; I removed it, rescanned with fl20's plugin manager, and now the 64 bit vst file works as it should
-
- KVRer
- 1 posts since 28 May, 2022
Audiority, can you please address this? I am having this same issue almost 2 years later (and there are a lot of FL studio users out there). If the VST3 file is having this issue, this should be looked into and fixed.
Thank you!
Thank you!
- KVRian
- 1337 posts since 15 Nov, 2005 from Italy
We got in touch with Image Line and they told me that was fixed with the latest version of FL Studio months ago.
This issue is not related to our plugin, but to their DAW and the way they classify plugins. If that's still happening with the latest version of FL Studio, please post here some screenshots (including FL Studio version) so we can forward that to Image Line developers again.
Luca
This issue is not related to our plugin, but to their DAW and the way they classify plugins. If that's still happening with the latest version of FL Studio, please post here some screenshots (including FL Studio version) so we can forward that to Image Line developers again.
Luca
You do not have the required permissions to view the files attached to this post.
-
- KVRAF
- 3089 posts since 4 May, 2012
Indeed. I had this issue with all plugins in FL Studio being detected as instruments.
Not a problem though: Just switch them to "effect" manually and hit "apply".
Not a problem though: Just switch them to "effect" manually and hit "apply".
-
- KVRist
- 76 posts since 3 May, 2021
I cant change it manually. Its blackout.
I hope next release of FL will fix it.
I hope next release of FL will fix it.