u-he

Stollmeister · Post by **Stollmeister** » Sat Sep 07, 2013 12:14 pm

Thing is, for em it appears as soon as I turn it up enough to hear two repeats. It only disappears if there is a single repeat. I can't seem to get a ping pong delay since that requires more than one repeat.

ducelare · Post by **ducelare** » Sat Sep 07, 2013 12:15 pm

it would be very much appreciated to have a demo with less crackling. Especially when using multiple instances i find it nearly impossible to judge the sound when constantly interrupted with bursts of noise.

zvenx · Post by **zvenx** » Sat Sep 07, 2013 12:23 pm

4damind wrote:Some bugs I found with the latest Beta (1818):

random crashes if switching presets on the main screen (not in the preset browser, this is working)

freezing of Cubase 7 64Bit if moving the range knob (Phaser)

Hi, are you on mac or pc?
I am trying to reproduce this......

all I am getting is a few audio dropouts, but no freezing or crashing.
Are they specific preset changes that are causing yours to crash?

edit:
spoke to soon.

on vst3 I couldn't replicate the range knob crashes but in vst2.4 almost instantly.

edit 2:
I eventually could on vst3 using wild range swings.....
rsp

4damind · Post by **4damind** » Sat Sep 07, 2013 12:38 pm

zvenx wrote:Hi, are you on mac or pc?
I am trying to reproduce this......

all I am getting is a few audio dropouts, but no freezing or crashing.
Are they specific preset changes that are causing yours to crash?
rsp

PC but I'm not sure if this specific for Cubase on the PC and I use the VST2 version (not the VST3 version).

[Edit] Aah, ok... are you on Mac?

Agility · Post by **Agility** » Sat Sep 07, 2013 12:42 pm

Urs wrote:
Agility wrote:One bug I've noticed so far is in one project I loaded Satin into, when using the A type compander encoding or decoding or both the audio would cut out until changing it to another compander mode and bypassing the plugin and unbypassing again, internally.
oh... can you reproduce it or is it random?
One question, Satin has a mix knob on it and is a nice feature, just wondering if back in the day in hardware, there was such a way to mix in NR?
It was a bit different back in the days. The reel 2 reel tape machines hadn't necessarily had noise reduction at all. But people would have separate NR modules in 19 inch racks. As those modules typically consisted of a compressor and an expander, one could just use them as such, even without the tape. Thus they could be used as send effects or inserts in a console, with the otion to do parallel compression. The mix knob in Satin lets one use them for parallel compression too

Yeah it happens every time, I did some more experimenting though, it only seems to happen on Group channels and the Masterbuss, not affecting individual instrument tracks. Note: this has only happened in 1 project and I've tried it in a few.

edit: It seems hit or miss actually, I've opened new instances a few times and set it to A type and it will work and then cut off..

RE: NR... I see, do you or anyone know of any resources for more info on common tape techniques and NR tricks etc?(PM me if OT) I'm making 80s music so trying to figure out what was done though Satin has become a god send, especially with the Compander section, I'm finally getting the sounds I was after!!

Thanks.

4damind · Post by **4damind** » Sat Sep 07, 2013 12:48 pm

zvenx wrote:spoke to soon.

on vst3 I couldn't replicate the range knob crashes but in vst2.4 almost instantly.
rsp

The good thing (I'm not sure if this is some improvement with later Cubase versions or has something todo with Windows 8 ) the Cubase task can be killed with the Taskmanager. The Asio driver is unloaded/released correctly and Cubase can be re-started without a reboot. In the past this doesn't work and needs a reboot.

Urs · Post by **Urs** » Sat Sep 07, 2013 12:50 pm

Quick round up:

A bug related to delay time length is fixed as of yesterday, a few unpleasant noises are not (will be updated in a few days, in a 1.0.x update)

The Cubase latency reporting problem (freezes, stalls on Flanger, Bypass, Preset loading) is a problem, and I'm working on a workaround.

Compander silence: Need Sascha for this, he can look into it for a 1.0.x update

NR techniques of the 80ies... maybe Sascha knows where to find that info - he's been consulting people/websites himself...

Compyfox · Post by **Compyfox** » Sat Sep 07, 2013 12:51 pm

I can also confirm that SATIN doesn't show the LED movement in the delay mode in the new Blue Cat Audio MB-7 Mixing Console (used the demo).

And, it takes a while after you messed with the settings, until SATIN updates the sound.

Another thing that I kind of miss with SATIN, is a "lofi" mode. I can't create proper lofi sounding tapes. I think the LPF/HPF of the delay is 6dB/Oct. Either a post EQ or a steepness control would be nice. Especially if you consider adding slower tape speeds. (couldn't recreate that dirty tape sound form the Roland Space Echo to be honest - or I'm just stupid).

And I have to agree with 4damind - a better tagging system for non-tech heads for the delay lines would be great.

Agility · Post by **Agility** » Sat Sep 07, 2013 12:54 pm

One other question, what is classed as a vintage tape machine date wise Are we talking 30s? 50s? 80s?

Thanks.

Urs · Post by **Urs** » Sat Sep 07, 2013 1:04 pm

Ok, just checked. Our Latency Reporting is absolutely conform with VST Specs. Steinberg writes "this could lead to audio playback interruption because the host has to recompute its internal mixer delay compensation" so I guess that this is what's happening.

Does anyone experience a real crash, i.e. Cubase "quits unexpectedly" when the flanger parameters are set, or when Tape Bypass is pressed?

4damind · Post by **4damind** » Sat Sep 07, 2013 1:04 pm

Compyfox wrote:And I have to agree with 4damind - a better tagging system for non-tech heads for the delay lines would be great.

I think a additional info only for time synced stuff.. eg. "4,00 (1/4)" in the info bar could be a quick workaround. Nice would be of course a right-click menu to select such typical delay times (1/8, 1/8d, 1/4, 1/4d,...)

zvenx · Post by **zvenx** » Sat Sep 07, 2013 1:09 pm

4damind wrote:
zvenx wrote:Hi, are you on mac or pc?
I am trying to reproduce this......

all I am getting is a few audio dropouts, but no freezing or crashing.
Are they specific preset changes that are causing yours to crash?
rsp
PC but I'm not sure if this specific for Cubase on the PC and I use the VST2 version (not the VST3 version).

[Edit] Aah, ok... are you on Mac?

I am on both.
wasn't able to replicate your first problem
but both on mac and pc in Cubendo....I was able to replicate the second....much easier with vst 2.4, but eventually with vst3 too.
thanks
rsp

zvenx · Post by **zvenx** » Sat Sep 07, 2013 1:12 pm

Urs wrote:Ok, just checked. Our Latency Reporting is absolutely conform with VST Specs. Steinberg writes "this could lead to audio playback interruption because the host has to recompute its internal mixer delay compensation" so I guess that this is what's happening.

Does anyone experience a real crash, i.e. Cubase "quits unexpectedly" when the flanger parameters are set, or when Tape Bypass is pressed?

I eventually did on both mac (cubase) and Pc (Nuendo)
way more so in the vst2.4 version.
I couldn't get it to do so in the vst3 under what would be my typical use, but if you really move the range back and forth in vst3 it crashes.....on the vst 2.4 I didn't have to do so much back and forth to get it to crash.
Mac quits......PC quits with a runtime error.

I emailed you...

rsp

Compyfox · Post by **Compyfox** » Sat Sep 07, 2013 1:17 pm

Urs wrote:Ok, just checked. Our Latency Reporting is absolutely conform with VST Specs. Steinberg writes "this could lead to audio playback interruption because the host has to recompute its internal mixer delay compensation" so I guess that this is what's happening.

Doesn't mean that Cubase shows the correct values.

Urs wrote:Does anyone experience a real crash, i.e. Cubase "quits unexpectedly" when the flanger parameters are set, or when Tape Bypass is pressed?

No crash, the host just hangs and you get the "hourglass" (or with Win7, the rotating cycle) treatment.

And... can we please talk about the reference level again?

It looks like you can setup the reference level of the VU, but is SATIN hardcoded to -12dBFS? I kind of expected the saturation to also shift, the lower the reference level.

Or am I imagining things?

EDIT:
I can now confirm that Cubase shows the wrong(!!!) sample values in the Plugin Information window. And I don't think this will be fixed with 7.06 (since they didn't track that yet - I remember something along the lines from longer phone calls).

Why? I just checked what Slate VTM shows in C.Budde's Analyser, and here it shows 1700 samples, in Cubase way past 3100 samples. Satin (VST2) shows correctly btw. Can't check the VST3 version, since it doesn't want to load anything VST3 on my end.

zvenx · Post by **zvenx** » Sat Sep 07, 2013 1:21 pm

4damind wrote:...............

I think a additional info only for time synced stuff.. eg. "4,00 (1/4)" in the info bar could be a quick workaround. Nice would be of course a right-click menu to select such typical delay times (1/8, 1/8d, 1/4, 1/4d,...)

+1000

rsp

u-he

KVR Audio

Satin goes V1.1