Satin goes V1.1

[alphadelphi]

TL; DR

my first impressions:

1 - good sounding
2 - i miss a wet/dry control

and most important:

3 - i think that buttons like "presets" should be bigger at least to underlie the label

[Compyfox]

Speaking of which... I don't know how to rename the Fostex... Grundig

suggestions: Foxtec, Grundge
Then there's Ronald, Apex, Taec, Rovex, Otrai... the list goes on

IMO, not a good solution.

Which is why I called the RE-201 initially "Roland Space" (which can be considered a play of words - also with my name), and I think the new name "Space Echo" is just too obvious.

But, I'll simply use abbreviations, and write the correct name in the preset info. This doesn't seem to be a problem so far. So going for REV-B77 or Fos-280, GR-TK747 is still fine. Just like the A8x8 presets in the studio section. Because the correct names can be written in the additional info block.

Actually, Nebula presets go the same route these days - sans the info block.

We had a bit of a problem that many presets went in just-in-time, and - of course - we made algorithmic changes until the last moment. This is far from ideal and we need to improve. That also affects organising, time schedules asf., which is not always easy when a company grows. Apart from that, I tend to be precise with preset terms and regulative aspects. We will be more stringent in the future, but that'll start first with our regular beta team first, and then expand ideas and rules outwards.

Fair enough.

I'll just continue using TXT files as additional info, I know how to name the presets now, and I'll let you know at which RMS levels we're at in terms of noise, if this is a send or insert effect, etc.

The more info, the better.

Compyfox, will you presets run on an OSX machine/ They show up as unix executable files on my mac, and I'm not sure that's going to work


Thanks for going to the trouble--I'm exploring the delay mode now and it's really cool.

Either you use the RL presets in the official Satin v1.0 release (in the Delay subfolder), but you need to turn back the Output knob to 0dB (then mess with the mix knob and either head at 0 or 100%). Or... you can still use my presets.

They're in the .h2p format - the native format of SATIN.

[sws2h]

I have a quick question. I'm transferring some 24 track masters that are Dolby A. Will Satin decode them? If so, is Satin calibrate just like the hardware units, with Dolby tone from the tape?

Yes!

If so, is there an AAX Beta if I were to buy?

No, not yet, and there's also no estimate as to when this will come to Mac and PC.

Very cool.

Can you bypass the tape machine and just used the encode/decode section?

Might have to decode this project in Garageband or something if that's the case.

[sascha]

Can you bypass the tape machine and just used the encode/decode section?

The button for it is labeled 'Bypass Tape'.

[legreg6]

If so, is there an AAX Beta if I were to buy?

No, not yet, and there's also no estimate as to when this will come to Mac and PC.[/quote]

That is NOT good. And not very encouraging. As an owner of Diva for quite some time and now Satin I was definitely counting on/hoping for AAX compatibility. As much as I love U-he stuff, it totally stops me from buying more. Was considering Uhbik effects...have been checking on Bazille updates... but it has to work in Pro Tools.
That's a shame.
I'm sorry about this quite negative post in an otherwise pretty positive thread but this is very frustrating. Maybe "support for Pro Tools tba" should be removed from the website since it does not seem to be in the pipeline.
Again, love your stuff and I am very impressed so far with Satin, but common, give me the option to use it in Pro Tools.

[sascha]

That's a shame.

Search around for the 'iLokalypse' and you have an idea of a drama that still persists (at least for us devs)...

[Krakatau]

Can you bypass the tape machine and just used the encode/decode section?

The button for it is labeled 'Bypass Tape'.

i assume it could be achieved by the "bypass plugin" button too on my AU instance for instance, right ?



Without kidding i just thank you all at U-he, because i just recover sensations that i didn't realise i've completely forgotten since the time i sold my 8 track in the middle of the neinties

It wasn't obvious at the early manipulation because they aren't such drastic differences at a first listening, ...but this is an absolutely stunning effect !!!!

i'm presently completely sold only by digging all the warming nuances and possibilities you can get
(compander + tape + circuit of the studio mode)




Thank you soooooooo much for this true enchantment !!!!!

[Seaside Music]

Running Satin in Samplitude 11.2.1 PRO.

Trying to name a preset but using spacebar to space between words results in no spaces inserted but playback start/stop engaging.

[djsubject]

Can you bypass the tape machine and just used the encode/decode section?

The button for it is labeled 'Bypass Tape'.

i assume it could be achieved by the "bypass plugin" button too on my AU instance for instance, right ?

nope that will bypass everything!

bypass tape is different to the global bypass button on the top left!

sorry if there was a part of that joke that i missed!

[EvilDragon]

Running Satin in Samplitude 11.2.1 PRO.

Trying to name a preset but using spacebar to space between words results in no spaces inserted but playback start/stop engaging.

That's up to your DAW. Not sure if Samplitude has an option to temporarily send all keyboard presses to the plugin. Reaper does.

[Krakatau]

sorry if there was a part of that joke that i missed!

You don't have to be sorry because i noticed this button a few minute after i posted



Unlike your nickname might suggest, this was, i need to admit, a truly objective remark !

[V0RT3X]

A work in progress track of mine that uses Satin on the Drum bus and another instance as a delay for the synth guitar part from Z3TA+2 (Even though I imagine Zebra2 could do it much better).

https://soundcloud.com/1v0rt3x/t-n-w-wip

[Urs]

That is NOT good. And not very encouraging. As an owner of Diva for quite some time and now Satin I was definitely counting on/hoping for AAX compatibility.

If it's encouraging then I can post a screenshot of Podolski - which we use as a prototyping project - running in PT11, without a hitch.

Our AAX code is nearly finished on Mac, it now needs to be integrated with our workflow (we don't compile our stuff by hand anymore, we have a server setup) and ported to Windows. This would have been finished months ago, hadn't PACE pulled a stunt that made us halt development at that time. Hence we postponed AAX, we put Satin on higher priority and we hope to go back to AAX shortly. I still feel reluctant installing any PACE software on our build servers, even if it's "just" for signing purpose. The whole thing is surplus in my eyes as it's basically offering the same thing that MacOS X and Windows offer for free, and from an IMHO more trustworthy source.

I emphasize my concerns in every single email to our partners at Avid, and I hope many others does too.

Anyhow, we haven't tried that PACE signing stuff yet as we were busy elsewhere. If it works then we'll be able to say "yes, it's coming!". But as long as we can't say for sure if and how it works (it may even interfere with our own signing process, who knows), we'll just say "we can't give an estimate yet". That's the only fair answer we have at this time.

- Urs

[sascha]

Is the feedback knob under the delay section supposed to sound like a really bad reverb when turned up?

Insert any synth with default patch (example: Harmor, Twin2, etc..) and play/record a few notes. Insert Satin, go to delay section and set up a delay (or use a delay preset). Turn up the feedback knob. All that I am hearing is a very bad sort of reverb effect. Is this the intended effect? Don't see myself every using this. Maybe it's because I am trying this on a synth sound? (?)

This 'glitchy' sound you're experiencing occurs with buffer sizes not being multiples of 16 (e.g. arbitrary sizes coming in). Meanwhile, I can tell that we've been able to reproduce it here by forcing our framework to divide the incoming buffer stream into random sub chunks, and the glitch on the feedback path was clearly audible. We spotted a design flaw in the underlying algorithm where writing to and reading from the delay was thrown out-of-sync under those circumstances.

I fixed it today. We'll have to test some more before I can be 100% sure, but things already look good here.

[K-Slash]

Hey guys,

Sorry to bother but, when can we expect the notes values to be displayed in delay mode ?

I'm just waiting for this to be sorted out before jumping in the Satin wagon :p !