196,053 users have contributed to 43,014 threads and 258,388 posts.
In the past 24 hours, we have 2 new thread(s), 18 new post(s) and 144 new user(s).
I did roll back to the previous version last night but it was happening with Kontakt 7 plugins specifically.
My crash happened exactly the way Choison explained. I click on an instance of Kontakt in a slot from the mixer view, make my edit, go back to mixer view, click on the instance of Kontakt in the second slot to make the same edit and that's when it hangs.
Same here with all instance that contains multiple instruments, let say if I have one "Strings" Instance with 4 channel (1xPlay/2xKontakt/1xHALion) if my first channel is selected and I want select another channel (channel view) with my mouse VEP freeze and it's happen with all my server (3) with any instrument loaded in, even with Komplete Kontrol empty instance.
In my case all of my Kontakt instances have a single instrument. Not sure if that's relevant.
A little more information on this issue. First of all I re-installed to the most recent version. Something got goofed up when I tried to rollback plus I needed to better document what is happening.
As previously stated if I click on an instance of Kontakt7 (v. 7.13), make an edit to the VST (infinite brass), navigate to the Mixer view, click on another instance of Kontakt7, VEPro hangs and never returns until i forcibly close it.
However, I did discover that if I save my change to the server project after making each edit this issue didn't occur. In fact if I open an instance but don't make a change, I can open another instance without issue. Only if I make a change to a VST does the issue occur.
Latest update has caused problems for me as well.
I just updated both Kontakt 7 and Vepro 7 to their latest versions as of Feb 19th and immediately ran into a problem. With two separate instruments of Kontakt loaded into a single Vepro instance, when switching between each Kontakt instrument Vepro will freeze/hang. Before it freezes I see the Kontakt display flicker, then Vepro completely locks up and I need to force quit to fix.
Single system use
Kontakt 7.1.8
Vepro 7.2.1503
Windows 10 Pro 22H2 19045.2604
I'll also add - I was unable to rollback vepro 7 to an earlier version that allows VST3 to test. When attempting the rollback from Vienna Assistant 1.0.272, it lists previous 7.2 versions as options, but when I choose a 7.2 option it actually downloads and installs only 7.1 software versions. I was unable to find previous 7.2 installers on the website.
Further additions - I was able to locate and install ViennaEnsemblePro-WIN-7_2_1495. This fixed the previous problem for me. The issue must have been with the 7.2.1503 update?
However, I did discover that if I save my change to the server project after making each edit this issue didn't occur. In fact if I open an instance but don't make a change, I can open another instance without issue. Only if I make a change to a VST does the issue occur.
I tested the same idea of saving after every change, and that worked for me, I was unable to rollback to a version that supported Kontakt 7, so am stuck on the latest release (on Windows 11 pro).
Hi Arlanda,
Please check the compatibility with Catalina because I didn't change anything on my side, and it became a nightmare. Thanks
B Ben moved this topic from Vienna Instruments Pro on
