This isn't exactly a bug, per se...but something that would be nice to have fixed in a future update.

Vintage Compressor makes everything louder, processed or not. I need to attenuate the gain after the plug in to compensate. This may be the case on some other plugs too, but this is the one I have used the most and been annoyed by.

This isn't exactly a bug, per se...but something that would be nice to have fixed in a future update.

Vintage Compressor makes everything louder, processed or not. I need to attenuate the gain after the plug in to compensate. This may be the case on some other plugs too, but this is the one I have used the most and been annoyed by.

Thanks.

Hello,

No, this is not a bug but the way the algorithm has been coded, actually, the plugin is NOT transparent but adds his own color, that's how some old vintage hardware compressors are, we do not add gain to the plug-in output, the algorithm react like that.

Of course you can say, change the internal output gain to be set to 0 dB, yes we can but it's not the idea, the idea is to have this plugin to react like his big brother, the hardware.

yesterday I bougth DC Brightness after trying the demo. But when i want to authorize the Plugin I get an error-message! "Cannot launch the software activator- re-install ....." I tried many times and many ways..but the plugin only works in demo-mode! I also tried to activate the plugin directly with the software activator (from the original folder- there i got the message that the authorization was successful....but it also dont work, i reinstalled all components of the software and so on...but nothing works...)

Greetings

Uli

ps i also sent an email yeserday to the support- no answer till now. ;(

yesterday I bougth DC Brightness after trying the demo. But when i want to authorize the Plugin I get an error-message! "Cannot launch the software activator- re-install ....." I tried many times and many ways..but the plugin only works in demo-mode! I also tried to activate the plugin directly with the software activator (from the original folder- there i got the message that the authorization was successful....but it also dont work, i reinstalled all components of the software and so on...but nothing works...)

Greetings

Uli

ps i also sent an email yeserday to the support- no answer till now. ;(

No, this is not a bug but the way the algorithm has been coded, actually, the plugin is NOT transparent but adds his own color, that's how some old vintage hardware compressors are, we do not add gain to the plug-in output, the algorithm react like that.

Of course you can say, change the internal output gain to be set to 0 dB, yes we can but it's not the idea, the idea is to have this plugin to react like his big brother, the hardware.

If too much gain, just reduce the global gain using the OUT control.

Hope this helps ?.

Thank You.--JonathanDC Tech Support

Thanks for the response. I understand that the volume difference is at least partially related to additional harmonics added by the compressor. It would be nice to have the output volume go negative at least a couple of dB to compensate. I find it valuable to do a volume-matched A/B with the processed / unprocessed signal.

Thanks for the response. I understand that the volume difference is at least partially related to additional harmonics added by the compressor. It would be nice to have the output volume go negative at least a couple of dB to compensate. I find it valuable to do a volume-matched A/B with the processed / unprocessed signal.

first thanks for the two new plugins. Sounds good.Here, as AU plugins, all Factory presets in v. 1.1.0 are lost. (All plugins) Only User Presets are shown in the plugins. But all Factory Presets are stored under HD/Library/ Application Support/Don't Crack. I think that's a bug, or not? (i7 iMac, OSX 10.6.7, Logic 9.1.5)

first thanks for the two new plugins. Sounds good.Here, as AU plugins, all Factory presets in v. 1.1.0 are lost. (All plugins) Only User Presets are shown. I think that's a bug, or not? (i7 iMac, OSX 10.6.7, Logic 9.1.5)

CheersMorpeus

Hi,I was just about to post something similar (so I will anyways )..But I think I have found the cause.. there is an inconsistency (at least on Mac) in the filepaths for the presets between the VST installer and the installers for AU and RTAS...(using just DC-Brightness as an example) AU and RTAS installers create the following filepath../Library/Application Support/Dont Crack/DC-Brightness (then the two subfolders for Factory and User Presets)But the Vst Installer creates the following../Library/Application Support/Dont Crack/Plug-In Settings/DC-Brightness/(etc)

If I remember correctly, the latter was the filepath used exclusively for all plugin formats in v1.0.1.

So now, if running all three installers, we end up with all the individual plugin presets folder twice.. once directly inside Application Support/Dont Crack, and then again inside a further subfolder, "Plug-In Settings".

I have only tried saving VST presets , so far, and they do indeed still get saved inside the "Plug-Ins Settings" subfolder (and I can load them, and Factory presets too.. no problem).. but the current conflict could be the reason why certain presets are not showing in AU and RTAS versions?

Hi,I was just about to post something similar (so I will anyways )..But I think I have found the cause.. there is an inconsistency (at least on Mac) in the filepaths for the presets between the VST installer and the installers for AU and RTAS...(using just DC-Brightness as an example) AU and RTAS installers create the following filepath../Library/Application Support/Dont Crack/DC-Brightness (then the two subfolders for Factory and User Presets)But the Vst Installer creates the following../Library/Application Support/Dont Crack/Plug-In Settings/DC-Brightness/(etc)

If I remember correctly, the latter was the filepath used exclusively for all plugin formats in v1.0.1.

So now, if running all three installers, we end up with all the individual plugin presets folder twice.. once directly inside Application Support/Dont Crack, and then again inside a further subfolder, "Plug-In Settings".

I have only tried saving VST presets , so far, and they do indeed still get saved inside the "Plug-Ins Settings" subfolder (and I can load them, and Factory presets too.. no problem).. but the current conflict could be the reason why certain presets are not showing in AU and RTAS versions?

So, would a DC support person please let me know asap if this is the case as I am downloading the new installer for v1.1.0 but I don't want to install if a new updater will be issued soon that will correct this problem.Thank you!