Sorry for the lack of info:

• AMD Ryzen 7 3700X, 64GB RAM DDR4 3200MHz with Windows 11 Pro up to date
• Latest VEPro version
• Cubase 12.0.52 Build 393

Another info that might help and I just noticed. I started a new blank project on Cubase. Since it's possible to see the server reference, I placed manually the info of both the server, and the instance. Once I did that, when opening the second VEPro instrument plugin, it actually showed all available instances. If I disconnect all of them, the instances can't be automatically found again.

Ok, it seems I found a new issue.

When I try to connect a new pre-made instance of VEPro on Cubase 12, it's not listed on the plugin.

Even worse, if I disconnect an instance and try to reconnect it, it happens the same.

Hello again,

Yes, I can report that all issues I mentioned before have been solved. Nice job! It's great to finally have the chance to load Steinberg VST instruments again on VEPro. Oh, and the EW Play VST3 engine became available after rescanning all plugins!

There's just a couple more issues that seem to have occured. Didn't notice them because these aren't currently on my template.

• All IK Multimedia instruments I own (Sampletank 4 and Syntronik 2) imediately crash VEPro once they're loaded.
• When searching for the plugins, I noticed that the search function stopped on Youlean Loudness Meter 2 plugin. Skipping it and rescan it manually solverd the problem.

That's about it all. Let me know if there's anything else I can help with.

Thank you again for your time!

Hello again!

I've tried the new VEPro version, and converted all Kontakt instances to VST3. All of the issues I mentioned before are now gone! Thank you, VSL!

That said, the EW Play engine isn't yet available to use as a VST3 plugin. It's listed on the Preferences Menu / Avaliable Plugins, but I can't assign it on the Mixer window.

Thank you for your time!

Finally, this instance works absolutely fine on VST3 Kontakt. It's from Impact Soundworks Bravura.

Hope this info helps understand what sort of issues are currently showing up. I haven't tried yet to build all Kontakt instances from scratch, so I can't tell if it would bring the same problems.

This one has quite a strange behaviour though.

The first three instances (Gran Cassa) seems to work fine, but the other 6 don't show any audio activitiy at all.

They're from the same library: Impact Soundworks Rhapsody Orchestral Percussion.

That said, except the Gran Cassa, the other instruments are mostly placeholders until I get the proper VSL counterpart.

Didn't know how attaching files to the post would work, so I didn't add all info on the last post. Perhaps it's better to add them according to the results.

The following instances are the ones that don't work the second time after converting Kontakt to VST

My results are a bit random with Kontakt.

When switching to VST3 version, I just load some multi instruments banks already preset from previous version.

During the second time I load the template file, I noticed some libraries not having any audio ar all, although I can notice that Kontakt shows that they're loaded. At the same time, A couple of other libraries seem to work fine. This is not a random event, because it's always the same result: for example, on a Kontakt instance with 7 instruments, it handles audio only 8dio's Century solo french horn (stereo output 7, 8 and 9), and does not show any audio movement with any of the others.

The EW Play engine is not even listed as an option on VEPro mixer. On preferences, it shows that it was recognized though.

So far, the plugin that seems to be hard to recognize is Youlean Loudness Meter 2. When doing the Reset and Rescan All, the progress window stays on it indefinitely. A manual rescan of the plugin seems to fix it.

Nice to see VEPro allowing VST3!

Although I didn't have any crash so far with my Kontakt instances, I noticed that they seem to not be working once I reload a project file. The first time they work fine, it's only after reloading it that the issue starts - that said, it's not on every instance and/or instrument, which is really weird...

Reapplied Kontakt VST2 version again, and they're back to normal.

Windows 11 Pro, Cubase 12 Pro and AMD Ryzen 3700x with 64Gb RAM.

I also noticed that EW Play engine is not recognized as a VST3.

Now with effects, I haven't noticed any issue beside some plugins being hard to recognize the first time.

 

In any case, it's a nice welcome to VEPro! Hope you can sort things out with time :)

Ok! My apologies for my previous posts. It seems that the issue was related with some poorly edited configuration on my end.

I just deleted the spiccato matrix tree and loaded the patches again, and it's now working as it's supposed.

Basically, it was the Attack on the Edit menu that a wrong value.

Again my apologies, and nice to get back to working order!

Thank you for your time, patience, and great libraries!

Yes, I'm aware of that, but even so, they seem to lack the same "bite" when it comes to the spiccato performance. It actually sounds like it's not actually a spiccato because it's a bit longer when compared with violins, viollas, or even cello.

Greetings,

A couple days ago, I was trying out the short spiccato articulations through all Synchron Strings Pro instruments, and I noticed that at least the spiccato and spiccato agile were not as loud on Violin 2 as it was with the rest of the other instruments. At first, I thought it was related to its overall position, but then I used the pizzicato articulation, that was basically at the same output level of the Violin 1.

Is this something  you're aware, and should we wait for a quick fix?

Thank you for your time,

João Guerra

Thank you for clarifying it, Paul.

Still, I hope that when the Synchron Player engine is revised (version 2.0), this is something you will consider.

This is what Paul told on another thread about the auto-trill request:

"Regarding the Synchron Player Legato: I'm afraid the internal logic won't allow to play these "auto-trills" when you hold down one note and then trigger another."

"This is not the question of adding a feature... I have been told that it is technically impossible."

Anyway, hope they can understand how important this feature is, and assuming that the Synchron Player will someday be improved, that this should be on the top list of things to implement.

I think it's what Paul Kopf once mentioned as "auto-trills": when using a legato patch, you hold down one note and then trigger and release another. With VI engine, it will perform as trill, or fast notes. With Synchron, it will stop after the second note, because the first one won't recall.

Afaik, the Synchron-ized versions are basically the VI version provided with the Synchron Stage Impulse Responses. You can turn off the reverb and use it almost like the VI version, but with Synchron Player UI. That said, in terms of realtime playability, I still find the VI version better than the Synchron-ized versions, specially when it comes to legato and performance trills. 

 

Personally, I decided to use VI's with the Vienna Instruments Pro, with the MIRx extension for Synchron Stage, and keep the Synchron Player to the new Synchron libraries that actually have multiple microphones and benefit a lot from its UI layout.

Hello, Rogier.

I never did the full math, but considering how upgrading from a solo instrument to a full pack can be done, I sense there isn't that much of a penalty of not going straight to it.

Considering that, I'd probably recommend you to get a solo instrument library, and compare it with the Special Edition version and see if you still find it lacking on any aspect.

By the way, were you using the Vienna Instruments, or the Vienna Instruments Pro player engine?

I totally agree there's room for both.

Personally, I still find the VI solo instruments a lot easier to get the proper results than the Synchron ones, specially when the articulations require a lot more agility. VSL got it right the first time.

The VI woodwinds are, imho, the best woodwinds available. Whenever I use them, people that hear the arrangement seems to focus a lot on them, and how well they fit the overall mood of the composition.

For ensembles, short notes, and most percussion patches, that's where the Synchron different microphone benefits start to show up. But even then, as mentioned before, the dry silent stage libraries can be added for extra detail, if you can find the balance between dry/wet output.

Good call, Thomas G!

I uninstalled the Pace software from both main and secondary PC, and reinstalled it.

Yes, it seems that finally the saving project time is similar as it was on eLicenser.

Thank you!

Just a quick update to this thread.

I've acquired a second iLok dongle (2nd version), and after moving all licenses from cloud to it, didn't notice any loading/saving improvements.

Anyway, I guess it's always good to have a second iLok dongle close, just in case.

There's the passive cooling cards, without fans.

Then again, most modern cards with fans have a working profile that only start working with noise when they reach high temperatures. That scenario should not be something common for a slave pc.

I'll have to disagree on that quote, Bill.

The fact that current motherboards come with HDMI/DVI/VGA output doesn't mean they are graphically capable.

They still relly on the integrated graphics card that come inside the CPU itself. Intel has it on most of their processors, but I think AMD only has integrated graphics card on the processors that end with a G (for example, Ryzen 3400G).

That said, integrated graphic cards will always get RAM from the system itself. If you have 64Gb of RAM installed, and the integrated GPU requires 2Gb, you'll have 62Gb of RAM to use to run instrument libraries.

Hello, Midimusik

I'm not sure if I could recommend regular hard drives for running libraries. The current ones seem to operate, and are optimized, to be run through SSD's, so they should benefit from that. Personally, I'm using a PCIe card Asus Hyper M.2 x16 card, that holds up to 4 PCI M.2 fast drives. Something like that could be built on a small form factor case.

Besides the system drive (a 128Gb ssd) I still have two other 500Gb ssd drives for the older libraries that doesn't require multi-mics.

If Intel is not mandatory, I would recomend you to check the AMD Ryzen platform, although it should be best first to check the cost/benefit factor. Both should handle the 128Gb RAM you're looking for (on Ryzen that's possible from 2nd Gen - the 3000 series - and more recent). The only thing you'll need to get on most Ryzen cpu's is a dedicated graphics card, though. Then again, any Geforce 710GT with 2Gb is more than enough to handle the requirements, without spending too much.

Considering the current processing power of modern cpu's, perhaps you could even get things done without needing a third pc.

Hope this info could help you out.

Hi, santamorphic,

Good call with the decouple mode, thanks. That sure speeds up the saving session times on Cubase.

Never had the need to use the decouple function before, but it's a good thing it's there. Saving the server status was actually something I already did by intuition.

That said, I still hope that the good people from VSL will take its time to optimize the save times. It's understandable that switching from a licensing procedure to other will have its ups and downs, and things will get better with the following releases.

Just in case, I ordered a second iLok dongle for the slave pc. Hope it helps with troubleshoot. I'll post here the results.
It seems like everytime Cubase 11 goes into autosave, the VEPro instances on the second PC take a lot of time on the save procedure. Almost like it's checking each Cloud license one by one.

If there could be a way for VEPro bypassing the autosave function each time Cubase needs to do it, I think I could be happy with that.

That or simply optimizing the procedure. Compared to the same operation but with the last eLicenser, I'd say it is taking 4 to 5 times longer.