Satin goes V1.1
-
- KVRAF
- 5510 posts since 6 May, 2002
An I the only one that thinks it would be a good idea to have the input gain value permanently displayed on the large input knob?
Last edited by electro on Mon Oct 07, 2013 2:37 pm, edited 1 time in total.
Intel Core2 Quad CPU + 4 GIG RAM
-
- KVRist
- 141 posts since 25 Feb, 2010
Which Satin preset or other settings would you recommend for solo piano? Thanks.
By the way, I just tried the RP Mastering Tape preset on a sampled piano, and I could hear the nice subtle glue and the replacement of harsh digital artifacts with some subtle warmth...simply amazing! Well done, u-he!
By the way, I just tried the RP Mastering Tape preset on a sampled piano, and I could hear the nice subtle glue and the replacement of harsh digital artifacts with some subtle warmth...simply amazing! Well done, u-he!
-
- KVRian
- 722 posts since 15 Feb, 2012 from France
Even if the monitoring section is great and useful as is, I have a small suggestion : a small blue LED (similar to the Clip/Headroom ones) next to the meters, that would get brighter as the signal saturates.
- KVRian
- 1141 posts since 2 Oct, 2001 from Berlin, Germany
I'd consider that obsolete.nilhartman wrote:Even if the monitoring section is great and useful as is, I have a small suggestion : a small blue LED (similar to the Clip/Headroom ones) next to the meters, that would get brighter as the signal saturates.
See, saturation can have 3 causes in Satin:
1) In one of the simulated circuits (eq, gainstages etc.). This would be shown by the 'headroom' LED.
2) Within the tape part. This is reflected by the VU meters when switched to 'input'. It depends a bit on the 'tape' model, but the reference point for 1% THD is around -15dBFS (look at the figures in the manual). So, if you set the VU reference to -15 approx., you have a good measure of the resulting signal. Keep in mind that the entire tape-saturation process is not frequency-linear, hence any visual indication isn't that much of value. Careful listening is mandatory.
3) The output circuit. It's got it's dedicated visualizer, plus the VU & peak meters when set to 'output'.
Sascha Eversmeier [formerly digitalfishphones]
TOURAGE DSP
croquesolid drum processor- mix real drums fast & focused
TOURAGE DSP
croquesolid drum processor- mix real drums fast & focused
-
- KVRist
- 37 posts since 13 Nov, 2009 from Barcelona / Spain
Just wanted to say hello. Bought Satin yesterday ^^
-
- KVRist
- 66 posts since 23 Feb, 2008 from france
just bought it !
well uh i hope i did actually i had to go though that Mycomerce or is it Share it ? pff i'm lost this payment method is real pain in the ass i always forget what login it is have to ask for new password by mail blablabl...
please add some paypal directly on your website !
well uh i hope i did actually i had to go though that Mycomerce or is it Share it ? pff i'm lost this payment method is real pain in the ass i always forget what login it is have to ask for new password by mail blablabl...
please add some paypal directly on your website !
-
- KVRist
- 37 posts since 13 Nov, 2009 from Barcelona / Spain
When I load Satin into Wavelab 8 (64 bit) I get an error both in VST3 and VST2.4 formats.
VST3 says the plugin it can't handle the number of input channels (2!).
VST2.5 (Satin(x64)) tells it has no GUI resources.
Both work fine in Cubase 7.
VST3 says the plugin it can't handle the number of input channels (2!).
VST2.5 (Satin(x64)) tells it has no GUI resources.
Both work fine in Cubase 7.
-
- KVRist
- 124 posts since 28 Apr, 2006
I can confirm the first one. As far as VST2.4 (I think you meant VST 2.4), I had no problems. I was going to put in a trouble ticket with U-he.dorremifasol wrote:When I load Satin into Wavelab 8 (64 bit) I get an error both in VST3 and VST2.4 formats.
VST3 says the plugin it can't handle the number of input channels (2!).
VST2.5 (Satin(x64)) tells it has no GUI resources.
Both work fine in Cubase 7.
For me right now it's no big deal since I can use VST2.4. But I would love to see this get fixed so I can use VST3 in Wavelab.
-
- KVRist
- 44 posts since 6 Jul, 2002 from Ibiza
I have a session with only one audio track (stereo/44.1kHz/24 bit)
from one minute to another I can't open Satin in that session anymore. No matter where in mixer. (track/mixbus)
the moment I assign satin as insert Cubase freezes/becomes unresponsive.
no crashlog available
I can see black (inactive) insert for satin in mixer with red frame but nothing more. It's not properly loaded and Cubase waits.
this is very annoying. I tried to save new version but satin won't load anywhere in session.
loads fine in other projects. I'm using VST3 64-bit (only)
I'm on W8 x64, Cubase 7.0.6 64bit, latest version of Satin (re-installed today)
from one minute to another I can't open Satin in that session anymore. No matter where in mixer. (track/mixbus)
the moment I assign satin as insert Cubase freezes/becomes unresponsive.
no crashlog available
I can see black (inactive) insert for satin in mixer with red frame but nothing more. It's not properly loaded and Cubase waits.
this is very annoying. I tried to save new version but satin won't load anywhere in session.
loads fine in other projects. I'm using VST3 64-bit (only)
I'm on W8 x64, Cubase 7.0.6 64bit, latest version of Satin (re-installed today)
- u-he
- Topic Starter
- 30174 posts since 8 Aug, 2002 from Berlin
Does the project open if you temporarily put Satin.vst3 somewhere else, i.e. not a Vstplugins folder?speed771 wrote:I can see black (inactive) insert for satin in mixer with red frame but nothing more. It's not properly loaded and Cubase waits.
This one is definitely new to us. We have been informed by a Steinberg employee about a requirement of Cubase that goes beyond interpretive results of our exegesis of the VST3 specification. We'll make updates available asap, but I can't promise that this is the same problem that we're addressing.
Please let us kow what's happening with the removed plug-in.
Cheers,
- Urs
- KVRAF
- 24403 posts since 7 Jan, 2009 from Croatia
Yep.
- KVRAF
- 5912 posts since 17 Aug, 2004 from Berlin, Germany
I have sometimes "pure virtual function call" errors and it seems only since using Satin as the vst3 version. Because it's the only new plug-in I used the last time, I would say it's Satin. I changed it to the vst2 version and since this time not such errors. (Cubase 7.0.6 64Bit)
| Links