u-he

mustgroove · Post by **mustgroove** » Tue Sep 17, 2013 1:13 am

Touching just the IPS and Pre Emphasis controls, this thing acts like a very easy and intuitive EQ... so easy to dial in a tone, trying to replicate it with an actual EQ is way more laborious

woodsdenis · Post by **woodsdenis** » Tue Sep 17, 2013 1:44 am

Just strapped one instance across the master bus on a mix. Superb. Blown my budget on Diva and Satin in the last couple of days, very happy camper though.

David Else · Post by **David Else** » Wed Sep 18, 2013 9:57 am

#rob wrote:
David Else wrote:controller knobs jumping all over the place (...) Reaper 32bit 4.52 / Windows 7 (...) Any idea?
Yup, there seem to be "jumpy knobs" problems with exactly this configuration: Win/Reaper/Satin. No other host (that we tested) shows this behaviour. OSX Reaper is fine...
We're onto it!

Really hope this gets addressed in the 1st minor update asap as it's a 'show stopper' here

Urs · Post by **Urs** » Wed Sep 18, 2013 12:15 pm

David Else wrote:
#rob wrote:
David Else wrote:controller knobs jumping all over the place (...) Reaper 32bit 4.52 / Windows 7 (...) Any idea?
Yup, there seem to be "jumpy knobs" problems with exactly this configuration: Win/Reaper/Satin. No other host (that we tested) shows this behaviour. OSX Reaper is fine...
We're onto it!
Really hope this gets addressed in the 1st minor update asap as it's a 'show stopper' here

I'll give it another spin today... we'll need to log all communication between Reaper and plug-in to figure this one out.

Urs · Post by **Urs** » Wed Sep 18, 2013 1:28 pm

Urs wrote:
Really hope this gets addressed in the 1st minor update asap as it's a 'show stopper' here
I'll give it another spin today... we'll need to log all communication between Reaper and plug-in to figure this one out.

It's an interesting phenomenon. I've started to get to its grounds.

In Reaper we get mouse events while we're still working on mouse events. In other words, while a mouse event on the slider is still being processed, another event comes in already.

That's very unusual and shouldn't happen. It means that mousing is somewhat multithreaded.

There's a quick fix, but that quick fix seems somewhat sluggish. I need to dig deeper and come up with a better workaround.

#rob · Post by **#rob** » Wed Sep 18, 2013 3:13 pm

From our bug database... just tested, working fine in Rev 1867.

*insert applause*

Burillo · Post by **Burillo** » Wed Sep 18, 2013 3:22 pm

that's 678 bugs for Satin, or 678 bugs for all u-he products?

David Else · Post by **David Else** » Wed Sep 18, 2013 3:57 pm

#rob wrote:
From our bug database... just tested, working fine in Rev 1867.
*insert applause*

Nice! Looking forward to the release

#rob · Post by **#rob** » Wed Sep 18, 2013 4:00 pm

Burillo wrote:that's 678 bugs for Satin, or 678 bugs for all u-he products?

678 entries for anything ever u-he, including feature requests, ideas, redundancies, notes... definitely not a number to worry about.

sascha · Post by **sascha** » Wed Sep 18, 2013 6:59 pm

#rob wrote:
Burillo wrote:that's 678 bugs for Satin, or 678 bugs for all u-he products?
678 entries for anything ever u-he, including feature requests, ideas, redundancies, notes... definitely not a number to worry about.

Haha, I just had to look up what entry #666 was about. Something about the iLokalypse???

... no, alas it's '0000666: Satin: Knobs have wildly differing sensitivities...'
Still unfixed, though... although not satanic, but more cosmetic

Ch00rD · Post by **Ch00rD** » Thu Sep 19, 2013 10:02 am

sascha wrote:
#rob wrote:
Burillo wrote:that's 678 bugs for Satin, or 678 bugs for all u-he products?
678 entries for anything ever u-he, including feature requests, ideas, redundancies, notes... definitely not a number to worry about.
Haha, I just had to look up what entry #666 was about. Something about the iLokalypse???

... no, alas it's '0000666: Satin: Knobs have wildly differing sensitivities...'
Still unfixed, though... although not satanic, but more cosmetic

Some numerologists may still be a bit worried that number 666 is a Satan -- oops, Satin bug, instead of a Tyrell N6 bug or something.

Sounds like knobs are much like humans, btw.

ThomasHelzle · Post by **ThomasHelzle** » Thu Sep 19, 2013 10:04 am

"wildly differing sensitivities" indeed! LOL
Good one Ch00rD

Cheers,

Tom

iamyourfather · Post by **iamyourfather** » Fri Sep 20, 2013 10:39 am

Urs wrote:
Urs wrote:
Really hope this gets addressed in the 1st minor update asap as it's a 'show stopper' here
I'll give it another spin today... we'll need to log all communication between Reaper and plug-in to figure this one out.
It's an interesting phenomenon. I've started to get to its grounds.

In Reaper we get mouse events while we're still working on mouse events. In other words, while a mouse event on the slider is still being processed, another event comes in already.

That's very unusual and shouldn't happen. It means that mousing is somewhat multithreaded.

There's a quick fix, but that quick fix seems somewhat sluggish. I need to dig deeper and come up with a better workaround.

I am on reaper and windows7 and have not had this issue (my reaper version is 4.32) I'll keep an eye on it and let you know if it happens.

EDIT : just saw you fixed it already

Rah · Post by **Rah** » Fri Sep 20, 2013 7:58 pm

David Else wrote:
#rob wrote:
From our bug database... just tested, working fine in Rev 1867.
*insert applause*
Nice! Looking forward to the release

Me too, any ETA on when the next build will be out? Could do with these knobs sorting out. Cheers

SJ_Digriz · Post by **SJ_Digriz** » Sat Sep 21, 2013 1:46 am

You wouldn't happen to have a nice Satin render for a desktop background like you have for Bazille would you?

u-he

KVR Audio

Satin goes V1.1