Drag&Drop of recorded loops in MSuperLooper does not work in FL Studio

[Blobby19]

Hi,

it seems like the drag & drop of recorded loops in MSuperLooper does not work in FL Studio. It works fine in Reaper, but in FL Studio the cursor just changes to a red icon.

I record a loop in e.g. track 1, and drag the loop to track 2. In Reaper it copies the loop to track 2, in FL Studio it does not work. Dragging the loop to FL Studio itself, e.g. into the channel rack as a sample, works fine as well.

Am I doing something wrong or is this a bug?

Greetings

[martin-meldaproduction]

Drag-and-drop into MSuperLooper does not work in FL Studio because FL Studio does not allow files to be dropped into third-party plugin windows. This limitation is known for a long time and it is specific to FL Studio’s plugin wrapper. While FL Studio’s native plugins support full drag-and-drop, third-party plugins cannot receive dragged files, even though this works normally in other DAWs like Reaper. Anyway, I will check with FL guys if we can do something about it.

As a workaround, you can export a loop (for example, to the desktop) and then load it using the Import Loop button inside MSuperLooper - this button exists specifically for DAWs like FL Studio and other hosts that restrict drag-and-drop into plugins.

[vanerio]

Drag-and-drop into MSuperLooper does not work in FL Studio because FL Studio does not allow files to be dropped into third-party plugin windows. This limitation is known for a long time and it is specific to FL Studio’s plugin wrapper. While FL Studio’s native plugins support full drag-and-drop, third-party plugins cannot receive dragged files, even though this works normally in other DAWs like Reaper. Anyway, I will check with FL guys if we can do something about it.

As a workaround, you can export a loop (for example, to the desktop) and then load it using the Import Loop button inside MSuperLooper - this button exists specifically for DAWs like FL Studio and other hosts that restrict drag-and-drop into plugins.

Mmmm dra&drop works perfectly fine with almost other plugins in FL Studio though.
Only 1% of plugins do not support it.
Last week I thanked Audija developer in this same forum for adding drag&drop support to FL.
I am sure something can be made

[martin-meldaproduction]

We currently use the WM_DROPFILES method for drag-and-drop, which is widely compatible across Windows and most DAWs. In FL Studio on Windows, this is disabled by default in the plugin wrapper. To enable it, open the Plugin Wrapper Settings and turn on “Accept dropped files”.

We are also considering adding support for the modern OLE/IDropTarget method in future updates to provide more flexibility and enhanced drag-and-drop functionality, while keeping full compatibility with the current method.

[vanerio]

Enabling “Accept dropped files” does not solve it.
I hope it is added in a future version. Maybe Image-Line or Audija could help with that.
I really miss it when dragging waveforms to MSF's wavetable.

[martin-meldaproduction]

I did just test and enabling “Accept dropped files” does solve it for MSuperLooper or any standalone MeldaProduction plugin loaded in FL Studio. But, it does not work for plugins loaded inside plugins (nested scenario), i.e. when you load MSuperLooper or WaveTable inside MSoundFactory. As this works OK in all other DAWs as well as on macOS, I assume that this is a bug in FL Studio and already reported this issue to guys in Image LIne.

As a workaround, if you detach nested plugin window from MSoundFactory modular view (by holding shift and clicking on the plugin block in the modular), MSoundFactory creates separate window, which bypasses FL Wrapper and it can then receive drop events from the OS normally without being filtered.

[vanerio]

I did just test and enabling “Accept dropped files” does solve it for MSuperLooper or any standalone MeldaProduction plugin loaded in FL Studio. But, it does not work for plugins loaded inside plugins (nested scenario), i.e. when you load MSuperLooper or WaveTable inside MSoundFactory. As this works OK in all other DAWs as well as on macOS, I assume that this is a bug in FL Studio and already reported this issue to guys in Image LIne.

As a workaround, if you detach nested plugin window from MSoundFactory modular view (by holding shift and clicking on the plugin block in the modular), MSoundFactory creates separate window, which bypasses FL Wrapper and it can then receive drop events from the OS normally without being filtered.

Right! I was testing dropping waveforms to Wavetable. I have been using the detached window trick!! haha but it would be nice not depending on it. Anyway, yeah, FL seems to be tricky with this for some reason, but I think tricking it will be great!
Thank you Martin!
Please let us know their response! Drag&drop is really a big feature!

[Blobby19]

Thank you very much much for your fast and helpful response Martin! The setting worked great. I thought I checked the settings and the documentation already, but somehow I missed this one, even though it is labelled rather obvious.
I didn't even test the nested part yet, nice to know about the detach workaround as well.

And thanks to vanerio for supporting this topic!
Would of course be nice to get a solution by FL Studio, but I am already pretty happy.

Have a nice day!