Thank you, NumanoidNumanoid wrote:I doubt RP effects can be loaded into, at least as of yet.
Rob Papen Prisma
-
- KVRAF
- 7045 posts since 28 Apr, 2004 from france
- KVRAF
- 44222 posts since 11 Aug, 2008 from clown world
I haven't even tried it yet but that sounds like a sensible idea.Karma_tba wrote:... If they would make it so you could pick a different folder for 32 than 64 it would be perfection.
This is the same method MJ used when he was working on Anthony Marinelli's Thriller.
- KVRAF
- 37536 posts since 14 Sep, 2002 from In teh net
I presume it just supports RP synths so why not just make a separate folder for RP synths (32 and 64 bit) and either copy them in or even create symlinks to them, then point Prisma to that?Karma_tba wrote:I absolutely love Prism!! Props to Rob Papen for offering this for free. I only have one gripe, but the issue is of my own making. I segregate my plugins...I have a 64 bit folder and a 32 bit folder. Prisma is set up to read all plugins from one VST folder regardless of 32 or 64 bit. So even though it installs both versions whichever folder I pick becomes the default for both. If they would make it so you could pick a different folder for 32 than 64 it would be perfection. Believe it or not I thought everyone had separate folders for 32 and 64. Since I don't feel like having to change horses in the middle of the stream I'll just use Prism for one or the other. I don't expect the dev to change things for me especially since I'm probably in the minority. Still....great plugin!!!
- KVRian
- 1268 posts since 12 Aug, 2004
Impeccable logic...but I am just so lazy. Every time I load an old project I would have deal with redirecting the DAW to the new location. I have other plugins that my DAWs only like the 64bit version so this will make me move more stuff into that environment. I am so reluctant to leave 32 bit...it's silly but there's a lot of nice 32 bit especially now because the devs pushing 64. So much 32 bit stuff is being set free and I'm a cheap/poor bastard.aMUSEd wrote:I presume it just supports RP synths so why not just make a separate folder for RP synths (32 and 64 bit) and either copy them in or even create symlinks to them, then point Prisma to that?Karma_tba wrote:I absolutely love Prism!! Props to Rob Papen for offering this for free. I only have one gripe, but the issue is of my own making. I segregate my plugins...I have a 64 bit folder and a 32 bit folder. Prisma is set up to read all plugins from one VST folder regardless of 32 or 64 bit. So even though it installs both versions whichever folder I pick becomes the default for both. If they would make it so you could pick a different folder for 32 than 64 it would be perfection. Believe it or not I thought everyone had separate folders for 32 and 64. Since I don't feel like having to change horses in the middle of the stream I'll just use Prism for one or the other. I don't expect the dev to change things for me especially since I'm probably in the minority. Still....great plugin!!!
- KVRAF
- 37536 posts since 14 Sep, 2002 from In teh net
Why would you need to redirect anything? It's just the path in Prisma you would need to change to the new folder - once. Doesn't change anything for your DAW.Karma_tba wrote:Impeccable logic...but I am just so lazy. Every time I load an old project I would have deal with redirecting the DAW to the new location. I have other plugins that my DAWs only like the 64bit version so this will make me move more stuff into that environment. I am so reluctant to leave 32 bit...it's silly but there's a lot of nice 32 bit especially now because the devs pushing 64. So much 32 bit stuff is being set free and I'm a cheap/poor bastard.aMUSEd wrote:I presume it just supports RP synths so why not just make a separate folder for RP synths (32 and 64 bit) and either copy them in or even create symlinks to them, then point Prisma to that?Karma_tba wrote:I absolutely love Prism!! Props to Rob Papen for offering this for free. I only have one gripe, but the issue is of my own making. I segregate my plugins...I have a 64 bit folder and a 32 bit folder. Prisma is set up to read all plugins from one VST folder regardless of 32 or 64 bit. So even though it installs both versions whichever folder I pick becomes the default for both. If they would make it so you could pick a different folder for 32 than 64 it would be perfection. Believe it or not I thought everyone had separate folders for 32 and 64. Since I don't feel like having to change horses in the middle of the stream I'll just use Prism for one or the other. I don't expect the dev to change things for me especially since I'm probably in the minority. Still....great plugin!!!
- KVRian
- 1268 posts since 12 Aug, 2004
Unfortunately whatever folder you set in one version of Prisma it sets both to that. So if you chose 64bit when you load 32 it's set for 64 and vice versa.aMUSEd wrote:Why would you need to redirect anything? It's just the path in Prisma you would need to change to the new folder - once. Doesn't change anything for your DAW.Karma_tba wrote:Impeccable logic...but I am just so lazy. Every time I load an old project I would have deal with redirecting the DAW to the new location. I have other plugins that my DAWs only like the 64bit version so this will make me move more stuff into that environment. I am so reluctant to leave 32 bit...it's silly but there's a lot of nice 32 bit especially now because the devs pushing 64. So much 32 bit stuff is being set free and I'm a cheap/poor bastard.aMUSEd wrote:I presume it just supports RP synths so why not just make a separate folder for RP synths (32 and 64 bit) and either copy them in or even create symlinks to them, then point Prisma to that?Karma_tba wrote:I absolutely love Prism!! Props to Rob Papen for offering this for free. I only have one gripe, but the issue is of my own making. I segregate my plugins...I have a 64 bit folder and a 32 bit folder. Prisma is set up to read all plugins from one VST folder regardless of 32 or 64 bit. So even though it installs both versions whichever folder I pick becomes the default for both. If they would make it so you could pick a different folder for 32 than 64 it would be perfection. Believe it or not I thought everyone had separate folders for 32 and 64. Since I don't feel like having to change horses in the middle of the stream I'll just use Prism for one or the other. I don't expect the dev to change things for me especially since I'm probably in the minority. Still....great plugin!!!
- KVRAF
- 37536 posts since 14 Sep, 2002 from In teh net
Yes but I'm saying make a separate folder just for Prisma and copy your 64 and 32 bit RP plugins into it (or symlinks to them might work just as well). So no need to switch anything.Karma_tba wrote:Unfortunately whatever folder you set in one version of Prisma it sets both to that. So if you chose 64bit when you load 32 it's set for 64 and vice versa.aMUSEd wrote:Why would you need to redirect anything? It's just the path in Prisma you would need to change to the new folder - once. Doesn't change anything for your DAW.Karma_tba wrote:Impeccable logic...but I am just so lazy. Every time I load an old project I would have deal with redirecting the DAW to the new location. I have other plugins that my DAWs only like the 64bit version so this will make me move more stuff into that environment. I am so reluctant to leave 32 bit...it's silly but there's a lot of nice 32 bit especially now because the devs pushing 64. So much 32 bit stuff is being set free and I'm a cheap/poor bastard.aMUSEd wrote:I presume it just supports RP synths so why not just make a separate folder for RP synths (32 and 64 bit) and either copy them in or even create symlinks to them, then point Prisma to that?Karma_tba wrote:I absolutely love Prism!! Props to Rob Papen for offering this for free. I only have one gripe, but the issue is of my own making. I segregate my plugins...I have a 64 bit folder and a 32 bit folder. Prisma is set up to read all plugins from one VST folder regardless of 32 or 64 bit. So even though it installs both versions whichever folder I pick becomes the default for both. If they would make it so you could pick a different folder for 32 than 64 it would be perfection. Believe it or not I thought everyone had separate folders for 32 and 64. Since I don't feel like having to change horses in the middle of the stream I'll just use Prism for one or the other. I don't expect the dev to change things for me especially since I'm probably in the minority. Still....great plugin!!!
- KVRian
- 1268 posts since 12 Aug, 2004
I see. BTW what is a symlink?aMUSEd wrote:Yes but I'm saying make a separate folder just for Prisma and copy your 64 and 32 bit RP plugins into it (or symlinks to them might work just as well). So no need to switch anything.Karma_tba wrote:Unfortunately whatever folder you set in one version of Prisma it sets both to that. So if you chose 64bit when you load 32 it's set for 64 and vice versa.aMUSEd wrote:Why would you need to redirect anything? It's just the path in Prisma you would need to change to the new folder - once. Doesn't change anything for your DAW.Karma_tba wrote:Impeccable logic...but I am just so lazy. Every time I load an old project I would have deal with redirecting the DAW to the new location. I have other plugins that my DAWs only like the 64bit version so this will make me move more stuff into that environment. I am so reluctant to leave 32 bit...it's silly but there's a lot of nice 32 bit especially now because the devs pushing 64. So much 32 bit stuff is being set free and I'm a cheap/poor bastard.aMUSEd wrote:I presume it just supports RP synths so why not just make a separate folder for RP synths (32 and 64 bit) and either copy them in or even create symlinks to them, then point Prisma to that?Karma_tba wrote:I absolutely love Prism!! Props to Rob Papen for offering this for free. I only have one gripe, but the issue is of my own making. I segregate my plugins...I have a 64 bit folder and a 32 bit folder. Prisma is set up to read all plugins from one VST folder regardless of 32 or 64 bit. So even though it installs both versions whichever folder I pick becomes the default for both. If they would make it so you could pick a different folder for 32 than 64 it would be perfection. Believe it or not I thought everyone had separate folders for 32 and 64. Since I don't feel like having to change horses in the middle of the stream I'll just use Prism for one or the other. I don't expect the dev to change things for me especially since I'm probably in the minority. Still....great plugin!!!
- KVRAF
- 37536 posts since 14 Sep, 2002 from In teh net
Like a shortcut or alias but most hosts can follow them whereas only a couple of hosts can follow shortcuts (Live mainly) - are you on Windows on Mac? There are various kinds but on Mac I find softlinks work fine for most plugins/hosts.
http://www.howtogeek.com/howto/16226/co ... -or-linux/
http://www.howtogeek.com/howto/16226/co ... -or-linux/
- KVRian
- 1268 posts since 12 Aug, 2004
Ok I understand....thank you I will try it. At the very least creating a Prisma folder seems to be the solution. Oh yeah!!! the fun begins!!aMUSEd wrote:Like a shortcut or alias but most hosts can follow them whereas only a couple of hosts can follow shortcuts (Live mainly) - are you on Windows on Mac? There are various kinds but on Mac I find softlinks work fine for most plugins/hosts.
http://www.howtogeek.com/howto/16226/co ... -or-linux/
-
- KVRist
- 274 posts since 27 May, 2013 from Leesburg, VA
created new folder just for Rob Papen plug "links", but -
shortcuts, symlinks (using Link Shell extension referred to above), even hard links using that same program, for the .dll files themselves are not recognized by Prisma for me on FL Studio 12 Win 7 64-bit. Also tried shortcut/symlink of the folder containing the .dll file, still no dice also.
Shame, want to try this; I keep each of my VSTis in a folder named by the plugin so there is no common folder at this level for me.
[edit] using the Link Shell extension, and "drop as..." -> "hardlink clone" of the dir containing the *.dll, does work! hallelujah.
also found that "symbolic link clone" works as well, so I'll probably be using symbolic link clones instead.
shortcuts, symlinks (using Link Shell extension referred to above), even hard links using that same program, for the .dll files themselves are not recognized by Prisma for me on FL Studio 12 Win 7 64-bit. Also tried shortcut/symlink of the folder containing the .dll file, still no dice also.
Shame, want to try this; I keep each of my VSTis in a folder named by the plugin so there is no common folder at this level for me.
[edit] using the Link Shell extension, and "drop as..." -> "hardlink clone" of the dir containing the *.dll, does work! hallelujah.
also found that "symbolic link clone" works as well, so I'll probably be using symbolic link clones instead.
Last edited by synzh on Fri Jun 03, 2016 4:16 am, edited 2 times in total.
- KVRAF
- 7873 posts since 21 Dec, 2002 from MD USA
only thing I don't like so far is the slow load times for patches
my music: http://www.alexcooperusa.com
"It's hard to be humble, when you're as great as I am." Muhammad Ali
"It's hard to be humble, when you're as great as I am." Muhammad Ali
- KVRAF
- 37536 posts since 14 Sep, 2002 from In teh net
You need to remove any symlink extensions that may get added - ie the file must appear to the host as a plugin so on windows plugin.dll symlink should just be plugin.dll, on Mac plugin.vst symlink should be plugin.vst. Ordinary shortcuts/aliases only work for Live (and a couple of minor hosts) but on Mac at least symlinks work for all hosts I've tried if you remove the extension and for all plugins except those that are symlinks already (eg Reaktor fx).synzh wrote:created new folder just for Rob Papen plug "links", but -
shortcuts, symlinks (using Link Shell extension referred to above), even hard links using that same program, for the .dll files themselves are not recognized by Prisma for me on FL Studio 12 Win 7 64-bit. Also tried shortcut/symlink of the folder containing the .dll file, still no dice also.
Shame, want to try this; I keep each of my VSTis in a folder named by the plugin so there is no common folder at this level for me.
-
- KVRian
- 568 posts since 2 Jan, 2004
A quick update on this ....MikeCallon wrote:Is anybody else getting 'empty' Bank dropdown lists for every instrument ? The Presets are populated but Bank is empty - is there somewhere to configure this or is it a bug ? I can open each instrument and change the bank from there but shouldn't the Bank list in Prisma be populated the same way as the list in the plugin ?
When I installed the individual instruments I was given a choice of location for the data (banks, presets etc) and I chose a 'non-system' drive as I have a smallish SSD as my system drive. The instruments themselves work fine with this non-system drive location. However it looks like Prisma is 'hard coded' to use the My Documents folder. If I copy the files from my non-system drive to My Documents the Banks list is correctly populated in Prisma.
Surely Prisma should read the location of the banks from the individual instruments? - I have the option when installing Prisma to save the Prisma presets in a specific location (again I chose a non-system drive) and Prisma reads this location fine, but will not read the Banks for the individual instruments from the same location !
I've submitted a support request - hopefully a fix for this can be included in the next release.
- KVRAF
- 25849 posts since 20 Jan, 2008 from a star near where you are
What is your system specs, do you use SSD hardrive?ATS wrote:only thing I don't like so far is the slow load times for patches
