u-he

T1mur · Post by **T1mur** » Sat Jan 03, 2009 9:54 am

Urs, do you have any idea yet on why the GUI freezes in host DAWs happen whenever U-HE plugins are clicked on (when using Windows, didn't check OS X yet)? I send you a mail about this describing the behavior in Live, Reaper and Sonar.

This is a bit of an inconvinience, especially if you need to watch some meters and graphs in the DAW while tweaking parameters of U-HE plugins (especially Uhbiks as FX plugins).

Urs · Post by **Urs** » Sat Jan 03, 2009 10:07 am

Oh... I thought I had solved that... hmmm... will check later if I can come up with a quick fix...

elxsound · Post by **elxsound** » Sat Jan 03, 2009 10:10 am

What freeze is this? ...I haven't had a single freeze or crash, making this the most stable beta I've ever tested... (I'm working through Live on PC).

Urs · Post by **Urs** » Sat Jan 03, 2009 10:23 am

elxicano wrote:What freeze is this? ...I haven't had a single freeze or crash, making this the most stable beta I've ever tested... (I'm working through Live on PC).

With some (all?) hosts on Win, the gui of the host and other plugins gets blocked while you drag a knob in my stuff... it unblocks right after releasing the mouse button...

Paul Russell · Post by **Paul Russell** » Sat Jan 03, 2009 11:03 am

Urs wrote:
Paul Russell wrote:Are you going to make x64 versions?
Not sure yet. I have planned to check out the options, but it's not going to be a straight recompile. No promises.

Ok, thanks. Let me know when, cos that's when I'll flex the plastic. (It's a new year resolution thing, don't ask

)

T1mur · Post by **T1mur** » Sat Jan 03, 2009 1:10 pm

Urs wrote:Oh... I thought I had solved that... hmmm... will check later if I can come up with a quick fix...

You mean, you solved that in Uhbiks already (any update available that I missed)?

It also happens with Podolski, Zebralette, Zebra2 (Demo) and ZRev (Beta). But all my versions are pretty old, so maybe you solved it already for those. The only other plugins I found to be behaving like that is DestroyFX ones.

Take another look at the email I send you to see how the different DAWs behave. Thanks for taking a look at it!

mystran · Post by **mystran** » Sat Jan 03, 2009 3:40 pm

Most old plugins that used VSTGUI of the time had that issue, because the toolkit would hijack host message loop by not returning from the mouse-down until a mouse-up event; one should do it by simply capturing the mouse, then relying on normal events, returning to host after each one.. not sure if there's other ways to hang the GUI, don't remember ever having the issue myself; if some host is immune it probably runs it's own GUI in a thread separate from the one it uses to create the plugin editors..

Anyway, the real reason I was replying here is that I wanted to tell Urs that his demo limitation in Ubhik's is absolutely lovely, with the least annoying noise I've ever heard in any plugin demo.. seriously, that's how to do it properly. Pretty much ruins the audio, but in a way that doesn't really distract when evaluating the plugins. You rule.

Urs · Post by **Urs** » Sat Jan 03, 2009 4:12 pm

New Uhbik:

http://www.uhbik.com/download/UhbikMacInstall_10RC1.zip
http://www.uhbik.com/download/UhbikWinstaller_10RC1.zip

- input/output LEDs
- various stereo/surround modes
- MIDI LED
- mono should work
- reverb now fully surroundish
- Runciter LP now (almost) fully open at highest cutoff
- improved memory usage
- S now with full reset (I hope?)

All worky? Any problems?

About the surround modes (right-click on display):

On a stereo track, all modes automatically revert to stereo, except mono mode.

As soon as more than 2 outputs are available, you'll get the full deal:

auto/surround does 1.0, 2.0, 3.0, 3.1, 5.0, 5.1, 7.0 and 7.1, where Center and Lfe can be put "through". The assumed channel order is L R C Lfe Lsurr Rsurr Lrear Rrear

multichannel treats the channels as if they were all placed next to each other, such that i.e. 4 channels would be like Lsurr L R Rsurr. No Lfe channel is assumed, the surround options have no effect.

stereo a+b - processes only a pair of channels, all other channels are let through.

mono - processes only channel 1, outputs on as many channels as are connected

stereo-surround copies channels 1+2 to channels 3+4, 5+6 and 7+8 before processing like just auto/surround - works as mono-surround if the input is a single (mono) channel

I have tested these carefully and they should be okay. However, I had to rewrite large parts of the channel handling code. I *hope* that irregular buffers (Fruity Loops anyone?) etc. do not screw any of these up.

Cheers,

Urs

xyzt · Post by **xyzt** » Sat Jan 03, 2009 4:18 pm

O OOOO, there goes my sleep, hehhehe

zerocrossing · Post by **zerocrossing** » Sat Jan 03, 2009 5:05 pm

Hurrah!

blakflag · Post by **blakflag** » Sat Jan 03, 2009 5:11 pm

Urs,

Hate to tell you this but so far my multichannel experiments with the new version have produced only stereo output. Host is Reaper 2.53 or 2.99, both seem to produce the same results.

Set track channels to 6 (or 8 ) and used an instrument with 2 outputs, hooked some Uhbiks up (Runciter, D & A) and no matter which surround options I choose only the front channels have any output (or show any activity in the AWESOME new channel activity indicators!!!) The mode icon looks to be stereo. I even tried panning the instrument around to make sure it wasnt the inputs that needed to be in surround, no luck.

I don't have any knowledge of how Reaper relays channel info to plugins. But I could try to find out if you need more info.

Can anyone else confirm?

On the brighter side they sound awesome otherwise!

mystran · Post by **mystran** » Sat Jan 03, 2009 5:28 pm

At least stereo still works fine in FL (with variable buffers in use.. didn't test 'em all but those I tried did work)..

found a small GUI bug though.. drag the window of a "small", "large" or "cinematic" GUI outside the bounds of the containing window in FL (that is, say behind the side browser or similar) and you get something like this picture.. the lines are 1 pixel wide with any of the sizes.. and it only happens with the above three sizes.. happens with any of them.

Urs · Post by **Urs** » Sat Jan 03, 2009 5:29 pm

Thanks blakflag!

blakflag wrote:The mode icon looks to be stereo.

This hints at only 2 inputs being connected - otheriwse you'd get a more complex logo in auto/surround mode. Another possibility is taht reaper hasn't requested the plugin's surround capabilities before processing audio, which makes me set it to stereo only.

I have only tested Surround with Cubase, Sonar, Vsthost on Windows so far, I can check with Reaper later.

Cheers,

Urs

mystran · Post by **mystran** » Sat Jan 03, 2009 5:35 pm

Oh and another.. set GUI size to something other than the default, and switch between patch browser and controls, and it'll keep the drawn GUI size, but resize the window back to the size of the "normal" GUI.. happens whether the GUI is set to smaller (some area is left undrawn) or bigger (half the GUI isn't visible). If you close and reopen the GUI, it'll fix the window size back to what it was set to (and draws right again) but now this new size is the size it resizes again every time you switch between patch browser and controls after first switching the size (without closing/reopening the editor afterwards).

Audio~Geek · Post by **Audio~Geek** » Sat Jan 03, 2009 6:00 pm

These work great so far in PT M-Powered 8 on PC, sound great too!
GUI is huge on my 19" 1280x1024.
What is the limitation of these demos?

I may have missed it in the thread, may have even asked you once before, but what will these cost?

[edit] $199 I think you said, great deal![/edit]

u-he

KVR Audio

Can! Not! Re! Sist!