Oh brother...an OSX fanboi.....

All platforms have their issues...

or a windows hater.

tbh some of the 'Apple is going to lose the pro line' seems, you know, hopeful. How long has it been since they made the 12-core now? I don't keep up, I feel future proof for a while with my octocore and 24GB with VE Pro on a slave. Those VSL devs swear up and down it's better performance on windows. 'the pitfalls of the OSX kernel', like that. They're smart fellows and I guess they know their shit. I don't love Apple really. But I hated windows enough to throw some money at that as though a problem to avoid. I don't mind if you think it's the shit.

Some despise the Mac platform to an extreme as if it's hurting them that people will throw money at a Mac. I've worked with both, I'd rather have the low maintenance and I like the directory structure better.

this would make an interesting anthropological study, wouldn't it.

some say that DP has a lot of legacy code that makes things clunky. I have it installed here but it hates VEP or VEP hates it so I have basically never used it. Part of this, interesting development could be that there is an opportunity to recode it more from the ground up.

I've heard that it has been completed recoded from the ground up.

+1

DP8 has been rewritten from the ground on up,all new coding, this is now a cocoa app not carbon.

Other people seem to love VE Pro and DP, something uniquely wrong there it seems?

It's called teh "we're f**king with your computer gnome" and is lurking to get onto your hard drives! (I experience this with studio one)

I never tried it. There are so many reports of problems that are common to various systems.

I use it connected to Cubase; there is one overarching reason: AU protocol allows one MIDI port per instance. VST 3 does not have this restriction. Now, VEP allows 48 ports (x16 channels)!.
But there is a workaround, at least for Logic. It's somewhat a PITA but it apparently works. They were going to do something for MAS but it never happened.

I bought DP and Logic because my latency with Cubase was too high. By far. But VEP gets rid of that probelem as far as I'm concerned.

EG:

"At this point, bouncing does not work for the new Audio/Event Input plugins unfortunately. It still works perfectly when working with just the main VE Pro plugin like in VE Pro 4 of course (nothing changes there). I'll do my best to get it fixed as soon as possible."

To avoid any confusion: This only applies to DP.
Karel Bassez
Software Engineer
Vienna Symphonic Library GmbH

"Well, I'm kind of sorry to aknowledge that the VSL's DP user base is so little that your beta test team didn't feel the urge to try one of the basic function of this DAW."

PLEASE tell me more...

are you talking about cubase having to run at higher latencies on osx to not click/pop and be more stable in cpu usage area?

Does VEP improve this really? how? i am extremely curious

yes, I mean just that.

VE Pro is its own process, if you run it as local host on the same machine. Cubase is not processing the plugins that VEP is, therefore is less busy, it just has a lighter load; following that the sound card is looking at a different situation.

another factor is the latency compensation of VE Pro is fantastic. The recommended usage, the developer recommends, you set the VE Pro interface to 'x2' which triples the latency of the DAW host where you set your latency as low as you can. It DOES compensate for that latency extremely well, the latency you do have is less unpredictable.

I honestly did not have enough of a gain in this respect as local host, even on the octocore I now use as slave, to the degree of satisfaction to keep me on Cubase, which is just too slow on Mac. But projects were more stable and there was less freezing of tracks, etc.

I use it via LAN on a slave and I no longer have any reason to go to Logic or DP to get around the Cubase latency.
For most things I'm using 128 samples in the buffer with that x2 setting and I can depend on things landing on time in the piano roll very well. I mean with a LOT of instruments and FX, a full-on mixing scenario. I haven't freezed tracks since I started using it this way. Some things, really intensive Absynth things I built with ridiculous long envelopes, I have to increase latency for, but this is pretty exceptional.

I've had some drumming I needed to get down to 64 samples for and I can't have a lot of instruments connected to do that. But, the compensation of their own latency is about perfect. I don't have Cubase do any compensation, I actually got things landing on the timeline ahead of time and not that predictably using both.

Using the two hosts decoupled, I can have large templates up and only connect to what I need to, and get that super low latency such as that 64 samples/buffering. I'm likely to get spinning beach ball on the VEP machine from interacting with the GUI during playback long long before I have a problem with playback. Genearally 128 in the buffer is my setting and the combined latency reads <10ms and my timing is reliable with completely clean audio. One project, everything I need is up at one time. I don't bounce, everything is running simultaneously.

And both hosts are stable. Now that VEP 5 will read automation for plugin parameters (VEP 4 will read them for volume and sends levels, its mixer, and of course an instrument reads its midi automation) I plug practically nothing into Cubase.

So you've never tried it but you heard stuff on the internet about it not working for people...
As a Cubase user you should be aware that the internet is not the place to decide on which platform is a working platform. Otherwise you would never be using the bug ridden crashing POS that is Cubase according to every forum out there!

VE Pro itself actually has built in support for more than 16 MIDI channels with AU plug ins, it's not a PITA so that problem is moot.

You mentioned a new feature they haven't figured out a bug for, well that IMO is not a reason to think DP doesn't work with VE Pro, especially if you've never tried it yourself.

why are you having at me? I only posted that quote (quoting THE DEVELOPER, not a rumor) because you suggested I was having a problem with DP that was particular to my system after I said I never used it, to explain why I didn't. You are characterizing what i said inaccurately, I did not say it does not work. Later I showed one example of why I would think, based on my reading, on a forum I frequented especially in the early days of this product, not to bother with it with DP; particularly since it works GREAT for me with Cubase.

The VSL forum is addressed on a regular basis by the very engineers that code the thing. Logically, 'every forum out there' does not equate to the situation I mentioned.

I mentioned in my own post that VE Pro, as VST3, does not have the MIDI port limitation, as it does with the AU protocol. Until VE Pro 5, VE Pro was subject to the AU protocol limitation. VEP 4 is. These are factual statements, and that there is a workaround for Logic now is a fact. For other plugins there is still the AU protocol limitation of one MIDI port.
Last edited by jancivil on Wed Jan 25, 2012 1:46 pm; edited 2 times in total

it is not moot. A single instance of VEP as VST3 has more than one, I think VEP 4 could go to 32 but I go with 16 MIDI ports. A single instance of VEP 4 as AU can have but the one midi port. That is a factual statement. Outside of VEP 5, AU cannot use but the one MIDI port per plugin instance. Fact. If one wants more than one port per instance, this is not a moot point.

So, you don't even know what you're talking about.

I decided for me it wasn't worth spending time on, based on THE VSL FORUM, eg reproduced situations on more than one system. I suggest you refrain from concocting narratives about what happened with another person.