KVR Audio

original flipper · Post by **original flipper** » Thu May 12, 2005 9:34 pm

HI

I managed to get most of the Project 5 plug-ins to work in Orion today (NOT by rewire but the dll files), a few crashed but the main ones - Dimension and Psyn seem to work fine, anyone else tried this out?

Flipper.

kevink · Post by **kevink** » Thu May 12, 2005 9:53 pm

The P5 synths and effects are, with one or two exceptions, vanilla DXi plugins that can be used by any DXi-capable host. I use nPULSE in Sonar pretty regularly, and Psyn works fine, too. However, I also found that P5's VELOCITY causes the Canopus "Let's Edit" video editing package, which allows the use of DXi audio FX, to crash, so I had to de-install it from my development machine.

uncadave · Post by **uncadave** » Thu May 12, 2005 10:02 pm

i can't get velocity to work in o-plat, either, tho i could with p5 version 1 velocity. it's ok, tho, the samples are available. i was acxtualy tempted to buy p5 before because i thought the price was worth it just for the dx plugs....still think so in fact. what pushed me to buy it, tho, was the free upgrade to p5 v2. i ended up picking up te last old p5 my area guitar center had......$160, screaming good deal.

snooky · Post by **snooky** » Thu May 12, 2005 10:02 pm

so, could I download the demo and use the synths in any dxi compatible host?

aMUSEd · Post by **aMUSEd** » Thu May 12, 2005 10:07 pm

dougsyo · Post by **dougsyo** » Fri May 13, 2005 12:40 am

snooky wrote:so, could I download the demo and use the synths in any dxi compatible host?

In the P5V1 demo, the DXI's were locked to P5.

The ones that I know CW has locked in the past were Cyclone (Sonar & P5) & the Roland Groovesynth (Kinetic, P5, and later Sonar)... if you inserted them into FLS, for example, they wouldn't generate any sound.

Several people have commented about Velocity crashes, but IMHO (speaking as a professional programmer) crashing is not an acceptable solution to software protection. Assuming that that it shouldn't crash, I'd suspect it's flakiness in Velocity... otherwise it would just be silent or pop up an error message or something.

Doug

kevink · Post by **kevink** » Fri May 13, 2005 5:03 am

The VELOCITY problem is *not*, as far as I can tell, a copy protection thing. I'm talking about the full P5v1 version, not the demo. The way it crashes the Canopus software suggests that it does the wrong thing when a host tries to open or probe it as a DXi audio effect, and makes a bad memory reference instead of returning an error. I filed a bug report with Cakewalk on it a year or so ago, but never got a response.

xylyx · Post by **xylyx** » Fri May 13, 2005 5:49 am

How do you know that it is a Cakewalk problem and not some flaw in Canopus implementation of DXi hosting? It is possible that Cakewalk ignored the bug report as it works perfectly in their hosts, so they came to the conclusion that the problem lay with the other host...

kevink · Post by **kevink** » Fri May 13, 2005 6:08 am

The crashes I was seeing clearing implied to me (as a software developer even before I bought my first synth, an Oberheim FVS-1) that there are bugs in both Let's Edit and Velocity. The Canopus code is broken because it fails to recognize the configuration bit that distinguishes a DXi synth from a DXi audio effect, and Velocity is broken because, alone out of 20 or so DXi synths, it makes an illegal memory reference when invoked as an effect.

I filed bug reports with both companies.

pseudonoise · Post by **pseudonoise** » Sat May 14, 2005 6:50 am

I used to use Velocity quite a bit, and never had any problems at all.

P5 dll's working in other hosts!