Public Beta: Everything u-he

[nimets]

After updating to the latest beta-versions of Diva (1316 and now 1331)
it won't play in draft-mode anymore. It's just a weird low noise which seems to be hanging until I switch to fast-mode or better and change the preset.

I have win32 and not the most powerful laptop around, so I have to play in draft-mode and render in higher qualities.

Best regards

I have the same problem. No sound in Ableton in draft-mode.
Diva in draft-mode even crashes Reaper.

[hakey]

Diva bug?

There's a 20dB volume range for successive, same velocity notes with this patch.

________


Cheers for oscillator reset!

[mustgroove]

The 64bit VST2.4 versions of these new betas have some GUI drawing issues in Reaper...


Here's how the AU versions look:


Notice the area where it says "No Preset", has the + icon, etc. - these are all the standard Reaper plugin controls that are overlaid at the very top of every plugin GUI window.



Now notice the way the 64bit VST2.4 plugin displays:


The Reaper menus from the previous screenshot actually do appear properly for a couple seconds when the plugin window initially pops up, but then the whole GUI is shifted up towards the top of the window, leaving white space at the bottom of the plugin window...




You manually have to expand the plugin GUI window off to one side to get the Reaper menus to appear again (I took this screenshot on "Cute" GUI size mode just so the screenshot wouldn't be super wide).

[Cmockett]

Keep up the great work guys!

I did notice in the Diva beta some heavier presets hit my cpu about the same as 1.1.1, but thought it weird that the first two template presets Alpha and June60, about 4 keyboard notes hit 90% cpu whereas it was (and is, i re installed and double checked with 1.1.1) about 20-25% (with multi threaded and "great" mode for both)... Nonetheless very happy with my early xmas gift to myself, and thanks for Podolski!! What a fat synth for one osc!

[EvilDragon]

The 64bit VST2.4 versions of these new betas have some GUI drawing issues in Reaper...


Here's how the AU versions look:


Notice the area where it says "No Preset", has the + icon, etc. - these are all the standard Reaper plugin controls that are overlaid at the very top of every plugin GUI window.



Now notice the way the 64bit VST2.4 plugin displays:


The Reaper menus from the previous screenshot actually do appear properly for a couple seconds when the plugin window initially pops up, but then the whole GUI is shifted up towards the top of the window, leaving white space at the bottom of the plugin window...




You manually have to expand the plugin GUI window off to one side to get the Reaper menus to appear again (I took this screenshot on "Cute" GUI size mode just so the screenshot wouldn't be super wide).

This might be as well be Reaper OSX issue - it does have some redrawing issues.

[iamyourfather]

hi Clemens...
ok let me try to hopefully explain it better.
on my PC, all except Diva, I make the next largest size GUI, and always do it for every new instance....would be nice to be able to save the GUI size as the default, so every new instance after then will open at that size.
re: multicore and accuracies, I always enable multicore and change accuracies to I think good and best for every instance, would be nice to save that as my default for every instance from now till the end of time .

thanks
rsp

Aaah, okay

Understood!

Will note this in our bug-tracker as a nice feature

Cheers!

2nded, a small thing but a welcome thing

[The Telenator]

This is all fantastic Stuff, and I truly appreciate all that Urs and Team U-he have done. But after reading carefully through this entire thread I'm afraid I am left with a bit of confusion. Perhaps while u-he is on vacation, someone knowledgeable here at this forum could answer a couple of my questions. These are quite simple and to the point really, and some concise answers would be greatly appreciated:

First, it sounds like the most recent 1331's have had most or all of the bugs fixed, yet I see still more posted in the last day or two. I'm fine at present with all the u-he products I have -- no issues. Would I be better off to just wait until early next year to 'upgrade' when ALL issues are finally resolved? I did take the new Podolski because it had new presets and the new skins are delightful, but I could easily wait on the rest if you think this wiser.

Next, aside from the VST 3 option, in a nut shell could someone briefly explain or tally the improvements in this 1331 beta deal? I'm afraid I'm quite lost now from reading the last 6 pages!

If someone doesn't mind, could I have the supposed virtues of VST 3 as it applies solely to these products reviewed for me? It has been ages since I studied up on this VST 3 issue, since its deployment got so universally delayed by everyone.

Last, obviously, my whole point here and what I'm driving at is that I have several of u-he's synths. They are all working perfectly, have customised skins and presets. So, before I go to a half day's trouble switching out what 'ain't broke' to something of potential trouble. I'd really like to understand better just what is going on here! Can someone explain? I'm sure I'm not the only reader who has been left puzzled and wary after reading this entire thread, so you might be helping many of us with your knowledge and clarity.

[chk071]

Nvmd

[EvilDragon]

Mr. Telenator - it's always good to be up-to-date. Unless you don't have a habit of testing betas.

[hakey]

could someone briefly explain or tally the improvements in this 1331 beta deal?

Oscillator phase reset is the only really significant addition.

For the rest, there's a link to the full changelog in the first post.

(Btw, the issue I reported in a post somewhere above isn't confined to the beta and isn't necessarily a bug.)

[Urs]

Well, we simply worked 5 months on fixing niggles. Lots of them. Most of these have hardly occurred to anyone, such as the issue with Wacom tablets (which unfortunately isn't fixed for Win8 - maybe new drivers or something). Other issues like the legato play when a NoteOff happens simultaneously with a NoteOn may have confused maybe a dozen users.

More obviously, we had flaws in our installers and in the registration process. File permission problems and not-realised-we're-in-demo-mode-or-how-to-get-out-of-it were two of our main support cases. Mountain Lion and Windows 8 made things worse and urged us to act quickly here.

Anyhow, a few months ago I decided that we would sit back, do the right thing and fix all those things. We also set up a new build system with testing procedures and such. Additionally we dug out all old projects (ZebraCM, Podolski) and took them to the current level, new compilers and an overall evolved codebase. That alone can break a lot of things.

In a wise move we started this public beta test. So far we had more than 15000 downloads and about 20 people reported problems. Most notably an installer issue on Leopard (which we don't have anymore).

I'm confident that we will have fixed all known issues once we send out a newsletter with a release announcement.

[Echoes in the Attic]

Just as an FYI, there is still the problem with Diva where it loads in Great quality in a project where it was saved as fast quality. For some reason this only happens with the first instance if you load a saved host preset. For example, save an Ableton instrument rack with Diva in fast mode. Then load it in a new project. It will load in Great mode. Delete it and reload it without changing the mode. It now loads in fast mode as it was saved. Not a big deal but thought I'd report it again.

[Rimwolf]

Legato mode doesn't seem to be working right in Ace 1331. For instance, if I do a rapid legato trill (I play wind controller) with standard patches "HS Squaw" or "HS Synger", it sounds like it's retriggering -- but not quite every time. In Ace 1.1 there's no retriggering sound through the whole legato trill. (And, alas, I hear the same in my wind patches.) Same problem whether I have multicore enabled or not.

environment: Logic Pro 9.1.8, OS X 10.8.2, Macbook Air 2012 (2.0 GHz i7)

[Urs]

Just as an FYI, there is still the problem with Diva where it loads in Great quality in a project where it was saved as fast quality. For some reason this only happens with the first instance if you load a saved host preset. For example, save an Ableton instrument rack with Diva in fast mode. Then load it in a new project. It will load in Great mode. Delete it and reload it without changing the mode. It now loads in fast mode as it was saved. Not a big deal but thought I'd report it again.

Ableton's Instrument Rack in Live "optimises" our chance away to save things with project. We can't distinguish whether something is saved with a Rack or a project. Things like multicore settings or accuracy might not recall reliably there (but we might be able to get around this somehow with some features we've planned sometime in the future)

[Urs]

Legato mode doesn't seem to be working right in Ace 1331. For instance, if I do a rapid legato trill (I play wind controller) with standard patches "HS Squaw" or "HS Synger", it sounds like it's retriggering -- but not quite every time. In Ace 1.1 there's no retriggering sound through the whole legato trill. (And, alas, I hear the same in my wind patches.) Same problem whether I have multicore enabled or not.

environment: Logic Pro 9.1.8, OS X 10.8.2, Macbook Air 2012 (2.0 GHz i7)

Can you send us a MIDI file to support at u-he dot com?

We might have actually *fixed* something there, but I won't be surprised if there were side effects that need fixing too.