Drag & drop to media player no longer working since v3.31a in Windows 7

I am running Windows 7 x64 and have never had an issue dragging and dropping audio files from the mp3tag filelist into the media player of my choice until I updated from v3.31a. All subsequent mp3tag releases including the latest v3.34 behave in the same way with the arrow indicating the drag operation is fine but on dropping the file/s they do not appear in the media player. I reinstate v3.31a and the operation works fine. I have tested with mp3, flac and wav files... have tried single files and numerous files at the same time with the same result. I have tried with Winamp, Wacup, MusicBee, VLC without success yet all work fine with v3.31a. Have tried running mp3tag as an admin, have tried uninstalling the x64 version of mp3tag and running the x86 version but the issue persists.

Any advice would be greatly appreciated.

oh, oh ...
Have you tried to press Ctrl while d&d?

There have been several changes to drag & drop since v3.32 according to the changelog:

including this one:

Yes i have tried holding ctrl while dragging and dropping but makes no difference

Yes i am aware of the new MOVE/COPY protocol but it is not relevant to the issue i am having whilst dragging & dropping files to a media player. It is not a MOVE/COPY operation.

Perhaps this sheds some more light on it:

Thanks for the D&D breakdown. In light of that I presume "4 DROPEFFECT_LINK dropping creates a link" is what takes place when D&D'ing from Mp3tag to a media player and it is that function that no longer works for me since v3.31a. I have made no other system changes apart from the Mp3Tag update so I assume some change in Mp3tag since v3.31a means it no longer receives the same feedback from the receiving program/s. It's a function I use all the time so unless there's a fix I will reluctantly stick with the version that works. Those new icons and scaling options will have to wait :slightly_smiling_face:

I just used MP3tag on W11 with the now "Windows Media Player Legacy" and d&d an mp4 file from MP3tag into the playlist section of the media player and it worked ..
It is important that both applications have the same privileges. Applications running in an elevated state do not accept d&d from lower-level apps.

Thanks for your reply. I have no applications running in an elevated state. Am running Windows 7 SP1 so performing a similar function in W11 is maybe here nor there

I just started one of my most ancient PCs which still has a W7 installation and installed 3.34 in 32-bit.
And I can drag&drop from MP3tag to the WIndows Media Player just like in the old days.
So it does not seem to be a general phenomenon that d&d does not work.

I tried the 32-bit version to see if the results would be different to the 64-bit version but results were the same. I don't have Windows Media Player but I have tested Winamp, Wacup, MusicBee and VLC and none are accepting dropped files from Mp3tag unless i stick with v3.31a

I can duplicate your results on Windows 7. It looks like this is one of the many areas where software no longer fully supports Windows 7. This is inevitable and we users need to accept this reality and to work around it as best we can.

Meanwhile, the right-click Play option still works with the system default player in Windows 7. And you can create Mp3tag Tools to load other players, as discussed here. No drag and drop will be needed. And you will be able to upgrade to the current version of Mp3tag.

I checked d&d with VLC and can confirm observation. I also tried Foobar2000 and that (also) does not accept d&d into a playlist in W7 with MP3tag 3.34.
(I took "media player" as synonym for the "Windows Media Player". But, of course, there are others around.)

Thanks for your response. Yes i was aware that the right-click Play option still works with the system default player but more often than not I want to enqueue files from Mp3tag in amongst tracks already in the media player playlist and I believe this can only be achieved via drag & drop. For that reason alone I will be sticking with v3.31a unless there's a fix in the future.

Thanks for confirming the issue