Plogue OPS7 (bit-accurate DX7 emulation!)

[gentleclockdivider]

This is the bug , I you save a patch which has extended features ( into patch panel ) and then save another patch without the extended features ( again into patch panel )
The first saved patch will lose it's extended features when reloaded from patch panel .
So if you really want your previouisly saved patches to sound exactly as they were meant , you should always enable extended features .
Please fix this , or choose a better system to layer fermata patches

[davidv@plogue]

@david: Will the demo version be updated with your latest performance improvements, too? That would be great, to estimate the cpu load

Hello
Sure we only make one install package our instruments. All downloads are full versions that act like demos until registered.

[gentleclockdivider]

I think I found another bug
Say you converted your fermata patches to sysex , you copy paste from column A -B
You want to add another preset at the end of your exisitng sysex list , in some cases this newly added preset fils the complete list with duplicates of the exisiting list ..pretty weird ..

[davidv@plogue]

I think I found another bug
Say you converted your fermata patches to sysex , you copy paste from column A -B
You want to add another preset at the end of your exisitng sysex list , in some cases this newly added preset fils the complete list with duplicates of the exisiting list ..pretty weird ..

Experimenting with _major_ changes in there, just bear with us.
Cheers

[gentleclockdivider]

BUg ?
IN extended mode , the operator gain is the only control that does not show any animation (visually) when modulated by step lfo

[gentleclockdivider]

New Bug or original dx7 sysex behaviour ?
Loaded sysex patches created with ops do NOT remember muted operators when imported
-Choose appropriate algoritm with +1 carrier
-Create patch
-Make sure some at least one carrier is muted
-save patch and save sysex file
-Import sysex file
Result : muted operator is unmuted

[nominil]

New Bug or original dx7 sysex behaviour ?
Loaded sysex patches created with ops do NOT remember muted operators when imported
-Choose appropriate algoritm with +1 carrier
-Create patch
-Make sure some at least one carrier is muted
-save patch and save sysex file
-Import sysex file
Result : muted operator is unmuted

I *think* your hunch that this might be expected behavior for original DX7 sysex is correct.

[gentleclockdivider]

Delete post

[Michael Sage]

Well, what’s new?

[gentleclockdivider]

Well, what’s new?

It still sounds as good as 3 weeks ago
No seriously , I think the developer is finetuning ( reworking ) the browser , he also posted that there is gonna be some cpu optimization .

[cantaloupe]

Man, OPS7 is just so impressive. Been using it constantly since it was released. Having the option of both original DAC and 15bit is great.

Part of the charm and longevity of the DX, to my ears, is the edge cases. Those strange settings where the alias and noise (and whatever else) hits just right and you get surreal timbres and moods that is pretty much impossible to get anywhere else. And that is where other attempts fall apart, while original hardware (and OPS7) don't.

And how did they ever manage to create a synth that actually sounds this melancholic? Releasing it in autumn was the only correct choice.

[davidv@plogue]

Ok we thought and worked quite a lot on this update to hopefully fix some of the "dual" preset making issues that were brought up. (without breaking anything you guys already made - which is always a great challenge)

To sum up our understanding of the issues: there is a clear workflow divide between the different use cases and we have tried our best to have them all coexist in the original release without success:

1)User wants to play master presets only -> nothing to see

2)User wants to load original DX7 SYSEX files in A and B, potentially using MIDI program changes to change both live - which is already possible with an entry in Settings. This mode is the one we thought would be most popular as this - more than anything - is a carefully modeled digital synth whose primary goal is to be the best emulation we can make of an existing synthesizer.
An out of the box experience of stacking two DX7s, with all their quirks

3)User wants to create their own A / B layered patches using Non-SYSEX compatible Extensions.
Save each layer separately, reuse specific sub layers in other presets etc.

As far as I know other plugins are either 2) or 3) but not both at the same time.

2) and 3) really are two very different workflows. We assumed 3 would be the minority and most people would fall into 1 an 2 - we still think its the case for the majority of users - but its hard to know with the feedback so far (you guys are very vocal 3)'s I know

So the compromise we came up with is to strengthen the idea of a global "Extended" params switch.
This time on the top right of the UI. You can set it to "Extended" OR "Classic (SYSEX)"

When Extended, the 32-slot SYSEX display/choice in A and B disappear and get replaced with a preset dialog that works the same way as in chipsynth MD. You can now save custom sounds in plain xml .fermatap (not .fermatax) files and load them in A and B at will.

Both patch selectors cannot live at once as it would be incredibly confusing for someone who is not familiar with the original sysex logic. Also, most of the SYX tab is now GREYED OUT in "Extended" mode. It makes no sense to use a lossy storage for Extended patches, nor to connect to hardware that doesn't support those features. You can still however use the SYSEX browser and its sounds as base for extended patches. We have now added means to audition/copy clicked sounds into A, B Both or None. (Previously it was always sent to A no matter what, and it was a UI oversight, the code internally always had a switch for that)

So after a long wait, you can get the update on https://plogue.com/downloads

Revision History:

v1.005 October 18th 2021
CPU usage greatly reduced.
Added: New preset drop downs for single sounds in Extended params mode
Added more "sub patches" in A and B extended mode.
Added: Init and Init(Template) shortcuts added in each preset menu
Fixed: MTS-ESP tuning changes are applied without requiring on/off cycle
Fixed: Built in Scala now supports non 12 tone scales
Fixed: License button was broken after a skin change
Fixed: EG Knobs misbehaving under certain DAWs using VST3
Fixed: Randomize now works for extended mode parameters

[EnGee]

Thank you

[Funkybot's Evil Twin]

David, very nice update!

Small bug:



I'm using Reaper (VST2, Windows), 125% GUI size, MKII skin, and when I open the settings window and move my mouse over the bottom left portion of the GUI, the wire from the below screen appears on top of the settings dialog.

[davidv@plogue]

Small bug:

Hmm yeah, known issue. Its a pesky refresh issue that only happens in Windows so far.