Hello,

I apologize for the late reply - I initially misunderstood the message, thinking that reducing the preload actually increases the memory usage, and was trying to fruitlessly reproduce the flaw.

Vienna Instruments Pro internally only reports the wave usage, not including the metadata. Dimension Violins however contain an immense amount of mapping/articulation data (the metainformation about placement of the notes, etc). This is not displayed on the internal counter, and indeed for the large presets this data may take gigabytes of memory and grow with each inserted VI instance. We will look into it for the future versions to avoid the confusion.

Thanks,
George.

Hello,

On a fresh 10.7 or 10.8 OSX installation the preset folder should be located here:

/Users/<YourUserName>/Library/Application Support/Vienna Imperial Presets/Vienna Imperial/ 

On earlier or upgraded systems - if these folders exist - the presets may go into /Users/Shared or /Shared Items 

On Windows presets go to:

C:\Users\<YourUserName>\AppData\Roaming\Vienna Imperial Presets\Vienna Imperial\

Please note, that some of the folders in these paths are hidden, so going inside would only be possible when typing the folder directly. I.e., typing AppData when being in C:\Users\George, for example. Or on Mac this would be pressing Shift-Command-G and typing ~/Library , etc.

Thanks,

George.

We never tested it with Ad-Hoc, so it depends on whether OS will handle it. Even if the app will work, I know that Ad-Hoc connections usually are very unstable by their nature.

Thanks,

George.

Hello,

AppData folder is hidden, so it will only respond when typing it in the explorer window. Please try typing the following in the explorer path line:

C:\Users\<UserName>\AppData\Roaming\VSL

(With substuting <UserName>)

Thanks,

George.

Hello,

Yes, under certain circumstances it may help to delete this file. Please indicate which platform/operating system is running on the affected computer.

On Windows the file is located as Herb indicated above, additionally also directories such as Vienna Instruments Pro and viprocache.bin could be present. On Mac the locations are ~/Library/Application Support/Vienna Instruments and Vienna Instruments Pro (relative to the user's home directly)

Thanks,

George.

Yes, this is correct.

There is additional MIDI port on the system called 'Vienna Instruments MIDI'. All changes made inside the app will echo as MIDI messages through this port, provided that all axes are assigned proper MIDI controllers.

Thanks,

George.

I didn't find that mode yet. iPad has a special mode for web applications, where the full screen mode is pretty much enforced.

Thanks,

George.

Features are equal, however iPad is slightly better supported. For iPad there are ways to install the web application on the home screen and open it full-screen. Android will require installing a separate browser, and also the browser controls and status bars will be always visible, taking the screen space.

Also to work comfortably a rather fast Android tablet will be required (such as the recent Samsung Galaxy). It will also work on cheap Chinese tablets, but will not be as responsive.

Thanks,

George.

This is an iPad-wide setting. Please change this in the global iPad power settings.

Thanks,

George.

No, it's not necessary as long as the IP address of the computer is the same. The app is basically a web page, and the installed icon is a bookmark.

Thanks,

George.

Hello,

Just one important note - the application is *not* a remote control of the VIPro GUI, but is rather a MIDI controller which allows to record CC and keyswitch feedback over MIDI. It has a limited set of those features that can actually be automated.

Thanks,

George.

It's a bug indeed. Please try turning reverb on with the VIPro interface first, then it should be possible to turn it on/off within the app. 

The bug will be fixed in the next build, so that on/off works correctly when enabled from the app.

Thanks,

George.

Normally no extra settings would be necessary, but we didn't test it with the ad-hoc connections (only with the wifi hotspot), since by nature ad-hoc connections are quite unstable. I will ask one of our guys to check. Please also try switching off the firewall.

Thanks,

George.

Guys - everybody who has GUI slowness problem or spikes, please forward the info file to the support e-mail. Here is a paste of the exact detail I gave to Domenico in another thread:

Please send a saved file from msinfo32 utility to

1. Please start msinfo32 from a start menu or a Windows 'Run' dialog.

2. On the application choose File->Save... and store the information to ComputerInfo_YourName.nfo

3. Zip the file and attach to a mail, sending it to

In the subject of the e-mail message please mention "VIP2 and slow/laggy GUI - please forward to George", or "VIP2 and ASIO spikes - please forward to George"

Please mark clearly, which problem is exactly concerned, as we seem to have two distinct problems here.

We will ask other affected customers to do just the same thing
and compare afterwards. VIPro2 drawing code is quite ordinary and also
quite optimized, except that there is a lot of drawing happening, so we
don't have a known reason yet, why on selected systems it would behave in this way.

Additionally, if such file exists, I would ask to attach also the
following log to the mail message, or otherwise mention, that the file is absent:

C:\Users\<CurrentUserName>\AppData\Roaming\VSL\Vienna Instruments Pro\log.txt

If somebody else stumbles upon this thread for the same reasons - please do the same. We will meanwhile continue with our investigation.

Thanks,

George.

We have a difficulty reproducing this (E.g., GUI barely takes 1-3% on my laptop, which is even older). So really it looks like there is some common factor that we have to establish. I apologize for being clueless (yet) - we will try to find a system, where it would be posible to debug it. Our hardware guys are looking, if they can recreate the problem on any of our office computers.

Please send a saved file from msinfo32 utility to

1. Please start msinfo32 from a start menu or a Windows 'Run' dialog.

2. On the application choose File->Save... and store the information to ComputerInfo_YourName.nfo

3. Zip the file and attach to a mail, sending it to

In the subject of the e-mail message please mention "VIP2 and slow/laggy GUI - please forward to George"

Additionally, if such file exists, I would ask to attach also the following log to the mail message, or otherwise mention, that the file is absent:

C:\Users\<CurrentUserName>\AppData\Roaming\VSL\Vienna Instruments Pro\log.txt

If somebody else stumbles upon this thread for the same reasons - please do the same. We will meanwhile continue with our investigation.

Just a few questions

- Is the software running on a local screen, or over a remote desktop connection?

- If it's run remotely, what kind of network connection is used (wifi, router speed, etc)?

- Is the project use in conjunction with Vienna Ensemble Pro?

- Are the latest video drivers installed?

- During the time when a slider is dragged inside VIPro interface with mouse pressed down - does it update smoothly (including the meters), or is there still a tremendous lag?

Hello,

For most of the time it should play identically. Due to some restructurization in the internal logic, we may have caused some unintentional changes in the behavior. If a project plays back incorrectly after upgrading to VIPro2 - then please submit a support request.

Thanks,

George

Hello,

Please send the very old project to support [at] vsl.co.at, so that we can analyze why it doesn't load.

'Show Window' is still present with old VI, however it's gone in VI Pro (which works immediately without this intermediate dialog).

Thanks,

George.

If I remember properly, Logic Pro on Mac has built-in Hermode tuning functionality, which is possible to switch on. VIPro should recognize sysex sent by Hermode tuning in Logic, and react adequately.

This is not supported in other hosts, and it is also not built inside VIPro by itself. As for improving the orchestra sound, this is a desputed question. Many people believe, that due to limitations of it - it actually makes orchestra sound worse, with an exception of few instruments.

I think Hermode Tuning should be already supported, if I'm not mistaken.

Hello,

VIPro has a larger base memory size and CPU usage per instance, than VI. For example, VIpro has a default polyphony of 128 voices, compared to 64 voices of VI, and thus will take more memory just for the buffers. Also VIPro contains multiple outputs, all of which need some post-processing.

However the increase in CPU usage with the amount of actually played notes should be approximately the same for VI and VIPro. Thus, the greater idle CPU usage should not really mean a proportional scale in CPU usage when the instruments are actually playing.

As for initial startup loading time, probably there is some room for optimization there. VIPro is different from VI in the fact, that VI will hog the complete system to obtain the resources to load the data, while VIPro is doing this in background.

Thanks,
George.

For now - if for somebody it is really essential to have this data stored under a different location (for backup or maybe out of principle) - what I can suggest is to make a symbolic link to the folder where preset data is desired to be stored. Use the following steps (for OSX):

1. Make sure that no VSL software is running
2. Save the content of /Users/Shared/VSL Custom Data at some other location.
3. Delete folder /Users/Shared/VSL Custom Data
4. Create a new folder, where you want to store presets. For example, /My/Preset/Folder
5. Open OSX Terminal program to access system shell
6. Type the following:

ln -s "/My/Preset/Folder" "/Users/Shared/VSL Custom Data"

Please replace "/My/Preset/Folder" with the actual new location, and remember to put doublequotes, this is quite essential.

7. Restore the content of your old folder to the new folder. Essentially, VIPro will still think that the data is located in the old location, but since it is now a symbolic link - files will be physicall present under a different location.

Now warning: watch the permissions. Since the setting is global, if the target folder is set within one user's home directory, another user may not be able to access it.

Additionally, '~' may not work as a substitute for a user name, so one may need to specify a full user name in the directory path.

Thanks,
George.

Hello,

As far as I know, /Library/Application Support is usually used for factory and static data, which is not changeable by the end user. Most of those folders even don't have permissions for regular users to write the files (only for administrators).

Thank you for the feedback. We will think what can be done about it - since some other things do not quite line up together, if we start changing this little part. But we will find a solution.

Thanks,
George.

Hello,

I'm sorry, but the present default location is used for at least quite some time since the previous software releases, so it's already too late to change it.

Maybe Custom Data Folder should have been a per-user setting, but it is historically made global. So it should reside at a location, accessible by all users. To change it as proposed above - will require changing several part of the software, and will introduce incompatibility to all current users of Vienna Ensemble Pro.

In the future version, perhaps we will re-introduce a possibility to save custom data in another location, and make it a per-user setting, while a default global location will be fixed to what it is now (and has been for quite a while already).

Thanks,
George.