MOTUnation.com

Not to beat a dead horse, but I'm loving my Receptor.

I would love to get a Receptor but have been waiting for them to get some issues worked out. I'm not familiar with the OS, concerned about the limited hardware expandability, and some of the things I want to run on it aren't working yet. Also, I've been waiting for them to get the AU version of UniWire working.

How are you using it? What's your experience, and have you tried running Ivory, BFD Drums, IK's Philmarmonik and Guitar Rig 2?

Thanks!
-Vincent

TOD wrote:Not to beat a dead horse, but I'm loving my Receptor.

RecordingArts wrote:I would love to get a Receptor but have been waiting for them to get some issues worked out. I'm not familiar with the OS, concerned about the limited hardware expandability, and some of the things I want to run on it aren't working yet. Also, I've been waiting for them to get the AU version of UniWire working.

How are you using it? What's your experience, and have you tried running Ivory, BFD Drums, IK's Philmarmonik and Guitar Rig 2?

Thanks!
-Vincent

TOD wrote:Not to beat a dead horse, but I'm loving my Receptor.

Right now I'm running Trilogy, BFD light, Stylus RMX, two other soft synths and a pile of PSP plugs simultaneously. They just released a NORD emulator called discovery that is almost an exact replica of the NORD, (I have a NORD Rack)..Dude, I'm running all this with Ultrafocus, iDrum, LIVE and MOTU Symphonic on my measely G4 dual 1.42. using the latest release of Uniwire 1.5 which works very well, (no latency).

I'm also anxiously awaiting for the AU version, I bought audioease's VST wrapper and it works fine. plus, now I have even more plugin accessibility for DP.

Tod,
That's amazing. Someone on the Receptor forum was having a lot of latency with the wrapper, that's awesome that it's working for you! I might have to grab one soon. Did you update the ram, and which hard drive do you have? Isn't BFD the bomb?

TOD wrote:

RecordingArts wrote:I would love to get a Receptor but have been waiting for them to get some issues worked out. I'm not familiar with the OS, concerned about the limited hardware expandability, and some of the things I want to run on it aren't working yet. Also, I've been waiting for them to get the AU version of UniWire working.

How are you using it? What's your experience, and have you tried running Ivory, BFD Drums, IK's Philmarmonik and Guitar Rig 2?

Thanks!
-Vincent

TOD wrote:Not to beat a dead horse, but I'm loving my Receptor.

Right now I'm running Trilogy, BFD light, Stylus RMX, two other soft synths and a pile of PSP plugs simultaneously. They just released a NORD emulator called discovery that is almost an exact replica of the NORD, (I have a NORD Rack)..Dude, I'm running all this with Ultrafocus, iDrum, LIVE and MOTU Symphonic on my measely G4 dual 1.42. using the latest release of Uniwire 1.5 which works very well, (no latency).

I'm also anxiously awaiting for the AU version, I bought audioease's VST wrapper and it works fine. plus, now I have even more plugin accessibility for DP.

So, as I promised, I loaded up Wormhole2 and tested it with two computers

DP is on a G5 Dual 1.8 talked to the other computer with 3 connections:
1: MIDI Express Xt -> Midisport 2x2
2: 896HD <- Mini Stero Out
3: Ethernet 100Mbit <-> Ethernet 100Mbit
Rax running Albino2 using an aux send to Wormhole2

I wont bore you with the details of setting up DP, suffice to say, I used the Apple synth as a low overhead synth sitting in an Instrument channel and just ignored it's output, put wormhole after it (set it's rending to minimum).

I created a MIDI track that just sent a single fast note to a very tight synth in Albino2. (a pulse) then recorded what came through Wormhole2 and what came through the standard audio interface.

Even with setting the driver down to a 64 buffer, the signal coming from wormhole was always slower. It was significantly slower than if I had a larger buffer setting, which makes total sense.

At 64 it could almost be usable for me realtime. At 1024 absolutely not, but, I can certainly understand that.

The point I want to make is running straight audio is faster, hands down, no matter what. For that reason, I can't see using Wormhole2 unless I was doing completely NO live work through the secondary machine, so I could setup the latencies and such.

Don't get me wrong, I think it's pretty damn cool. And I am sure there are probably more things I could do to get the time more aligned overall. But not for live sounds. It just adds more latency in all situations where I could get faster throughput with a direct audio connection.

Hi Rick,
Sounds pretty simular to my experience with WormHole2. In theory it would be a big help to us. With OSX supporting MIDI over Network connections, it could be the Mac version of UniWire, but I had the same experience with latency problems....

-Vincent

grimepoch wrote:So, as I promised, I loaded up Wormhole2 and tested it with two computers

DP is on a G5 Dual 1.8 talked to the other computer with 3 connections:
1: MIDI Express Xt -> Midisport 2x2
2: 896HD <- Mini Stero Out
3: Ethernet 100Mbit <-> Ethernet 100Mbit
Rax running Albino2 using an aux send to Wormhole2

I wont bore you with the details of setting up DP, suffice to say, I used the Apple synth as a low overhead synth sitting in an Instrument channel and just ignored it's output, put wormhole after it (set it's rending to minimum).

I created a MIDI track that just sent a single fast note to a very tight synth in Albino2. (a pulse) then recorded what came through Wormhole2 and what came through the standard audio interface.

Even with setting the driver down to a 64 buffer, the signal coming from wormhole was always slower. It was significantly slower than if I had a larger buffer setting, which makes total sense.

At 64 it could almost be usable for me realtime. At 1024 absolutely not, but, I can certainly understand that.

The point I want to make is running straight audio is faster, hands down, no matter what. For that reason, I can't see using Wormhole2 unless I was doing completely NO live work through the secondary machine, so I could setup the latencies and such.

Don't get me wrong, I think it's pretty damn cool. And I am sure there are probably more things I could do to get the time more aligned overall. But not for live sounds. It just adds more latency in all situations where I could get faster throughput with a direct audio connection.

RecordingArts wrote:Hi Rick,
Sounds pretty simular to my experience with WormHole2. In theory it would be a big help to us. With OSX supporting MIDI over Network connections, it could be the Mac version of UniWire, but I had the same experience with latency problems....

Yes, but you have the same issues with realtime performance on ONE computer if the buffers aren't low enough. Everything else should be latency compensated.

My comparison point was between running the audio in through the 896 or through the ethernet and the plugin. No matter what I did, even at 64 buffer size, the audio coming out of the mini output jack and into my 896HD was always faster. Moving away from 64, it seemed to scale at a sort of exponential rate.

Realtime compensation can't exist if you are playing real time, meaning, you hit a note, it can't know that you were going to hit it already, so the only option, as you might be implying, is to delay all the other audio. That may be possible, I didn't test that particular aspect of it, but it doesn't help for my situation.

I rarely have audio files until the very end, I tweak my synths VERY much during the writing phase. So, I monitor through effects on 24 channels in almost every song. I need as low of a latency as possible if I want to try and record anything, since everything is playing in realtime.

For someone with recorded pieces, just the delay from what you play to what you hear is going to be the issue. at 64, it was usable. At 128, it was too far for me. Since most of the time I run at 128, and since I have extra audio hookups in my system (have 32 total, well, really 36 if you include the AES/EBU) so it wasn't an issue.

This was basically a test to see how it compared to hooking up directly, which is just can't compete with for realtime.