VSL-Vienna Instrument

[ceproaudio]

Has anyone tried to load VSL Vienna Instrument onto the Receptor? Any thoughts or concerns?

[Ben [KVR]]

The VSL VI dongle won't work on Receptor, yet.

[Arys Chien]

Just got my copy of the first half of VI. So far it's impossible to use VI on Receptor. They use the same kind of USB dongle with Steinberg, not iLok.

[Bryan@MuseResearch]

I'll be talking to the VSL people at the Musik Messe about having their stuff work on Receptor... hopefully I'll bring back some good news.

Cheers

Bryan

[Robert Karasek]

Indeed, Bryan! that would be awesome!
Hope to easily find your booth ...and hay: one goood german beer is on the house, eh ?!
Rob

[Bryan@MuseResearch]

We're in the Hyperactive booth, Hall 5, Floor 1, Walkway B, Stand 54.

You are absolutely right, German bier is the best, end of story!

Cheers

Bryan

[Arys Chien]

Hi Bryan,

Hope you got good news for us.

But I really don't want to pay any extra crossgrade fee anymore.... I've been a loyal VSL user, from the Pro Edition to VI. We have spent a lot already....

By the way, it's said that the total library of VI would be as large as 550G, though the first half is only 170G now. If it should work on Receptor, how do we get a HD so big?

[Bryan@MuseResearch]

Right now everything has to run off a single drive, and the single drive limit in capacity is 500GB. We haven't tested 500GB drives, but we're reasonably confident they will work, although we would definitely recommend against touring with such a large drive.

The only other ways to get around this is to off-load unused samples to your computer on a temporary basis, buy a second Receptor hard drive to swap in and out as needed, or pick up another Receptor. I know that might sound like an outrageous suggestion, but that is what a majority of the film composers are doing these days.

For example, composers will divide these ultra huge libraries among different computers, like EWQLSO Platinum where you might have Brass on one computer, Solo Strings on another, Woodwinds and percussion on another, etc. This is done primarily to provide reasonable polyphony across the whole library. Its not untypical to see 3, 4, 5 or more computers running large libraries in a composers studio these days.

And although Receptor is fairly new to the film composer world, early indications are that they are taking a similar approach across several Receptors. Of course in the case of Receptor, the task of integrating the individual units into the host computer is actually MUCH easier thanks to UniWire, since it takes care of all the audio and MIDI routing between separate units.

We will look at streaming off of extermal hard drives in teh future, but for right now, the above suggestions are the only solution I can think of...

Cheers

Bryan

[jstaczek]

Bryan, I'm a film composer trying to integrate Receptor into my studio, and so far I haven't been able to make UniWire useful at all. What's the workflow that gets you around the latency at 2048 buffer sizes? Do all of your sequence editing graphically? You certainly can't play anything at those latencies. Help me understand how UniWire is useful for anything but printing tracks after all the sequencing is done. By the way, I'm using Pro Tools and DP. Is there magic in Logic or Nuendo that I'm missing?

Thanks,

Jason Staczek
www.chromasound.net

[Bryan@MuseResearch]

Hi Jason

Not sure how you're even able to get Pro Tools to work with Receptor right now, since we haven't released the software to support it. And to be honest, I'm not a PT user, so I'm not sure why you are seeing such high latency.

I know it is working very well in Cubase and Nuendo, and a couple of composers using Nuendo with Receptor have reported no problems... as far as your specific situation is concerned, I should talk to some of the QA folks and see where they are at.

Unfortunately, I leave on Monday for Musik Messe, I won't be able to reply to you for the next week and a half, unless some other Muser can answer in the mean time...

Bryan

[DanTimis]

Bryan, I'm a film composer trying to integrate Receptor into my studio, and so far I haven't been able to make UniWire useful at all. What's the workflow that gets you around the latency at 2048 buffer sizes?

I suppose you are using the FXpansion VST to RTAS wrapper version 2.0. This problem has been fixed in the 2.0.1 version of the wrapper. We tested it with the beta version of 2.0.1 and it works with smaller buffers too. I forgot what was the smallest latency, I think it was 256 or maybe 512. In any case it was very usable.

You can either ask FXpansion to become a beta tester and get 2.0.1 right now, or wait until it is officially released.

[Arys Chien]

My own solution now is to move Ivory to Receptor, and leave VI to my PC with 3G RAM. Much less trouble, and working wonderfully.

[jstaczek]

I'll try to get the beta from FXPansion. In the meantime, the lowest I can get from DP is 512, which is not "very usable" for recording sequence data from a keyboard. The latency is simply too high.

Can anyone report a real-world experience of Uniwire improving their workflow? I really want to believe that it can be useful, but I just haven't been able to produce my own evidence.

Jason Staczek
www.chromasound.net

[jstaczek]

Still looking for anyone willing to report a real-world experience of how Uniwire improves workflow. Any takers? Please, make me a convert...

Jason Staczek
www.chromasound.net