Touble with Installation of Diva Despite Cautious Attention to Installation Instructions

[bmrzycki]

Finally, I've seen others have trouble with keyboard input to u-he plugins with Sonar. Something about Sonar intercepting keystrokes (especially space-bar). People have worked around it by typing into something like notepad, then cutting and pasting into the save dialog box. It's not pretty but it seems to work around the problem until Urs can fix it properly.

Hehehe, that makes it sound like it's my fault - I strictly follow Microsoft's sample code, and it's Sonar/Samplitude that jump through hoops to make plugin's life difficult. I will however try to workaround these hosts as I don't believe they'll correct their behaviour after all those years...

Now on to the new thread, I'll try to figure it out...

I didn't mean to imply it was your fault! I have a feeling you have many if..else code blocks to detect the DAW and "fix" fun little problems for each of them.

[Urs]

I didn't mean to imply it was your fault!

I know

I have a feeling you have many if..else code blocks to detect the DAW and "fix" fun little problems for each of them.

Not too many. I always strive for a common case that works for everyone. Which somehow often leads to strange paths...

[Funkybot's Evil Twin]

Urs, is there a reason you don't place presets in the C:\Users\[USER]\My Documents\ folder that's become common since Vista? It's nice knowing that if I just backup that single folder, I'm covering the majority of my presets. Much easier than having things scattered about. It's something I'm actually glad Microsoft did...

[Urs]

Urs, is there a reason you don't place presets in the C:\Users\[USER]\My Documents\ folder that's become common since Vista? It's nice knowing that if I just backup that single folder, I'm covering the majority of my presets. Much easier than having things scattered about. It's something I'm actually glad Microsoft did...

You can of course do that, and our installation instructions strongly recommend to do so. However, many people have voiced their need to install things their own way, hence we give a choice.

I've made a concept for a bunch of very simple things that'll hopefully prevent such problems in future. Just need a couple of days inbetween things to implements this. E.g. if the OP had a readout of path to Vstplugin, path to data and path to presets, he wouldn't have had the issue in the first place. Also, our stuff should just offer to divert into AppData if current path is write protected - right out of he running plug. And of course the installer should never default to Vstplugins if that is in Program Files. A bunch of simple enhancements could most likely prevent 95% of support cases - and save a lot of frustrtion on the user's side.

We'll get there...

[Guitarman1]

Hey, All:

That would be a great idea as it would have helped me sort the problem out much sooner on my own, but I have finally figured it out after all. This afternoon I found Diva installed where I would have never intentionally installed it, with the .dll file in the same folder as the .data file, which is contrary to the installation instructions, and the folder of presets empty, which I would never have intentionally done, of course, so I have no idea how that all came about. I had my intentional installation elsewhere, but when I scanned my VST's in Sonar, it must have decided to grab onto the other one that had no presets associated with it.

In fact, that Preset folder was almost empty but not quite. It contained the empty "Local" folder I mentioned, and it is where Diva saved the two presets I made and could not subsequently find (I have no idea why Windows Search could not find them there). If Diva could tell you where its data folder is, a problem like this would be much easier to sort out. I had intentionally installed it elsewhere and only found this folder today by accident.

Since that was the installation Diva wanted to save to, I deleted my other, intentional installation, dragged the functional folder to where I wanted it in the first place, and dragged the presets from another Diva Preset folder I subsequently deleted into the empty folder, and now it works fine. It is curious that it is working in spite of the fact the .dll file and .data folder are both in the same place and that is in Program Files, both of which are recommended against in the installation instructions.

x3hrv had recommended I try to find the active Diva.data folder by creating presets and saving them and then using Windows Search to find where they were saved to. It turned out that would have been the perfect solution if Windows Search had managed to find them.

It remains confusing to me that the first preset I created was saved to my intentional installation folder, where Diva could not find it and Windows could, but that somehow for the period of time until I closed Diva after creating that first preset, the full set of presets showed up on Diva's preset page and I was able to use them. The next time I opened it, they were gone again--I don't know if there is any sense to be made of this.

Anyway, thanks to all. If anyone else has difficulty with the installation maybe there is something in here that will help them sort it out.

Rob R