When I use Wave Hammer, the used preset doesn't appear again. Same issue as version 16.
The same happens with others directx plugins.
I tried using LoudMax 1.43 VST3 and I can't.
I've tried LoudMax and it worked for me. Did you try to reset all settings and cached data?
Yes, i did. But not working.
All VST2, 32bit plugins, presets are Untitled.
In version 17 plugins are loaded after Sound Forge is opened. I have many plugins installed and it takes almost 50 seconds for Sound Forge to be ready.
Magix developers have removed the old Show Peak Meter.
Magix developers should fix the issues and not make Sound Forge worse.
Magix developers have removed the old Show Peak Meter.
That is the first thing I noticed and It sucks big time! There is also no option or preset to show any full scale peak meter without the VU.,, which nobody uses much these days.
The 32 bit VST-2 display issue still exists.. which I expected. I am sure there are other issues I have not encountered yet.
All eFX VST2 x64 plugins has issues. When i change preset, nothing happens. Other VST2 x64 plugins don't have this problem.
Your post to this thread has been hidden. The OP is commenting on Sound Forge 17, you have Sound forge 16.
Please create a new thread with your question, giving rather more details about your computer and your audio interface.
Thank you.
Jeff
Forum Moderator
Sound Forge has many types of native plugins: DirectX, VST2 x32, VST2 x64. That's why it's hard to fix problems with plugins.
I tried using LoudMax 1.43 VST3 and I can't.
I have LoudMax v1.4.2 and the 64 bit VST 2 and 3 work on my PC (Win 10, SFP-17).
On my computer (Win 11), LoudMax v1.43 VST3 does not work in Sound Forge 17. But it works in Audition and Studio One.
It works for me (manually) but imported presets or newly created ones do not.
I reinstalled Sound Forge and LoudMax no longer crashes. But the first time I drag the button it always goes back to zero and the volume never increases.
RVox has a similar problem as LoudMax. When I pull the compressor slider, the slider goes back to where it was and the preset name changes. This problem can happen with other plugins as well.
Today magix released version 17.0.1 build 85, but the same problems remain.
I don't know why Sound Forge has duplicate plugins. This makes the installer larger (over 900MB) making it harder to fix problems. Audition under 500MB and Studio One under 300MB.
@john_barr The plugins are not duplicated. These are VST2 and VST3 versions.
The plugins are not duplicated.
If you look carefully, the plugins have the same features and the same presets. You must review before commenting.
@john_barr Yes I reviewed it and VST3 offers new features compared to VST2. Depends on the plugin developers if they use them:
Improved Performance with the Silence Flag
Processing can optionally be applied to plug-ins only when audio signals are present on their respective inputs, so VST 3 plug-ins can apply their processing economically and only when it is needed.
Multiple Dynamic I/Os
VST 3 plug-ins are no longer limited to a fixed number of inputs and outputs, and their I/O configuration can dynamically adapt to the channel configuration. Side-chains are also very easily realizable. This includes the possibility to deactivate unused busses after loading and even reactivate those when needed. This cleans up the mixer and further helps to reduce CPU load.
Sample-accurate automation
VST 3 also features vastly improved parameter automation with sample accuracy and support for ramped automation data, allowing completely accurate and rapid parameter automation changes.
Logical Parameter Organization
The plug-in parameters are displayed in a tree structure. Parameters are grouped into sections which represent the structure of the plug-in. Plug-ins can communicate their internal structure for the purpose of overview, but also for some associated functionality (eg. program-lists).
Resizeable UI editor
VST 3 defines a way to allow resizing of the plug-in editor by a user.
Mouse Over Support
The host could ask the plug-in which parameter is under the mouse.
Context Menu Support
VST 3 defines a way to allow the host to add its own entries in the plug-in context menu of a specific parameter.
Channel Context Information
A VST 3 plug-in could access some channel information where it is instantiated: channel name, color,...
Note Expression
VST 3 defines with Note Expression a new way of event controller editing. The plug-in is able to break free from the limitations of MIDI controller events by providing access to new VST 3 controller events that circumvent the laws of MIDI and provide articulation information for each individual note (event) in a polyphonic arrangement according to its noteId.
3D Support
VST 3 supports new speaker configurations like Atmos, Auro 3D or 22.2.
Factory Concept
VST 3 plug-in library could export multiple plug-ins and in this way replaces the shell concept of VST 2 (kPlugCategShell).
Support Remote control Representation
VST 3 plug-in can deliver a specific parameter mapping for remote controls like Nuage.
While designing VST 3, we performed a careful analysis of the existing functionality of VST and rewrote the interfaces from scratch. In doing so, we focused a lot on providing clear interfaces and their documentation in order to avoid usage errors from the deepest possible layer.Some more features implemented specifically for developers include:
More stable technical host/plug-in environment
Advanced technical definition of the standard
Modular approach
Separation of UI and processing
Advanced Preset System
Multiple plug-ins per Library
Test Host included
Automated Testing Environment
Validator (small command line Test Host) and plug-in examples code included.
In my humble opinion, Magix should remove the VST2 plugins (already obsolete) and use only VST3. This would make Sound Forge cleaner and fixing problems with plugins would be less difficult.