u-he

dorremifasol · Post by **dorremifasol** » Mon Sep 30, 2013 8:15 pm

Greetings.

I'm having problems with Satin and Wavelab. I haven't been unable to make it work in Wavelab 7 or 8, both 32 and 64 bits, and vst2.4 and vst3 versions. Last version (rev.1900).

No problems in Cubase 7 though.

@l3x!5 · Post by **@l3x!5** » Mon Sep 30, 2013 9:07 pm

Hello,

I had a 1.1 Satin-related crash while quitting Logic Pro X. I can send you the crash report if you provide me with an appropriate email address.

On an unrelated note, I also had a VAT related problem from the purchase, it's a bit tricky (country not listed but part of France, EU VAT should not be applied else I pay VAT twice) so if I could talk to a human about it and not some robot from share-it, it would be greatly appreciated

Is the web support form the best way to address this?

Cheers!

EvilDragon · Post by **EvilDragon** » Mon Sep 30, 2013 9:25 pm

Just e-mail Urs directly at urs@u-he.com, he was very helpful with my VAT issue.

@l3x!5 · Post by **@l3x!5** » Mon Sep 30, 2013 9:27 pm

EvilDragon wrote:Just e-mail Urs directly at urs@u-he.com, he was very helpful with my VAT issue.

Thanks! Will do

I'll join the crash reports, now my session crashes consistently unless I remove Satin 1.1 from the component folder.

mljung · Post by **mljung** » Mon Sep 30, 2013 9:30 pm

Just my appreciation for the new slower speeds, in Satin 1.1, adds more colors to choose from.
Would make an overall mix-knob even more useful I think [as in more pronounced color in smaller dozes, when dialed back]. Wonderful!

::
Mads

ho66it · Post by **ho66it** » Tue Oct 01, 2013 12:23 am

FWIW:
On a project with four instances of Satin (AU v1900) running in Reaper v4.21, I saw about a 10% CPU load increase after upgrading from v1837.
iMac 3.07gHz Core 2 Duo

mustgroove · Post by **mustgroove** » Tue Oct 01, 2013 3:44 am

Is it just me or is the "lfo rate" of the wow & flutter parameter way way faster now? It seemed like much more of a slow subtle warbling before, but now when you crank it all the way up it's super fast and not really pleasant...

sascha · Post by **sascha** » Tue Oct 01, 2013 5:29 am

mustgroove wrote:Is it just me or is the "lfo rate" of the wow & flutter parameter way way faster now? It seemed like much more of a slow subtle warbling before, but now when you crank it all the way up it's super fast and not really pleasant...

It's not faster, it's just more complex and realistic, and simulates scrape flutter, too. Perhaps you were expecting some pleasent warbling & chorusing but imperfect tape transport sounds way different...

wald · Post by **wald** » Tue Oct 01, 2013 8:42 am

Urs wrote:
wald wrote:I assume hiss automute can be disabled? I.e., you don't remove features from Satin?
But of course!

Great!
I can't wait to try your new "lofi" modes (I guess that was not what you guys expected when you spent months analyzing high quality tape

)

Ch00rD · Post by **Ch00rD** » Tue Oct 01, 2013 11:13 am

mustgroove wrote:Is it just me or is the "lfo rate" of the wow & flutter parameter way way faster now? It seemed like much more of a slow subtle warbling before, but now when you crank it all the way up it's super fast and not really pleasant...

The W&F speed is directly related to the tape 'Speed ips'; so if you lower the tape speed, the W&F 'rate' will go slower as well.

silhouette · Post by **silhouette** » Tue Oct 01, 2013 11:54 am

All good here! What am I saying? I mean all fantastically good here. Well done to the team.

geronimo · Post by **geronimo** » Tue Oct 01, 2013 12:41 pm

geronimo wrote:Since Digital Performer 8.04, with a project loaded medium, playback correctly performed with seven instances of SATIN. As soon as I add an eighth SATIN instance, the speed of the Project is much slowed and the sound deteriorating:.

It's work fine henceforth with 12 Satin instance open in D.P. 8.04 with 1.1. Satin Version .

Endor-8o8 · Post by **Endor-8o8** » Tue Oct 01, 2013 2:05 pm

Hello U-He guys !
I recently bought my Satin license and I just wanted to stop by and express my gratitude to your team for making such great tools and instruments !
I also wanted to ask a stupid question, why does the minimum value of speed ips knob is set "1.87" ? Is there a special reason for that so specific value ?
Yes stupid question...

#rob · Post by **#rob** » Tue Oct 01, 2013 2:10 pm

ho66it wrote:FWIW:
On a project with four instances of Satin (AU v1900) running in Reaper v4.21, I saw about a 10% CPU load increase after upgrading from v1837.
iMac 3.07gHz Core 2 Duo

Very strange.

I just recently put together a Logic 9 project with 10 instances of Diva (yup, the CPU muncher) and 20 instances of Satin, that took OSX's Activity Monitor to 40% CPU with Rev 1874 (pre 1.1) on a Mac Mini with i7 2.6 quad.

Today I tested it with Rev 1901, and the CPU load is exactly the same as with Rev 1874, no increase in CPU hunger detectable.

So I really don't know what to tell you...

EDIT:

Rev 1874:

Rev 1901:

Ch00rD · Post by **Ch00rD** » Tue Oct 01, 2013 2:13 pm

Endor-8o8 wrote:I also wanted to ask a stupid question, why does the minimum value of speed ips knob is set "1.87" ? Is there a special reason for that so specific value ?
Yes stupid question...

It probably makes more sense when you see that it misses one digit (it actually is 1.875), and that the most commonly used tape speeds are 30.0, 15.0 and 7.5 for high-end machines, 3.75 and 1.875 simply follow the series of 'powers of two' downwards to the low end.

u-he

KVR Audio

Satin goes V1.1