By lobit
Tue Oct 11, 2022 10:24 pm
would be an easy way for Akai to beef up its FX options with nearly no effort though
AndyRAW wrote:I think it is a good synth, but the UI needs work. Moving the Mod Matrix page to be next to the Operator page would be a big improvement. Hopping between those pages when designing is a pain.
AndyRAW wrote:I hope Akai/inMusic keep working on updates for OPx-4, and other plugins. I don't see much indication of that, and I don't think their support is good, which means they don't pay much attention to user feedback.
AndyRAW wrote:On the OPx-4, just moving the Mod Matrix page (currently next to settings) to be next to the Operator page would be a simple but big improvement to the UI.
dustyslices wrote:Unfortunately it won't work - there is a lot of items in this skin that call "CurrentSubTab" parameter. Problem with this parameter is that it's not defined anywhere within the TUI file which makes me belive that it is stored internally within the plugin itself. When I shuffle the tabs, all hell breaks loose and indexing of the items that call "CurrentSubTab" gets wonky and out of sync. oh well... you won't know if you don't try
AndyRAW wrote:dustyslices wrote:Unfortunately it won't work - there is a lot of items in this skin that call "CurrentSubTab" parameter. Problem with this parameter is that it's not defined anywhere within the TUI file which makes me belive that it is stored internally within the plugin itself. When I shuffle the tabs, all hell breaks loose and indexing of the items that call "CurrentSubTab" gets wonky and out of sync. oh well... you won't know if you don't try
Thanks for looking at this. It sounds like it will require a major review of the code just to move the tab, which suggests the coding has not been well structured. We can only hope for a major update.
Are you working for Akai?
AndyRAW wrote:Other issues (this is on an Akai Force):
1. Many changes do not take effect until the note is retriggered. For example, turning an operator an/off, which is an important compare function during sound design mode. This means you can't check an operator's effect on the sustain part of a sound unless you retrigger the whole envelope, which can be very long on an ambient sound, which is one area I think this synth is great for.
2. There seems to be a number of bugs with the mod matrix. E.g. I enabled and assigned the ramp to various destinations and it did nothing.
Tinwhistle wrote:Hello everyone,
I also play a Yamaha WX 7 wind controller through a Yamaha WT11 synth module which is in fact a TX81Z performance player. The sounds are programmed for breath control Midi CC 2.
What I would like to do is to play the OPX-4 with the WX7 wind controller.
When programming the TX81Z for wind control I got good results by setting the parameters for EG Bias and Pitch Bias to breath control to get expressive phrasing typical of a wind instrument.
On looking at the modulation parameters of the OPX-4 I cannot seem to find
anything that could correspond with EG Bias and Pitch Bias so that I could set to breath control.