But now I have confirmed that on both Mac and PC, a lot of the times, it does *not *load correctly in Ableton. This is why the internal test we carried out didn't discover this problem. It's another VST3-specific problem I am afraid. I have even experienced it loading a random plugin, from other manufacturers. The same applies to Ableton Live sometimes it can load old documents, and sometimes it cannot. I mean that both sincerely and ironically because, like, why fool other DAWs to use mechanisms you don't use yourself?) If the plugin's name is the same, it will use it. You see, Cubase itself doesn't care about the ID. There is a convention for how VST3 IDs of VST2s are created, and all of our other products follow this convention, except Synplant 1.2.īecause very few hosts actually allow upgrading a VST2 to VST3, except Cubase, this problem slipped through our fingers when we released our VST3s one year ago. It simply didn't construct the plugin ID correctly. The problem is that we had a bug in Synplant 1.2 already. I have investigated this problem extensively, and unfortunately, we are caught in a tricky dilemma. Thanks for providing the workaround, I'll keep it in mind - however, I would rather wait for the proper solution. From my understanding, it is just wrapper/bridge to the VST2 and mostly came about because of Cubase not supporting VST2 any longer. And I don't think the VST3 offers anything special. Then when you access the VST3 in your previous projects via v1, you could save the patch, and then reopen that patch with the VST2 of v2 if you wanted. Just make a backup of the v1 VST3 and v2 VST2 and replace one or the other, depending on the installer you run last. I was able to reproduce it and I know they are looking into it.Ī workaround you could do would be to just replace the VST3 with v1, then have that for compatibility when opening v1 projects and have VST2 of v2 to continue to play with. I might try that later just to see if I can reproduce the issue. Yeah I was only suggesting reverting in case it was urgent for a project. Yes, I know I can roll back to version 1 however, a fix would be suitable to use the new features. The new version as a new instance works fine it just doesn’t work with backward compatibility to Synplant 1. It would be difficult for me to find a VST 2 version of the project as most of my projects I’m working on are using VST 3 as I swapped them from VST 2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |