maybe the plugins that communicate with the servers (which are free) will get different IDs so that you can use these with your VEP6, while "new" client plugs will connect to VEP7 upwards.

In this case you wont have to alter any of your projects, wont lose any license and get additional license(s) for VEP7...

What’s the best way to profit from mpe controllers like the seaboard regarding articulation realism?

Is mpe supported by Synchron?

https://youtu.be/IKSplgK5IEg

as the title says...

As the title says: are these available?

That did it.

I added 12 additional paths, x86 and x64, for each plugin.

any feedback please?

Hi,

I noticed that on Win 10 my flux IRCAM plugs are not available, like verbv3, verbsessionv3, trax etc...

Reasons is, that the flux installer creates a /flux/plugin.vst/... folder inside my plugins folder (c:/program files/common files/vst2/)

as with packages on Mac OS X the plugins folder hierarchy is

plugin.vst/.
|
+- Contents
|
+- x64
|
+- plugin.dll

and VEPro Win doesn't recursively follow folders with names ending with .vst, so plugin.dll is not found/scanned.

When I rename the "package" folder. I.e. Removing the .vst ending, the plugin is found and available to VEPro.

But this will clash with the flux installer... so I can NOT simply rename the folders.

Any chance for a fix?

HAAAAA!!!!

I just NEED to resurrect this old thread from Dec 15 2015.

With VEPro 5, I suddenly couldnt use my beloved HDSP Digiface. VEPro 5 gave me an error that it couldnt properly initialize the device. I tried everything I could, but neither VSL, nor RME had any clues about why it didnt work.

As a workaround, I used my MOTU 828x or a Babyface and piped audio via ADAT to the central HDSP. Of course, I needed to run way higher buffer sizes via USB than I had to, using the HDSP ASIO directly.

Then there came VEPro 6, I had high hopes. But no, my HDSP still did not work with VEPro.

Yesterday, all of a sudden, I wasnt able to change the interface in VEPro 6s preferences. Trying to change from MOTU (default) to any other interface (ASIO or not!) had VEPro 6 freeze! I was like WTF!?!?

Today, VEPro 6 couldnt event launch! It froze upon launch. Hell.

I remembered a strange behaviour with my MOTU (VEPro 6 default interface): When I launch the MOTU Audio Console (where I change buffer sizes and such), and afterwards open CueMix FX (with the MOTU console open), I get an error from CueMix that it couldnt find any MOTU interface. So I thought maybe its the same with VEPro 6, that it cannot find the interface to open, with the MOTU Audio Console visible...

So, i opened the Console and launched VEPro 6. It gave me an error that it couldnt properly initialize the interface. I clicked "OK" and VEPro6 launched with the engine off. Fine!

So I went into preferences and tried to change interface from MOTU ASIO to HDSP ASIO, just to try. I clicked on the HDSP Hammerfall ASIO entry in the list and clicked on the routing tab. Frezze! I was WTF again.

I waited, thinking.

Suddenly VEPro6 UI responded again and showed me zero inputs and zero outputs, but NO ERROR MESSAGE. I clicked "reset" on both inputs/outputs and there they are again: 26x26 I/Os with my Hammerfall HDSP Digiface! It works again!

I have absoluteley no clue what was going on here, but, after nearly two years of working around VEPro5/6 being unable to use my otherwise rock solid HDSP with additional audio interfaces, it works again!!!

There SURELY must be some kind of "bug" in VEPro5/6 regarding ASIO implementation!?!? I gave up long ago.

I got my HDSP back, with a stable 32sample buffer!!!

Now on to image the system to freeze it to this situation! :)

VEPro 6 does not scale on Windows 10 Bootcamp on a MacBook Pro retina.

Paul?

The ASIO issues seems to become more and more frequent lately? Is there a chance to investigate further, instead of just advising using another ASIO driver? I so want to use my Hammerfall DSP due to latency...

No luck. I tried multiple different configurations (inactive/active audio interfaces in device manager). Even the Hammerfall HDSP alone without Hammerfall WDM. VEPro 5/6 simply doesn't work with the HDSP, saying it could not initialize the device. VEPro works with any other device, the HDSP works with any other ASIO hosting software.

Neither RME nor VSL can help here :(

Had this behavior with VEPro 5, too, unable to use a RME HDSP interface: http://vsl.co.at/communi...ammerfall-DSP#post243898

The interface works with anything ASIO hosting, but VEPro :(

Thanks.

what about the UI (not) scaling issue? VEPro is nearly unusable without hidpi support...

1) Mac OS X 10.11.6
A) Zynaptic Morph2 scan hangs VEPro
B) "raise instance" does nothing when server window is hidden or minimized
C) there's a "0.0.0.0 <servername>" server visible in the Connection pane, alongside the "127.0.0.1 localhost " entries for x32 and x64
2) Windows 10 (MacBook Pro retina bootcamp)
A) UI is way to small, no hidpi!
B) Image-Line Harmor is scanned successfully but freezes VEPro when instantiated
</servername>

What are your Findlings?

No, not that I'm aware of. I authorized Harmor by installing the regKey, as mentioned by IL.

What are your findings?

It does not crash. Ve pro hangs infinitely

kind of frustrating

Did that help in any way?

Windows 10 Pro x64
Latest versions of both VEPro 5 and Harmor

Acknowledged?

Still nothing?

I mean, the HDSP and RME are well known for driver stability. Why is it that VEPro can't use it?

Known issue?
Any feedback?

As soon as I load the IL Harmor plugin, VEPro 5 freezes.