Yep, that`s the point, nice attitude ...Izak Synthiemental wrote:Too bad. But thanks for trying!
Dead Duck Software - opinions?
- KVRian
- 933 posts since 25 Dec, 2007 from Hamburg,Germany
Intel i7-4790K | Gigabyte Z97X-UD3H | 32GB Crucial Ballistix Sport | RME Babyface Pro | UAD PCIe Octo, Quad | Asus GT 730 | Toshiba DT01ACA200 2TB | LG GH24NSB0 | W10 Pro 64bit | S1 latest
-
- KVRist
- 137 posts since 22 May, 2017
Is it an oversight that the DD Channel has no toggle to turn the limiter stage off? When you're pushing frequencies on the EQ, it hits the limiter and distorts. There doesn't seem to be an obvious way to turn it off and on. Any help would be great
Last edited by BRBWaffles on Mon Jun 26, 2017 1:35 am, edited 1 time in total.
-
- KVRist
- 486 posts since 22 Aug, 2013
+1BRBWaffles wrote:Is it an oversight that the DD Channel has no toggle to turn the limiter stage off? When you're pushing frequencies on the EQ, it hits the limiter and distorts. There doesn't seem to be an obvious way to turn it off and on.
So we can add another inserts after it, but before the limiter
-
- KVRer
- 23 posts since 27 Apr, 2015
+1 for an on/off switch for the limiter on DD Channel. The limiter seems to be the only unit adding latency to the channel plugin (checked the separate plugins).
Coincidentally doing an amateur live audio project needing (latency free) freeware. This plugin is (almost) a gift from heaven!)
Greetings, Psync
Coincidentally doing an amateur live audio project needing (latency free) freeware. This plugin is (almost) a gift from heaven!)
Greetings, Psync
-
- KVRist
- 381 posts since 12 Jul, 2006
No, it was a deliberate choice. The limiter introduces latency which it reports to the host when the plugin is loaded. Making the limiter bypassable messes with this and I decided at the time that the simplest solution was to just not have a bypass switch. I wasn't particularly comfortable with this at the time as it makes the plugin less versatile and goes against the overall design where every module is optional, but it was necessary to keep the project moving.BRBWaffles wrote:Is it an oversight that the DD Channel has no toggle to turn the limiter stage off? When you're pushing frequencies on the EQ, it hits the limiter and distorts. There doesn't seem to be an obvious way to turn it off and on. Any help would be great
So I guess it's probably time to revisit that decision. Stay tuned
-
- KVRist
- 381 posts since 12 Jul, 2006
What state is the plugin in when you hear this click? If the gain is not set to zero and there is audio passing through then it will click when activated/deactivated.kinwie wrote:@swatwork
Just a report, hopefully a fix for it.
The TiltEQ produce a tick noise when opening a session or when activated/deactivated it.
-
- KVRist
- 486 posts since 22 Aug, 2013
Do you mean if the gain not set to zero and there is no audio passing?swatwork wrote: What state is the plugin in when you hear this click? If the gain is not set to zero and there is audio passing through then it will click when activated/deactivated.
That's the state of the plugin when I hear the click noise, quite loud.
Only on one channel, sometime left, sometime right, and the fader meter is red clipped.
Continuing working and reopening a session that use TiltEQ will have that click noise at very first beginning.
I check other plugins, they are no problem.
-
- KVRist
- 381 posts since 12 Jul, 2006
OK, I can reproduce the click on loading a session in Mixcraft so something's not right. I'll look into it.kinwie wrote:Continuing working and reopening a session that use TiltEQ will have that click noise at very first beginning.
I check other plugins, they are no problem.
Thanks for reporting.
Steve
-
- KVRist
- 486 posts since 22 Aug, 2013
Ah, yes, I always scared that any problems is on the fxpansion's adapter.swatwork wrote: OK, I can reproduce the click on loading a session in Mixcraft so something's not right. I'll look into it.
Thanks for reporting.
Steve
Thanks to look into it!
- KVRian
- 1207 posts since 28 Jun, 2005
Not really a bug but,
In FLStudio (11) on W7 the monodelay (32 bit) gives an error when it is inserted in an fx track without activating it, and then pressing "bypass" on the plug in.
When it's activated the bypass on/off works fine, without an error message.
PS, I'm using version 1.3.2. with mousewheel and space-bar support
In FLStudio (11) on W7 the monodelay (32 bit) gives an error when it is inserted in an fx track without activating it, and then pressing "bypass" on the plug in.
When it's activated the bypass on/off works fine, without an error message.
PS, I'm using version 1.3.2. with mousewheel and space-bar support
-
- KVRist
- 381 posts since 12 Jul, 2006
OK, this should be fixed in the next release.kinwie wrote:Continuing working and reopening a session that use TiltEQ will have that click noise at very first beginning.
Definitely a bug. Reproduced and fixed for the next update.Yeager wrote:Not really a bug but,
In FLStudio (11) on W7 the monodelay (32 bit) gives an error when it is inserted in an fx track without activating it, and then pressing "bypass" on the plug in.
When it's activated the bypass on/off works fine, without an error message.
PS, I'm using version 1.3.2. with mousewheel and space-bar support
Thanks for reporting.
-
- KVRist
- 486 posts since 22 Aug, 2013
swatwork wrote:OK, this should be fixed in the next release.kinwie wrote:Continuing working and reopening a session that use TiltEQ will have that click noise at very first beginning.
Definitely a bug. Reproduced and fixed for the next update.Yeager wrote:Not really a bug but,
In FLStudio (11) on W7 the monodelay (32 bit) gives an error when it is inserted in an fx track without activating it, and then pressing "bypass" on the plug in.
When it's activated the bypass on/off works fine, without an error message.
PS, I'm using version 1.3.2. with mousewheel and space-bar support
Thanks for reporting.