It makes sense that the file would be temporarily locked, but the current behavior is that it is permanently locked. This is because the app is adding the file to the cache, so it's ready for playback. If it was suddenly moved, this would cause difficulties, so it's somehow reserving it. > It's currently expected that the file is marked as in use when the app is open and it's set to monitor the Downloads folder. This is great to hear, this is a long-requested feature. > FLAC Local Files support is being added. This seems like a serious privacy concern and the community deserves an explanation. Also, I would appreciate an explanation for why Spotify's Client is doing this obviously inappropriate access to files in the User's Downloads directory. This strongly suggests that the new Spotify Client has been specifically coded to interact with FLAC files in the Downloads directory only.Ġ) Create FLAC file in Downloads directoryĢ) Try to delete that file and explorer says 'The action can't be completed because the file is open in Spotify.' This happens immediately if one creates a new FLAC file, suggesting that the Spotify Client is 'watching' the Downloads directory.Ĥ) Try to delete the file again and it works New FLAC files created outside of the Downloads directory also do not exhibit this behavior. MP3 files, which ARE supported, do not exhibit this behavior.

This seems especially serious because Spotify doesn't support importing FLAC files into your local library so why is it opening them at all? Given that I haven't asked Spotify to monitor my Downloads directory and that the client keeps each of these files open in such a way that I can't delete them or the directories that contain them, this seems like a serious issue. FLAC files in Downloads directory opened, accessed.Įver since the most recent update, the desktop Spotify Client has been accessing FLAC files (.flac) in my Downloads directory.

The payolas flac downloads