Has anyone experienced this odd behaviour using FMOD 2.03.09 on Mac OS 15.7.3?
Scenario:
Normally, the first step after creating a Loop Region is to adjust its borders in the Logic Track – to encompass the event portion that must be looped. NOTE: Immediately after creating the Loop Region, the region’s borders are highlighted by FMOD; that is to say, FMOD recognises it as the object you are currently editing.
Odd behaviour:
Immediately after creation, I adjust, say, the righthand border of the Loop Region. Consistently, FMOD refuses to recognise the mouse click+hold and drag. The solution seems to be executing an extra mouse click, which deselects the Loop Region as the current object being edited. Then, hover the mouse over the righthand border of the Loop Region, again. Next, click+hold and drag.
This is extremely annoying because not only does FMOD not recognise the attempt to adjust the Loop Region border, but sometimes, FMOD interprets the mouse click as an attempt to create a Transition Timeline.
We all know what that feels like – when you’ve accidentally created an unwanted Transition Timeline: “silence”.
So, then you have to execute extras mouse clicks to delete the unwanted timeline and finally, get back to resizing the Loop Region.
This would seem to be an interface issue.
Any suggestions?