Satin goes V1.1

[Tp3]

Any chance of making the two last dots of the "peak bar" in the color red ?

Erm... the region from 0 to 3db IS red, or did I miss something here... ?

Let me explain...

I meant discernible means to understand where the peaks are exactly. as of now, if signal is under 0vu, it is blue throughout. when signal passes the 0vu, everything above 0vu is red (all the "dots" are red).
I asked if it would be possible that only the two last "dots" in the peak meter would be red (and if signal is below 0vu, that the last dots are in some other color. and in any case - make the area between the peak value and RMS value fade slower).

The reason that I'm asking is because when I tweak the setting, I strive for the same peak values as the untreated signal. it's kinda hard to see what's going on there...

[Urs]

We'll look into the CPU issue. Our tests haven't shown any significant difference yet, but maybe it's related to settings. Is there any particular preset that's got an obvious increase in CPU consumption?

[sascha]

as of now, if signal is under 0vu, it is blue throughout. when signal passes the 0vu, everything above 0vu is red (all the "dots" are red).

When monitoring the peaks, forget the VU for a while. The peak meter bars are independent of the VU meter (e.g. they don't respond to the reference-level setting). The peak-meter bars are 'absolute', while the VUs are 'relative', since they have a reference point.

If the peak meters go into the red, it definitely means you're over 0dBFS. It's that simple. Try switching it to 'output', leave the soft-clip off and you'll notice once the peaks leave the blue region, you're shooting through the roof. 0dBFS is the limit in the digital realm, I see no reason why we should have a fuzzy window here. It's either above or not.

The reason that I'm asking is because when I tweak the setting, I strive for the same peak values as the untreated signal. it's kinda hard to see what's going on there...

You should perhaps aim more at an equal RMS level, rather than peak. Peak says nothing about the sonic integrity and the perceived volume. Our hearing sense is tuned to RMS. And, as saturation chops off the peaks, you're just ending up with increased volume when you're only monitoring peak levels. If increased volume is what you want from the plugin, you're better off judging via the VUs and choose RMS as their mode.

[Tp3]

Well, I'm looking for evaluating what SATIN is doing to my audio, where audio levels of wet/dry are exactly the same (so I wan't have a placebo effect because of increased volume). and as peak levels are absolute numbers, reading the exact peak value is quite hard (I do not aim for increased volume or saturation or such... just means to understand what's going on...).

[Garycactus]

Just checked the CPU again with Satin 1.1.
10 tracks (VI) in a song. 3 Satins on the tracks and one on the master.
4 Satins 1.1 doubled the CPU.
Satin 1.0 didn't create any problems.

Can't find 1.0 version, probably I deleted it...

But I have found the answer - just ordered a new iMac i7 with SSD especially to run Satin-))
Shall I send the bill to U-he?

[sascha]

Well, I'm looking for evaluating what SATIN is doing to my audio, where audio levels of wet/dry are exactly the same (so I wan't have a placebo effect because of increased volume).

That's exactly what the auto-makeup functionality is made for (above the input-level knob). Use it.

and as peak levels are absolute numbers, reading the exact peak value is quite hard (I do not aim for increased volume or saturation or such... just means to understand what's going on...).

You seem to be ignoring what I wrote previously. Trying again.
Understand: peak level tells your ears NOTHING about perceived volume. Your hearing sense uses a window function to determine volume. Just as your eyes need to adapt when you're walking from the open daylight into a darkened room, all of our senses include inertia. Peak metering tells you only about transients and overshoot, as this is important for 'absolute' systems like digital recording media, but it is completely pointless to apply this to human perception.

Don't get me wrong, but these are audio engineering fundamentals. For Satin, we have written an in-depth manual covering monitoring aspects, too. Did you read it?

[Tp3]

Well, I'm looking for evaluating what SATIN is doing to my audio, where audio levels of wet/dry are exactly the same (so I wan't have a placebo effect because of increased volume).

That's exactly what the auto-makeup functionality is made for (above the input-level knob). Use it.

I do use it. a lot. to "fine-tune" the results (as the manual suggests)

and as peak levels are absolute numbers, reading the exact peak value is quite hard (I do not aim for increased volume or saturation or such... just means to understand what's going on...).

You seem to be ignoring what I wrote previously. Trying again.

No, I am not ignoring. and I do try to adhere to the "audio engineering fundamentals" (about peak levels and perceived volume).

I know that peak level tells us nothing...

For Satin, we have written an in-depth manual covering monitoring aspects, too. Did you read it?

Yes, I did (more then once).

And I do understand (and know) what you have told me. but I seem to fail in explaining myself....

Anyway, thanks

[Krakatau]

Just checked out the update, wonderful job as far as i could judge, i noticed both the duration of delays and the equilibration of feedback control, ...needless to say the mute control of both asperity and hiss is very useful !!!!!

[electro]

Any chance of direct text input?

Then you could also increase the Output gain to -20 / +20 db without having any resolution / precision issues

[David Else]

bought it... love it!

new 1.1 is great, the reaper jumping knobs bug is gone

bad news, i have had a crash with 1.1 already:

Faulting application name: reaper.exe, version: 4.5.2.0, time stamp: 0x52291d3c
Faulting module name: Satin.dll, version: 0.0.0.0, time stamp: 0x5249606f
Exception code: 0xc0000005

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-10-02T17:08:19.000000000Z" />
<EventRecordID>8132</EventRecordID>
<Channel>Application</Channel>
<Computer>David-PC</Computer>
<Security />
</System>
- <EventData>
<Data>reaper.exe</Data>
<Data>4.5.2.0</Data>
<Data>52291d3c</Data>
<Data>Satin.dll</Data>
<Data>0.0.0.0</Data>
<Data>5249606f</Data>
<Data>c0000005</Data>
<Data>00059f82</Data>
<Data>668</Data>
<Data>01cebf8e1e9a9b99</Data>
<Data>C:\Portable Apps\Reaper 4\reaper.exe</Data>
<Data>C:\Portable Apps\Reaper 4\Plugins\VST\Satin.dll</Data>
<Data>3bae367a-2b85-11e3-a6b6-001641f6705b</Data>
</EventData>
</Event>

[thinman]

I'm super-in-love with this plugin but I'm having some issues with the new version 1.1. I'm on Windows 8 64-bit, AMD FX8350 processor, AMD 7570 GPU, and Reaper 32-bit 4.52. I'm getting freezing and stuttering using Satin now. It happens mostly when I have the UI open and gets worse as more instances are loaded, even though my processor is showing less than 25% use in most projects. I haven't found a consistent "trigger" for this behaviour yet but I'll keep playing around.

[geronimo]

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:

I do not know how this is possible but if I do so, it never is .



Buffer Setting: 512
I'm on a MacPro (2 X 2,66 Ghz) with 10 Go RAM Memory under Snow Leopard 10.6.8. with LOGIC 9.1.8. or Digital Performer 8.04 . Same behavior with Digital Performer 8 + graphics freeze _
This does not occur with instances of SATIN in bypass mode _ _

[David Else]

I know you guys are busy with AAX, but any luck finding the crash bug?

[Urs]

I know you guys are busy with AAX, but any luck finding the crash bug?

Sorry, the 3rd of October was a public holiday here and Sascha took the 2nd off already until Monday. We'll look into it next week.

What exactly did you do when it crashed? Is it a reproducible thing?

Cheers,

- Urs

[David Else]

I know you guys are busy with AAX, but any luck finding the crash bug?

Sorry, the 3rd of October was a public holiday here and Sascha took the 2nd off already until Monday. We'll look into it next week.

What exactly did you do when it crashed? Is it a reproducible thing?

Cheers,

- Urs

Satin was running as an insert effect, I was not doing anything in the interface, not sure how to reproduce it, reaper just froze totally, was hoping the error codes i posted might help.