I was just wondering who, besides me, is not satisfied with the (non)compatibility of the Receptor with current plug-ins and Muse's apparent refusal to tell us - even privately - what the plan for the future is. Simply, I would just like to see a "show of hands" of any and all who are not satisfied. I would really like this to become a list that conveys the dissatisfaction, so those of you who may be content with the way things are, please keep those comments out of this thread, if you don't mind, or put them in a different thread.
Thank you all,
Batgab
Who's Not Satisfied with Receptor's VST Compatibility?
-
- KVRist
- 173 posts since 3 Sep, 2007 from CT
An update on Ivory iLok and Kontakt Player Instruments would be good and a release roadmap.
-
- KVRAF
- 4071 posts since 4 Mar, 2008 from Near Pittsburgh
I'd rather not have to figure out a way to rig up Amplitube stuff myself, and still wait. I won't wait long as I guess it can be done based on the creative ways I see there are to install others, and the fact that they've been selling a unit with the Amplitube line preinstalled.
Other than that, I'm OK with the other methods available in most cases but if you aren't comfy with the methods involved I can see why out-of-the-box compatibility isn't satisfactory for some.
Other than that, I'm OK with the other methods available in most cases but if you aren't comfy with the methods involved I can see why out-of-the-box compatibility isn't satisfactory for some.
-
- KVRist
- 223 posts since 2 Dec, 2006 from Minnesota
There are now a plethora of newer sampled pianos that do not run on Receptor - Garritan Steinway, QL Pianos, Bluthner Digital Model One, Latest Ivory (iLok), newest Galaxy Pianos, Pianoteq 3. I chose to upgrade my Receptor rather than sell and go with a laptop. I remain a bit concerned about this decision as the newest plugin (prior to the updated Ivory March 2009) was September 2008. Having said that, I still have confidence that Muse is aware of the problem and know that they have to do something about compatibilty. I think that they have been focused on hardware in the recent past. Now that the new line is shipping, I hope that they will address the software side more aggressively. I appreciate that Muse is a small company with limited resources in a tough economy, and it is a hugely daunting task to keep up with all the new plugs and updates of old plugs. Despite some of my "disappointments" (and I get as impatient as others for plugs I want) I've used and enjoyed my Receptor more than any hardware instrument/keyboard or module I have ever purchased. And I've been buying stuff for a long time 
Tom B
Tom B
-
- KVRist
- 223 posts since 2 Dec, 2006 from Minnesota
I'm not sure what was updated, or why it was updated. It's still version 1.6x. I believe the newer iLok Ivory stuff is 1.7. Ivory always ran great on my Receptor - installed probably 18 months ago? I don't think the update changes Ivory in any way, probably just the install, or maybe fixed some Receptor/Ivory related minor bugs?
Tom B
Tom B
-
- KVRist
- Topic Starter
- 269 posts since 23 May, 2008 from Lake Stevens, WA, USA
TWB, I hear what you're saying about Muse being distracted with new hardware/upgrades, and like you I hope they are planning plugin compatibility improvements for the near future. And I agree the Receptor is fun for what it currently does. But I don't think we should be cutting them any slack just for being a small company. Their products are marketed just like everybody else's stuff, just as if they're one of the "big boys", with absolutely no disclaimers about product limitations. So I figure, hey, any plugin oughta work, and I don't really care what their excuses are if they're not going to give us any advance warning that that is not the case. (I'm probably being naive there, but I don't think I'm alone.) Anyway, I'm with ya, not arguin' with ya - tho it might sound like it!
Anybody else want to voice their concerns? I really just want to make this visible (not that I think anyone from Muse Research is actually paying attention...
), so please jump in!
Thanks!
Anybody else want to voice their concerns? I really just want to make this visible (not that I think anyone from Muse Research is actually paying attention...
), so please jump in!Thanks!
-
- Banned
- 22457 posts since 5 Sep, 2001
[DELETED]
-
- KVRer
- 11 posts since 25 Feb, 2009
I purchased a receptor about a week ago and I am not impressed. You have to deal with vst compatibility issues. Many of my old vst's do not have receptor installers.
I have no doubt that the hardware is powerful, however, you have to play within receptors strict vst requirements. At least in the mac/pc world I can use my vst's.
I'v also had issues with my new receptor crashing and rebooting. I'm concerned about using this thing live. In my mind I'll be worried about this thing suddently doing a reboot on me while playing live.
Yes theres an entire list of famous poeple that use this and can afford to replace their non working vst's with receptor compatible stuff and continually put money towards finding software that work with the receptor.
If your thinking you can buy a receptor and its going to be smooth sailing, you're wrong. There are issues to deal with and limitations that are not spoken about in the main website.
Yes "theoretically" the receptor can play any vst, but the reality is, it can't becuase you are creating receptor installers for a Linux operating system.
I am not giving up just yet. I have 30days to return my receptor.
By the way, i've worked with various linux platforms and currently run 2 linux servers in my own business everyday. So I do believe in this operating system.
I have no doubt that the hardware is powerful, however, you have to play within receptors strict vst requirements. At least in the mac/pc world I can use my vst's.
I'v also had issues with my new receptor crashing and rebooting. I'm concerned about using this thing live. In my mind I'll be worried about this thing suddently doing a reboot on me while playing live.
Yes theres an entire list of famous poeple that use this and can afford to replace their non working vst's with receptor compatible stuff and continually put money towards finding software that work with the receptor.
If your thinking you can buy a receptor and its going to be smooth sailing, you're wrong. There are issues to deal with and limitations that are not spoken about in the main website.
Yes "theoretically" the receptor can play any vst, but the reality is, it can't becuase you are creating receptor installers for a Linux operating system.
I am not giving up just yet. I have 30days to return my receptor.
By the way, i've worked with various linux platforms and currently run 2 linux servers in my own business everyday. So I do believe in this operating system.
-
- KVRAF
- 4071 posts since 4 Mar, 2008 from Near Pittsburgh
abelaguilar - have you joined the two Yahoo Groups dedicated to the Receptor? Being that you are working with Linux servers daily (that's what I did last job and this one is all Solaris, so I know where you are coming from) I know you are capable of doing some of the things that I personally think are required to get the most out of the Receptor. That stuff doesn't seem to be talked about here, probably with good reason (certain things void warranty etc) so look for two Yahoo Groups on Receptor and there is information about getting things going by enabling regedit etc. Have to make the disclaimer than anything like that is at your own risk and likely voids the warranty but I found it opened up a lot of possibilities.
-
- KVRAF
- 6323 posts since 30 Dec, 2004 from London uk
Im not a Receptor owner but I follow what happens with interest. Receptor is not sold as a PC. It just happens to run Linux. I think problems have arisen due to expectations. Customers thinks its just a PC and expect it to run any PC plugin. It cant and wont. Ive learnt from the past that if you buy something on the basis of what is expected/suggested for the future - you will be unhappy. You have to buy for what the unit does now. The same thing is happening with V Machine, people expect it to be a PC. FWIW - I think the situation would have been better if they had both used Windows XP embedded but that isnt going to happen.
Last edited by UltraJv on Fri Mar 13, 2009 1:10 pm, edited 4 times in total.
-
- KVRer
- 11 posts since 25 Feb, 2009
buscemi: Thanks for the info. I will definatly look into the yahoo groups.
-
- KVRist
- 387 posts since 24 Aug, 2004
I'm pretty well satisfied with the compatibility. I think if someone is considering purchasing, they should do so based on what DOES run well, and not expect it to run every VST. I would love for the Ivory Uprights, and for Pianoteq 3 to
be compatible, but I am very happy with what I do run frequently- Kontakt, Ivory, Minimonsta, Scarbee electric pianos, M-Tron, Vb3 and B4 II. These make the receptor MORE than worth the money for me and my needs.
Also - to respond to recent post in this thread - I have used Receptor on literally hundreds of gigs and never once has it crashed. I do always make sure I have some redundancy and can still play if it were to go south, but it never has.
I can make it crash if I want to by loading a sample heavy multi while one is already loaded, but as long as I stick to my well tested snapshots , and load blank multis in between snapshots, I feel pretty secure.
be compatible, but I am very happy with what I do run frequently- Kontakt, Ivory, Minimonsta, Scarbee electric pianos, M-Tron, Vb3 and B4 II. These make the receptor MORE than worth the money for me and my needs.
Also - to respond to recent post in this thread - I have used Receptor on literally hundreds of gigs and never once has it crashed. I do always make sure I have some redundancy and can still play if it were to go south, but it never has.
I can make it crash if I want to by loading a sample heavy multi while one is already loaded, but as long as I stick to my well tested snapshots , and load blank multis in between snapshots, I feel pretty secure.
-
- KVRist
- 93 posts since 10 Feb, 2009
So far so good, but I don't have a massive, pre-purchased softsynth library that could be rendered "obsolete" (in a sense) because the Receptor won't load or run it. I'm sure I'll encounter something where I say "darn, wish it worked"........
I suppose that if I had $4000 in VSTs that I couldn't load, then I'd be responding differently. If you are starting from scratch, and are content with the Receptor compatible plug-ins, then that situation might predict greater satisfaction.....
I suppose that if I had $4000 in VSTs that I couldn't load, then I'd be responding differently. If you are starting from scratch, and are content with the Receptor compatible plug-ins, then that situation might predict greater satisfaction.....
-
- KVRer
- 11 posts since 25 Feb, 2009
PHil: I would agree that as a new user i'm loading all kinds of stuff and experimenting. This may be causing the receptor to crash at times.
Can you help me understand how you setup your receptor for live use with respect to snapshots?
I envision saving a bank of lets say 5 vst's that I always use and save patches within that bank for each song inthe set list. Some vsts are muted and some arent depending onthe song.
Is this the way i'm supposed to set things up? Will this help each patch load up faster?
I've watched the videos and read the manual, but still not understading exactly how this works.
Can anyone else jump in here.
Thanks
ps. maybe this belongs in another post.
Can you help me understand how you setup your receptor for live use with respect to snapshots?
I envision saving a bank of lets say 5 vst's that I always use and save patches within that bank for each song inthe set list. Some vsts are muted and some arent depending onthe song.
Is this the way i'm supposed to set things up? Will this help each patch load up faster?
I've watched the videos and read the manual, but still not understading exactly how this works.
Can anyone else jump in here.
Thanks
ps. maybe this belongs in another post.