VSL team, 

I'm curious about the performance difference between mac and PC with VEP pro.

Has the gap closed? or does pc still outperform mac os?  If so, are there any benchmarks available.

(note to forum members. I'm well aware of the common thinking on this but the data I've found is several years old at this point. I'd like to know what the current performance variance is comparing Mac 10.10 vs windows 7 pro)

Thanks!!!

Same with me.

Constant crashes DP 8 with 5.4.13682

rig was stable under old VEP.

Seems to be as the VEP template gets larger, crashes started occuring.

Sent support an email.

Love you guys - but this one sucked boiled eggs. Lost a lot of time dealing with it.

Gents,

had DP setup and working great with VEPro

Went to open a new file and suddenly none of the VEPro midi ports show up. Nadda. Zippo

Old files that were previously setup with VEpro work fine.
New Files are blind and don't see vepro at all.

Stumped and on a deadline.
Any help greatly appreciated

I received the offer to extend the upgrade by three months.

Unfortunately I can't justify the $5K+ by october.

Allowing a year would be the right thing to do imho and its worth at least my $5k to the VSL bank account to do so.
Herb - just as a practical matter you may want to consider the lifetime cost of losing customers such as myself.

By eliminating my upgrade path you run the real risk of eliminating me as a customer and with past being prologue I am worth at least $6000 to you over the next couple years.
I can't jump and upgrade in six months but can and would in a year and it seems that there are more than a few of us in that same boat.
10 guys equals $60K. Seems worth keeping the upgrade path going for another year.
Not to mention the simple good will you would garner.

This idea would solve the problem in my case.
Since we all pay the full price for the standard VI the issue is unlocking the extended set (which is what the VIP offer currently is).

When a Pro Edition owner is ready to make the move - one email to customer support and they setup the unlocking of the extended.

I'm sure its not quite that simple but its what we were promised when we bought the Pro Edition.
All I am asking is to not have that portion of my purchase revoked on July 15th.

Herb and all at VSL,



I was an early adopter. First edition. Made the big upgrade to the Full Pro Edition.


Love your libs and have been an evangelist for them.


When the VIP agreement changed upon the release of the VI edition my impression of VSL soured a great deal. Over time this impressioned softened and I decided to make the move the VI edition once things looked stable on the latest mac-intels. Understandably it took VSL time to fully realize the VI on the mac platform and it seems to be "there" at this point so I was planning out the expense involved in this upgrade only to stop by the forum a few days ago and see this thread.



Needless to say I find the termination of my VIP upgrade options objectionable.
I was counting on this upgrade path to the point that I acutally purchased horizon titles that I have not even installed or registered (time and HD space are personal issues), buying them mostly to avail myself of the upgrade discounts. Upgrade discounts that I will now lose in two and half months.


I respectfully request VSL honor the original VIP upgrade path as it was promised when I purchased the Pro Edition and the Horizon titles as it will take more than two and half months for me have both the funds and time to purchase and install the new software.



kind regards,
Ed Hamilton

any update on this????

From all reports is seems that Ram will limit you before the CPU will.
So until 64 bit osx (and shitloads of ram) it looks like the octocore is overkill for sample farm use.
I haven't heard of anyone maxing out the CPU on a quad core macpro.
Scary.

Appleinsider had been more right than wrong for awhile now.
Mostly because the don't go out on any limbs.

macosrumors is nearly dead and mostly wrong.
macrumors makes few predictions themselves as they mostly copy and link any dumb ass thing posted anywhere on the web.

Nick - please stop bestowing us with "nasty" posts and focus on giving us (your subscribers) 12 full issues each year!
The friggin wait in between issues is driving me crazy - especially now that keyboard mag is only about 10 pages cover to cover these days. (I play the b'way pits for a living and the lastest keyboard issue didn't even get me through one damn show - I ended up actually having nothing to do but pay attention the that guy waving that stick).[]

Mac Mini's looks to be discontinued
http://www.appleinsider.com/articles/07/05/24/closing_the_book_on_apples_mac_mini.html

I had been waiting and hoping for the new generation of mini's but alas it looks not to be.

Maya - would it be possible to do some deep testing of your Macpro as a VSL Farm? (as in not also hosting the sequencer - just using it as a slave farm PC).
It looks like the macpro is going to be our only sample farm option if we want to stay mac only.
THANKS!

Wasn't this the bug ????

If you do a search you will find a ton of posts about G5's not working as farm pc's and I don't recall anyone from VSL saying that the bug was fixed.
Maybe it was ........

JWL - that's an awesome post.

Andrew - don't over look his isight removal tip.
It's an oldie but apparantly still a good one.
The isight driver used to cause all manner of weird issues.

First - make sure you have the latest build of DP5. If you recently bought it off the shelf it sould be 5.01 which has issues with the later tiger builds.
I haven't heard of any issues with DP on the octocore but 5.12 is probably a must.

Second - M audio interfaces have been a nightmare for me. Utter total crap.
M audio drivers are weak at best and really problematic for any other daws (than Pro Tools m powered). They are the worst I have ever run into.

With the later DP revs and a good interface (rme/motu etc) your system will be incredible.

Chris K,

Would it be possible to continue this thread with the update you offered?
Would be greatly appreciated.


basically a macpro in that configuration is equal to the cost of three self assembled shuttle pc's.

Would the macpro equal the performance of the three shuttles?
Looks like it might and thats a trade off I'd go for.

Ding Ding Ding -
Correct answer.

7.1 no workie on Intel.
Send apple $49 for 7.2 and you will be stunned at how much you can get running on a macbook pro.

I've been sitting on the fence waiting for the next macbook pro refresh but spent a day at the apple store. They had one macbook loaded with "Pro" apps (finalcut pro, logic pro etc.).
Track after track with dense drawn in midi with excessive drawn in controller data. track after track of sculpture's with insane midi data, convolution verbs, not to mention hacking up the demo songs audio into tiny chunks and scrambeling them all over the project to try and make the hard drive bark.

I finally got there but it was pretty clear the macbook was a step past what my dual 2.5 G5 could handle.

Remember all the VSL protestations that "their are no plans to release a VI version of Opus 1-2" ????

This special edition looks pretty close and even better in some respects.

Thanks for that reply.
Are the mini's ok now in OSX or is it bootcamp only?

thanks again!

Where does this issue stand at the moment?

I'm debating using G5 towers as VSL farms or moving to mac minis.
Seems like the G5 makes sense (one audio interface and lots of cheap ram) but this issue is a potential problem.

So just for clarifications sake -
Does a G5 running osx have a problem hosting VI's when used as a slave ?
Is there a particular version of OSX that gets better/worse results?

Thanks !

If anyone at VSL is interested - this issue is the last one that keeps from updating my pro edition to the Cube.
The list of bugs that gave me pause has improved (DP bug, OSX slave, load times etc).
It all looks pretty good at this point. All except the limitations on licenses.

The posters here have all made excellent points. This issue should be re-thought.

RIKP - re loading a project is not the problem so what your are describing does not address what this bug is.
Try bouncing a VI track to an audio track - does the vi retain its presets ??

Hello to all at VSL.

I remember that there was some sort of deadline for Pro Edition owners to upgrade to the VI and get the appassionatta strings as a bonus.

Is there a deadline?

I ask because in my case the VI is not yet a stable working solution as of yet (DP user and my slave machines are Mac OSX so I run into both issues).

The quick demo's that were done using the appassionatta strings are excellent (are there any more official demo's??) and I look forward to eventually having them in my template.

thanks!

JWL - I just read a couple threads about your syncrosoft issues and install problems.

Dude, you have the patients of a saint and I'm sorry if I seemed argumentative with you even a tiny bit!

May your syncrosoft/DP/install issues be solved soon!

JWL - agreed on all points.

Your last point about "substantial investment" is an interesting one.
It used to be that we invested a few hundred bucks and ALOT of time in our sequencers. When studiovision died it was a drag that many had to invest a ton of time learning a new sequencer but financially it was only a few hundred bucks lost.
And our hardware synths/samplers/mixers/effects all worked together as advertised and actually had a resale value.

Now we all have a huge investment in software that has no resale value and from time to time no longer works together!
We are at the mercy of the developers to maintain an impossible compatibility list to make our software work for us.
Add in things like Apple moving to Intel and ..... wow.... tough job.

In many ways VSL deserves kudos for the VI. For a version 1 app things have gone pretty well with the software itself. Factor in how innovative it is and it looks like quite an achievement.
The synchrosoft problems are a disaster and its a shame that it has undoubtedly hindered wider adoption of the VI. Even with the improved (faster) load times it still concerns me.

But I have to give VSL a pass on the VI's problems in DP. Its still a version one app and while I am bummed that the VI has a problem with my prefered daw I am sure they will work it out in due course.

But any info VSL could give as to a timetable for a fix would be most welcome! []

It's assumed that when a manufacturer announces that their VI will work on a DAW it should really work.
If it has problems on a certain host its seems strange to them blame the DAW.

Clearly there are grey areas in the AU VI spec that can result in compatibility problems.
But I have not heard of Apple going out of their way to make logic more hospitible to VI's that had logic issues. The VI maker had to solve the issue.
In fact Apple changes the AU spec - releases a new logic version and forces Plug makers to deal with it.

Same should apply to VI's that support Motu.

So are you suggesting that Motu should actually change their code to suit the one VI that has a bizarre problem. In fact its the only plug I have ever heard of that loses its presets after bouncing.
And IF motu were to change code to suit VSL VI - what happens when the new code causes problems for other VI's that were previously stable?

I'm not being argumentitive here. I think motu is an arrogant company and their tech support kids are shmuckheads sometimes but at least THEY HAVE tech support.(miss you logic support guys!)

Point of fact that I agree with you that motu should bend over backwards to help plug makers in every way possible.
Motu is in third place (PT, Logic) and should always be worried that sometimes the third place company ends up not finishing the race.
Motu should works is butt off to be the most stable DAW in the market and the most stable with ever VI and plug out there. That would go a long way to earn them more market share.

It just seems that logic/apple gets a free pass on issues like this and motu always gets beat up.

no other VI has the "losing presets" issue so its a VSL problem. One that I can't wait for to be fixed!
Best wishes to the VI programmers in solving it.

As much as I love to Flog Motu - I don't think this problem is on Motu.

If there were at least one other VI that had this issue than maybe that case could be made but since its only VSL VI - how can the Daw be faulted?

Waves had an issue with recalling presets (not losing them) and ultimately waves had to acknowledge (while not fixing) that it was on there end since no other plugins had a similair issue.

To all at VSL - I can't wait for this issue to be resolved as its the only thing holding up my upgrade purchase!