I get your explanation, Urs. I just thought it was a typo worth pointing out.Urs wrote: ↑Thu Jul 22, 2021 5:44 amYes, the labelling/naming is inconsistent.Weasel-Boy wrote: ↑Wed Jul 21, 2021 6:03 pm[...]“Vibrator” is mentioned on the website…but that, too, is incorrect as far as the actual UI control labeling is concerned.[...]
Calling the Vibrato-LFO "Vibrator" was meant to be funny in the infant days of our business. We have however since grown up and developed a more subtle and refined kind of humour. Hence, we simply dropped the last R wherever we could.
We can't however drop it everywhere without risking preset compatibility issues: Renaming things on certain levels of application layers is prone to causing bugs and issues. The effort to minimise the risks is in stark contrast to the gains. We have therefore decided that the best way to go about is to simply ignore the matter, i.e. to simply live with the inconsistency - particularly as it's such an easy one to neglect.
Hope everyone can agree.
2021 Silicon summer updates RC1 12001 (Mac, Win, Linux)
- KVRian
- 646 posts since 12 May, 2004
On a number of Macs
- KVRAF
- 4123 posts since 23 May, 2004 from Bad Vilbel, Germany
According to Urs's explanation it's not actually a "typo"Weasel-Boy wrote: ↑Thu Jul 22, 2021 6:42 amI get your explanation, Urs. I just thought it was a typo worth pointing out.
Worth pointing out anyway... cheers!
- KVRian
- 646 posts since 12 May, 2004
Yes, I get it, Howard. So it’s a battery powered LFO after allHoward wrote: ↑Thu Jul 22, 2021 7:12 amAccording to Urs's explanation it's not actually a "typo"Weasel-Boy wrote: ↑Thu Jul 22, 2021 6:42 amI get your explanation, Urs. I just thought it was a typo worth pointing out.
Worth pointing out anyway... cheers!
On a number of Macs
- KVRian
- 840 posts since 8 Mar, 2008 from Crestview, Florida
Oh, hey, look, it's another aptly timed Big Sur update!
- u-he
- 28067 posts since 8 Aug, 2002 from Berlin
Yeah, it's really only a Big Sur update. The other 50 or so major improvements, refactorings, redesigns and fixes really just happened purely by chance. The new UIs just randomly popped up out of nowhere, for M1 support a developer had to just click a widget in Xcode and there it was. The reworked preset with revised tags and more consistent volumes and stuff were sent in voluntarily by the sound designers, our content team had no work with it. For a year, the team at u-he headquarters just had to sit and wait it out until the pieces simply aligned all by themselves.
Only, they weren't sitting in the headquarters, they were working remotely, juggling life and work in a pandemic and none of the above happened by itself.
Only, they weren't sitting in the headquarters, they were working remotely, juggling life and work in a pandemic and none of the above happened by itself.
- KVRian
- 840 posts since 8 Mar, 2008 from Crestview, Florida
I apologize, I was not implying that these updates weren't a huge undertaking, which they clearly have been. Just a poorly timed joke. I appreciate everything u-he does for us, and very much look forward to the official releases.
-
- KVRAF
- 6468 posts since 17 Dec, 2009
Someone got up on the wrong foot (at 5AM no less)Urs wrote: ↑Fri Jul 23, 2021 2:59 am Yeah, it's really only a Big Sur update. The other 50 or so major improvements, refactorings, redesigns and fixes really just happened purely by chance. The new UIs just randomly popped up out of nowhere, for M1 support a developer had to just click a widget in Xcode and there it was. The reworked preset with revised tags and more consistent volumes and stuff were sent in voluntarily by the sound designers, our content team had no work with it. For a year, the team at u-he headquarters just had to sit and wait it out until the pieces simply aligned all by themselves.
Only, they weren't sitting in the headquarters, they were working remotely, juggling life and work in a pandemic and none of the above happened by itself.
- u-he
- 28067 posts since 8 Aug, 2002 from Berlin
Hehehe, sorry, it's just that after a year of excessively tedious work, I might have lost my humour there for a bit.
It occurs to me that the time it takes to bring everything up to date takes longer now than Apple and others need to change the equation again. That is also because we don't just have to deal with Apple, we also have to sync those updates with our own schedule, and with stuff like VST3, AAX and external contributors/contractors. This has taken months and we still had to compromise. It just really hurts to be forced to drop out of running projects simply because there's no way to align them with the stuff that's going on.
So we'll spend some time on a technology that will hopefully make those things somewhat independent. Like, we hope to be able to at least update plug-in layers independently from our internal versions. With AAX this is going to be a necessity as it is currently not possible to build proper AAX plug-ins on a machine that also builds for Apple Silicon (unless we force ourselves into workarounds that may take weeks to debug). But it will also prevent issues like the major changes to AU that broke things for us on Big Sur.
So maybe in a few months we'll simply be able to add a Mac AAX layer to the same version/revision that we're going to release in a week or two. Then yes, maybe we can time our updates a little more competitively
It occurs to me that the time it takes to bring everything up to date takes longer now than Apple and others need to change the equation again. That is also because we don't just have to deal with Apple, we also have to sync those updates with our own schedule, and with stuff like VST3, AAX and external contributors/contractors. This has taken months and we still had to compromise. It just really hurts to be forced to drop out of running projects simply because there's no way to align them with the stuff that's going on.
So we'll spend some time on a technology that will hopefully make those things somewhat independent. Like, we hope to be able to at least update plug-in layers independently from our internal versions. With AAX this is going to be a necessity as it is currently not possible to build proper AAX plug-ins on a machine that also builds for Apple Silicon (unless we force ourselves into workarounds that may take weeks to debug). But it will also prevent issues like the major changes to AU that broke things for us on Big Sur.
So maybe in a few months we'll simply be able to add a Mac AAX layer to the same version/revision that we're going to release in a week or two. Then yes, maybe we can time our updates a little more competitively
- KVRAF
- 2491 posts since 3 Dec, 2006
Thank you Urs And Your team for the hard work you guys put into your products, I have great admiration and appreciation for that even if there was no pandemic or other obstacles in the way!
- KVRian
- 1294 posts since 12 Nov, 2002 from Newcastle, UK
Massive thanks for these updates! CPU usage is down in Hive And the new GUIs for ZebraCM and Triple Cheese have got me revisiting these old classics, they really do feel like new synths
"Micro Kid speaks digi-talk.."
-
- KVRist
- 74 posts since 22 Apr, 2018
That new GUI for triple cheese is excellent and intuitive. I hadn't given triple cheese much attention before in favour of it's paid and more fully featured older brothers and sisters. Today though I was able to make something vibrant and playable with it right away. Great job, worth the wait!
-
- KVRist
- 58 posts since 10 Dec, 2004
Thanks for the udpates !
There is an issuexwith Podolski : the preset HS Edge Bastion sounds differently that previously with precedent versions. So, I had to reinstall an old version of Podolski to keep working on a song . Hope you can identify the reason of this strange problem.
There is an issuexwith Podolski : the preset HS Edge Bastion sounds differently that previously with precedent versions. So, I had to reinstall an old version of Podolski to keep working on a song . Hope you can identify the reason of this strange problem.
-
tasmaniandevil tasmaniandevil https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=62450
- KVRAF
- Topic Starter
- 1737 posts since 22 Mar, 2005 from a planet called u-he
There have been three bug fixes which might affect how some Podolski presets sound:
* the single trigger LFO was free running
* the arpeggiator wasn't taking the main transpose setting into account
* notes have been clamped to the MIDI range, so any notes lower than C-2 or higher than G8 will now play those notes to avoid sound glitches and worse problems
In case of Edgebastion, it's most likely the main transpose which is now using the value saved in the preset, which is 0. Previously all arpeggiator presets would default to a -12 setting instead.
You can manually adjust the Podolski transpose setting in your project and it should sound as before.
That QA guy from planet u-he.
-
- KVRian
- 678 posts since 15 Feb, 2012 from France