Nepheton update
Hi,
I'm on Mac OS X 10.4.11 Tiger with Cubase 4, and it looks like it's not possible anymore to put the Nepheton and Drumazon VST plug-ins into subfolders inside the VST folder. Yet it's a great thing to do to keep the Cubase plug-ins drop-down menus tidy and usable. Is it a lost feature?
I would strongly advocate for its return!
Here what happens:
I replaced old versions by new versions in the same subfolder. Old Projects using the plug-ins strangely don't find them, even if the plug-ins do appear in the drop-down menu at the right place. And when I reload them, I get this strange GUI, certainly not the one intended.
(edited)
I'm on Mac OS X 10.4.11 Tiger with Cubase 4, and it looks like it's not possible anymore to put the Nepheton and Drumazon VST plug-ins into subfolders inside the VST folder. Yet it's a great thing to do to keep the Cubase plug-ins drop-down menus tidy and usable. Is it a lost feature?
I would strongly advocate for its return!
Here what happens:
I replaced old versions by new versions in the same subfolder. Old Projects using the plug-ins strangely don't find them, even if the plug-ins do appear in the drop-down menu at the right place. And when I reload them, I get this strange GUI, certainly not the one intended.
(edited)
Last edited by Widowsky on Tue Jul 07, 2009 7:31 pm, edited 1 time in total.
Drumazon 1.6.2 - Nepheton 1.6.2 - Phoscyon 1.9.5 - Frontier 1.1.0 - Cubase Pro 10.0.60.396 - macOS High Sierra 10.13.6
I had a really hard time reinstalling the old versions. A lot of "you don't have the permission" even if I rebuilt the permissions. Then Cubase 4 blacklisted them; or put them in the "authorized" plug-ins list (the 'Vst2xPlugins.xml' file) with not enough info and the plug-ins didn't show up in the drop-down VST Instruments menu...
Finally I had to replace the Cubase Preferences folder with a backup from two days ago to make them work again as before. Pretty strange and unusual. It looks like the new versions installer is messing with something it shouldn't. Probably there's something to be looked at.
I don't think I did anything wrong. I followed the same standard procedure as always. I just wanted to put those plug-ins in a subfolder, which is pretty common.
Finally I had to replace the Cubase Preferences folder with a backup from two days ago to make them work again as before. Pretty strange and unusual. It looks like the new versions installer is messing with something it shouldn't. Probably there's something to be looked at.
I don't think I did anything wrong. I followed the same standard procedure as always. I just wanted to put those plug-ins in a subfolder, which is pretty common.
Drumazon 1.6.2 - Nepheton 1.6.2 - Phoscyon 1.9.5 - Frontier 1.1.0 - Cubase Pro 10.0.60.396 - macOS High Sierra 10.13.6
- Sebastian@d16
- Posts: 1526
- Joined: Tue Nov 07, 2006 9:20 pm
- Location: Katowice/Poland
Hi,
I'm sorry We should put the paragraph we put at the end of
notification email on the beginning of it. Due to technical reasons we
had to partially break with compatibility with previous versions of
Nepheton (Number of output channels has changed and way of recalling
Nepheton's parameters during loading the project). All those problems are caused by unification we were forced to make because of AU compatibility. PLEASE finish Your current critical projects with previous version of Nepheton before any update, or at least make the backups of old files.
The previous version of Nepheton is available to download in User Area
(add-ons tab), You can easily go back. Nepheton.vst is only a file
which can be renamed, so after installing new version You may rename
it however You'd like (e.g. Nepheton1_1_2) and then install the old
version. Host is supposed to see those two plug-ins separately. The
old one as Nepheton the new one as Nepheton1_1_2. Project You made
will be loaded with previous version.
Best regards,
Sebastian
I'm sorry We should put the paragraph we put at the end of
notification email on the beginning of it. Due to technical reasons we
had to partially break with compatibility with previous versions of
Nepheton (Number of output channels has changed and way of recalling
Nepheton's parameters during loading the project). All those problems are caused by unification we were forced to make because of AU compatibility. PLEASE finish Your current critical projects with previous version of Nepheton before any update, or at least make the backups of old files.
The previous version of Nepheton is available to download in User Area
(add-ons tab), You can easily go back. Nepheton.vst is only a file
which can be renamed, so after installing new version You may rename
it however You'd like (e.g. Nepheton1_1_2) and then install the old
version. Host is supposed to see those two plug-ins separately. The
old one as Nepheton the new one as Nepheton1_1_2. Project You made
will be loaded with previous version.
Best regards,
Sebastian
OK thanks for your reply. It's great to be able to have both old and new versions active at the same time.
Anyway it looks like compatibilty is totally broken (not just "partially") when subfolders are used.
Could you please brind back this feature in the next revision?
To be able to put Nepheton and Drumazon VSTs into subfolders (in the main VST Plug-ins folder), so they appear into submenus (in the host VST Instruments dropdown menu).
It was possible with the old versions. It's very handy to keep the VST menu under manageable proportion and to quickly find a plug-in amongst many.
Best regards,
Anyway it looks like compatibilty is totally broken (not just "partially") when subfolders are used.
Could you please brind back this feature in the next revision?
To be able to put Nepheton and Drumazon VSTs into subfolders (in the main VST Plug-ins folder), so they appear into submenus (in the host VST Instruments dropdown menu).
It was possible with the old versions. It's very handy to keep the VST menu under manageable proportion and to quickly find a plug-in amongst many.
Best regards,
Drumazon 1.6.2 - Nepheton 1.6.2 - Phoscyon 1.9.5 - Frontier 1.1.0 - Cubase Pro 10.0.60.396 - macOS High Sierra 10.13.6
- Sebastian@d16
- Posts: 1526
- Joined: Tue Nov 07, 2006 9:20 pm
- Location: Katowice/Poland
Finally I found the problem: spaces are not allowed in the subfolder name!
And in the same fashion, spaces are not allowed in the plugin name. If I put a space I got the strange GUI. If I don't put a space I've got the right GUI.
My subfolder was called " D16 Group": no way. "D16_Group" is fine.
Also no way to rename the new version "Nepheton 1.1.7.vst". It has to be "Nepheton1.1.7.vst".
I think this should be put in the release notes, and the ability to use spaces in the subfolder names should be bring back
HTH
Best regards
EDIT: by the way, wouldn't some conflict occur with the .ini files inside the Application Support/D16 Group folder, if we keep two different versions active? I understand this files command output configurations.
And in the same fashion, spaces are not allowed in the plugin name. If I put a space I got the strange GUI. If I don't put a space I've got the right GUI.
My subfolder was called " D16 Group": no way. "D16_Group" is fine.
Also no way to rename the new version "Nepheton 1.1.7.vst". It has to be "Nepheton1.1.7.vst".
I think this should be put in the release notes, and the ability to use spaces in the subfolder names should be bring back
HTH
Best regards
EDIT: by the way, wouldn't some conflict occur with the .ini files inside the Application Support/D16 Group folder, if we keep two different versions active? I understand this files command output configurations.
Drumazon 1.6.2 - Nepheton 1.6.2 - Phoscyon 1.9.5 - Frontier 1.1.0 - Cubase Pro 10.0.60.396 - macOS High Sierra 10.13.6
- Przemek@d16
- Posts: 550
- Joined: Tue Nov 07, 2006 3:10 pm
- Sebastian@d16
- Posts: 1526
- Joined: Tue Nov 07, 2006 9:20 pm
- Location: Katowice/Poland
- Sebastian@d16
- Posts: 1526
- Joined: Tue Nov 07, 2006 9:20 pm
- Location: Katowice/Poland