The upgrade does not work with VEP 6 - only VEP 7. Also Dewdman is right- there needs to be a setting between 100 (too small) and 200 (way to big). Currently I am using a LG 43" 4K monitor.
Thank you, Eloy
200,318 users have contributed to 43,195 threads and 259,071 posts.
In the past 24 hours, we have 1 new thread(s), 9 new post(s) and 69 new user(s).
The upgrade does not work with VEP 6 - only VEP 7. Also Dewdman is right- there needs to be a setting between 100 (too small) and 200 (way to big). Currently I am using a LG 43" 4K monitor.
Thank you, Eloy
Thanks! I've been hoping for a bigger VI pro 2 for years.
Although I do agree, 200% is too large, and I have a 5k screen. 150% would probably be better, and an option for various sizes would be nice. I will probably still use 100% most of the time because at 200% I can barely see my DAW.
Does this update affect CPU usage?
Thank you,
Eloy
For my setup, it is affecting CPU in a major way on my Windows slave. Passages in large sessions that had no issue at a <256 buffer now peak the CPU and cause hanging notes at a 1024 buffer.
Stephen,
My set up - 12 core 2013 Mac Pro and a 6 core Mini Mac 2018 slave using VEP 6. Upgraded to VEP 7 (beacause retina update does not work in VEP 6) and and new Pro Instrument 2 retina - it looks gorgeous! However, my CPU went through the roof/ buffer sizes went up,up,up. I had to revert, brook my heart as everything was so clear. Paul, I for one could live with with Pro Instrument 2 at 100%. I look forward to VSL working on the performance issues. Thank you, Eloy
Hello VSL Team!
Unfortunately, installing the new update on a DELL XPS15 (Win 10) and using it inside Vienna Ensemble (6.0.18443) did not work, nor did the standalone version!
I got the red "!Vi-Pro!" exclamation marks in the VI-Pro instances in VE.
Updating the entries in Directory Manager had no effect.
The standalone version would not start at all.
Paul,
I know it's small potatoes, but any chance a 150% option can be added at some point?
- Sam
Hi Sam,
I wish that would have worked, but unfortunately this scaling simply produced too many artefacts...
Sorry to have no better news there.
Best,
Paul
Ohhhhhhhh, that would explain it. No worries at all. Thanks!