Problems with Transport loop - First note/hit missed... in Mutools MUX and RapidComposer

[tl]

With activated transport loop the first note/hit is missed in plugins which internal sequences rely on Bitwigs timing information.
...
From the RapidComposer bug report thread:

Hello BuckSnot,

Unfortunately I am convinced that the looping bug is in Bitwig, because RC&Melodya works well in other hosts. In the old times I used to insert workarounds for such issues, but not anymore: everybody should fix their own bugs. These workarounds made things complicated, and sometimes introduced new problems. 4-5 years ago I contacted several DAW companies with detailed description of the looping problems, and debug dumps, and most of them were open, and fixed these bugs. The plug-in renders what the host tells it to render. If the first note is outside the audio sample range (when the loop restarts), it won't be rendered. Even an error of a few audio samples can cause this.

I added an option to Melodya to invert the scroll wheel when editing. If this is annoying, I can send you an update.

Thanks,
Attila

Hello Attila,

I updated RapidComposer today & got Melodya. Im using Bitwig 3.2.8. when im using the VST's & I have the transport looping. the 1.1 notes play in RapidComposer & Melodya when first starting the transport but when the transport loops back to 1.1 again the first notes on 1.1 in RapidComposer or Melodya do not play again when the transport loops back to 1.1 in my host.

In melodya can you add the option to invert the scroll wheel when editing. it has always felt backwards to me. Thanks

I have this problem with Mutools MUX (and its Audio Sequences) and with RapidComposer.

Already reported this problem to Bitwig in February but nothing happened...
Maybe others who face this annoying issue could also contact the Bitwig dev team.

Regards,
tl.