Latest Builds (revision 3857) of nearly every u-he plugin (Public Beta 2)

Official support for: u-he.com
Locked New Topic
RELATED
PRODUCTS

Post

Urs wrote:
Igor Amos wrote:In Studio One 3, version 3.02.34331 in OSX Yosemite 10.10.5 using iMac with i7 processor and 24 gigs memory, the following revision 3857 builds crash:
MFM2, Podolski, TripleCheese and TyrellN6

Zebra 2, ACE and Bazille do not crash

All load fine in Bitwig 1.1.11
For the crashes, please send crash.logs to support@u-he.com - seems like it's the plug-ins that don't yet have a preferences panel.

(good thing is, I have to work in S1 V3 anyway during the weekend… I'll see if I can reproduce it)
Checked with Podolski 3857 AU & VST in Studio One 3, version 3.02 on 10.10.5.
No Crash.

There must be an issue on your side.

Please try this:
- Reinstall the problematic plugins
- Use OS X Disk utility to repair file permissions
- Rescan all u-he plugins in Studio one 3
Last edited by u-he-michael on Thu Sep 17, 2015 7:36 pm, edited 1 time in total.

Post

ok, thanks. will do this and report back. thanks!

Post

Thanks U-he! Seems everything is working fine. Didnt had time yet to check deeper, but no need to "reset" the latency to have a proper sound, that will do for me.

Post

I'm not sure if I'm too happy with the plugin reverting to 16 samples latency in case it detects the host sending irregular buffers.

With Reaper this means increasing the latency to full buffer size, which is not cool for recording, at all. Especially with synths (seriously, why would 16 samples of latency be necessary for ACE, Bazille, Zebra, etc.?). And I'm not sure if there's a solution for this within Reaper. I notice the plugin reverting to 16 samples latency after a loop has been played once.

Post

u-he-michael wrote:
Urs wrote:
Igor Amos wrote:In Studio One 3, version 3.02.34331 in OSX Yosemite 10.10.5 using iMac with i7 processor and 24 gigs memory, the following revision 3857 builds crash:
MFM2, Podolski, TripleCheese and TyrellN6

Zebra 2, ACE and Bazille do not crash

All load fine in Bitwig 1.1.11
For the crashes, please send crash.logs to support@u-he.com - seems like it's the plug-ins that don't yet have a preferences panel.

(good thing is, I have to work in S1 V3 anyway during the weekend… I'll see if I can reproduce it)
Checked with Podolski 3857 AU & VST in Studio One 3, version 3.02 on 10.10.5.
No Crash.

There must be an issue on your side.

Please try this:
- Reinstall the problematic plugins
- Use OS X Disk utility to repair file permissions
- Rescan all u-he plugins in Studio one 3
Ok, I did this and I apologize. I was not paying close enough attention to the plugins I was loading in Studio One. The AU and VSTs seem to work ok, its actually the VST3s that are crashing Studio One. Should I still send a crash report?

Post

Igor Amos wrote:Ok, I did this and I apologize. I was not paying close enough attention to the plugins I was loading in Studio One. The AU and VSTs seem to work ok, its actually the VST3s that are crashing Studio One. Should I still send a crash report?
No worries - we'll go deeply into VST3 soon enough. I don't think that current crash reports will help much.

Post

ok, thanks and thanks for the updates!!!

Post

Appreciate your hard work. Btw can you add an "Initialize" blank preset for ZebraHZ?

Post

EvilDragon wrote:I'm not sure if I'm too happy with the plugin reverting to 16 samples latency in case it detects the host sending irregular buffers.

With Reaper this means increasing the latency to full buffer size, which is not cool for recording, at all. Especially with synths (seriously, why would 16 samples of latency be necessary for ACE, Bazille, Zebra, etc.?). And I'm not sure if there's a solution for this within Reaper. I notice the plugin reverting to 16 samples latency after a loop has been played once.
We're open to discuss this.

The main problem is that people won't make the connection between "horrible distortion" and having switched the latency off. So we did this new thing as quickly as we could. This (and the UI opening time) is the main reason we do a whole new round of public betas instead of taking it to a release candidate.

If there's another way that we can go, it needs to be absolutely fool proof, i.e. it must not spoil the experience of the not-so-technically-savvy user.

Post

I have to say I personally didn't notice any horrible distortion using u-he plugins on my config... Playing a looped time selection in my DAW always worked just fine, but now it adds latency as soon as it goes through the loop once. Not sure what to suggest here, except please don't do that :D


Interestingly the same thing doesn't happen in Studio One. Hmmm. In Reaper I had it set to 128 samples latency, that IS a multiple of 16...


EDIT: Hmmm, seems like it was PEBKAC. Now it doesn't happen. There was a sample rate mismatch between what audio interface was locked to (48k) and Reaper requesting 44.1k from it. Oops. Sorry! All fine now, phew. :)

Post

Urs wrote: No worries - we'll go deeply into VST3 soon enough. I don't think that current crash reports will help much.
I'm glad to hear you say this Urs. Honestly, I've had no issues that I know of with the VST2 versions. When I was a new zealot, er, customer, I automatically began installing the VST3 versions, had some minor issues, and was later squared away by a quick support request. That all comes down to the only "pressing" need for VST3 is to make side-chaining faster in Cubase in Presswerks. (I'm not sorry for the bad pun). I've held off on buying it because I have a ton of compressors and didn't really need to add another unless it would be completely hassle free. I would feel all warm and fuzzy if everything were VST3, but that's just OCD talking.
In rotation here: Helios- Eingya

Post

In light of the manifold mayhem of multiple 'betas' - would this be a bad time to purchase and download ZebraHZ? :D

Since today's my BD....hmmmm....survey says: "Pull...the.....HZ.....handle....Bill!!"

Thanks for all your diligence - and *AWESOME* products - "team u-he !!!"

On my way to purchase....

Post

tomsa wrote:
Any word on the Linux versions? I'd love to throw the new stuff at the wall with Bitwig and see what comes out!
Urs wrote:
I'm so focussed on other stuff, I haven't followed the latest on Linux. I still think though that we need to fix the remaining issues first before we can update Linux. It won't be too long though 8)
Thanks for the speedy reply (from the old thread- I'm in a goofy time zone for the rest of this board, I think), and the continued love for *nixers! Please let your Linux dev team know that I'm happy to test for them!

TS
...If you have to fix it with a computer: quantized, pitch corrected, and overly inspected, then you can't do it, and I can't get behind that!
-Henry Rollins; I Can't Get Behind That-from William Shatner's, "Has Been"

Post

Plugin loading/opening time exceptional fast! :o :clap:

You are indeed magicians. :tu:

Post

2ZrgE wrote:Plugin loading/opening time exceptional fast! :o :clap:

You are indeed magicians. :tu:
Nah we just had two unnecessary "safety measures" when scanning for image files which cost a lot of time when themes were installed. Took them out, everything is still fine, loading time cut down dramatically :dog:

Locked

Return to “u-he”