Receptor 1.5 Now Available

[Ben [KVR]]

Receptor 1.5 and the UniWire plug-in in VST format for Windows 2000/XP and Mac OS X (10.3 and higher) are now available to all Receptor owners.

[edit]
UniWire 1.1 VST/AU Windows and Mac OS X Universal Binary available.
[/edit]

The UniWire plug-in acts as an interface to your Receptor, allowing you to send MIDI or audio data to your Receptor and have the processed results returned to your computer software as if it is internal to your computer. Sometimes referred to as a "virtual-virtual instrument" the UniWire plug-in takes the MIDI and audio data sent to it by your host program, converts it for transmission via Ethernet, sends it over to your Receptor where the audio is processed or generated and then returned to your host computer, all in a matter of a few milliseconds.

http://www.plugorama.com/

[multree]

finally.... YEAH....

I have waited very long for this feature....

good work guys... will test it ASAP

[tconrardy]

Beta report

When first installing the new version, went to 100%, but then siad it failed and robooted. ( however..I think this is normal for my receptor, as it does this with every update)

Saw the new Uniwire dialogs on the setup page..YEAH!

Installed the Windows VST..no problems. Loaded it up in MiniHost.

Saw it load up. After a while, got audio and playing from my MIDI keyboard which is directly connected to Receptor, but was hoping to get midi playing from MiniHosts internal MIDI keybard...guese I have to RTFM...but up to this point..did not need it.

EDIT: got this to work...wonderfull!!

It did reboot on me while I switched presets from the VST, but not from the Receptor GUI.

EDIT: but now works flawlessly..you have to wait for the preset to load before attempting to play

Now to explore some of the other features...but NICE JOB...really glad this is working!!..knew you would reveal something for NAMM!! you sly devils!!

[Scot Solida]

I just wanted to express my appreciation to the Muse guys for UniWire. I got it installed and running on my Mac with absolutely NO trouble at all. I wish all my hardware were this easily integrated into my system. The fact that my Receptor now gives me an extra MIDI interface is a nice bonus, too.

This was indeed worth the wait.

[Cantinero]

it is very impressive, although not without glitches..I find that it causes the CPU on my MAC to spike with no instruments actually playing..I have tried buffer sizes etc..This is when Both my computer and receptor are using very little power....other than this, I love it..

CH

G5 2.5
Cubase SX3.1
Uniwire 1.5 beta.

[DanTimis]

Are you running any browser, email, or anything else that uses the network? A browser could cause glitches, even it if stays idle in the background.

[Cantinero]

Thanks Dan, that was my problem it seems, i had airpot on in the background..Turned it off and things seems to be working..

Thanks.

[Jayman]

Dan, in the Uniwire video (from a few months ago), a feature called multi-port is described. In the Uniwire supplement, I found what seems to be describing how to do this, but I can't figure out how to implement it. The only thing I'm able to do is use each channel of receptor as ONE instrument with ONE midi channel. I'm probably missing something. Note that I'm using uniwire through a VST wrapper on Digital performer.

Thanks!

j

[tjodoin]

Haven't installed 1.5 yet. Just wondering if anyone is syncing with SPDIF as indicated in the Uniwire manual to use Receptor as an audio interface. Why isn't the clock sent embedded with the audio signal as in ADAT or SPDIF? Is there a bandwidth issue via ethernet? Just curious.

[DanTimis]

I think that in Digital Performer each MIDI track has only one MIDI channel. There are no multi channels MIDI tracks like with Cubase. Moreover, in Cubase you create a VST instrument and you send MIDI to it from MIDI track(s). So you can have either one muti-channel MIDI track, or several MIDI tracks sending MIDI to the same instance.

Here is how you can set this up in DP:

• - Create a virtual instrument track with UniWire. Set the DP track to MIDI channel 1. Set the UniWire plug-in to send MIDI to Receptor channel 1, to control the VST Instrument.
  - Create another virtual instrument track with UniWire. Set the DP track to MIDI channel 2. Set the UniWire plug-in to send MIDI to Receptor channel 1, to control the VST Instrument. Set the UniWire instance to MIDI only.

This way you send MIDI channels 1 and 2 to the instrument on Receptor channel 1, but only the first UniWire instance receives audio back. If you do not set the second instance to MIDI only, you get the same audio twice and it gets louder in the mixer. UniWire will not send the audio twice, it will be sent only once, then copied to both instances. So you do not get a performance penalty, you just get the same audio twice in the mixer if you do not set the other instance(s) to MIDI only.

Incidentally, this is also how you control an effect plug-in or the mixer section in Receptor. You create another virtual instrument track in DP. Set the UniWire instance to send MIDI to Receptor channel 1, to control FX/A, FX/B, FX/C, or the Mix section. You set the instance to MIDI only. You can use MIDI controllers to control the effects or the MIX section, but you get audio back only from the first track in DP.

This last paragraph applies to all hosts, not just DP.

[Jayman]

Got it! Makes total sense. Thanks Dan. I'll post any future uniwire ??s in the new thread.

j

[Cantinero]

Sorry to be the pain..But, it seems the cpu problem has not dissapeared..It has improved since i turned off airport, but still continues to be an issue..Any other thoughts as to what I may be doing wrong ?.

[DanTimis]

Make sure there are no internet applications still running, even if you have the airport off. Look for applications or utilities that may do something periodically. Try increasing the buffer size. Or try increasing the latency.

[Briggity]

I'm finding that the Uniwire Instrument plugin sends the last selected Multi or Single selection to the receptor when I instantiate a new copy of it...not desirable. For example: I'm controlling Receptor from Live on my PowerBook. I load a new Uniwire Instrument, use the Multi select commands to call up a previously-stored template with several VIs and effects. Maybe I make some changes to the sounds via REceptor Remote.

Now I'm using this instance of Uniwire for a Multitimbral sample VI on Receptor channel 1...so I need to load a second instance of Uniwire, MIDI-only mode, to control one of the other VIs in my template. As soon as I launch this copy of the plugin, it sends the last selected multi again - over-riding any changes made on the Receptor, without warning.

Please modify Uniwire plugins so that they load with NO multi or single selected, and do not send and program changes until the user specifically selects one.

Brian

[DanTimis]

There has to be something else happening there.

When you instantiate UniWire it will ask Receptor for a list of multi and single banks and patches, and it will ask Receptor for the current bank and patch, then set the menus to reflect the current settings on Receptor. IT WILL NOT, set any banks or patches.

When you save a Live document, then reopen it later, UniWire will set the multi and single to one that was selected when you saved the Live document.

Here is what I just tried:

• Start Live. It starts with an Audio Track and a MIDI track.
  Select the MIDI track
  Drag "UniWire Instrument" into the "Drop MIDI Effects, Audio Effects, or Instruments Here" area
  Select a Multi patch from the menu
  Launch Receptor Remote Control and make changes to the selected multi
  Insert a new MIDI track
  Drag "UniWire Instrument" into the "Drop MIDI Effects, Audio Effects, or Instruments Here" area
  Go to Receptor Remote Control and observe that nothing changed

So you must be doing something in a different way. Could you describe in great detail what you are doing?