u-he

travelquarterly · Post by **travelquarterly** » Mon May 22, 2006 5:03 am

Will Zebra 2 work on Receptor?

Urs · Post by **Urs** » Mon May 22, 2006 8:49 am

Honestly, I have no idea.

If it doesn't work and if Muse has some reasonable dev support, I'll happily see what I can do about it. The only thing I can think of is that their Windows layer might not support all functions that my stuff needs.

Cheers,

Urs

travelquarterly · Post by **travelquarterly** » Tue May 23, 2006 12:00 am

Thanks Urs,
Been using the demo and this is a great synth. I will have to join the Zebra legion! Working on a tune at the moment utilizing Zebra 2 and another favorite Rhino 2. I think I'll call it Galactic Zoo

Regards,
Kevin

nobody21 · Post by **nobody21** » Thu Oct 12, 2006 11:44 am

Hi Kevin,

have you been able to run Zebra 2 on Receptor? Mine installs and loads fine but doesn't show the user interface.

Jens

Urs · Post by **Urs** » Thu Oct 12, 2006 12:52 pm

nobody21 wrote:have you been able to run Zebra 2 on Receptor? Mine installs and loads fine but doesn't show the user interface.

Funny thing is, it shows off my integrated gui editor! You can create some rects and the populate them with the controls for each module... hehehe

Urs

nobody21 · Post by **nobody21** » Thu Oct 12, 2006 1:22 pm

Hi Urs,

ok, that's not what it should do, should it? Other plugins like Filterscape seem to work. Would you have any idea if Zebra will work some time?

Thanks,
Jens

Urs · Post by **Urs** » Thu Oct 12, 2006 2:01 pm

nobody21 wrote:ok, that's not what it should do, should it? Other plugins like Filterscape seem to work. Would you have any idea if Zebra will work some time?

My personal intelligence agency (Ben|KVR, that is) has already found out that my new data setup is the problem. My stuff used to have a folder called "uhe_data" in the Vstplugins directory. That wasn't so great (many, many complaints...), so I have gone for an installer and now I put this in my subfolder in Program Files.

The problem is, the loaction where my data sits now is write protected on Receptor.

As an alternative, I will try to come up with a scheme that actually *preserves* the uhe_data folder (or ZebraData) in Vstplugins for Receptor users. It'll just take some time to work it out and to schedule the next update.

Cheers,

Urs

nobody21 · Post by **nobody21** » Thu Oct 12, 2006 2:10 pm

Great news! I'll wait for that...

nl3 · Post by **nl3** » Mon Oct 16, 2006 1:06 am

Urs wrote:
nobody21 wrote:ok, that's not what it should do, should it? Other plugins like Filterscape seem to work. Would you have any idea if Zebra will work some time?
My personal intelligence agency (Ben|KVR, that is) has already found out that my new data setup is the problem. My stuff used to have a folder called "uhe_data" in the Vstplugins directory. That wasn't so great (many, many complaints...), so I have gone for an installer and now I put this in my subfolder in Program Files.

The problem is, the loaction where my data sits now is write protected on Receptor.

As an alternative, I will try to come up with a scheme that actually *preserves* the uhe_data folder (or ZebraData) in Vstplugins for Receptor users. It'll just take some time to work it out and to schedule the next update.

Cheers,

Urs

As i have to purchase Zebra 2 for using on my Receptor, do you think the new update will be released within a couple of weeks/one month?
Thanks,
NL3

Urs · Post by **Urs** » Mon Oct 16, 2006 7:20 am

Will do my best!

Seeing the current amount of traffic, I won't be able to start on that before a week from now...

Cheers,

Urs

nl3 · Post by **nl3** » Mon Oct 16, 2006 1:35 pm

Urs wrote:Will do my best!

Seeing the current amount of traffic, I won't be able to start on that before a week from now...

Cheers,

Urs

Ok, i'll be waiting for that issue watching here on KVR.
Thanks and good work...
NL3

blurk · Post by **blurk** » Sun Nov 05, 2006 1:23 pm

Urs wrote:My personal intelligence agency (Ben|KVR, that is) has already found out that my new data setup is the problem. My stuff used to have a folder called "uhe_data" in the Vstplugins directory. That wasn't so great (many, many complaints...), so I have gone for an installer and now I put this in my subfolder in Program Files.

The problem is, the loaction where my data sits now is write protected on Receptor.

As an alternative, I will try to come up with a scheme that actually *preserves* the uhe_data folder (or ZebraData) in Vstplugins for Receptor users. It'll just take some time to work it out and to schedule the next update.

FWIW I'd much rather have the installer ask me where I want the data folder to live. Personally, I hate programs that ferret away stuff in "Program Files", because I like to keep my OS partition as clean as possible (old habits from many years ago: I used to need to be able to reformat OS partitions without affecting my data too much). Yes, I am fussy.

Urs · Post by **Urs** » Sun Nov 05, 2006 2:04 pm

blurk wrote:I like to keep my OS partition as clean as possible

That's why I do it the way I do... having everything in Program Files means not having to clutter the Registry. So there's no hidden something. Everything u-he (except for the .dlls of course) is in a single place, you just put it in the trash to get rid of it.

As soon as the location is user definable, I have to put something hidden somewhere. Which commonly means keys in the Registry and thus the need to provide an uninstaller...

Cheers,

Urs

dln · Post by **dln** » Sun Nov 05, 2006 8:13 pm

Urs wrote:As soon as the location is user definable, I have to put something hidden somewhere.

True, and definitely I understand your point. However, one important benefit of user definable location for patches/banks, is that you can keep settings for all VSTs in a single location for easy backup and transfer. I do this, and so far zebra is the only data I have that resides outside either my "banks" folder (not on system drive), or in the user application data folder.

I think it might be a good idea to store plugin settings (the U-He folder basically), in the user's "application data" folder. On windows, this would be in c:\documents and settings\USER\Application Data\U-He , and on osx in ~/Library/Preferences/U-He.

... And location of presets/banks could be userconfigurable in these settings, with default being in the same dir as the settings dir.

This way, it'd be following the respective os system guidelines, be completely flexible, and still stay clearly away from the magical windows registry.

As a side-effect when programming, the Receptor could just be treated as another platform with its own default settings dir. This should solve the receptor-specific problem, no?

Just an idea.

-d

blurk · Post by **blurk** » Mon Nov 06, 2006 2:17 am

Urs wrote:
blurk wrote:I like to keep my OS partition as clean as possible
That's why I do it the way I do... having everything in Program Files means not having to clutter the Registry. So there's no hidden something. Everything u-he (except for the .dlls of course) is in a single place, you just put it in the trash to get rid of it.

OK. I see your point. I don't necessarily agree, but I'm happy you've at least thought about it and have your reasons for doing things this way. I think ferreting things away in application data would be an improvement though (as dln suggested), and still no need to touch the registry directly. I tend to expect actual programs to live in Program Files, not application data files.