Hello!
I'm on a mac (OS 10,4,11) running DP and VE2. it's all been working smoothly. However, instead of waiting for all those load up times on every film q, I want to run it as a standalone application instead. Can someone run me through, in baby terms what i need to do?! I've read the manual, but can't find anything on setting up standalone...
So far, I've:
launched standalone and loaded up instruments
in midi preferences I set it to input network:1
in DP i assign midi channel 1 to network-1
should this then work or am i missing a step, as I can't make a working midi connection through it at the moment?
Sorry for the basic questions!
-
very basic help with setting up VE 2 standalone
-
If you're running on the same machine then you want to use the IAC for midi, not the Network. Midi channels are set in each instrument, not in the preferences. I'm using it in standalone on a second computer and enjoying it. However, I had to duplicate the VE2 application and put the strings on one instance and the winds on another due to memory limitations.
-
Another point about using the standalone on the same computer as your DAW:
You need some means of looping audio back from the standalone to your DAW. If one has an RME or Apogee Symphony card based (this does not work with non Symphony card Apogee interfaces such its Ensemble or Duet) audio interface, this can be accomplished with the I/O routing software that accompanies these interfaces. Theoretically you could also do this by using VE3 in local host mode, but then you would be limited to approx. 2.75 GB of samples - - as multiple instances of the 32bit version of VE3 inhabit the same memory partition, whereas multiple instances of the VE2 standalone inhabit separate memory partitions.
I use a simple hardware loopback: I run an ADAT cable from the ADAT output of Bank C to the ADAT input of Bank B of my MOTU 2408. Then, in Logic, I create an AUX channel whose inputs are assigned to Channels 9-10 (the first two channels of Bank B) and whose outputs are Channels 1-2 (Bank A). The drawback to this scheme is that it introduces significant latency. However, in Logic, inserting the I/O helper plugin (meant for live performance) into the AUX channel strip reduces latency to a reasonable level. I don't know if DP has a similar plugin.
Forum participant and publisher of Virtual Instruments magazine, Nick Batzdorf, has reported success using Cyling 74's SoundFlower, a freeware virtual audio interface, for this purpose. However, I and at least one colleague of mine have tried SoundFlower and noted frequent and random digital artifacts during playback when SoundFlower is used. At first I attributed to this to the fact that I am working on a now outdated dual 2.5GHz G5, but my colleague is working on a 8 core 3.0GHz MacPro.
-
Steve: A couple of questions. Does Jack X work on Leopard and is it another option instead of sunflower? 2408mkIII seems a good path to go. Isn't there internal routing through MOTU software included? Do you believe this loopback methoud would also work with a Prosonus or m-audio lightpipe box (such as the bridge), or is FW latency an issue with these devices...e.g...would IO puggin help make these an alternative solution to 2408?
-
I could not figure out or get OSXJack to work at all. In my opinion, its human interface design leaves a lot to be desired. Supposedly it "works" in Leopard - - but I know no one who has had success with it - - one friend did get it to "work," but, as with SoundFlower, on his system it produced freqent digital artifacts.
I have no personal experience with PreSonus or M-Audio audio interfaces. The PreSonus LightPipe box looks like it might work since it appears to have 4 ADAT ins and outs + a summing mixer and volume control for your main monitors and for earphones. Also, you don't have to pay for mic preamps - - which you won't need if the only use of the interface is for virtual instruments or audio editing rather than live recording. I don't think it has a software loopback feature - - but you should correspond with their technical support people regarding any questions you might have.
Regarding the 2408, I asked MOTU if they had plans for a software update that would allow loopback in software and they stated that it was extremely unlikely that they would ever release such software for the 2408. (It's always possible - - although there is no reason to believe that such a thing is, in any way, imminent - - that they will release a new card based audio interface with this feature.) If you don't have an audio interface and want to have loopback via software, you might consider the RME's FireFace 400, FireFace 800 or HDSPe PCIe card with a MultiFace II converter box. Although not cheap, they are less expensive than the Apogee Symphony card based systems. The TotalMix software that accompanies RME interfaces reportedly provides routing of any output to any input. No doubt latency is slightly greater via FireWire, but you are eliminating the kind of latency that my setup introduces.
-
this is all great, thanks guys. can't quite work out this IAC though, so i'm running it inside DP as a plug-in at the moment. so if i want to use it as a standalone, how do i set up the IAC? I went to audio/midi preferences on the mac, clicked on IAC driver, made it online. it says IAC Bus 1, midi 1, midi out 1 (these are unchangeable). However, if I then record enable IAC midi channel 1 in DP, it tells me that I can't do this as it would create a midi loop. So what do i need to do on the midi side? (audio will be fine - i've got 2408's, etc)
-
I got jackosx working on leopard. Didn't have much problem. Bit tricky because instructions are short on what an aggregage device is. To think it sinply, If you think of Jackosx as a server, the clients are the sound cards etc and your applications. Jackosx sits in the middle as a conduit to them all sending audio this way and that way based on how you have set up a patch in it.
Jackosx only has one place for hardware clients e.g. your sound cards etc as apart of the system. In osx leopard, because ins are separate from outs, you need to create whats called an aggregate device. An aggregate device is simply a virtual device that you can assign many hardware or system ins and outs to, so it looks like a single device that jackosx can use.
Once you set this up, the rest is just defining how many ports you want to use for all your applications and then mapping inputs to outputs. You choose Jackosx as an audio driver inside any applications you want to employ it in. Others can route to CoreAudio as they do now.
JackOSX also allows you to use their AU plugin to perform a SEND from your mixer to Jackosx as an additional output. I wish the had a similar INSERT return which could allow audio to come into the AU.
Works pretty well. I havent used it on anything big. However, its free,
Remember though, its a daemon which is pulling processor. Depending on your machine, it may chunk some cycles. Hecnce getting a sound card might mak ethe most sense. However, I didn't feel like spending $1200 on a RME HDSPe PCI + Digiface.
As for IAC, each bus is a synonym for a midi PORT - 16 channels each. Rather than turning iIAC driver on and adding additional buses in the setup (for teh number of MIDI ports you need), I created a new "configuration" which allows me to save different midi situations. After adding the number of MIDI ports (Buses) I need, I switch IAC driver on, In my applications these can be enabled as IN or OUT MIDI ports. For example, ito use it with VSL and Sibelius. First i enable the Bus1 as an output device in Sibelius. I launch an instance of VE2 and set the MIDI setup to accept Bus1 In each instrument I choose BUs1 and teh channel it should listen on. Thats it. Side note. In Sibelius, VSL soundsets will not show up for VSL unless they are edited and redefined to MIDI. This is a quick patch to one of the tags in that XML file. You might also check out MIDI Patch Bay application. I am not sure how it will work with VSL http://pete.yandell.com/software/midipatchbay/Read%20Me.html