Dmitry Sches' Thorn VI

[Sampleconstruct]

Thanks for sorting that out, Simon

I was anticipating a flood of support requests so I better sorted it out right away

[popskull]

Is anyone using DS Thorn in Bitwig OSX? It doesn't load for me. Thorn worked however.

[popskull]

Is anyone using DS Thorn in Bitwig OSX? It doesn't load for me. Thorn worked however.

On further testing, VST2 works, not VST3

[sqigls]

If one already owns the extra Rob Lee presets, is there any reason to install version 1.2 instead of v1.1 ??

[aMUSEd]

If you install the new version over the old version it's getting really messy, Logic will not recognise/validate the new version, it still sees the old version but puts that into demo mode. Now I have no Thorn whatsoever, I have manually removed the old AU component for Thorn and will see how I can validate the new version. Not so cool...

So all user of the AU version, first remove the old plugin component from
Library/Audio/Plug-Ins/Components

then install the new version using the PA installation manager, otherwise you'll get into trouble. The second installation on my main studio computer went smoothly, the first installation on my laptop was a mess.

Does it still identify in hosts as the same plugin so projects are intact?

[DrGonzo]

I should probably do a bit of research before posting, but why all the hate towards PA? I feel like I missed something.

I bought a few of their plugins a couple of years back - good stuff. I opted out of their newsletter due to their constant mailbombing but that's about it.

/C

[ATS]

I love PA, I spent $75 on a plug and they now give me $25 a month for a while now. I used it this month to get the upgrade for Thorn. Their sales are fun too.

[Sampleconstruct]

If you install the new version over the old version it's getting really messy, Logic will not recognise/validate the new version, it still sees the old version but puts that into demo mode. Now I have no Thorn whatsoever, I have manually removed the old AU component for Thorn and will see how I can validate the new version. Not so cool...

So all user of the AU version, first remove the old plugin component from
Library/Audio/Plug-Ins/Components

then install the new version using the PA installation manager, otherwise you'll get into trouble. The second installation on my main studio computer went smoothly, the first installation on my laptop was a mess.

Does it still identify in hosts as the same plugin so projects are intact?

I wouldn't expect so as it's a new plugin component with a different name. Will check now.

[aMUSEd]

If you install the new version over the old version it's getting really messy, Logic will not recognise/validate the new version, it still sees the old version but puts that into demo mode. Now I have no Thorn whatsoever, I have manually removed the old AU component for Thorn and will see how I can validate the new version. Not so cool...

So all user of the AU version, first remove the old plugin component from
Library/Audio/Plug-Ins/Components

then install the new version using the PA installation manager, otherwise you'll get into trouble. The second installation on my main studio computer went smoothly, the first installation on my laptop was a mess.

Does it still identify in hosts as the same plugin so projects are intact?

I wouldn't expect so as it's a new plugin component with a different name. Will check now.

That would suck - PA should be paying users to upgrade

[Sampleconstruct]

If you install the new version over the old version it's getting really messy, Logic will not recognise/validate the new version, it still sees the old version but puts that into demo mode. Now I have no Thorn whatsoever, I have manually removed the old AU component for Thorn and will see how I can validate the new version. Not so cool...

So all user of the AU version, first remove the old plugin component from
Library/Audio/Plug-Ins/Components

then install the new version using the PA installation manager, otherwise you'll get into trouble. The second installation on my main studio computer went smoothly, the first installation on my laptop was a mess.

Does it still identify in hosts as the same plugin so projects are intact?

I wouldn't expect so as it's a new plugin component with a different name. Will check now.

I was wrong, it does open old projects with version 1.1 just fine and substitutes the old plugin with version 1.2 - in LogicX that is.

[aMUSEd]

That's a relief.

(Although possibly it may still affect some hosts if the name has changed - depends on if they go by the plugin ID or plugin name)

[Rivanni]

to make things more interesting i got no email from ds. nothing. not in spam or anything. i'm sure i can't be the only one. is there any important info in there we should know about?

Same here. No email from DS or PA. So there are users left out of this so called deal, which in the future could turn out to be more expensive than $19 you apparently have to pay.

[Rivanni]

DS is not an EU company. So no GDPR.

Wrong. They do business with EU citizens so GDPR applies.

[imrae]

I got a PA upgrade email but no DS. Extra weird!

[Rivanni]

I think the benefits of PA relate mainly to the devs not having to spend time on marketing.

Not sure if this is a benefit. They screwed up the marketing for Thorn.