196,523 users have contributed to 43,021 threads and 258,416 posts.
In the past 24 hours, we have 4 new thread(s), 7 new post(s) and 111 new user(s).
Good questions.
I guess that you will still need MOL and an audio card on the slave, unless you use FXT. If it did audio and MIDI over LAN, cross-platform I would have thought that VSL would have been trumpeting that fact by now. However, I have been known to be wrong.
BTW Does Receptor actually send audio? It never used to.
DG
So if you're using this stand alone, you'll still need a MIDI yoke right? Are there any 64-bit MIDI yokes out there right now? Does MIDI over LAN work in 64-bit?
I have a feeling this won't work, DG, as it sounds as though the VE uses a client-server model, like the VI on OS X. So multiple standalones of the VE would not launch multiple servers... I'm not sure about this, of course, but from what I understand, they've made the new VI (2.0) VST/AU use host-based memory (as it already did on Windows), and the VE use "vsl-server"-based memory. The idea being that you can access double the RAM on 32-bit systems (well, OS X anyway, since xp standard can only ever access 3GB) by maxing out the hosts memory with VI instances, and maxing out the VE server as well. On 32-bit OS X, that would give you 3.x GB in the host and 3.x GB in the vsl-server (or whatever they call it). And what's cool about the new model (again, if I'm understanding it correctly), is that you could load VE instances **as VSTs** and still be loading up memory external to your host. This way, with a mix of VI and VE instances (all VSTs), you'd get your 7-ish GB of RAM loaded, and still be running all the audio from within your host app! But what I really don't understand is where the VE Standalone loads its memory. Is it another separate process, like the old VI Standalone, or does it also load to the vsl-server??? Of course, the real point is to just go 64-bit asap, and solve the problem in one go.... But we OS X folks are going to have to wait on that. Thanks, Apple... --- J.@DG said:
Well, out some time in October. Probably *very* near the end of the month. But they're not making any noises about more delays, so I do think we'll see it in October. However, the problem with Apple and 64-bit is that they apparently got rid of a framework that VSL was using for their 64-bit support. From what I understand, frameworks are small, dynamically loaded files, so I'm not quite sure why Apple wouldn't just let VSL install the framework as part of their VE installer... (??) Dunno. But the point is that VSL now has to adapt their 64-bit support for Leopard to some new Apple framework. This won't mean a complete re-write, I don't think, but it could be a nightmare of refactoring, and then, of course, testing... And speaking of testing... 😉 ---J.@Simsy said:
I thought that leopard was supposed to be out at the start of october?
No, no, no! Please, no... I'm absolutely dying for this app... It seems like the beta program has been delayed, or maybe even cancelled, but I really hope they don't delay the release. It would be very odd for a company to specify an actual day, and not deliver. So, I doubt the release is delayed. But, considering that 1) it's a host for VI, and VI alone, and 2) it's free, they may not be in such desperate need for a beta program after all. ---J.@Christian Marcussen said:
So.... can we assume the release date is delayed?
I guess what you are asking makes sense, but I think that it would be a little bit complicated to do. Perhaps a re-learn feature, where you play the tracks, and VE checks which notes are changed, if any, and then loads the appropriate samples.
However, this features would only be quicker if there was a global learn and re-learn button, as in most cases it would probably be quicker to load the whole instruments than to play the track!
DG