MUSE RECEPTOR ??

[PodBoy]

A decades long evolution now has my studio functioning in a 100% virtual world, including all my MIDI instruments. Of course I also have a nice MIDI keyboard / MIDI module museum set up in the corner (DX7 D50 Proteus MKS70 (Jupiter) etc etc ).
But now I'm back in a live playing situation but don't want to be lugging all those things around or having to layer them just to get a decent sound. And I don't want to invest in a modern all-in-one super keyboard/workstation.

So how is the MUSE Receptor? Its not cheap, but I might justify the expense if I could also use it in the studio, to offload some heavy duty instruments from the DAW.

What are the practical issues?
Is latency ?
Can I have my plugins on BOTH the DAW and Receptor at the same time, or do plugin manufacturers not allow that?

 

[Arys Chien]

Muse Receptor user here.

1. The UniWire driver doesn't support multi-core yet. Therefore, if you want to use the UniWire function (transmitting MIDI and audio data via ethernet cable) but have a multi-core (dual or quad) DAW, either disable the multi-core support of your host application (like Nuendo), or use MIDI cables, ADAT cables or analog cables instead of UniWire.

2. If you're using UniWire, the latency is always 2x of the DAW at least. Say the audio buffer of your sound card is 512 samples, then the minimum latency of your Receptor would be 1024 samples. If you're using cables instead of UniWire, then you can get latency as low as 32 samples without dropouts.

3. Some company allows you to use your legal copy of plug-ins on both your DAW and your Receptor. Others demand a \"crossgrade fee\", which is much less than the plug-in itself, not much enough to cause you problems.

4. The Receptor is a good help. With complicated arrangements and mixes, I usually launch VSTis on the Receptor, and then use the UniWire so that they appear like regular VSTis in Nuendo's mixer view. Then I can run more native plug-ins to process them.

I suggest use it to run VSTis that consumes much more PC horsepower than the others, like the Ivory piano (a memory hog), or play a pad with Z3ta+, etc..

 

[PodBoy]

Thanks for the very informative response!

I read a review and an article they failed to mention that nasty little tidbit about the dual-core limitation - thats a potential showstopper for sure, so I'll have to investigate when it might be addressed...

Not sure about the cable alternative, I have to check my old RME Multiface to see about its ADAT support (never had to think about that before) ; and audio lines are conceptually \"icky\"

I read about the 2X latency, mine is pretty low so i MIGHT be able to get away with it

Thanks again!

 

[Arys Chien]

They didn't mention the dual-core thing. And it cost me one day and one night to figure it out. I was very upset about it. More upset when I got a reply to say that they were not sure when they could fix it.

The previous driver was released April 2006. That was almost one year ago. I don't know anything about programing, so I don't know if this is an issue that takes one year to settle.

I'm using RME Digiface, but got a Multiface for my laptop. The ADAT interface works fine. Yet I forgot that if the ADAT interface of the Receptor is optional, ie you need to pay extra for it. You'd better ask Muse about it.

 

[PodBoy]

thanks again;
They seem to revamping the models - seems they realize that the basic offering of 256 MB RAM is pretty weak even for a non-windows, optimized PC. But the base price will probably be higher. and then of course the optional ADAT interface....