Diffuse v1.1.0

Hi!

Some of you have pointed out that there is already a plugin out there named ‘Diffuse’ by another developer and this is a problem if you would like to install both on the same machine.

To resolve the issue, the plugin is renamed to ‘DG_Diffuse’ starting with v1.1.
I will use the same naming scheme for any new plugins I release to avoid conflicts with existing plugins and new plugins released by other developers in the future. (To maintain compatibility, the Emergence plugins will not be renamed.)

You can download the latest version here:
https://daniel-gergely.itch.io/diffuse

If you have never installed the v1.0 version, you can stop reading now and simply start using the latest version. If you already use v1.0, please read the information below carefully.

Migrating presets

Since the plugin name is changed, most DAWs will not list presets that were saved with the old version.

This the plugin does not have a built-in preset manager, so the preset format will depend on your DAW. For this reason I cannot offer support for migrating presets.

However I would like to share my method for recovering presets saved in REAPER (I only tested this on windows):

• Open REAPER’s resource directory. The easiest way to do this is to run the action ‘Show REAPER resource path in explorer’
• Navigate to the ‘presets’ directory.
• Find the file named ‘vst3-Diffuse.ini’
• Create a copy of the file and rename the copy to ‘vst3-DG_Diffuse.ini’ (You might want to keep the original file, so the presets remain available in the original 1.0 version of the plugin)

Similar methods may be available for other DAWs (and for the AU version), but unfortunately these are all different and I cannot help you with more specific instructions.

Migrating projects

For projects using Diffuse 1.0, you have a couple of options:

Recommended: Do nothing, and keep using the original plugin in existing projects. Start using the renamed v1.1 in your new projects.
This works precisely because the plugin name is different: you can have both installed side by side at the same time.

If you really need to update existing projects, you can save the current settings as a preset and try loading that in the renamed plugin.
One way to do this in reaper is described above, but again, this is not guaranteed to work in all DAWs.

It is also a good idea to backup your work and render your tracks before you decide to delete the original v1.0 plugin.

I hope some of you will find this helpful and I apologize for any inconvenience this may have caused.
Thank you to all, who have paid for the plugin to support my work!

Daniel
https://danielgergely.net/