Plogue OPS7 (bit-accurate DX7 emulation!)

[Funkybot's Evil Twin]

Small bug:

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

Very minor cosmetic thing. No worries here if it gets squashed at some unknown time in the future (or never at all).

[jbraner]

v1.005 October 18th 2021

What an interesting update!
It's interesting to find out about the different way people have been approaching this. I just always thought you'd want to maybe use the syx files to load up sounds - and then save them in a OPS7 format (whether single or double).
I'm not trying to start an argument - or even a discussion - just realising that other people approach it differently.

It's still a little weird how a patch name can appear in the screen for A or B, but a completely different sound is playing. This is easily fixed though, by clicking (in extended mode) init - then reload your fermatax preset - voila! blank patch name

One little not so important thing for the future. It's still a little awkward to load a syx patch and then save directly as a fermatap file. It would be cool to somehow "copy" the name from the syx screen - so when you change to extended mode and want to "save" the patch - you could just "paste" the name.
Either that or somehow save the patch name, in the A and/or B screen - when you change from classic to extended mode - so when you "save" the patch, it's name is still on the patch name screen. (this is harder to explain than it actually is)

Or maybe there's no need to actually do this.

[gentleclockdivider]

Congrats on the cpu optimization
Classic dx takes only 7% , and extended on 10 tear old pc

I've got a question about the fast versus accurate channel mix settings
Mostly using it in fast and default resampler , since accurate is pretty cpu intensive , but I can't really hear any big difference
Could you give some guidelines where the differences are most profound ?

[davidv@plogue]

Congrats on the cpu optimization
Classic dx takes only 7% , and extended on 10 tear old pc

I've got a question about the fast versus accurate channel mix settings
Mostly using it in fast and default resampler , since accurate is pretty cpu intensive , but I can't really hear any big difference
Could you give some guidelines where the differences are most profound ?

It really only matters if you run your DAW at 96kHz and up, the junk at 49kHz (the DX7's native samplerate) appear there. Its really a pedantic thing that bothered me looking at a spectrograph. I can't hear the difference.

Fast mixes everything at 49kHz, while accurate internally runs at 16*49kHz just to emulate what the original hardware does (Time Division Multiplexing), but that's the sort of stuff that you can't really hear that I wanted to add just because ....

Cheers

[davidv@plogue]

Hi

It's still a little weird how a patch name can appear in the screen for A or B, but a completely different sound is playing. This is easily fixed though, by clicking (in extended mode) init - then reload your fermatax preset - voila! blank patch name

Our preset boxes always contain whatever last populated them from its current list, not depending on what else has changed. We know about this. We are thinking of clearing what they show at least in an update.

One little not so important thing for the future. It's still a little awkward to load a syx patch and then save directly as a fermatap file.

Hmm
Again (as I pointed out in a video before) I'm not sure I understand the point of doing this for more than say 20 or so sysex sounds since the original sysex files still contain that info when you need them and the session should recall the last 2 sets of 32 patches loaded in A or B in Classic Mode for rapid changes using program changes.

If I read between the lines, you want to make your own short list of favorite sounds out of thousands of SYSEX files and save them for quick access?

Cheers

[gentleclockdivider]

Awesome ,I am enjoying it so much but could it be possible to adjust the zoom ratio from the bottom of the screen when the keyboard is hidden , and some options between 75% and 100 % ?
Once again , congrats !

[cantaloupe]

Great update, thank you

[jbraner]

If I read between the lines, you want to make your own short list of favorite sounds out of thousands of SYSEX files and save them for quick access?

That is it exactly!
And it's quite easy to do - except you have to remember the name of the syx preset - to type it when you save as a fermatap one.
This is hardly a major problem

[gentleclockdivider]

O.K. so there is now a dedicated dropdown for loading extended (factory) patches in the A-B panel
Still there no easy way to load our own different ( extended patches, fermata ) in both panels .
I tried pointing it to my user folder ( fermata but it doesn't work) , only factory

[jbraner]

Still there no easy way to load our own different ( extended patches, fermata ) in both panels .

You do that in the A and B panels - don't you?
RH click on the patch name.

[davidv@plogue]

Still there no easy way to load our own different ( extended patches, fermata ) in both panels .

Not sure I follow. Which both panels?
A and B's new Extended "patch" dropdowns feed from the same pool of .fermatap files (Factory and user) in both case. The stuff in SYS is classic read-only SYSEX only in this mode.

[gentleclockdivider]

Still there no easy way to load our own different ( extended patches, fermata ) in both panels .

Not sure I follow. Which both panels?
A and B's new Extended "patch" dropdowns feed from the same pool of .fermatap files (Factory and user) in both case. The stuff in SYS is classic read-only SYSEX only in this mode.

Patches created with extended features on , that appear on the top window

If we want to load two different ones , we still need to go through the whole conversion process from fermata -->sysex , in order to load them in the two panels.
Unless there is a way to point them them to the user folder (see my previous post ) whcih I can't make it do , feeding from the same pool like you described
How do I get my user patches belong to that pool ?

[davidv@plogue]

Master presets that appear in the top (full/recall with .fermataX extensions - which include everything in the whole UI) should not be used to feed A and B separately.
The two individual A and B patch boxes use .fermataP extension and only contain one slot worth of extended parameters. You can save fermatap presets at anytime, whether you want to RIP one of the two slot's data from a top full/recall/fermataX or using random, or importing classic sysex.

I'm very confused.

[davidv@plogue]

1)Load top preset X
2)In A, click on patch drop down, hit save "part A of X"
3)in B, click on patch drop down, hit save "part B of X'

4)Hit top "Init" entry
5)In A ,click on patch drop down, hit "user/part B of X" (or whatever)
6)In B.. do anything else you want, audition a SYSEX entry from SYX (making sure audition is set to B only), hit random, etc.

[gentleclockdivider]

1)Load top preset X
2)In A, click on patch drop down, hit save "part A of X"
3)in B, click on patch drop down, hit save "part B of X'

4)Hit top "Init" entry
5)In A ,click on patch drop down, hit "user/part B of X" (or whatever)
6)In B.. do anything else you want, audition a SYSEX entry from SYX (making sure audition is set to B only), hit random, etc.

Ah , ok I see now .. It's more or less the same procedure as in previous versions
We need to actually re-save the (top bar ) preset in the patch panel in order to load and layer extended patches
See screenshot


This is really counter intuitive since we already have those (extended ) presets , resaving already saved patches just for making layers is ..hm strange
On top of that the user user locations for presets is getting more complicated
Imho , this system is not good

Edit ,Where is the main user fermata patces ( top bar ) located ?