Vienna Symphonic Library Forum
Forum Statistics

194,269 users have contributed to 42,914 threads and 257,946 posts.

In the past 24 hours, we have 2 new thread(s), 18 new post(s) and 88 new user(s).

  • Well, as you say, it turns out that it does work pretty well on one slave machine if you set Wormhole's buffer to 0 on the sending machine and - realistically - about 600 samples on the receiving one (I was getting crackles at lower settings and lots of voices when I played a harp). That gets the latency down to a reasonable level - still noticeable compared to an audio interface but not out of the question.

    I'm going to have to try it with four of them (for eight outputs) and see how that does. It's good to see that it might work with for one slave machine.

    This test was with...dare I say EWQLSO Platinum Pro on the slave, which is the toughest test of all since it has all those release samples ringing and eating up voices.

  • So I have a few questions.

    I am currently running Logic 6.4.3 (MOTU 240[H] to host my VIs and EX24s but after 5 string VIs and 4 woodwind VIs logic is out of juice.

    I have a dual 2.5 G5 maxed out with 8 gigs of ram.

    Can I run RAX along side of logic and squeeze out a few more instances of VI?

    I was thinking of loading DP on this machine and using that as a host when I stumbled on this thread.

    I use DP as my sequencer (MOTU 82[H] on my main mac and Logic as the slave

    thanks

  • VI uses it's own ram pool, which is external to the sequencer it's running under. Once you reach about 3GB of samples, you can't load more on that computer (except if you use the Stand Alone trick, which has its own limitations).

    If your problem is a CPU one, loading samples in another app won't change much either.

    Jerome

  • well, the only limitation is that the player can't access individual outputs. I actually wonder whether Rax or Kore the problem. Can you run the Vienna Instruments plug-in simultaneously in two hosts on the same machine?

    I'll try Kore later today when I get back in.

    You know, I enjoy this silly stuff just a little bit too much...

  • so i decided to experiment.

    i can in fact run Logic 6.4.3 with 5 VIs (violin 1, violin 2, violas, celli and basses)
    and RAX handling 5 VIs (flute, oboe, clarinet, bassoon and bass clarinet)

    RAX doesn't give you an audio output option but it doesn't seem to affect my audio in Logic.

    i'm trying different things but it does seem to help splitting things.

    Logic would crash when i tried to load that last VI (bass clarinet)
    now i can by using rax for the woodwinds

    oh, i'm just using the RAX demo as i am trying to decide on whether it'll do what i am trying to do. it's looking very, very promising!! simplicity is nice.

  • The VST plug-in shows up in Kore when you launch it after loading the AU one in Logic (the AU one doesn't). Kore itself takes up about 20% CPU (which isn't really 20% since there are two processors) and about 62MB, but it seems to work fine. And it certainly solves the output problem.

    So I was able to load Vienna Instruments plug-ins in Logic and Kore while running a stand-alone player too.

  • After having Kore re-scan all my plug-ins, both AU and VST plug-ins show up. You can run AU inside Logic, and AU and VST in Kore at the same time no problem.

    ...except it looks like there's only one VSL server running, so there goes the memory access benefit. I think, anyway - that's one more thing to investigate.

  • i'm still testing as well. i also downloaded the demo for Plogue Bidule. Is either RAX or Bidule any better than the other as far as simple hosting goes?
    i had RAX up and running in about 3 minutes. Bidule is another story.

    i just need a place to hold my VIs.

  • Rax:
    good if you dont care about accessing multiple inputs
    Easy UI

    Ploque Bidule:
    multiple, flexible and assignable outputs
    takes a lil more to understand to setup things, but is very very easy once you figure it out



    Nick and homebilly, remember that the VI plugin is actually running in the background even if you open it inside your DAW, and will always access the VSL server app for memory access, no matter how many instances you open in various hosts/squencers. Only exception to my knowledge is the standalone VI workaround (renaming copied instances).

    Btw Nick, do you say that if you open up multiple VIs inside KORE you will be able to route the outputs of them to multiple channels, ie. having them streamed into Logic from the background?

  • in reality what i am researching is the future use of mac mini slaves and not havig to use logic. already i have found that using the VIs in RAX leaves me free of Logic until i need something that is not VI as in EXS.

    what i can't figure out is if RAX is a pro app or not in terms of level. it seems that my VIs are coming out at a lower volume than the same VIs in Logic. could it be that it is wired for -10 and not +4 before it hits the hardware?

    i'll mess with RAX again today taking a VI and playing a sequenced line from my DP mac and then playing it in Logic then RAX to see what the story is.

    other than that i am digging RAX. Bidule is a bit of a chore to set up, a bit like Logic.......?, but i want to check it out. if anyone has a template for me to check out i'd love to see it. thanks

    ron

  • Yes Vagn, that's what I thought in my last post: multiple hosts don't help access more memory (although they do make things easier to deal with in some ways).

    The answer to the other question is yes - the host routes the player to its outputs. If you're using Soundflower as the audio interface, you have 16 outputs.

  • last edited
    last edited

    @rpmusic said:



    So there you have it....unfortunately this is not a viable solution anymore. Guess us Mac guys have to wait or FX-Teleport (which I got an email form Andy at FX in which he wrote: Hi Rob,

    We really hope to ship it early next year. Be sure to sub to our news update
    at www.fx-max.com (if you've not done so already [:)] ).

    Best,

    Andy).

    Rob


    I really hope that FXT will actually be released for mac, but I'm not holding my breath as I received almost the exact same email from Andy last year and subsequent promises throughout this year that they were only a couple months away.
    Unfortunately audio interfaces are the only viable solution so far.
    Keep your fingers crossed though.

  • Thx Nick.

    Homebilly: u are talking analog when it's actually digital. As long as it's inside the box, the signal will have 0 dBFS as the upper limit, and only when it hits an analog output will it get transformed to the analog specification of the output it's routed to.

    So to make it simple, Rax should have no influence on signal level. The output you choose should be the factor determining the signal level, ie. routing it to the built in Mac output will conform the signal to -10dB consumer level.

  • what i am saying is that when i play the same VI flute in Logic and then in RAX. RAX is considerably softer in volume. they are both going out the same output.

    on the RAX forum thread someone else has asked the same question and i have an email in to the plasq guys. the mystery will be solved soon.

  • Thats strange Homebilly, as I haven't experienced that problem. What ouput are you routing to?

  • i'm using the ADAT 1 & 2 outs on a MOTU 2408 mkII
    routed back into my main mac

    i'm going to try some other tests. I really like how simple, in a good way, RAX is. load and go.

    I have a feeling that i will have to get my head around Bidule in order to accees the rest of my ram though.

  • so here is an audio file of the two programs playing the same sound.

    i played a whole note on one track then duplicated it a measure later on another track. there is a CC#7 of 100 on both tracks and the velocity is 127 for both.
    this way i know that they are identical.

    i printed back into DP and made this file. there is a clear volume difference.

    http://ronmeza.com/VI-TEST/Logic-RAX%20volume%20test.mp3

  • Big difference indeed. [:(]