Upgrade to V4.0 and VST Effects
Upgrade to V4.0 and VST Effects
Wanted to post this, in case someone runs into the same issue after the upgrade.
Transition to V4.0 is seamless, with the exception of VST effects. The mixer effect settings are not automatically transferred over from V3.0.
4.0 manual is a bit misleading in that in parts it continues to refer to the VST folder path settings from 3.0 - which are no longer there. However, VST effects can still be added directly from the mixer in 4.0 by choosing the individual effect .dll file (usually under \Program Files\VSTPlugIns\).
The key point is that only 64bit effects are now supported (under V3.0 only 32bit were recognized). So I had to install the 64 bit versions (only had 32bit ones originally). You can go back to 3.0 (to write down exact effect settings) by changing where the ProppFrexx shortcut points to (3.0 vs 4.0 in the path).
The 4.0 way of handling VST effects does significantly reduce the amount of time needed to start up ProppFrexx.
Transition to V4.0 is seamless, with the exception of VST effects. The mixer effect settings are not automatically transferred over from V3.0.
4.0 manual is a bit misleading in that in parts it continues to refer to the VST folder path settings from 3.0 - which are no longer there. However, VST effects can still be added directly from the mixer in 4.0 by choosing the individual effect .dll file (usually under \Program Files\VSTPlugIns\).
The key point is that only 64bit effects are now supported (under V3.0 only 32bit were recognized). So I had to install the 64 bit versions (only had 32bit ones originally). You can go back to 3.0 (to write down exact effect settings) by changing where the ProppFrexx shortcut points to (3.0 vs 4.0 in the path).
The 4.0 way of handling VST effects does significantly reduce the amount of time needed to start up ProppFrexx.
Re: Upgrade to V4.0 and VST Effects
Yes, I pointed this fact out in the 'News and Announcement' section.
VSTs could not be transferred 1:1, as in the 64-bit Version ONLY 64-bit VST plugins might be used!
But as v3.0 was still 32-bit, These could of course NOT be transferred automatically.
See here: viewtopic.php?f=4&t=1347
In case someone really needs a 32-bit VST plugin, he can simply use the 32-bit Version of ProppFrexx ONAIR!
A reminder note:
A 64-bit application can only load 64-bit libraries (dll’s), as such only 64-bit VST versions (compatible with v2.4 hosts) are supported as DSPs (e.g. use the 64-bit VST version of Stereotool)!
- Winamp DSPs are NOT supported anymore (as they are all 32-bit)!
- The latest .Net Framework 4.5.2 needs to be installed (https://support.microsoft.com/kb/2901954)!
- Windows XP is not supported anymore (as the latest .Net Framework doesn’t support XP anymore).
VSTs could not be transferred 1:1, as in the 64-bit Version ONLY 64-bit VST plugins might be used!
But as v3.0 was still 32-bit, These could of course NOT be transferred automatically.
See here: viewtopic.php?f=4&t=1347
In case someone really needs a 32-bit VST plugin, he can simply use the 32-bit Version of ProppFrexx ONAIR!
A reminder note:
A 64-bit application can only load 64-bit libraries (dll’s), as such only 64-bit VST versions (compatible with v2.4 hosts) are supported as DSPs (e.g. use the 64-bit VST version of Stereotool)!
- Winamp DSPs are NOT supported anymore (as they are all 32-bit)!
- The latest .Net Framework 4.5.2 needs to be installed (https://support.microsoft.com/kb/2901954)!
- Windows XP is not supported anymore (as the latest .Net Framework doesn’t support XP anymore).
Bernd - radio42
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution