Here is a list of LittleOne's known incompatibilities / GUI inaccuracies :

• Due to limitations in the VST3 standard and its missing full support by the major development frameworks, for certain aspects the VST3 plugins are not stable as the VST2 or AU plugins.
  
  

  • VST3 plugin : Clicking on the "Previous" and "Next" preset arrows/buttons (GUI elements) may advance 2 presets at time instead of one. Instead, the presets "Menu" and/or the "Load" button are full working also on VST3 plugins. Otherwise, simply select an "even(or odd) order" preset and then use the "Previous" and/or "Next" arrow/buttons to advance all "even(or odd) order" presets in the list.
    
    

  • VST3 plugin : Some MIDI control assignments (for example the Modulation Wheel) may not be available. Use Host parameter automation instead.
    
    

• In all the Hosts with no support for plugins latency auto-compensation, using very big audio buffer sizes (example : 2048) together with low sampling rates (example : 44100) could lead to timing inaccuracies with MIDI events. To avoid this and have a full and solid MIDI timing accuracy, just be sure - during a real-time performance and/or an offline rendering - to select lower audio buffer sizes and/or higher sampling rates.
  
  

LittleOne - including its embedded Sequencer and Trancegate modules - feature a solid, sample-based timing accuracy with Hosts and DAWs sequencers. By the way many external factors (e.g., audio devices using unconventional buffer sizes, the use of 32-bit to 64-bit bridges and wrappers, etc.) could lead to some timing inaccuracies (it could happen mostly with previous versions of Image-Line FLStudio, since it uses a wrapper for plugins, no other Hosts or DAWs seem to be affected). By the way, this can be easily fixed: the first way to do it is specific to Image-Line FLStudio Host / DAW, the second could be applied to any Host / DAW.


First Way : changing the settings in the FLStudio VSTi-wrapper

In the VSTi-wrapper select :

Adv. Settings [Cogwheel Icon] -> Processing [Tab] -> Opt. -> Use fixed size buffers [Activate]


Second Way : forcing notes to retrig


This scenario produces the retrig issue (bad Host syncing)


Just end a note before the next one starts to avoid the retrig issue