On the op1-f you can see the impact the lfo has, for example if you set it to impact synth param 1 then the graphics for synth param 1 are animated accordingly with the lfo. However on the op-xy it doesn’t appear as if there is any visual connection to the onscreen graphics on m1, m2, or m3 pages with the lfo. If you param lock one of the values such as filter cutoff then it is correctly animated and the number values will be dynamically displayed based on the p-lock but this same visually responsive feedback isn’t there with the lfo. I might be misremembering but I thought the lfo on the op-xy at least caused the number values to dynamically change but in the last couple firmware updates it doesn’t look like the lfo has any visual impact on the m1, m2, or m3 pages regardless of what it modulates. Of course you can hear the impact the lfo has but I think it’s important to get visual feedback as well. I was wondering if anyone knows of a workaround or perhaps my device is working atypically. Is this normal behavior and do you expect they will fix this in upcoming firmware.
Yeah. I wish that aspect of interface was implemented the same as op-1 I really don’t understand the rationale for it to be different. I am still secretly hoping that an update one day will bring this back, but not holding my breath!
Ok thanks. I think not animating.the lfo modulation is a real shortcoming. I also think not persistently showing an indication of the fx send levels on the mixer m1 page is another place where the ux graphics need to be refined. These graphic updates could definitely provide a more dynamic and informative experience for the user and I would think these sorts of things would be the easiest to remedy via firmware since they aren’t caused by any hardware limitations but rather they feel more like a placeholder for a more realized solution that is yet to come.
Yeah, sends being persistent view in the mixer would be nice. Just in case you don’t know, you can go to the M2 page in Aux tracks 7 and 8 to see all send levels at once in the meantime.
The only problem is the numbers shown on the m2 page for fx1/2 don’t update correctly. If you sequence the sends on a synth track you’ll see the m2 page on the fx track won’t indicate the correct sequenced values.