But Seriously.... [UniWire]

[DanTimis]

We tested it with Pro Tools 6, I think. I haven't done it myself, so I don't remember the details. We tested the FX version. We plan on testing the Instrument version with Pro Tools 7.

Do you have Pro Tools 7? Did you use the Instrument version?

Anyway, it's nice to hear that it worked for you.

[Ben [KVR]]

I cant download these updates: Javascript void(0). in both I.E. & AOL browsers.
Can you provide a non-Java Link?
Thanks...

It worked OK for me in IE6, Firefox and Safari but it didn't work in Opera.

I've just fixed the code to work in Opera so this may fix your problem too.

Give it a go and let me know.

cheers

[fishermusic]

Hi Dan,

Yes it was PT7. I used both the instrument track and the midi/aux input way of doing things as PT has a problem of continuing to send a midi signal on a 'instrument' track even when record is disabled. This happens with all plugins. I fear PT will never really get their act together MIDI wise.

[Gymnopedies]

I cant download these updates: Javascript void(0). in both I.E. & AOL browsers.
Can you provide a non-Java Link?
Thanks...

Give it a go and let me know.

cheers

Worked!! Awsome!!!!Thanks Ben.

[tconrardy]

Got the whole thing to work..and its just GREAAAAAT!!

Thanks Muse Team!

[RecordingArts]

Dan, have you guys got Guitar Rig 2 working on Receptor and does it work with the foot controller? Thanks, -Vincent

[DanTimis]

Farhan should answer this question.

[rubaiyat_23]

"Although it was not approved for Pro Tools, I converted the Uniwire VST to RTAS and messed around with it for a bit. Worked great! Obviously this is not much of a test, but it did exactly what it was supposed to do."

Didn't work here at all - will try 10.4.4 and older version of fxpansion adapter.

iMac G5 1.8, 2GB RAM, Seagate 300GB SATA drive - OS X 10.4.3 - PT M-Powered 7 - VST-RTAS adapter 2.0b4 - M-Audio FW1814

Performance seems iffy when Receptor Remote is open, though improves once the session is closed. Works alright under the obvious VST hosts (Cubase SX 3, V-STack).

No feedback is given that a patch (multi, single or otherwise) is loading–this would help when loading big multi-sample programs in Kontakt.

[nedrob]

No Sonar . I guess that means that not only will I have to wait for UniWire but it will also force me to update to Sonar 5 as it sounds like some of the fixes are going to have to come from the Cakewalk side.

Do you know if UniWire works with Podium from Zynewave? It's a "professional production software solution" that I found here on KVR.

[DanTimis]

Have not tried with Podium.

[RecordingArts]

Farhan have you got to try Guitar Rig 2 and the Rig Control (Their USB hardware controller) on Receptor?
Thanks,
-Vincent

[Hybernation]

There are a few major problems with Sonar. As we test more and fix the problems we find we will know more. Here is what we know so far:

• 1. I think Sonar works like Logic and treats VST Instruments in a semi-offline kind of way. That means that it tries to run the plug-in in big chunks ahead of time. It is kind of like freezing a plug-in, running it ahead of time, caching the sound and playing it back later.
  
  You can force an instrument to be treated in real time by assigning a MIDI input to it. I'm new to Sonar and I don't remember exactly what I did, but when I could play from a MIDI keyboard in real-time, then the MIDI track also played fine. When I had a MIDI track without MIDI input, it did not play.

• 2. Sonar does not update VST plug-ins when their GUI is closed. We are working with the good people at Cakewalk to solve this problem.
  
  When you instantiate a UniWire plug-in for the first time, the GUI window is opened and Sonar sends updates regularly. UniWire will look on the network for Receptors and connect to them. It may take a second or two.
  
  If you open a Sonar file, Sonar will instantiate the UniWire plug-ins, will not open their GUI, and will not send updates to them until you open the GUI. As a result the UniWire plug-ins will not get a chance to find and connect to Receptor(s) on the network. You will have to open the GUI of each instance, and then it should work. Once it is connected and works, you can close the GUI

• 3. This is maybe a minor problem. There is a difference between how Sonar and Cubase treat timing (we have not figured out exactly what happens, but we will). If you loop in Sonar you can hear a small glitch when the sound jumps back to the beginning of the loop (in Cubase it works flawlessly).

You can try UniWire with Sonar. It is not going to break your PC or your Receptor. You may have to perform a bunch of extra steps that may be annoying or tedious, but it is possible to get something out of it.

Yes, there is a little bit of "corporate speak" if you want to call it that way. We can also call it "covering our asses." We can't get into this level of details on the UniWire opening page, plus we are working to fix these problems so the situation may change any time.

Dan,

I've been using Uniwire with Tracktion2 and Sonar 5, and I'm pretty impressed. This is definitely worth the wait!

I'm having pretty good success with BOTH hosts. I know Sonar isn't officially supported, but I want to let you know TWO things about Sonar:
1) the good part: "Freeze" works PERFECTLY if you simply disable "fast freeze" on the "freeze options". An Audio track is rendered in real time. You can then cut and paste this to another audio track (not linked to the VST) for slicing and dicing as need be.
2) the bad part: Uniwire crashes Sonar when I do the following: a) instantiate an instance in a new song b) change that instance from "global" to "track1" c) instantiate a 2nd instance. Boom. Alternatively, you CAN instantiate several instances (not changing them from "global") but the minute you change one of the to send/receive on a single Receptor track the same crash happens. The reason this is such a dissapointment is because I intended on using multiple instances, each sending/receiving a different Receptor track. This is exactly what I am doing in Tracktion2 and it works GREAT. Unfortunately, Tracktion2 offers NO "real time" freeze or render options, so I was hoping to stick with Sonar.

Hoping you will of course get this one fixed (eventually) along with the other Sonar things you mentioned

Oh, and I tried Uniwire in Sonar with the directiXer VST wrapper, which many Sonar uses use instead of the Sonar VST wrapper, and it wouldn't work with Uniwire at all (the Uniwire GUI would not appear or function). That's neither here nor there, but I'm sure other Sonar users will try this so I just thought I'd mention it. I personally LIKE the Sonar VST Wrapper and have had very few problems with it (though lots of people hate it apparently).

Thanks again for Uniwire. For a Beta release, it really is some first class software!!

John H.

EDIT: Well I have just discovered a nice little workaround on Sonar for my problem! The reason I wanted to use multiple instances of the Uniwire VST was so that ultimately, when I'm finished tracking, I could just freeze (in realtime) each one and have each on a separate AUDIO track for mixing down. I don't like mixing a song with virtual instruments running, for many reasons. Plus I like everything completely in Audio tracks for archiving.

Anyway, using ONE instance of Uniwire VST I can accomplish the same thing rather easily. Each of several MIDI tracks is set to a different MIDI Channel and hence will trigger only one channel on the Receptor during tracking. All audio from all Receptor channels returns to Sonar on one audio track, which is ok for tracking. When I'm ready to mixdown, I simply solo one of the MIDI tracks at a time and freeze the Uniwire VST. Then I "clone" the resulting audio track to a new track and then "unfreeze" the VST. Lather, rinse, repeat and presto I have separate audio tracks when I'm done. It's only about 3 extra mouse clicks per Receptor track! (and it would have been 2 extra clicks per track to insert the multiple instances )

In some ways this is a better way of working with Uniwire than my original approach: 1) why take up all those audio tracks during tracking, since they serve no purpose 2) less memory is used since only one instance of the Uniwire VST is used.

UNIWIRE ROCKS!!! (and Sonar is not too shabby either )

[DanTimis]

1) the good part: "Freeze" works PERFECTLY if you simply disable "fast freeze" on the "freeze options". An Audio track is rendered in real time. You can then cut and paste this to another audio track (not linked to the VST) for slicing and dicing as need be. " the resulting audio track to a new track and then "unfreeze" the VST. Lather, rinse, repeat and presto I have separate audio tracks when I'm done. It's only about 3 extra mouse clicks per Receptor track! (and it would have been 2 extra clicks per track to insert the multiple instances )

Thanks for the tip. BTW, in Cubase I could not find a way of using the plug-in freeze function in real-time. But, you can use "Export" (I think that's what it's called), and check the real-time check box. You can solo the tracks you want to render and the result will be imported in a new track. After that you can mute the tracks you just rendered. Same little problem, a few extra steps, but you can get basically the same results as with freeze.

About the crash with multiple instances and changing from "All Receptor Channels" mode, we will look into it and fix it. We tested Sonar and we did not have this problem. A few things to try would be, try closing all windows as you instantiate UniWire, then try keeping them opened. Is the crash happening because the other windows are opened or because they are closed? Try setting the plug-in to the channel you want, then deselect Receptor in the "Connected To" menu (set it to "No Receptor Selected"). Is it still crashing. If it's not crashing, try selecting the receptor again. Is it still crashing?

Thanks,

[Bryan@MuseResearch]

[quote="RecordingArts"]Farhan have you got to try Guitar Rig 2 and the Rig Control (Their USB hardware controller) on Receptor?
Thanks,
-Vincent[/quote]

Farhan is out of the office and probably won't be able to reply for a couple of days, so I'll chime in!

Guitar Rig 2 isn't quite ready for prime time on Receptor quite yet, but we're sure it will work very soon. I know that the new GR2 control surface is USB, and instead of using standard MIDI commands they have a proprietary protocol. NI has said that they will provide the documentation so that we can support it (bless 'em!) but it might take a little time. Plan on the GR2 plug being released very soon, the controller as soon as we can get around to it, but there are a lot of other plug-ins "on deck" so it might be a little while (as always, thanks for your patience!)

Speaking of NI, I've been playing with B4II on Receptor at NAMM, and I'm really impressed by the quality of the upgrade. They've done a nice job with it, and alot of the artists who have played it at the show (at 32 sample buffers no less!) have been impressed as well.



Cheers from Anaheim!

Bryan

[Bryan@MuseResearch]

By the way gang, this is great feedback and is extremely useful to us here at Muse. Thanks very much!

Bryan