discoDSP Discovery Pro 8.15 released

[george]

8.9.1.1 has been released with a few minor tweaks.

• Added CC 63 display on layer selector buttons (A/B/C/D) in MIDI CC mapping view for better visibility of hardcoded layer selection functionality
• Moved MIDI CC mapping display options from Help menu to MIDI menu for better logical organization
• Renamed "MIDI CC Buttons" to "MIDI CC Button Mode (CC 71)" for improved clarity and MIDI implementation understanding

https://www.discodsp.com/discoverypro/

[shorty]

Linux activation fixes with cURL support

Wait… I thought you said that the Linux version wouldn’t have copy protection?!

it does now???

[audiojunkie]

What else could “Linux activation” be?

And doesn’t it seem strange that George posted another update and didn’t respond to my question?

[Teksonik]

I don't think it's George. I think he's using some kind of A.I. bot.

I'd like clarification on this posted in the non-pro version of Discovery thread:

[*]Replaced demo/full version builds with dynamic runtime license checking.

So can DiscoDSP please explain in detail what "dynamic runtime license checking" means and how it works?

[dayjob]

8.9.1.1 has been released with a few minor tweaks.

• Added CC 63 display on layer selector buttons (A/B/C/D) in MIDI CC mapping view for better visibility of hardcoded layer selection functionality
• Moved MIDI CC mapping display options from Help menu to MIDI menu for better logical organization
• Renamed "MIDI CC Buttons" to "MIDI CC Button Mode (CC 71)" for improved clarity and MIDI implementation understanding

https://www.discodsp.com/discoverypro/

download is still 8.9.1... and is from October 3rd. is there supposed to be an updated version beyond that to 8.9.1.1 ?

[george]

download is still 8.9.1... and is from October 3rd. is there supposed to be an updated version beyond that to 8.9.1.1 ?

The 8.9.1.1 update was uploaded on October 4. The version number remains unchanged at 8.9.1, as it represents a trivial update. It is likely that you are receiving a cached download.

[midi sentinel]

I don't think it's George. I think he's using some kind of A.I. bot.

I'd like clarification on this posted in the non-pro version of Discovery thread:

[*]Replaced demo/full version builds with dynamic runtime license checking.

So can DiscoDSP please explain in detail what "dynamic runtime license checking" means and how it works?

Well, considering that account section now has a 'counter' next to each registered plugin, I suppose it is doing exactly what you think it is doing

Like this:



I always disliked DiscoDSP but now I dislike them much, much more. Changing important things like this, without giving a clear notice to customers is really a bad move (especially when one doesn't even have basic decency to respond to questions about said change).

And again, we will depend on someone's good will in order to have licenses reset. I can't explain how much I despise this idiotic method. If they really want to limit the number of activations, then implement a proper back-end where I can remove activations by myself and not depend on someone else.

[MOD EDIT]Unnecessary bad language removed[/MOD EDIT]

[dayjob]

download is still 8.9.1... and is from October 3rd. is there supposed to be an updated version beyond that to 8.9.1.1 ?

The 8.9.1.1 update was uploaded on October 4. The version number remains unchanged at 8.9.1, as it represents a trivial update. It is likely that you are receiving a cached download.

emptied cache, cleared history, restarted.. still says oct. 3rd.

[shorty]

What else could “Linux activation” be?

And doesn’t it seem strange that George posted another update and didn’t respond to my question?

hm, seems you're right. byebye, discoDSP, then.

[audiojunkie]

Thank goodness Shortcircuit-XT is coming along well. That will be my main sampler on Linux. I hate C/R copy protection. I hate how sneaky DiscoDSP is with their business dealings. And the AI stuff drives me crazy. It reminds me of back in middle school where I would use a slightly larger font, with a slightly larger line spacing to turn a one and a half page essay into a two page essay to meet the minimum requirements. Only in this case, he has AI rewrite his update announcements to be wordy and filled with techno babble to make it look like it is a worthy version update. Look back at the updates and ask AI to make the announcements less wordy and in layman’s terms if you think I’m exaggerating. There is very little substance to these updates. He’s not doing anything illegal, but I feel like I need a shower after dealing with him.

[audiojunkie]

Give me an honest, even blunt dealer anytime over this sneaky, in the shadows crap.

[tumface]

To me, the updates look like they're written by a programmer and relayed directly, not like they're written by AI. For example, I know exactly what "FMA instruction support" means (fused multiply-add) and it's a nice thing to add, and since they're calling it out in patch notes it's probably via SIMD intrinsics instead of a compiler flag. That doesn't seem like something AI would write coherently.

The licensing stuff is no good, though.

[george]

emptied cache, cleared history, restarted.. still says oct. 3rd.

There may be a date mismatch. Please verify if the MIDI menu has the show MIDI CC mappings. If so, you are running 8.9.1.1

[Teksonik]

To me, the updates look like they're written by a programmer and relayed directly, not like they're written by AI. For example, I know exactly what "FMA instruction support" means (fused multiply-add) and it's a nice thing to add, and since they're calling it out in patch notes it's probably via SIMD intrinsics instead of a compiler flag. That doesn't seem like something AI would write coherently.
The licensing stuff is no good, though.

If I understand you correctly, no one is saying the plugin code is written by A.I. only the "support" responses here. Just read them. If it's not an A.I. bot then George is just willingly ignoring customer's questions.

If he feels he has a right to use KVR as a vehicle to advertise his products and announce updates then he should have the responsibility to answer simple questions about those updates.

That's not asking too much of any developer.

[tumface]

If I understand you correctly, no one is saying the plugin code is written by A.I. only the "support" responses here. Just read them. If it's not an A.I. bot then George is just willingly ignoring customer's questions.

Sorry, my bad. I wasn't being clear. I meant to say that the release notes were not being written by AI, referring to this comment:

I don't think it's George. I think he's using some kind of A.I. bot.

I wasn't saying the code was written by AI, which I think would be pretty much impossible for a functioning audio plugin.