Tokyo Dawn Labs

FabienTDR · Post by **FabienTDR** » Tue Jan 08, 2013 2:14 am

Discuss the beta 2 here please.

mwaudioprod · Post by **mwaudioprod** » Tue Jan 08, 2013 2:41 am

As the first the high buffer of 1024 spls and the high CPU value has struck me. I find this is still very improvement-worthy.

FabienTDR · Post by **FabienTDR** » Tue Jan 08, 2013 3:05 am

mwaudioprod wrote:As the first the high buffer of 1024 spls and the high CPU value has struck me. I find this is still very improvement-worthy.

Not sure what you mean with the "high buffer", latency maybe?

There's a price to play for high quality processing.

The cpu performance will improve, though. The processing delay will not. This tool is optimized for mastering. Performance only has a very low priority in this concept, it's all about the sound.

Audio Freak · Post by **Audio Freak** » Tue Jan 08, 2013 3:24 am

Hello, I am posting here as directed for beta 2 posts...

I was saying that the TDR Compressor II beta 2.0.0 is showing up in Reaper but not showing up in Presonus Studio One 2. Fabien said that it worked for him in "Studio One" ...
Could it be that I am using Studio One 2 ??

I am using Windows XP service Pack 2. (this is a very stable system for me!)

The dll file is in the same Steinberg - VST folder that has the original Feedback Compressor in it.

And as stated before, both Feedback Compressors are showing up and functioning in Reaper...

Any Ideas?

FabienTDR · Post by **FabienTDR** » Tue Jan 08, 2013 4:02 am

I really mean studio one 2. I downloaded and installed the demo about an hour ago. Just tested again, plugins show up. Maybe it has been blacklisted before because of a crash? You tried to rescan your vst folder?

Audio Freak · Post by **Audio Freak** » Tue Jan 08, 2013 5:01 am

Thank You ! It must have been blacklisted. I cleared my blacklist and it now shows up!

Another question... Is the new TDR Compressor II ok to use on tracking as well as on the master bus for mastering?

Is there any reason to keep using the former TDR Compressor? Thank You

FabienTDR · Post by **FabienTDR** » Tue Jan 08, 2013 5:39 am

The compressor is made for mastering and the stereo bus.

However, it's fast enough all kinds of compression applications. CPU wise it's an overkill on mono material, but it's fine if you can "afford" it.

Version 1 works slightly differently and has additional features such as the color section. Also, it's very stable and well optimized. If you have a fast cpu and haven't used the version 1 in previous projects, just delete it. Just keep in mind we're still in the beta phase!

paterpeter · Post by **paterpeter** » Tue Jan 08, 2013 10:21 am

I just tried the compressor real quick. It looks very promising. The combined peak/RMS detection with crest control is really nice. This is definitively a keeper, together with V1, of course. Good work man!

A SC peak/RMS meter wouldn't hurt, though. I know, I know, use your ears. But still I like visual feedback.

DuX · Post by **DuX** » Tue Jan 08, 2013 12:41 pm

Working normally here. It uses a little less CPU now. When I say "a little less", I mean "a little less". Like 0.1% less.

I find it very comfortable to work with. Very versatile compressor. I was also playing with the limiter mode. Very nice. Yeah, since it is so clean and transparent, it is obviously made for compressing busses, or to compress the whole mix. Yeah, the buffer of 184 samples is on the tad "too big" for tracking, but nothing is impossible when you're deep into the mix and finished with tracking...

However, I would like to use something more "colourful" in the mix, especially for bass, but one can always combine plugins, too... When you think about it, we actually lack clean compressors like this. There are tons of colourful ones with saturation and even noise, and heavy aliasing ones that sound awful...

This compressor feels like hardware to me, regarding its compression characteristics, but hardware without all the noise, saturation, and AD/DA artefacts.

Noice

Anyway, no stability problems here so far. I had 4 or 5 instances running at once. I didn't throw a look at the memory consumption, to see if there are any memory leaks, damn... sorry.

Great work, Fabien. Thank you!

tico-tico · Post by **tico-tico** » Tue Jan 08, 2013 2:30 pm

Hi, Fabien.
Sometimes plugin's GUI is not properly updated when i'm changing presets using the drop-down menu.

It's not 100% reproducible and usually happens in heavy projects. Sometimes knobs have wrong position, sometimes only the graph affected.

Win 7 x32, Reaper 4.31

Thanks.

DuX · Post by **DuX** » Tue Jan 08, 2013 2:43 pm

That same GUI glitch happens in FB Compressor I, too. It doesn't affect its functionality, and the GUI corrects itself as soon as you move some control, but I guess it does qualify as a bug. It happens when I change presets in Reaper, but a drop-down menu or a window has to partially cover its screen , exactly like in your example.

I kinda got used to it and it doesn't bother me. Changing GUI priority and GUI refresh frequency is very tricky and could impair its performance. It's a very complicated "thingie". As far as I know, the trickiest thing about coding a VST plugin is to correctly code the GUI. That's why I often say - "just give me a GUIless plugin".

I don't care about the GUI when there are just a few parameters. Even a dozen can do. But hey, people like colours, "buttons", "faders"... me too, don't get me wrong

but... We forget we have to listen to how it sounds.

FabienTDR · Post by **FabienTDR** » Tue Jan 08, 2013 4:45 pm

tico-tico wrote:Sometimes plugin's GUI is not properly updated when i'm changing presets using the drop-down menu.

It's not 100% reproducible and usually happens in heavy projects. Sometimes knobs have wrong position, sometimes only the graph affected.

Win 7 x32, Reaper 4.31

Oh thanks for reporting the issue. It's the first time I saw it, some users reported the same problem a while ago. I will try to reproduce the problem here.

It looks like a UI refresh issue to me, but a strange one. Maybe a VSTGUI bug, is this standard behaviour for other plug-ins as well? (I can't see such things, probably because of my super fat gfx card). It looks really ugly, time to fix this problem somehow!

btw, how did you create the nice animated gif?

FabienTDR · Post by **FabienTDR** » Tue Jan 08, 2013 5:16 pm

DuX wrote:Working normally here. It uses a little less CPU now. When I say "a little less", I mean "a little less". Like 0.1% less. I find it very comfortable to work with. Very versatile compressor. I was also playing with the limiter mode. Very nice. Yeah, since it is so clean and transparent, it is obviously made for compressing busses, or to compress the whole mix. Yeah, the buffer of 184 samples is on the tad "too big" for tracking, but nothing is impossible when you're deep into the mix and finished with tracking... However, I would like to use something more "colourful" in the mix, especially for bass, but one can always combine plugins, too...

..ehmm..

DuX wrote: When you think about it, we actually lack clean compressors like this. There are tons of colourful ones with saturation and even noise, and heavy aliasing ones that sound awful...

ah! that's what I was about to say

I already started work on a dedicated colour processor few months ago.

DuX wrote: This compressor feels like hardware to me, regarding its compression characteristics, but hardware without all the noise, saturation, and AD/DA artefacts. Noice

Exactly! That was the goal.

In some aspects such as fast dynamic range reduction and high frequency handling, even the cheapest analogue compressors sound far superior than most digital implementations. This relates to super strong aliasing in the "gain cell" and most of all massive aliasing in the side-chain which a both difficult to control.

However, even a high-end mastering DA/Compressor/AD loop introduces severe signal degradation (I use a HEDD for the analogue loop), not to mention recall struggle and other things. The noise level alone is easily pushed up to -90dB and the bandwidth gets restricted.

So, neither way truly offers clean processing (and I'm someone enjoying the fact that nothing can be as warm, crisp, intensive and vibrant as a "clean" dynamics processing).

I try to fill this gap with my plug-ins. It's really time for high-end audio processors that make no compromises on audio, no matter the price. The "I don't care how big, how heavy or how expensive it is, just give me the best sound possible" approach isn't uncommon in the analogue market, but I can't see any true high-end plug-ins (except the excellent Algorithmix products and Crane Song maybe).

DuX wrote:Anyway, no stability problems here so far. I had 4 or 5 instances running at once. I didn't throw a look at the memory consumption, to see if there are any memory leaks, damn... sorry.

I hope there aren't any left! Zero!

tico-tico · Post by **tico-tico** » Tue Jan 08, 2013 5:19 pm

FabienTDR wrote:Maybe a VSTGUI bug, is this standard behaviour for other plug-ins as well?

I have this issue with FB Comp I & II only. At least I think so.

FabienTDR wrote:btw, how did you create the nice animated gif?

using this great tool from Cockos
http://www.cockos.com/licecap/

Thanks.

kvaca · Post by **kvaca** » Tue Jan 08, 2013 6:44 pm

FabienTDR wrote: I try to fill this gap with my plug-ins. It's really time for high-end audio processors that make no compromises on audio, no matter the price. The "I don't care how big, how heavy or how expensive it is, just give me the best sound possible" approach isn't uncommon in the analogue market, but I can't see any true high-end plug-ins (except the excellent Algorithmix products and Crane Song maybe).

well written!

I can imagine how many people are waiting for affordable compressor or limiter in Splitcomp quality

Tokyo Dawn Labs

KVR Audio

Tokyo Dawn Labs - Feedback Compressor II - beta 2