Hi
I've been using Pianoteq with Cubase 10.060 for quite some time. Bu today I can't get the plugin working. I tried reinstalling, but it still does not work.
This is the error I get:
The plug-in "Pianoteq 7 STAGE" could not be found for VST Synth 3!
It seems that Cubase does not recognize the plugin as 64-bit.
My OS is MacOS 10.12.6.
(I'm running on an old Intel Mac so I can not update the OS)
Hi
I've been using Pianoteq with Cubase 10.060 for quite some time. Bu today I can't get the plugin working. I tried reinstalling, but it still does not work.
This is the error I get:
The plug-in "Pianoteq 7 STAGE" could not be found for VST Synth 3!It seems that Cubase does not recognize the plugin as 64-bit.
My OS is MacOS 10.12.6.
(I'm running on an old Intel Mac so I can not update the OS)
I just noticed the newly installed plugin is blacklisted and can not be activated.
Arlaharen wrote:Hi
I've been using Pianoteq with Cubase 10.060 for quite some time. Bu today I can't get the plugin working. I tried reinstalling, but it still does not work.
This is the error I get:
The plug-in "Pianoteq 7 STAGE" could not be found for VST Synth 3!It seems that Cubase does not recognize the plugin as 64-bit.
My OS is MacOS 10.12.6.
(I'm running on an old Intel Mac so I can not update the OS)I just noticed the newly installed plugin is blacklisted and can not be activated.
Try:
"Re-setting the Cubase plug-ins cache manually : Acustica Audio Help-Desk Portal" https://acusticaudio.freshdesk.com/supp...e-manually
Arlaharen wrote:Hi
I've been using Pianoteq with Cubase 10.060 for quite some time. Bu today I can't get the plugin working. I tried reinstalling, but it still does not work.
This is the error I get:
The plug-in "Pianoteq 7 STAGE" could not be found for VST Synth 3!It seems that Cubase does not recognize the plugin as 64-bit.
My OS is MacOS 10.12.6.
(I'm running on an old Intel Mac so I can not update the OS)I just noticed the newly installed plugin is blacklisted and can not be activated.
Tried to remove the .vst files and only kept the .vts3 files. The only thing that changed is that the plugin is no longer blacklisted.
Arlaharen wrote:Arlaharen wrote:Hi
I've been using Pianoteq with Cubase 10.060 for quite some time. Bu today I can't get the plugin working. I tried reinstalling, but it still does not work.
This is the error I get:
The plug-in "Pianoteq 7 STAGE" could not be found for VST Synth 3!It seems that Cubase does not recognize the plugin as 64-bit.
My OS is MacOS 10.12.6.
(I'm running on an old Intel Mac so I can not update the OS)I just noticed the newly installed plugin is blacklisted and can not be activated.
Try:
"Re-setting the Cubase plug-ins cache manually : Acustica Audio Help-Desk Portal" https://acusticaudio.freshdesk.com/supp...e-manually
Still doesn't work I'm afraid. Cubase blacklists the plugin.
Key Fumbler wrote:Arlaharen wrote:I just noticed the newly installed plugin is blacklisted and can not be activated.
Try:
"Re-setting the Cubase plug-ins cache manually : Acustica Audio Help-Desk Portal" https://acusticaudio.freshdesk.com/supp...e-manuallyStill doesn't work I'm afraid. Cubase blacklists the plugin.
I also have Cubase 10.5.20 and Pianoteq is listed as "Not a valid plugin-in", even after re-setting the plugin cache manually.
So far I have tried the following:
Cubase 10.0.60
Cubase 10.5.20 (and update to 10.5.30)
Manual plugin cache reset.
Manually adding the VST3 folder to the plugin path
Temporarily removing the non VST3 plugin.
Try clearing that cache but don't restart. Delete Pianoteq. Restart machine. Install latest Pianoteq.
Restart DAW.
See if that works.
If that doesn't work contact Steinberg.
Try clearing that cache but don't restart. Delete Pianoteq. Restart machine. Install latest Pianoteq.
Restart DAW.
See if that works.If that doesn't work contact Steinberg.
That did not change anything unfortunately.
Key Fumbler wrote:Try clearing that cache but don't restart. Delete Pianoteq. Restart machine. Install latest Pianoteq.
Restart DAW.
See if that works.If that doesn't work contact Steinberg.
That did not change anything unfortunately.
Was that with a renewed download or trying with the same copy?
Worth trying even if it's the same version, in case the file is corrupted. It's probably something else but it doesn't hurt to try.
Arlaharen wrote:Key Fumbler wrote:Try clearing that cache but don't restart. Delete Pianoteq. Restart machine. Install latest Pianoteq.
Restart DAW.
See if that works.If that doesn't work contact Steinberg.
That did not change anything unfortunately.
Was that with a renewed download or trying with the same copy?
Worth trying even if it's the same version, in case the file is corrupted. It's probably something else but it doesn't hurt to try.
I tried uninstalling Pianoteq 7 and then installing it again. There was no change. Also tried manual plugin reset after I re-installed Pianoteq 7. I’ve updated the eLicenser and downloaded a patch for Cubase 10.5. No change. Lastly, I have Pianoteq 5, 6 and 7 installed. Pianoteq 6 & 7 does not currently work. But strange enough Pianoteq 5 seems to work. But alas, all my projects are either with Pianoteq 6 or 7.
I also tried to load Pianoteq into Reaper (tried a re-scan).
I currently have Pianoteq 5, 6 and 7 installed.
In both Cubase and Reaper only Pianoteq 5 is working.
All versions of Pianoteq has previously worked.
I tried reinstalling Pianoteq 7, but no change.
Seems to me that this is not a DAW issue?
Either MacOs related (have not updated recently) or Pianoteq related.
I've checked the hardrive for errors and repaired permissions. No change.
I just tried loading Pianoteq into the latest version of Reaper and it appears to be working correctly. My system is running Debian 9 (linux), so it is an old version of Linux with the latest applications on it. I can't try it with the latest version of Debian as I haven't got round to upgrading my system as yet, thus the test is not definitive.
It would tend to suggest, however, that is OS related rather than Pianoteq related.
Do check that your library name for the Pianoteq vst is still modified. I needed to change the name to "Pianoteq_2chan.so" to get the vst to work in Linux, not sure whether you need a similar workaround in MacOs.
Michael
It's clearly a Mac version specific issue. Latest Pianoteq fine in latest Reaper x64 in Windows 10. Actually never had the issue you described in Windows with Reaper.
I used PTQ 6 and 7 with Cubase 9, 9.5, 10, 10.5 and 12 on Windows 10 64bit.
No issues.
It's clearly a Mac version specific issue. Latest Pianoteq fine in latest Reaper x64 in Windows 10. Actually never had the issue you described in Windows with Reaper.
Ok, I will try to upgrade to MacOS 10.14 and see if that solves the issue.
Key Fumbler wrote:It's clearly a Mac version specific issue. Latest Pianoteq fine in latest Reaper x64 in Windows 10. Actually never had the issue you described in Windows with Reaper.
Ok, I will try to upgrade to MacOS 10.14 and see if that solves the issue.
In your first post you stated that you could not upgrade due to your Intel CPU?
What happened to this?
..
My OS is MacOS 10.12.6.
(I'm running on an old Intel Mac so I can not update the OS)
Arlaharen wrote:Key Fumbler wrote:It's clearly a Mac version specific issue. Latest Pianoteq fine in latest Reaper x64 in Windows 10. Actually never had the issue you described in Windows with Reaper.
Ok, I will try to upgrade to MacOS 10.14 and see if that solves the issue.
In your first post you stated that you could not upgrade due to your Intel CPU?
What happened to this?
Arlaharen wrote:..
My OS is MacOS 10.12.6.
(I'm running on an old Intel Mac so I can not update the OS)
Sorry, I meant I can not update to the latest MacOS. I think Catalina is the last OS I can update to.
Sorry, I meant I can not update to the latest MacOS. I think Catalina is the last OS I can update to.
Okay, I hope that does the trick then.
Arlaharen wrote:Sorry, I meant I can not update to the latest MacOS. I think Catalina is the last OS I can update to.
Okay, I hope that does the trick then.
It did! Updated to Mojave. The latest version I could install is Catalina, but will stay at Mojave for now.