What's the state of the acknowledged bugs in ProAudioDSP DSM V2? - ANSWER: Unresolved

[dwozzle]

A while back there was a thread on GS about problems with DSM V2, where PA acknowledged that there were issues, and was going to investigate. Does anyone know the final outcome of that? Are you experiencing any issues with it?

Three-page thread is here:
https://www.gearslutz.com/board/music-c ... sm-v2.html

Acknowledgement of problems by PA is post #64.

Best description of the issues is probably posts #58 and #59.

That thread is from Feb 2017, and there have been several updates to DSM since then, but a) none right after that like it was in response to those problems, and b) there's nothing in the changelog that's recognizably related as far as I can see.

It's on sale for $49, ending today, is why I'm asking. I wrote PA support, but it's the weekend, andit's unlikely I'll back while the sale is still on.

[dermage]

I think the bug where the "learned" curve was disappearing after saving a project and opening it again was never fixed. As far as I remember, this was discovered way earlier than 2017. I've had it around 2016 or so already.

[dwozzle]

I think the bug where the "learned" curve was disappearing after saving a project and opening it again was never fixed. As far as I remember, this was discovered way earlier than 2017. I've had it around 2016 or so already.

Blarg. Doesn't that make it difficult/obnoxious to use?

If that's the case, it's odd that I see lots of people saying how incredible and indispensable it is.

I'm not doubting you -- as I said, I see no evidence it *was* ever fixed. Which is a shame if true.

[dermage]

I think there's a possible workaround. You have to close the window before saving & closing the project. Then it won't happen.
I'm not using it that often, but never occurred to me again after I followed that workaround.

[Christian_D]

From the PA website:

Known Issues -
The DSM v2’s spectral curve file can’t be opened on Windows machines.

Some Windows users have reported that when they try to load the DSM v2’s spectral curve files, the files do not appear in the file selector window. If this happens, please go to your desktop and find your spectrum capture files, and add the extension “.crv” to the end of the filename. Then you should be able to open them within the DSM v2.

Thing is pretty amazing beat out fab filter de-esser on a vocal.

[dwozzle]

Sounds like a different bug, where the standalone curve files don't get saved with the right extension.

Seems different than not loading the curve contained in a session or a preset.

[dwozzle]

I think there's a possible workaround. You have to close the window before saving & closing the project. Then it won't happen.
I'm not using it that often, but never occurred to me again after I followed that workaround.

Interesting. You'd think if that was known, that they'd fix it, or at least document the workaround publicly.

Part of what people were unimpressed with was the seemingly we-know-and-we're-not-gonna-fix-it response from PA. This isn't so great in that light.

[dermage]

I think there's a possible workaround. You have to close the window before saving & closing the project. Then it won't happen.
I'm not using it that often, but never occurred to me again after I followed that workaround.

Interesting. You'd think if that was known, that they'd fix it, or at least document the workaround publicly.

Part of what people were unimpressed with was the seemingly we-know-and-we're-not-gonna-fix-it response from PA. This isn't so great in that light.

As I said, I'm not sure, maybe they have fixed it in the meantime. But did not read anything about it in the change logs.

Also with their consoles, they knew since bx_console, that their metering is broken/does not comply to the standard, and they did not fix it until now. Maybe they will, but there has already been many angry users over at GS. There was more or less an answer by Dirk, that they'll discuss it with their team, not implying that they'll fix it or when.

Anyway, I think DSM v2 is usable in its current state, the bugs are not showstoppers, but possibly annoying to the workflow.

[dwozzle]

I asked PA support about this a few days ago. Got this reply last night:

They are still outstanding for us and unfortunately the dev team has not indicated when they will be fixed.

Best,

_________________________________
Vadim - Senior Product Specialist
Plugin Alliance Support Team

It is what it is.