There is single app scaling in Windows, or at least the possibility to allow certain apps to scale but not others - although legacy software doesn't do a great job at it (it basically blows up pixels into a sometimes blurry mess!). Nevertheless, it's better than using a magnifying glass. I wrote in the other thread:

"Here's perhaps a better fix: find the Vienna Ensemble.exe (mine in program files > vienna), right click, properties, compatibility tab, select Override high DPI scaling behaviour, and change to System or System Enhanced. Now the application will be blown up by a factor defined by system. I believe this is somewhat new, perhaps a Creator's Update or so. It's less than ideal, obviously, as things won't look as crisp as they would on real scaling; basically we're just doubling pixels here. But for everybody who doesn't have laser-eyes, or wants to use an analog/digital magnifier, it works much better."

Perhaps it's useful to you. 

Note that this thread was from 2015. The suggestion was then, too, that this was being looked into and that this was certainly next in line. I think VI/VIP could really do with an update by now!

Best,

mspape

You're very right - and updates do not seem to happen. Elsewhere, I posted the following "fix" that makes Windows show the VSL with blown up pixels. This works similar to, but much better than (magnifying) glasses:

"Here's perhaps a better fix: find the Vienna Ensemble.exe (mine in program files > vienna), right click, properties, compatibility tab, select Override high DPI scaling behaviour, and change to System or System Enhanced. Now the application will be blown up by a factor defined by system. I believe this is somewhat new, perhaps a Creator's Update or so. It's less than ideal, obviously, as things won't look as crisp as they would on real scaling; basically we're just doubling pixels here. But for everybody who doesn't have laser-eyes, or wants to use an analog/digital magnifier, it works much better."

The problem is, presumably, that the whole GUI was created on windows without such vector based designs as the OP suggests. So, until the entire GUI is remade for VIProPLUS!, it would be a lot of work for relatively few users to do anything about at the moment. Anyway, the above way works and has been the *only* way I have been able to successfully cope with Vienna Instruments / VE / VIP on a HiDPI screen. 

Hope it helps.

Best,

MS

Hi,

Thanks, this works somewhat - though about as well as using an actual magnifier, not the most pleasant experience!

Here's perhaps a better fix: find the Vienna Ensemble.exe (mine in program files > vienna), right click, properties, compatibility tab, select Override high DPI scaling behaviour, and change to System or System Enhanced. Now the application will be blown up by a factor defined by system. I believe this is somewhat new, perhaps a Creator's Update or so. It's less than ideal, obviously, as things won't look as crisp as they would on real scaling; basically we're just doubling pixels here. But for everybody who doesn't have laser-eyes, or wants to use an analog/digital magnifier, it works much better.

Hope that helps!

Best,

MS

It appears you were not wrong - sooner than next year came and went, and another half a year passed.

I have to fiddle with VI/VIP at a distance of ca. 5 cm in order to see something, it's more or less impossible to look for something and it is the reason I haven't bought a single library in the last year and a half or so.

Any chance that this will be updated a bit sooner than later? How about a single switch that at least circumvents the issue by blowing the whole interface up by a factor 2?

Best,

MS

Hi,

I've been buying Vienna Symphonic Library products for years now, it's my favourite company, please don't think I'm slamming them. So when I say I believe this is their core software (VI, that is, perhaps not even VIP), I don't mean to sound like a pathetic gamer who feels mistreated for my favourite product not being updated as much as I unreasonably feel it should. Instead, I would argue, VI ought to more prioritised than anything else, because without it, we can't play the samples, and in the end, we buy VIP, VEP, VS, MIR, and so on, to get more out of these samples. I'm sure a lot of people use VS and MIR for more than just VI and the samples, but the greatest attraction is surely how nicely it builds on top of the samples (triggered in VI), as is recognised by the company, evidenced by the collection of specialised presets.

Anyway, I'm not here to argue, and as someone who's dabbled in programming quite a bit I understand it is easier to build scaling from the ground up than rewrite the old code, and actually pretty boring to work on getting old stuff to still work in a new age! I would, however, like to hear someone from the company saying this is in the pipeline, that they're still developing these products, because it's been quite quiet for a while now (last update in February, wasn't it?), while the first request down below was from a year and a half ago.

Best,

MS

Hi,

Time to bump this. It's been half a year, any news on this topic? Actually, I am kind of worried about the lack of any kind of update on the core software. Well, I imagine that is sampling, but perhaps I'm wrong here!

You say this because you're developing this? I imagine that you are right, but that doesn't invalidate the necessity of implementing this sooner rather than later.

I get that a good scaling UI is hard to implement, but right now a quick hack (e.g. an options for upsizing every UI element x 2) would be better than anything, because VI/VE/VIP on high DPI remains broken. Imagine I just bought the latest new (Windows) system and decide to try VSL products for the first time, wondering if i should dish out a couple of thousands on libraries. Surely, I'd be a group one would focus on to impress.

Thanks, great to hear this!

Anyone reading this? Perhaps I was making it sound like this wasn't a big problem:

* Vienna Instruments / VIPro / Vienna Ensemble are all about the size of my phone when displayed at high DPI, it's nearly unreadable.

* Almost all new Windows PCs (laptops) are at high DPI and resolutions.

In other words: most Vienna software is at risk of becoming unusable for people on Windows who have less than stellar eyes. Please implement at least some form of scaling other than "just run a low resolution".

Thanks!

Hi, this is starting to become important with Windows running in resolutions at high DPI. Many programs do indeed scale well (e.g. Cubase does) with Windows setting "Change the size of text, apps and other items: " - mine is currently running at 175% on a Surface Pro 4. However, Vienna Instruments and such totally ignore the setting, meaning it looks TINY on my screen. I think this kind of thing does work in the OSX version of the software, so would it be possible to implement a scaling Vienna Instruments / Ensemble in Windows? Or even just a setting "blow up everything x 2" i'd be happy with.

Hiya

Also had a similar issues and found the search button eventually. But, first browsing, then searching makes as much sense as asking people to first go to Yahoo sections, then search. It's not exactly modern. Wouldn't it make more sense to add search in the corner right of every section of VSL (including the forum, and already before entering a subsection of the forum)? I mean, I like the new VSL site in many ways, but the fact that it still has a "sitemap" tree view tells one there's still a definite 90s vibe.

Sorry for the late reply, I'm actually only here because every now and then I forget what is the "change all patchnames to" shortcut which isn't in the manual. So I just noticed your reply, and wanted to say: thanks. Never noticed that - this does save time.

Hi,

Oh, it probably reset my preferences (to this strange default) with reinstalling Windows! Thanks, good to know!

Two new ones in the new Vienna Ensemble 5.3.13166 (64 bit) with Vienna Instruments Pro:

* Enable cells on Midi Activity now works as an instance specific measure, it seems? Setting it to ON enables it for that VIP instance, but even though it remains ON for the next one, I have to manually switch it off and on before it works.

* Mousewheeling over the channels (which i do an awful lot, because of the dimension strings!) so to scroll down, sometimes adjusts the balance/volume sliders if one happens to just mousewheel over the varied slider. I think normal usability suggests we use mousewheel for scrolling, but manual click/dragging for adjusting sliders - having BOTH is, however, can make one unwittingly distort the mix.

Nothing serious no. In fact, I thought I should write it before I forget about it and figured the Vienna team might be interested.

BTW, would it be possible to enable a "ENABLE/OFF/LEARN optimize" global setting or perhaps a shortkey? It gives me RSI to relearn 80 instances!
Best,
MSpape

Agreed with Dominique. I consistently use matrix, patch/cell and slot to not confuse these things. Anyway, when I write "speed control as a midi parameter", I know quite well it is not - I have done quite a lot of C programming and am aware it is not. To integrate it as in the way described here could of course be very difficult (since, as civ3 says, it's not a real midi controller), or reasonably easy (since, as I noted, VI already keeps track of speed and quantifies this as a parameter), and the demand could be big or small; I do not have access to the source code of VIP, nor to the marketing data of VSL, so these questions are best answered by people who do.

In any case, the method as described by Paul (and myself) is useful, unless you, like me, already use different parameterizations for the current matrix in use (i use arco vs pizz for that now) and the XY axes within matrices and don't like spending many hours readjusting the carefully made personal presets. Likewise, some people (like me) make use of humanization presets, even though, strictly speaking, this could presumably also be achieved from within the preferred DAW. If it's not a ton of work, and there are at least 2 persons in favour, the requested feature would be greatly appreciated, but could safely be ignored by puritans.

Cheers,

Michiel

Wondering if that'd be clear. To explain, 1) set up a row of patches for a single matrix, select speed as the switch parameter; 2) select patch 1 (all left in row), select the first slot (upper left slot) in advanced (because, oddly*, the humanize settings are locked to the particular slot); 3) performance tab, humanize, for each iteration of the humanize, turn the delay to a lower ms; 4) select patch 2 (and up) and do same, but increase the milliseconds. Voila.

Anyway, I also thought about this, and do think there is something to be said for greater speed should result in worse tuning and perhaps timing. Would it be possible (i.e. implementable) to have the speed parameter which is available anyway, to work as a midi controller; one could then assign the speed in the same way to the humanize parameters as one could to the horizontal / vertical matrix switcher?

Best,

Michiel

* oddly, because if you want to adjust dozens of patches, it doesn't always select the first and only slot in the patch, so I've ended up adjusting humanize presets for dozens of empty slots in cells before! (hint: can the first slot be automatically selected while editing?)

Hi, yeah - I still stand by this as well. I'd particularly like it if I'd be able to select multiple patches/slots and can edit multiple values (i.e., if the parameters have the same value X, we see X and can set all to new value, while if they have different values, we see -- or such, as is the way some graphic design and IDEs work).

In the mean time, I too look forward to each new bit of Vienna Dimension with that kind of awful feeling: it's so great, but SO MUCH WORK :) Bitter sweet.

Michiel

 Hi,

No problem! My favourite way is to load each instrument as a separate matrix within the same preset, so that a single mouse click immediately activates the correct instrument. Of course, I don't use an awful lot of instruments - it's pretty much always "loads of strings", "piano", "various woodwinds" or "brass". The alternative would be to load separate instances within the same vienna ensemble, but then, if you need to switch instruments, you need to solo the one instrument and mute the others (setting each to respond to omni midi channel) - which is more clicks and thus more that can go wrong. It's a bit silly - I have this massive midi channel switch pedal specifically for this purpose and obviously this would be easier, but I dislike carrying stuff around! (also, i do like the visual certainty).

Best,

Michiel

Hi,

While spending quite a number of hours doing mindnumbingly tedious clicking, I was contemplating what could be done to improve VIPro somewhat more. Here's what I was doing.

I had made a new preset for dimension strings, violins 1. Using ViPro and the nifty ctrl+alt+w trick described elsewhere, I changed VI_P1_ into VI_P2, all good and saving a lot of time*, but the humanise presets (curves, delays, etc) stays the same. As one might expect, I suppose. So, I go, for the other 7 violins, x matrices, and y cells, change them all into a different preset (because otherwise, the randomness will be the same 12 sequence randomness for each violin, mainly making the whole orchestra sound wonky rather than natural). Given x is 3, y is 15, I was getting rather fed up by the time I had done this 315 times. But then I noticed it's actually 7 violins, x matrices, y cells and z slots. And I gave up.

So, the request is: can a feature like "apply change over all matrices/cells/slots" be implemented somehow? My favourite way would be by being able to select multiple cells in a matrix and affect the same parameter over all slots within that matrix. Some software does this by only showing the value of the parameter if it is equal across instances.

Sorry about the rant, thanks for listening. I like MirX by the way (trial), though I dread implementing that across all my VE presets...

Best,

M.

* Notice this works, but not necessarily to VC_P1, even if the patches are named accordingly. There seems to be some sort of bug by which the register of VI will be applied to VC, so no sound is coming out of the lower register. In fact, even if you at that point reload the patch from VC_P1_RE_, this still doesn't change. However, if you load VC_P1_C_ into it, it does. I know the ctrl+alt+w thing isn't supported, so it doesn't constitute as a bug, but thought I should mention it anyway.

 Yes, the picture does suggest something of that sort... but as someone who doesn't own MIR, I'd be extremely surprised if i should get some features of that as a freebie!

 Hi,

I do. Though I will admit I don't use VE as a host to plugins other than VIP, so I can't be of too much help. The plus, for me, is that the setup, without VE running in Cubase (which I'd been doing before this) is that there's less overhead in many ways: less happening on the screen and a better overview, less cpu and memory consumption, better stability. Mainly the last, actually - I stopped using cubase live when one day it crashed during a gig: not the fault of cubase as such, but I remain a bit traumatised :)

Best,

Mich

 I'm also interested!

I don't think anyone has seriously suggested they prefer too-early-released junk? An update of progress, however, would be appreciated (saves me feverishly checking this thread twice a day).

 Hurrah, it's June!

Agreed! Though you could do it yourself, no? Some work could be saved with this nifty, unsupported and seemingly (last time I read the manuals) undocumented feature: http://community.vsl.co.at/forums/p/34585/215832.aspx#215832 .