Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
If the sub-options for local file sources are NOT disabled, the Spotify desktop app will still attempt to access local files present.
To wit, I had some FLACs from Bandcamp in my Downloads folder. "Show Local Files" unchecked. Went to rewrite the tags and move the files with a separate program (Picard Musicbrainz) only for the process to complain that some other process (*cough* Spotify) was hogging those file handles.
Only after briefly ENABLING "Show Local Files" and explicitly DISABLING the sources and once again DISABLING the parent toggle was I able to interact with my files that should be 100% outside the purview of Spotify's processes.
If "Show Local Files" is disabled, the application should assume the sources are also disabled and all relevant logic paths should be accounted for. Otherwise, this is extremely unexpected behavior.
Solved! Go to Solution.
Hi @user-removed,
Thanks for getting in touch about this here in the Community.
Currently, it's 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 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.
That's why the file can be modified when the setting to monitor this folder is turned off. The refresh however occurs after a restart of the app, hence why turning it off while the app is open doesn't free up this reservation.
In this case, if you've already disabled all sources below the Show local files option, the app shouldn't keep accessing the sources.
Hope this helps. If you have any other questions, don't hesitate to let us know.
Hi @user-removed,
Thanks for getting in touch about this here in the Community.
Currently, it's 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 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.
That's why the file can be modified when the setting to monitor this folder is turned off. The refresh however occurs after a restart of the app, hence why turning it off while the app is open doesn't free up this reservation.
In this case, if you've already disabled all sources below the Show local files option, the app shouldn't keep accessing the sources.
Hope this helps. If you have any other questions, don't hesitate to let us know.
Groovy-- yeah that makes sense. Thanks for the clarification.
Hey @user-removed,
You're welcome! If you ever need anything else, we're just a post away.
Have a great day 🙂
Hey there you, Yeah, you! 😁 Welcome - we're glad you joined the Spotify Community! While you here, let's have a fun game and get…