Sonic Projects OP-X Pro 3 released

[Niowiad]

Yeaaaugh - I just loaded up OP-X Pro-ii on the macbook and honestly I much prefer it. The UI of Pro 3 is a mess - Pro-ii is clean, clear and BLUE.

The poor guy got criticism for years because of the hidden parameters. It looks like this is the result
That has been pretty much constantly brought up whenever OP-X was being discussed.
It's not a surprise that "No more hidden functions" is one of the main features listed for v3, but that comes at a price.

I've personally always thought the interface and UX for v2 was actually nice, especially in "rack edition".

I'll agree the brown is weird... I have a feeling it's not going to last too long. Maybe I'm wrong.

[Funkybot's Evil Twin]

I'm going to preface this post with, "I haven't actually tried it myself, so I'm basing this just off seeing screen prints". So feel free to take this with an extra grain of salt.

I was definitely in the camp of "expose the hidden parameters" but it seems like the developer started with a skuemorphic looking OB style skin that was close to the prior version and just added some extra room for hidden features to be crammed into. Versus trying to incoporate them into the design of a new synth in a logical way. Probably done to maintain compatibility while also avoiding having to go a re-architecturing/factoring effort.

And I don't think Teksonic is necessarily wrong in his overall points. He's got a little bit of what BONES suffers from in that he seems unable to express his opinions without throwing in charged language that's going to annoy people and steer the conversation towards that and detract from the valid part of the posts, but I agree overall: $99 for a SynthEdit synth just isn't for me. I'd have preferred the developer switched to JUCE and sucked up the licensing cost, and spent the last few years sorting it out for a brand new V3. That might also negate the need for separate versions of the plugin (I mean like the low CPU, normal CPU, high CPU versions) and might have lifted some additional constraints by forcing a re-architecturing/refactoring, which might've been a good thing here.

If the developer did sound design for other synths, I'd probably buy his packs though!

[beely]

Do we know this is a SynthEdit synth, or is this just an assumption? I know it was in the early days, and this was one of the reasons there wasn't a Mac version (where SynthEdit does not run) - but there has been a reworking of the synth for V2, and a Mac version for years now, so I don't see how it still can be a SynthEdit synth...

[Odd Fella]

Whether it is made with SE or not should be irrelevant. If it sounds good, why would anyone care why it sounds good? SE is not a dangerous bug giving you a disease.

[Funkybot's Evil Twin]

Do we know this is a SynthEdit synth, or is this just an assumption? I know it was in the early days, and this was one of the reasons there wasn't a Mac version (where SynthEdit does not run) - but there has been a reworking of the synth for V2, and a Mac version for years now, so I don't see how it still can be a SynthEdit synth...

Open up your VST3 folder, look for the OP-MTX.vst subfolder, open that up, look fro Contents\Plugins and you'll see a bunch of .sem folders and files.

[seafire]

Do we know this is a SynthEdit synth, or is this just an assumption? I know it was in the early days, and this was one of the reasons there wasn't a Mac version (where SynthEdit does not run) - but there has been a reworking of the synth for V2, and a Mac version for years now, so I don't see how it still can be a SynthEdit synth...

https://www.synthedit.com/downloads/making-mac-plugins/

[JonSolo]

God I hate cats.

[chk071]

A SynthEdit discussion? Really?

As has been pointed out, it doesn't matter whether or not it was made in SynthEdit. You can do anything in SynthEdit.

That said, I would be surprised if he reverted back to SynthEdit, after v2 wasn't made with SynthEdit. But, what do I know?

[mcbpete]

I've personally always thought the interface and UX for v2 was actually nice, especially in "rack edition".

Definitely prefer the look of PRO-II vs PRO-3 ... except one usability issue: I'd spend ages trying to figure out whether a button is active/selected or not:


(top: no buttons are active, bottom: two buttons are active . How long did it take to work out which they were !)

[beely]

https://www.synthedit.com/downloads/making-mac-plugins/

Ah, thanks - this I didn't know.

[Caine123]

I've personally always thought the interface and UX for v2 was actually nice, especially in "rack edition".

Definitely prefer the look of PRO-II vs PRO-3 ... except one usability issue: I'd spend ages trying to figure out whether a button is active/selected or not:


(top: no buttons are active, bottom: two buttons are active . How long did it take to work out which they were !)

Wow this is really a strange decision i wonder this should be already fixed before release. Did you write support?

[mcbpete]

Yep, and still have Peter's reply:

Yes, it obviously depends on the monitor (I can see the difference clearly on my one), probably mainly how precise blue tones are rendered

It's clearly my eyes that are the problem not the design

[Aloysius]

Yes. It must be the customers fault. It has nothing to do with the design.

[Caine123]

Yep, and still have Peter's reply:

Yes, it obviously depends on the monitor (I can see the difference clearly on my one), probably mainly how precise blue tones are rendered

It's clearly my eyes that are the problem not the design

wow lol, im going to write him too cause this is bullshit

[mcbpete]

Note my screengrab is from Pro-II not this new one .... Looks like it's the same blue shade when switched on in v3 but as the un-active buttons are now 'baby-poo' brown at least it's visible with this colour scheme