WACUP is almost perfect, 2 minor issues

[dro]

I know the reasons why things can appear as locked be it via CreateFile or via the *open equivalents which often can then drill down to using that OS api call.

What I however need is a means to replicate & determine _what_ is actually causing it to happen which I still can't replicate or I'm just missing something. As the input plug-ins & anything looking for metadata from files should only be working on the file & I'm not sure how the folder itself would be locked unless maybe that folder is listed on Preferences -> Media Library -> Folder Monitor?

I'm also assuming that you're still having this problem with the current 1.99.32.21640 preview build?

[nxho]

Thanks for the response dro. I'm using the latest build, and yes, I still have the problem.

You really can't recreate it? This is so weird.

Regarding Media Library

I don't have a Folder Monitor submenu, weird. See attachment below. But I'm sure the folder is not listed in it.

[Aminifu]

Have you tried the Playlist File Remover v3.4.3 (gen_play_remove.dll) plug-in? It has several configuration options for controlling how it functions.

[nxho]

No, never tried it. I can't locate it in the Plug-in menu... Where is it exactly?

found it. Untick only or delete?

[dro]

From the screenshot it seems like you've not installed most of the media library features & have stripped out a load of things which is why you're not seeing the folder monitor & doing so is fine but it means I've not be doing anything comparative with my testing.

The suggestion is the File Remover prefs page but I honestly don't think that's going to help as it'll be affected by the same potential issue if something is holding onto a handle when MP3s are involved & there's nothing in place to cache the metadata from the files causing either my metadata reader or the input plug-ins to be used for every metadata request (am still suspecting in_mp3 is involved though I can't remember if you'd disabled wacup from using it or not).

[nxho]

Aminifu: I unticked gen_play_remove.dll, restarted wacup played fileA in folderA, then doubleclicked fileB in FolderB and deleted folderA, and it worked! I tested 3 times! I can't currently restart my PC but let's see if this state remains after a restart. Looking good so far! Thank you!

dro: you were always directing me towards plug-ins and you may have been right!

[Aminifu]

When gen_play_remove was being loaded (ticked in the listing), was it also enabled (in it's configuration options)? If it wasn't enabled, then I don't understand why not loading it would make a difference. I assume dro would have the answer.

[dro]

I don't see how / why PLFR would ever have been involved (which isn't enabled by default) unless it was being used to try to remove the playlist items (I don't see that having been mentioned previously & was under the impression it was external file removal being done) & then it shouldn't be the cause of such issues since it's actions work only on file path of the playlist item.

So I still don't think whatever is causing issues for nxho is actually resolved & still would view it to be some other plug-in (wacup uses a load of plug-ins so often plug-ins will be the reason behind things when there's an issue).

Tbqh I think it needs to be re-detailed on what exactly is being done. As right now I don't think I've done any testing that matches what's being reported when I was under the impression it related to the last file that was being played not being able to removed & not the one prior to what's now playing as the last post seems to be implying :confused:

[nxho]

Aminifu It wasn't enabled, but wacup required me to restart when unticking it.

dro: Files are not removed through the playlist, but in Windows Explorer.

Play FileA from FolderA.

Play FileB from FolderB.

Try deleting FolderA → Fails until WACUP is closed. (Deletion is attempted while having FileB play, and also while it's stopped. Only closing or restarting wacup helps


Additionally: FileA can be deleted while running FileB. But empty FolderA can't be deleted unless wacup is closed or restarted.
I run wacup barebone. No visualization, timer, media library or anything fancy running.Even the equalizer window is closed

[dro]

Disabling a plug-in will require a process restart as that's the simpler way to ensure it's been removed & the state change is applied vs trying to live unload which complicates what the plug-ins have to do without it generally being worth the potential complications from doing it.

As we're talking about plug-ins, Preferences -> Plug-ins -> Input -> is in_mp3 shown in there & if it is, is it enabled or disabled?

[nxho]

dro: you mentioned in_mp3 couple weeks ago when we first tried troubleshooting. I remember it briefly working but after a restart it stopped working. I re-enabled in_mp3. Yesterday, with the newest version I attempted unticking the in_mp3 trick again, but it resulted in a new bug: Doubleclicking an mp3 in Windows enqueued it, but didn't start playback. I had to doubleclick again in wacup to start playback. So I quickly re-ticked in_mp3

[dro]

Disabling in_mp3 shouldn't be causing playback to require that sort of interaction to get it to then work & as in_mp3 is the plug-in that I strongly suspect is causing you these locking issues to start with we're now back to using something that is known to be buggy & was why I'd said to disable it as then I'm at least potentially comparing with code that I've control over which is not the case with the re-used in_mp3 dll. Then again I don't even know if the fallback in_wave plug-in is now present & enabled in that install if other aspects have been stripped out which wasn't indicated to start with. I'm now done for the day.

[nxho]

dro: Sorry mate I hope I'm not annoying you too much. It was a while back when I first installed wacup, and I may have done a unique install with lots of stuff crossed out, yes... Forgot about this aspect sorry!

in_wave.dll is ticked and enabled

should I reinstall with everything enabled as offered in the installer?
or should I disable "Media Library support"? perhaps?

[Aminifu]

I would try a full removal and reinstall with all the defaults enabled, to see if that makes a difference. dro may have another recommendation later.

You can remove (disable) selected stuff one by one later and test to see if/how each removal changes things. Keep notes, until you learn how WACUP works for you. WACUP can look simple on the surface, but there is a lot to it.

[dro]

Doing the above isn't ideal if the installation is showing a consistent issue but another portable install would be better for comparison testing with the suggestion made. Alternatively I'd need a copy of the install.ini from the program folder to see what is potentially installed in the misbehaving install.