197,312 users have contributed to 43,059 threads and 258,564 posts.
In the past 24 hours, we have 1 new thread(s), 15 new post(s) and 85 new user(s).
Ray:
It would be extremely helpful to other forum participants if you would write step by step directions for configuring and using Jack OSX - - going through each setting and dialog box. If you have the time and inclination, I think many here would be most appreciative of your effort.
Stephen
FYI, they have a beta download at their Yahoo club site, and I'm happy to say that is works with multiple instances of VE (audio and midi). I even tried to play about 40+tracks all at once and it doesn't top out on CPU yet.
Still, since I have the ability I'm going for optic out/in since it'll eliminate a 3rd party app like that.
Sure, and when you do that write up, don't miss teh following that I spent hours finding out lol
1. If you are using Logic, you must set buffer size to 1024 on both Jack and Logic, or else audio will stutter.
2. When selecting IAC ports in VE. If you run multiple instances, you must have all 4 selected in the options, and then just pick which one you need in the popup. This is because VE regardless of what copy, keeps the same settings in the preferences. So if you make one VE instance copy for IAC 1, and select JUST that in preferences. It will show up the same settings in your next copy
3. Unless I"m mistaken, your pretty much forced to use a record enabled track in Logic to get the audio from VE standalone. Just record enable, and track protect the track so it doesn't unrecord enable itself when you select the MIDI tracks.
Everything else worked for me.
Ray
Many thanks for your advice. I'm going to try and give the VE Standalone scenario a run-through today.
Unfortunately it seems others are finding even the standalone VE introduces greatly increased CPU overhead (compared to the VI plugins) which is causing audio glitching in some cases, so I guess this may be another solution which still needs some refining by VSL.
The other thing that ocurred to me is that I actually don't need to route my standalone VE outputs back into Logic, as I actually mix outside Logic. Persumably this means I can just run the VE standalone outputs to whatever physical outputs I want to use, and just avoid using those outputs in Logic. This assumes Logic and VE are able to share hardware, which must be the case.
Jules
Yeah, It's not perfect Jules, but it's so promising!. I have noticed glitches as more instruments are used, but it's not apparent if this is caused by latency, bandwidth, Logic 8 or something else.Personally i feel a little silly for going to Logic 8 so soon-Maybe all will be fixed with 8.1. .I thought VI was a towering work of genius when it appeared first, and now with VE it's a classic setup with a number of small, hopefully fixable issues. I think you might be onto a good thing if you don't mix in Logic-VE will see all your hardware outputs if setup right- Ray@Trailerman said:
Ray
Many thanks for your advice. I'm going to try and give the VE Standalone scenario a run-through today.
Unfortunately it seems others are finding even the standalone VE introduces greatly increased CPU overhead (compared to the VI plugins) which is causing audio glitching in some cases, so I guess this may be another solution which still needs some refining by VSL.
The other thing that ocurred to me is that I actually don't need to route my standalone VE outputs back into Logic, as I actually mix outside Logic. Persumably this means I can just run the VE standalone outputs to whatever physical outputs I want to use, and just avoid using those outputs in Logic. This assumes Logic and VE are able to share hardware, which must be the case.
Jules
Hi Ray
It's certainly promising, but still a few weird things going on here.
First, when I launch Vienna Ensemble standalone, it takes 3 minutes 30 seconds to load, with nothing but the little VE splashscreen visible. Don't know why it takes so long - Logic (7.2.3) itself launches in about 20 seconds, despite scanning presumably the same list of plugins (of which there are very few on this system). Can't help feeling some people would have given up after a couple of minutes and force-quit.
After that it works pretty much as you describe. Setting up MIDI routing is a snap (although I did need to terminate my IAC ports), and I can freely route audio out of whichever hardware outputs I want (not quite true - it only shows 32 out of 64 outputs on this system, but I can live with that).
However, the CPU and memory usage (at least according to Activity Monitor) is all over the place. If I load around 400MB of samples, VE uses more than double that amount. Every time I load an additional matrix, VE seems to grab an extra chunk of RAM for some reason. It also seems to use significanlty more CPU than the Logic/VI combination, with just two simple parts requiring around 30%, where the Logic/VI combination uses around 80% for 12 parts. Not exactly scientific I appreciate, but it's certainly using more CPU than the the VI plugins, or appears to be.
Nonetheless, this looks like a great way of loading perhaps an extra 5 or 6 instruments when you've maxed out the amount of ram that the VI plugins alone can use.
Thanks again for all your help with this
Jules
Mac Pro (8Core), 8GB Ram, OS 10.4.10, Logic 7.2.3, MOTU PCIe-424
PS. No idea how I managed to change the font to Times NR, but turning it back is way beyond me.
Clearly somebody at VSL has sabotaged the forum server to make us both look like idiots [:D]
I take your point on the workflow benefits of VE. I'm sure it's going to be great once they iron out a few quirks.
Incidentally, I see no latency (literally) when I route VE straight out of my hardware and not back into Logic. I can set the latency setting in the VE preferences right down to 64 samples, and it runs fine, and is extremely responsive - possibly even more responsive than using the VE or VI plugins. I guess this suggests that the latency is occuring as audio is routed back into Logic. Presumably your Audio Inputs in Logic are subject to Automatic Delay Compensation, and so will be delayed by the equivalent of the 'slowest' (most delayed) track in your mix - which if you're using Altiverb and the like, will be pretty latency-heavy.
All the best
Jules
If I understand correctly, Logic takes the track with the most latency in your entire mix, and then delays all the other tracks by that amount, in order to apply automatic delay compensation. As a result, if you have any plugins in your mix which introduce latency, everything else will be delayed as a result. Not an issue with normal audio and MIDI tracks (Logic probably bypasses ADC when the transport is static anyway), but for your audio input tracks, Logic is having to delay them all the time at the mix's maximum latency, because they are 'live' all the time.
I can't believe I just explained that so badly!!
My suspicion is that your Powercore Reverb will introduce a LOT of latency. Most DSP based effects introduce even more latency than native effects, because the audio has to be routed to the device in question via the PCI or Firewire bus, and then back into 'native' land. I use a Powercore Firewire and also use UAD-1 cards - tha latter introduce huge amounts of latency - depending on the host often twice the host buffer setting or more.
The best way to test whether it's ADC causing the latency problem is just to disable it in Logic (in Audio Settings or Audio Hardware Settings from memory), and see if the latency improves. If it doesn't then the issue must be elsewhere, and given that VE is so responsive when routed direct to hardware, that suggests the issue must be with Jack OSX.
I route my entire Logic mixes into ProTools HD on a different system, via 64 channels of lightpipe, and then mix in ProTools in real-time (ie. with the arrangement still running in Logic). I just happen to like the ProTools mixer, have lots of plugins on that machine and have just always worked that way.
All the best
Jules