I have purchased EVE 2 and attempted to install it using the Unsupported method. When I attempt this by copying the EVE 2 dll into the Unsupported Plugins folder and checking the appropriate box so that Receptor "sees" the Unsupported directory and then trying to install, I continually get a failed install.
Does anyone know the details to this? I have seen some unsupported plugs fail installatiion when they cannot find a specific file (other than the DLL) or a specific subdirectory beneath the DLL location when attempting installation.
Any help would be appreciated.
Thank you!
Need help installing EVE 2
-
- KVRian
- 691 posts since 13 May, 2004 from Silicon Valley
Hi Todd,
Maybe you already know this, but perhaps you should check the system log file (in the Reports folder). It often will list linkage errors (ie. when a windows dll is not found).
Regards,
Kevin L
Maybe you already know this, but perhaps you should check the system log file (in the Reports folder). It often will list linkage errors (ie. when a windows dll is not found).
Regards,
Kevin L
-
- KVRist
- Topic Starter
- 64 posts since 31 Dec, 2006 from California
I received a response from Muse suggesting a clear of the Plugin Cache but this did not work. I spent 2 hours on this tonight and got nowhere.
On one occassion and one occassion only, I deleted the DLL and EVE Data directory, cleared the plugin cache but noticed that the restart was too quick - Receptor didn't sit at the "Loading..." message for more than 1-2 seconds. So I shut Receptor down and restarted. I then copied the DLL and EVE Data directory to the Unsupported directory and tried installing the plug and this one time only, a dialog box appeared asking the location of the EVE Data directory (which I pointed the dialog box to) and then the install failed anyway.
No other time did I even get the dialog asking for EVE Data.
I'm about ready to give up on EVE and purchase NI Elektrik Piano or LL3.
I've sent Muse my System Log also.
Any last minute ideas?
Thanks.
On one occassion and one occassion only, I deleted the DLL and EVE Data directory, cleared the plugin cache but noticed that the restart was too quick - Receptor didn't sit at the "Loading..." message for more than 1-2 seconds. So I shut Receptor down and restarted. I then copied the DLL and EVE Data directory to the Unsupported directory and tried installing the plug and this one time only, a dialog box appeared asking the location of the EVE Data directory (which I pointed the dialog box to) and then the install failed anyway.
No other time did I even get the dialog asking for EVE Data.
I'm about ready to give up on EVE and purchase NI Elektrik Piano or LL3.
I've sent Muse my System Log also.
Any last minute ideas?
Thanks.
"Better the pride that resides in a citizen of the world then the pride that divides when a colorful rag is unfurled." - N. Peart
-
- KVRian
- 691 posts since 13 May, 2004 from Silicon Valley
Hi Todd,
I am assuming that there were no other DLLs the install was asking for.
Perhaps you might wish to investigate from another angle. I believe EVE was one of the original plugs that MUSE gives when you first purchase Receptor.
I'm guessing that since Receptor already knows about 'EVE' (since there is an installer for it), that the plug has a 'sign' (eg. ID) that Receptor already knows about. I think there is code in Receptor's install process that makes it fail for plugs that it already knows the sign for.
For example, I had (GMedia) impOscar that I used to install via the 'Unsupported' method just fine. Muse followed with an OS update that recognized a (plugorama-supplied) installer for impOscar. My previously installed impOscar stopped working, and any unsupported install I tried to do after this failed. After some going back and forth with Muse, we realized this was a conflict with Receptor's signing rejecting the User Install.
The suspicion I have is that you are trying to (unsupported) install a vsti with an ID that the Receptor OS has already reserved.
You might also wish to talk with the EVE programmers to see if they intend to support EVE II on receptor (eg. create a new installer for EVE II). Also, you might wish to simply find other plugs that do what you wish to do in EVE (I have much overlap from other plugs, and almost never use EVE).
Hope this helps,
Kevin L
I am assuming that there were no other DLLs the install was asking for.
Perhaps you might wish to investigate from another angle. I believe EVE was one of the original plugs that MUSE gives when you first purchase Receptor.
I'm guessing that since Receptor already knows about 'EVE' (since there is an installer for it), that the plug has a 'sign' (eg. ID) that Receptor already knows about. I think there is code in Receptor's install process that makes it fail for plugs that it already knows the sign for.
For example, I had (GMedia) impOscar that I used to install via the 'Unsupported' method just fine. Muse followed with an OS update that recognized a (plugorama-supplied) installer for impOscar. My previously installed impOscar stopped working, and any unsupported install I tried to do after this failed. After some going back and forth with Muse, we realized this was a conflict with Receptor's signing rejecting the User Install.
The suspicion I have is that you are trying to (unsupported) install a vsti with an ID that the Receptor OS has already reserved.
You might also wish to talk with the EVE programmers to see if they intend to support EVE II on receptor (eg. create a new installer for EVE II). Also, you might wish to simply find other plugs that do what you wish to do in EVE (I have much overlap from other plugs, and almost never use EVE).
Hope this helps,
Kevin L
-
- KVRist
- Topic Starter
- 64 posts since 31 Dec, 2006 from California
Hi, Kevin. Thanks for the input. I have been working with Dash and they are working with Muse to support a Receptor version of EVE 2 but it hasn't materialized yet. Since EVE 1 was consistently locking up my Receptor, I uninstalled it. Would doing this remove any possibility that Receptor was rejecting my EVE 2 install because it saw EVE 1 already installed?
I have been in contact with Muse on this and as of now the only suggestion they have given me is to refresh the plugin cache (which did not solve the problem).
Last night I sent them my system log and I am hopeful that they will be able to determine why the install is failing.
When I was installing OP-X I had a few failed installs before it finally installed correctly. There was one missing/incorrect step that I was given and when I corrected it, things worked like a charm. No problems since.
Given my experience with OP-X and the fact that when I did certain things in a certain sequence EVE responded differently by asking for EVE Data subdirectory (delete the plugin from the Unsupported directory, clear the cache, reboot Receptor, etc...) I would bet that I am just doing things out of order or maybe missing a step. A guy named JV on this message board has EVE 2 working on Receptor.
My feeling is that Muse often gives me part of the answer (unintentionally, of course) and as a result I spend a bunch of time missing the target.
I hope I can get a clear and complete set of guidelines from them shortly. Your suspicion may very well turn out to be correct.
Thanks for your advice.
I have been in contact with Muse on this and as of now the only suggestion they have given me is to refresh the plugin cache (which did not solve the problem).
Last night I sent them my system log and I am hopeful that they will be able to determine why the install is failing.
When I was installing OP-X I had a few failed installs before it finally installed correctly. There was one missing/incorrect step that I was given and when I corrected it, things worked like a charm. No problems since.
Given my experience with OP-X and the fact that when I did certain things in a certain sequence EVE responded differently by asking for EVE Data subdirectory (delete the plugin from the Unsupported directory, clear the cache, reboot Receptor, etc...) I would bet that I am just doing things out of order or maybe missing a step. A guy named JV on this message board has EVE 2 working on Receptor.
My feeling is that Muse often gives me part of the answer (unintentionally, of course) and as a result I spend a bunch of time missing the target.
I hope I can get a clear and complete set of guidelines from them shortly. Your suspicion may very well turn out to be correct.
Thanks for your advice.
"Better the pride that resides in a citizen of the world then the pride that divides when a colorful rag is unfurled." - N. Peart
-
- KVRist
- Topic Starter
- 64 posts since 31 Dec, 2006 from California
I have been playing more and more with this install and your comment, "The suspicion I have is that you are trying to (unsupported) install a vsti with an ID that the Receptor OS has already reserved." I believe is correct.
Through multiple install attempts I was able to get EVE to ask me for the data directory. I mistakenly entered an incorrect one. Now, when I try to clear out the cache, Receptor does not let go of the fact that it thinks the data directory is where I incorrectly typed it!!
So, even though I can now get Receptor begin the instantiation of EVE, it no longer asks me for the data directory, it just assumes I want the old one (the incorrect one) and continues to fail.
I cannot get the reference to the EVE data directory removed from Receptor.
Any ideas on how I do that?
Through multiple install attempts I was able to get EVE to ask me for the data directory. I mistakenly entered an incorrect one. Now, when I try to clear out the cache, Receptor does not let go of the fact that it thinks the data directory is where I incorrectly typed it!!
So, even though I can now get Receptor begin the instantiation of EVE, it no longer asks me for the data directory, it just assumes I want the old one (the incorrect one) and continues to fail.
I cannot get the reference to the EVE data directory removed from Receptor.
Any ideas on how I do that?
"Better the pride that resides in a citizen of the world then the pride that divides when a colorful rag is unfurled." - N. Peart
-
- KVRian
- 691 posts since 13 May, 2004 from Silicon Valley
Hi Todd,
I would bet that this "stashed" version of the 'old' data directory is in a resource somewhere.
This is a 'Last alternative" thing to do, and you should only do this if you feel confident about changing registry entries. This is a kind of thing that programmers typically mess with, but is not recommended for typical users to do this.
I am suggesting here that you bring up the Registry editor, find the resources associated with EVE, and find the specific one that has a path to the Data dir. From this editor, you can directly change the path, and things should just work. The important thing is that you should not change anything else in the registry.
If you go to Ogg's instructions:
http://ogg.kicks-ass.net/receptor/
he describes how to enable your receptor to bring-up the Registry editor. From here, You would look for entries under the tree:
HKEY_LOCAL_MACHINE/SOFTWARE
(you would probably find entries either under the name EVE or DashSignature).
This isn't very hard to do, but you could really screw-up your machine if you change entries you shouldn't.
Hope this helps. Regards,
Kevin L
I would bet that this "stashed" version of the 'old' data directory is in a resource somewhere.
This is a 'Last alternative" thing to do, and you should only do this if you feel confident about changing registry entries. This is a kind of thing that programmers typically mess with, but is not recommended for typical users to do this.
I am suggesting here that you bring up the Registry editor, find the resources associated with EVE, and find the specific one that has a path to the Data dir. From this editor, you can directly change the path, and things should just work. The important thing is that you should not change anything else in the registry.
If you go to Ogg's instructions:
http://ogg.kicks-ass.net/receptor/
he describes how to enable your receptor to bring-up the Registry editor. From here, You would look for entries under the tree:
HKEY_LOCAL_MACHINE/SOFTWARE
(you would probably find entries either under the name EVE or DashSignature).
This isn't very hard to do, but you could really screw-up your machine if you change entries you shouldn't.
Hope this helps. Regards,
Kevin L
-
- KVRist
- Topic Starter
- 64 posts since 31 Dec, 2006 from California
Kevin,
Thanks very much for the info. I'm afraid that's a bit over my head. Given the fact that I have spent 6+ hours trying to get EVE to work, all I need now is to screw up what I already have. For less than $200 I can buy Elektrik Piano and get the Wurly I need so I think I am going that route!!!
Thanks again.
Thanks very much for the info. I'm afraid that's a bit over my head. Given the fact that I have spent 6+ hours trying to get EVE to work, all I need now is to screw up what I already have. For less than $200 I can buy Elektrik Piano and get the Wurly I need so I think I am going that route!!!
Thanks again.
"Better the pride that resides in a citizen of the world then the pride that divides when a colorful rag is unfurled." - N. Peart
-
- KVRian
- 691 posts since 13 May, 2004 from Silicon Valley
Ahh - Wurly! So that's what this is about 
I have Elektrik Piano going, and it is pretty nice. I still can make the Kontakt player choke when playing with heavy sustain - but you can play around this limitation.
I also have Scarbee libs running on Kontakt, and those are quite nice too.
Hard to go wrong with either of these.
Also, you might wish to check out some of the freebie emulators like MrRay - these are quite good too.
Regards,
Kevin L
I have Elektrik Piano going, and it is pretty nice. I still can make the Kontakt player choke when playing with heavy sustain - but you can play around this limitation.
I also have Scarbee libs running on Kontakt, and those are quite nice too.
Hard to go wrong with either of these.
Also, you might wish to check out some of the freebie emulators like MrRay - these are quite good too.
Regards,
Kevin L