What to do when Receptor loses UniWire connection?

Locked New Topic
RELATED
PRODUCTS

Post

Hi,
Using Ableton Live as my DAW, I'll try to load certain Kontakt patches or send program changes via UniWire to Receptor ...it gets confused then stops working (the cursor turns to an X and I see the desktop image of a Receptor unit). I spoke with someone at Muse Research Tech Support about this. He said the DAW needs to be restarted to reinstantiate the UniWire plug-in and get Receptor working again. I find that to be a little troubling in the middle of a show, should Receptor decide to stop working.

Can anyone suggest a better way to reset the connection in a high-pressure moment, such as being on stage...particularly in Ableton Live? I've tried the reloading the Bank/Presets button and deselecting and reselecting the connection to my Receptor, but neither gets the sound going again. Thanks.

Post

Perhaps it doesn't have anything to do with Ableton Live or Uniwire...
I have quite the same problem sometimes, especially with Kontakt. When I instantiate Kontakt, or when I try to load a patch or a bank containing Kontakt, Receptor has a tendency to reset, depending on what other synths or effects are loaded together with it.
Try to do the same manipulations with Receptor alone (no Live and no Uniwire) and see what happens.
I don't remember where, but I've read that version 2 of Kontakt was not very stable on Receptor... I have version 2, so maybe that's why.

Demierra

Post

Thanks for the response. I am hoping that once I have my show together I'll know which patches work and which don't so I know what to avoid.

I have Kontakt 3 and it still crashes, so I'm not sure if it's just the version. As I mentioned in my original post, sometimes Receptor will reset from simple "Multi" program changes...loading Akoustik Piano and Battery.

Receptor is truly amazing, but it's definitely not perfect, as no instrument (especially computer-based) is. I just want to be prepared should Receptor reset on stage or in the middle of a song, God forbid!

Post

For me the way to go has been using snapshots, rather than loading new multis during a performance. This approach can seem limiting at first, but after working with it I have found snapshots to be very effective. I use Kontakt 2 extensively- you can do quite a lot with snapshots by loading multiple patches withing a Kontakt instance and using the Receptor midi filter within the snapshots. The biggest reason for working this way is that it avoids the need of loading new multis and the possible crashes that can be associated with that pprocess!

Post

Loopis Lucas,

What version of Kontakt 3 do you run? we've noticed a lot of problems with the first version of Kontakt 3. These can be eliminated in most cases by downloading the Kontakt 3.0.2 update. You can install this update by downloading the windows version from the Native Instruments site and running the update through direct install.

Locked

Return to “Muse Research and Development”