Diva 1.3, Zebra 2.7 (rev2126)

[Howard]

What mabian wrote. The fix is in another thread:
http://www.kvraudio.com/forum/viewtopic ... 1&t=400485

[mcnoone]

Just did a clean install of both Zebra and Diva latest versions.
On mac os 10.6.8 the permissions are set incorrectly
They add some and take some away.
They add this one.
_unknown, and everyone (not normal)
they also do not add to permissions.
michaelsmac or adminstrator
After doing a repair permission, some apps and folders changed and corrected, but still Diva component and the u-he folder for vst's still had permissions for _unknown.
It also will not allow me (running as administrator) to delete this _unknown permission.

Please check your installers with mac os 10.6.8.
I will be getting 10.7 soon though.

edit: Yes this did happen the last time I installed the newest version of Diva, and Zebra, and I mentioned it in this thread then. The situation has not changed since then.

edit: I found that the u-he presets folder has one permission named ...
"wheel"

[Urs]

Sorry, we have not updated the installers during the holidays…

I'll deal with this once I'm back from vacation.

[mcnoone]

Sorry, we have not updated the installers during the holidays…

I'll deal with this once I'm back from vacation.

Hope you enjoy your vacation.
Post pictures, and that.

[Geron]

I have an unpleasant issue within Zebra.

In some sessions the cursor will transform itself into a small point after a few seconds of use. It's nearly invisible and will only transform back when i right-click somewhere.

I'm using Logic Pro X and i don't think i've encountered this issue outside of Zebra so far.

Anyone knows what exactly is happening there and whether i can fix it?

Cheers!

[Geron]

Thinking about it, maybe the sleep-mode could cause it, when i leave the DAW open?

[Geron]

Oh, just found out that it's got nothing to do with Zebra. Happens outside of it too.
Guess i'll ask about it on a dedicated Logic X forum then.

Anyway, Zebra is great

[fisherKing]

Oh, just found out that it's got nothing to do with Zebra. Happens outside of it too.
Guess i'll ask about it on a dedicated Logic X forum then.

Anyway, Zebra is great

odd one, not seeing that (also using zebra in LX)...just mentioning

[marcoskohler]

DIVA: One thing I can't stand is that the toggle for the main components is way too sensitive to mouse scrolling. The entire bottom section of a module can be "mousewheeled" and I'm constantly having them change when I didn't want them to. I think the hit are should just be the text, and not the entire bottom of a module/section. I'm using Apple's magic mouse, so the entire mouse is a scroll wheel.

[Examigan]

I have just started using Zebra 2.7 over the past few days. My DAW is Sonar X3 Producer. Love the synth so far

It seemed to be working ok, until today when I tried to save a preset.
I click Save, and the window opens where I can save it.

After I clear the Initialize name out, and start to type a letter, Sonar opens up a window or changes the screen's look, depending on what letter I type. Those keyboard shortcuts are great if I am trying to do that on purpose, but this is happening when I am typing into a field in Zebra.

It doesn't happen in other plugins in X3 that I've used so far. It seems like Zebra doesn't register any letters I type at all, and then they just get passed them along to Sonar instead.

Also, I tried clicking on the keyboard icon at the top/right of the plugin "Give all Keystrokes to Plugin" (its a Sonar function) but it still won't let me type in anything.

EDIT: Just went back and checked to see if it does the same thing if I load it in using VST3, same issue.

Thanks ahead of time
-Rob

[winds350]

Known comparability issue between SONAR and u-he plugins. On the SONAR forums, the commonly recommended work around is to open a notepad window, type the new preset name in there, copy it and paste it into the VST save window.

I recommend filing a bug report through the formal support channels at Cakewalk and at u-he. The problem has existed for years, so don't hold your breath waiting on a fix.

[Examigan]

Known comparability issue between SONAR and u-he plugins. On the SONAR forums, the commonly recommended work around is to open a notepad window, type the new preset name in there, copy it and paste it into the VST save window.

I recommend filing a bug report through the formal support channels at Cakewalk and at u-he. The problem has existed for years, so don't hold your breath waiting on a fix.

Ok thanks, I know someone at Cakewalk so will pass it along.

[Urs]

Well, we've tried *everything* we possibly could, without squandering into hack territory. Sonar obviously uses a hook to intercept key strokes before they reach the plug-in. We could now escalate with our own hook that has higher priority, but we think that this shouldn't be necessary. A well behaved host should respect the Win API and let a key focus on a window be a key focus on a window - or pass keys via the VST API.

[Examigan]

Well, we've tried *everything* we possibly could, without squandering into hack territory. Sonar obviously uses a hook to intercept key strokes before they reach the plug-in. We could now escalate with our own hook that has higher priority, but we think that this shouldn't be necessary. A well behaved host should respect the Win API and let a key focus on a window be a key focus on a window - or pass keys via the VST API.

Thanks Urs


I'll see if I get a response from Cakewalk about it.


-Rob

[Funkybot's Evil Twin]

Well, we've tried *everything* we possibly could, without squandering into hack territory. Sonar obviously uses a hook to intercept key strokes before they reach the plug-in. We could now escalate with our own hook that has higher priority, but we think that this shouldn't be necessary. A well behaved host should respect the Win API and let a key focus on a window be a key focus on a window - or pass keys via the VST API.

Thanks Urs


I'll see if I get a response from Cakewalk about it.


-Rob

FYI, I reported this to Cakewalk months and months ago and got acknowledgement of the bug. I guess it's still happening in X3E?