Tritik tkDelay public beta release. UNLIMITED Demo - (winXP support added)

[iDesignSound]

Don't get me wrong, it's still usable as is, but it's clearly not the norm. Or do other plugins do this? I've not seen any that do!

[spirit]

I'd looked at Fabfilter Timeless (CPU too high and far too complex with it) and a few others but overall preferred this. It has a clarity that works for me and is processor friendly.

Timeless-II is certainly more complex and I personally strongly dislike the mostly useless presets, but high CPU?! Absolutely not.

[RockinMillie]

I'd looked at Fabfilter Timeless (CPU too high and far too complex with it) and a few others but overall preferred this. It has a clarity that works for me and is processor friendly.

Timeless-II is certainly more complex and I personally strongly dislike the mostly useless presets, but high CPU?! Absolutely not.

spirit, you are absolutely correct in some respects.

I have re-checked my comparison and the Timeless II CPU usage was only slightly higher than that of tkDelay, apart from when the GUI is opened.
However, on opening the timeless GUI I noticed a momentary jump in CPU utilisation similar to this issue but not as extreme.:
http://www.kvraudio.com/forum/viewtopic ... 7&t=419671
Having read this post I believe this may possibly be an issue with Studio One and how it handles Fabfilter Open GL graphics.

I still found Timeless quite overwhelming in its complexity. I was looking for something that sounds good, is flexible and is simple to use.
I also bought HoRNet Deelay as well at the same time, as it fulfilled my criteria and also had very low CPU overhead.

[Tritik]

sorry - deleted, That was meant to be a PM.. !
arf. ok, too late. now that this thread came up on the first page I can actually let my message here.
so it's here below.
But if you want to talk about tkdelay don't do it here, use the other more recent thread :
http://www.kvraudio.com/forum/viewtopic ... 6&t=426762

sorry about that mess

===============================

I bought it and think it's pretty good, looking forward to the things that you've said will be added for v1.0

Hi

So first, thank for your purchase! With such a low price and an unrestricted demo, it's really important for me that users get a license! your money will be used wisely!
I hope that the v1 meets your expectations.

One thing I really don't like though is where quite a few parameters have knobs with orange indicators showing positive and negative positions (like a pan knob should have) when infact the parameter values are all positive (0 to 100%). This includes the feedback knobs and BP filter Freq and DW knobs.

Is this something you could change, or maybe give us the option to change? It just seems wrong to me, my brain keeps telling me that zero starts at the 50% position and everything lower than that is somehow a negative value.

I also find it odd that 100% wet and 100% left/right volumes have the orange indicator set at zero.

Does anyone else find this arrangement odd? Can we have the option to correct this behaviour?

Yes, I understand what you mean. 2 other users asked me about that.
But If you think about it :
If the orange color was as you would like, than it would just 'double' the information given by the mark on the knob (that is just showing it's position).

But more importantly :
the orange colour catches the eyes, and so it should convey a pertinent information. And I consider the needed 'information' to increase when you go further from the default value.

here was a mail of one user :

"The Dry/Wet knob orange color is wrong and should be no color at 0% and full orange at 100%."

and that was my answer about it :

Concerning the color, it is like that on purpose in fact :
We consider that :
- the 'values' that should be colored are the ones that should catch your eyes.
- when something sounds wrong it should be easy to find, and it's faster to find something which is colored.

that's why also the input gains get colored when they go down :
Imagine there are -inf db, you won't have any sound. When you look to see what's wrong your eyes will go at it pretty fast because they will be colored.

Same for the dry/wet :
If you got tkDelay loaded, you expect to have some delay. If you unintentionally set the wet to 0% (or loaded a preset with wet at 0%), then you'll wonder why there's no delay sound. Fortunatelly you'll find out why faster because the dry/wet will be colored entirely.

Does that make sense to you?
also all the colors are drawn from the factory default value of the knob, which is marked by a small orange point. Double click on a knob, it will jump to that value.

Are you ok with that?
I guess you gonna say 'yes, but my brain still thinks something is wrong'

my brain keeps telling me that zero starts at the 50% position and everything lower than that is somehow a negative value

I understand, but I really think the current behaviour makes sense.
Having the input gains to their maximum is just a normal thing, so there is no reason to make them appearing really strongly when they are in that position.
tell to your brain that if there's nothing to see there's nothing important. If there's colour, then it is.
I agree that some default values (such as the delay times) are pretty subjective though.
but if you got a really short delay time or a really long one, then it's something that takes an important part in the sound result and that should be shown. a middle delay time value is just a common thing.

hope you can live with that (it seems so regarding your last post on the new release thread!)

best,
Charles

[iDesignSound]

I agree that some default values (such as the delay times) are pretty subjective though.
but if you got a really short delay time or a really long one, then it's something that takes an important part in the sound result and that should be shown. a middle delay time value is just a common thing.

hope you can live with that (it seems so regarding your last post on the new release thread!)

I really like the plugin and to some extent have already got used to working with it that way, but I do still think this behaviour is strange. I guess our brains think in different ways

Using your example, if I open a delay plugin and hear that there is no delay then I would quickly confirm that by seeing that none of the dry/wet knob is coloured, so it is completely dry.

Following on from this, as you've also had a couple of emails, it's obviously not just me that thinks this way, so maybe there could be an option available for the user to choose between the 'classic' and tk approach.

or maybe an idea could be for it possible for us to save our own default patch. But as well as saving the save the knob positions it would zero or centre (as approriate) the coloured marker at the chosen positions. I'm not sure if this could be easily doable but then this way we can all have it the way we like!

So, for example, if I want the default knob position for delay time and the starting point of the coloured marker to be centred at 1/8 and not 1/4t I can save that in a default patch.

I understand if this is not possible. I still really like your plugin and will use it as my go-to delay. Infact, give it a few months and I'll probably be cursing other plugins for not using knob indicators in the same way! LOL

[ignaceland]

Hi, I'm yet to try this Delay, but looks really interesting.

One simple thing I miss from most delays when using them as inserts, and usually use use Kjaerhus one for that, is the ability to Pan the delayed signals within the GUI. So you can pan delays to the other speaker or do some weird combinations in one interface.
For me, that combined with the mix knob is a very powerful tool when looking to place an element in the mix.