You COULD run both, (but I can't think of any reason I'd ever do that).

I have done it cause it’s fun to experiment.

. Perhaps after all, it doesn’t take a Rhodes scholar to go figure, figure out, eventually, the methodology of a myth is just a method in the madness!

Ha, "Rhodes" scholar was genius enough, but then following it with that brilliant alliteration.  Hats off to you, sir!   

I agree with you now that I've been through it.  Pianoteq 5 and Pianoteq 6 are seen as separate Audio Units in Logic/Mainstage.  You COULD run both, (but I can't think of any reason I'd ever do that).

Like I said originally, the idea of effortlessly moving from 5 to 6 was something I read on a less-learned forum.  It didn't work that way for me, so I figured I check here.  I guess I thought it would be like most app upgrades.   Say, for example,  you go from Word 2011 to Word 2016.  After installing the newer version and then deleting the older, all your .doc files should now open fine in Word 2016, right?  No need to re-assign them like I had to do with all my instances of Pianoteq 5.   Probably not the best equivalency I could come up with but it's KINDA like that.    (PS I don't use Word)

Perhaps after all, it doesn’t take a Rhodes scholar to go figure, figure out, eventually, the methodology of a myth is just a method in the madness!

If you updated to version 6 from version 5, Logic Pro will automatically scan the latest update version to ensure the plugin will work.  Once confirmed (a one-time deal with each new update), when you instantiate Logic Pro, you be presented with the choice of invoking Pianoteq 5 -- OR -- Pianoteq 6.  Assuming you haven't deleted the earlier version, you should be able to select Ptq 5 OR Ptq 6.  In Logic Pro, you will need to select a new AU (audio units) instrument, of which Modartt will be one of your choices.

Hope this helps,

Cheers,

Joe

In your DAWs, look for a setting like:

"Refresh Plug-ins" - or

"Re-scan Plugins" - or

"Flush Plug-in Cache".

Also, some hosts may have a check-box in their settings like:

"Rescan Plugins on Startup"

Good luck - hope that solves things. If not keep posting.

For most people, in most circumstances, it should just work, and does. Although not quite a myth, there are always some of us who experience the times something doesn't automatically work

There are always some DAW and VST combos (some reasons below) which require some user intervention, to this day, unfortunately.

Different DAWs and hosts handle things differently, and makers of VST products can only adhere to known conditions and standards. Pianoteq has never borked anything here where other VSTs have.

Currently, VST 3 might be a cause of a few DAWs failing over as some might have been loading a VST 2 version before an update - so following from there, if said DAW has itself recently updated, and had newly coded better handling for VST3, then perhaps it's maybe just "stuck" looking for your new compatible PTQ6 inside some newly obsolete VST 2 folder.. who knows. A DAW's plugin cache will sometimes remain with incorrect pointers for the DAW, so expunging the cache is always one of the first things I do after installing any updates or new plugins.

Hopefully that's what you're also encountering, as the fix is usually a click away.

Was that bad information or did I do something wrong?    That's a lot of channel strips that need fixing.