@kohlhtor said:

How to rescan single plugin

Go to Options -> Preferences -> Plugins
then right-click on the plugin you want to rescan and klick on "Rescan plugin".

@Paul said:

@Dewdman42: You need to be on macOS 10.13.6 or higher and Logic Pro X 10.4.4 to install AU3. 

Well given that AU3 is really not fully functional yet due to LPX deficiencies...I won't worry about it.  Sad to hear you built that only for High Sierra or newer as I don't wnat to leave Sieera until I'm absolutely forced to.  Was there really a High Sierra requirement in the software somehow?

thank

Hi,

Software Updates for Vienna Instruments, Vienna Instruments Pro and Vienna Synchron Pianos are online. Synchron Player is already up to date.

Best,
Paul

It would be helpful to put the "NEW" there :)

Also, even though the installation doesn't require a re-boot, I found that doing that solved a few small problems I was having.

Thanks Paul.  I do have to say this increased CPU usage a lot when I started getting the articulation updates on the screen.  It appears to me VEP is taking a lot more cpu in order to update its own GUI.  if you minimize the VEP window CPU usage drop a lot.  And I notice a big change this away after updating VIPro to get the aerticulation updates happening.

So just one suggestion, have a look at how much CPU is getting eaten by VEP to update the articulation names when the GUI is active, but secondary to that, an option for us to turn it off entirely would be welcome

Been testing with Cubase 10 now.  using exactly the same midi file and VEP frame as I was using to test with LogicPro.

Overall CPU usage on this machine is WAY higher with Cubase then with Logic.  LIke Double.  That being said, playback was flawless, not any dropped notes or noteOff, hanging notes, etc.. as is the case when using LPX and multiport macro.

Quite impressed with the playback under Cubase, but as I said, CPU usage is hitting 80% using the example ET Score from VST site, from LPX, the same score plays back and rarely goes over 40%.  It could be that Logic is under utliizing the CPU in some way, which is why its getting dropped events.  Not sure.  Just an observation.

I am definitely noticing that since I updated the VIPro just now, CPU use of VEP is higher when the GUI is active.  I am guessing this is related to to keeping the articulation names updated, but whatever it is, I could live without that if its going to be so expensive on the CPU.

Hi, 

Good points there, let's see what can be done regarding the real-time display. 

The performance of Cubase under macOS has unfortunately been underwhelming with VE Pro 6 as well. 

Best, 
Paul

well it might be underhwhelming in terms of hitting the CPU hard, but I also have to say it was very smooth and glitch free audio on Cubase..  I think Logic tends to have problems choking on too many midi events, while CPU utilization is still quite low.  

I just ran the GUI refresh test on LPX also..  I think the GUI updating is adding 10-20% of cpu utilization there as well when the VEP gui window is active.  I really noticed this after I upgrade VIPro to get the articulation names, but I wasn't looking that hard before, its possible the GUI is always adding some CPU usage, which makes sense that it would, but I think 10-20% is far too much for that.  If so we need option to disable those things where are nice to have but not really always neccsaary, like the articulation names or perhaps more places you're updating the CPU usage on each instance, etc.. don't know...  just observations...

I use Cubase on Windows 10 and it makes no difference in CPU load here when the VEP window is open on my secondary screen, or when minimized.

on the mac I am seeing 10-20% bump in CPU utliziation for both LPX and Cubase when VEP window is open.

@Dewdman42 said:

on the mac I am seeing 10-20% bump in CPU utliziation for both LPX and Cubase when VEP window is open.

It's quite normal for the system CPU usage to go up when the computer is doing more things (drawing audio meters, updating other GUI parts etc). The VEP CPU meter should stay the same, since it measures realtime thread CPU.

Alright, but I'm noticing quite a bigger jump in VEP7 compared to VEP6.  That's all I'm saying.  Plus I don't agree with you that its normal for the GUI to be sucking 20% of cpu just sitting there playing the meters.  If so, there is something that could be done better.

Enjoy your cpu use!

On the mac, it sounds quite normal - if you're displaying a lot of things on screen. Remember that it is only 20% of one core, and in a low priority thread at that.

Any open plugin GUIs will of course add to the main thread CPU usage as well.

I'm looking at 20% increase on the overall computer usage aross 12 cores.its not just 20% bump on one core.  If I open the GUI...my machine's overall 12 core CPU usage goes up 10-20%,  Hide the gui and and drops back down.

That sounds like quite a bit of activity.

Could you send me a screenshot of your VEPro in action, so I can assess what activity is going on?

I am having trouble with my Izotope Ozone 8 plugins. It seems like they crash the initial vst search and all other vst after them becomes "unknown".

Is this a known bug?

@Andreas Waldetoft said:

I am having trouble with my Izotope Ozone 8 plugins. It seems like they crash the initial vst search and all other vst after them becomes "unknown".

 Is this a known bug?

Not a known bug. Which operating system are you on, and which exact version of Ozone is this?

All iZotope plugins have in my experience two sets of plugin. One does always not load (even in Cubase). But if you look in the FX list, Ozone should be there (just checked it on my system and the plugin works, but is also in the unknown List).

I know that the iZoptope VST plugins can be incredibly slow in scanning - since they appear to completely tear down and setup everything for each channel configuration.