u-he

rockmachine · Post by **rockmachine** » Tue May 30, 2017 2:37 pm

Okay, wondering guys. I just downloaded Reason's 9.5 version which adds the ever useful VST apps to its arsenal. So I can see Zebra and Zerbalette, but Podolski and Bazille are not there. Plus. I got the file permissions issue again with Zebra, it would not load the GUI and got a window saying both Zerba and Zebralette had crashed and would not load. I know it's a new game but does anyone know what is going on with these 2? I got all my Korg Legacy to load and have yet to be able to see the rest of my VST synths.

rockmachine · Post by **rockmachine** » Tue May 30, 2017 2:41 pm

Addendum- it looks as if all of Uhbik are there and are working fine as I just tried a couple of them, but MFM2 I still need to locate and place somewhere so Reason can see its .dll

bmrzycki · Post by **bmrzycki** » Tue May 30, 2017 2:52 pm

I tested everything but Filterscape, Podolski, and the u-he CM yesterday and it all worked. I'm on Windows 10and have my VSTs in D:\Plugins\VST64 and the support data in D:\Plugins\Data. I use symlinks to *.data/ in VST64/ to speed up scanning.

I never install plugins in the default locations, they are to directories that Windows sees as special and have caused me no end of trouble in the past.

aMUSEd · Post by **aMUSEd** » Tue May 30, 2017 2:54 pm

All working for me but I'm on Mac

rockmachine · Post by **rockmachine** » Tue May 30, 2017 3:18 pm

Thanks bmrzycki and aMused. My VST plugins are all over the place thanks to how different companies allocate them when updating and downloading, etcetera. I am on Windows 7 here, and 10 on the laptop and have been thinking for a while to do something similar to what you've done for economy's sake. Seems like the best and cleanest approach, so may have to do some organizing and homework. Other than that, I love how steamlined Reason is already and usual am impressed with the job they've done. Already thinking Cubase is going to be used less and less in the future.

eXode · Post by **eXode** » Tue May 30, 2017 6:40 pm

Also remember that Reason only loads 64-bit VST2.4, so if you've got any 32-bit VST2.4 or VST3 installed it won't work.

rockmachine · Post by **rockmachine** » Tue May 30, 2017 8:00 pm

Yeah, another issue and thinking that is why I am not seeing Attack, D Pole and the PPG. So far, for reasons unkown, I am now seeing the GUI of Zebralette and Zebra and they are working fine, but not Poldolski or Bazille. I can get the initialized sound out of both, but when I click the open for the GUI, get 2 consezutive windows then another one about no GUI resources.

Urs · Post by **Urs** » Wed May 31, 2017 7:57 am

We have an eyebrow raising increase in support requests related to intallation issues in the past few days/weeks. Looks like Microsoft managed to do it again.

We might have to move to set installation path, wherever Microsoft thinks plug-ins and their data need to go.

Aspects of Tone · Post by **Aspects of Tone** » Wed May 31, 2017 9:33 am

Urs wrote: We might have to move to set installation path, wherever Microsoft thinks plug-ins and their data need to go.

Nooooo....please, please don't force an install path on me. Like bmrzycki I have all my plugins on a seperate drive. Also, with the state of the world today (ransomware, malware, borked MS updates, etc) I take regular images of my system drive, so the less stuff is on there the better.

As for where the plugins go, surely that is down to the DAW not the OS? In Reaper I just set my plugin folder(s) in the preferences. I did the same in Cubase before switching to Reaper.

Also, I have noticed that some other developers (e.g. Tokyo Dawn Labs) offer an installer for those who want it and a .zip file for those who want control of where things are installed. Perhaps you could do the same?

Really hoping you don't go down this road of fixed install paths

Nielzie · Post by **Nielzie** » Wed May 31, 2017 9:51 am

Aspects of Tone wrote:
Urs wrote: We might have to move to set installation path, wherever Microsoft thinks plug-ins and their data need to go.
Nooooo....please, please don't force an install path on me. Like bmrzycki I have all my plugins on a seperate drive. Also, with the state of the world today (ransomware, malware, borked MS updates, etc) I take regular images of my system drive, so the less stuff is on there the better.

As for where the plugins go, surely that is down to the DAW not the OS? In Reaper I just set my plugin folder(s) in the preferences. I did the same in Cubase before switching to Reaper.

Also, I have noticed that some other developers (e.g. Tokyo Dawn Labs) offer an installer for those who want it and a .zip file for those who want control of where things are installed. Perhaps you could do the same?

Really hoping you don't go down this road of fixed install paths

I fully agree with you. And besides it's very nice to have the plugins installed into one place that I can choose myself, it's even better if I can choose where all the data of the plugin goes and also not store info in the registry (txt/xml files ftw). Why? Because it makes the plugin fully PORTABLE, which is very easy to backup in workable state. That's why I love plugins that put their data in the same folder as where the .dll resides.

EvilDragon · Post by **EvilDragon** » Wed May 31, 2017 3:08 pm

Urs wrote:We have an eyebrow raising increase in support requests related to intallation issues in the past few days/weeks. Looks like Microsoft managed to do it again.

We might have to move to set installation path, wherever Microsoft thinks plug-ins and their data need to go.

Microsoft did nothing, nothing was changed AFAIK, W10 requirements are the same as in W7 and W8: Program Files are not supposed to be written into by the user or programs, period. However, the main problem is that the default VST2 plugin folder is C:\Program Files\Steinberg\Vstplugins, as you know. And if that default wasn't changed (by means of tweaking the registry, or simply not using Cubase but some other DAW), that's where I suppose your installer picks things up to go, and then there are issues accessing that folder for writing by the DAW, if it wasn't run in Admin mode?

I would say that by default u-he data folders should go into %USERPROFILE%\Documents\u-he, NOT in the same path where plugin DLL is.

I think your installer should still allow the user to change the path, but if it detects Program Files (or Program Files (x86)), warn the user and disallow from installing in that path.

Urs · Post by **Urs** » Wed May 31, 2017 4:49 pm

Well, MS must have changed something, because our trusty support solution to move the data folder where you want it and put a shortcut back to the dll does not work anymore in Windows 10, as it seems.

Aspects of Tone · Post by **Aspects of Tone** » Wed May 31, 2017 6:55 pm

EvilDragon wrote: ... However, the main problem is that the default VST2 plugin folder is C:\Program Files\Steinberg\Vstplugins, as you know. And if that default wasn't changed (by means of tweaking the registry, or simply not using Cubase but some other DAW), that's where I suppose your installer picks things up to go, and then there are issues accessing that folder for writing by the DAW, if it wasn't run in Admin mode?

Yes, this seems to be the main culprit. Many of the installers I run default to this path, even though I have never had Cubase on this computer. I can only conclude that this is built into the intallers themselves.

EvilDragon wrote: I would say that by default u-he data folders should go into %USERPROFILE%\Documents\u-he, NOT in the same path where plugin DLL is.

Sorry EvilDragon, I don't think I would like this either. More stuff filling up my system drive.

EvilDragon wrote: I think your installer should still allow the user to change the path, but if it detects Program Files (or Program Files (x86)), warn the user and disallow from installing in that path.

Now this makes sense to me

If I can't just move the files where I want them, then an installer that puts everything in the one folder of my choice, but won't allow installing to any system folders that need admin level access, is the next best thing.

EvilDragon · Post by **EvilDragon** » Wed May 31, 2017 8:42 pm

Urs wrote:Well, MS must have changed something, because our trusty support solution to move the data folder where you want it and put a shortcut back to the dll does not work anymore in Windows 10, as it seems.

It works just fine over here?

I have my VST folder on another drive (D:, not in Program Files), and all u-he data folders in %USERPROFILE%\Documents\u-he. Everything OK. Are users having issues still ultimately linking to the VST folder within Program Files, perhaps?

Also...

Urs wrote:Looks like Microsoft managed to do it again.

As if Apple doesn't break things with new versions all the time?

Aspects of Tone wrote:
EvilDragon wrote: I would say that by default u-he data folders should go into %USERPROFILE%\Documents\u-he, NOT in the same path where plugin DLL is.
Sorry EvilDragon, I don't think I would like this either. More stuff filling up my system drive.

Not a huge problem, overall. Some other plugins too also put their user data to Documents folder (as they are supposed to, in fact - either there on in user's Roaming folder - per MS programming guidelines), and you CAN'T change this path (short of using symlinks). XLN Audio, Kuassa, PPG, Toontrack, UVI plugins come to mind.

I'm saying by default it should go to Documents folder, but the user should still be able to change the path (except that path should NEVER be in Program Files).

I have all my VST presets in the Documents folder, and I have that folder backed up regularly. Absolutely not a taxing thing for system drive, at all. You shouldn't worry about it, unless you have, like, <100 GB system drive. Which you shouldn't have in the first place

(My OS drive is M.2 SSD 256 GB.)

Terrafractyl · Post by **Terrafractyl** » Wed May 31, 2017 9:20 pm

hmm Agreed, another Uhe folder move would be a bit of a pain!

I don't understand why no other companies plugs have problems with these windows permissions.
I can't think of a single time over the past 20 years I have had to move any plugins to a different location, to get them to work, except in the case of Uhe plugs. (totally worth it of course!)
It still catches me out every now and again, when I do a fresh install or something.

u-he

KVR Audio

Trouble in Reason paradise