Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - ioomusicbee

Pages: 1
Scanning the entire library again is not an option
Why not?

I can't scan the entire library now due to bandwidth constraints as the files are not local.

Or is there a way I can possible toggle this warning off?
No such option exists.
I coudn't find any toggle either. This is why I am asking about the specifics of how MusicBee is determining how a file was updated outside. Do you know if it is looking at mod time + file size or is there a checksum involved? File size and checksum wouldn't have changed. The mod time is the same also however different filesystems have different resolutions for storing timestamp values. If I know how musicbee is making this determination I can try to adjust my mount settings so I don't trip the warning. I searched this forum various search engines but didn't find too much helpful information about this issue. Perhaps @Steven could add some insight.

I moved my library to a remote location. Everything is working fine in terms of playing and accessing the files except when I try to edit a file I get the message:

The File(s) being edited have been updated outside of MusicBee...

How does Musicbee determine that a file has been updated outside of Musicbee? Does it compare the size + mod date? Although the mod date has not changed, my guess is that the resolution of the mod date on the new remote filesystem is different enough to trip this warning.

Scanning the entire library again is not an option and I know none of the files have actually been updated. If I know what criteria Musicbee is using to determine that a file has been updated I could possibly adjust my mount parameters so as not to trip this warning. Or is there a way I can possible toggle this warning off?

Plugins / Re: MusicBee Remote (Remote Control for Android)
« on: December 24, 2021, 11:15:37 PM »
Hi Kelos,

Thanks for the amazing plugin. I am having an issue with the Playlists. When I click Playlist in the app I get a blank screen with a spinning ball. I have left it spin for up to an hour but it never actually loads any playlists.

From what I can tell everything else appears to be working perfectly. I can play tracks, access the library nodes, Radio, Lyrics etc. Unfortunately I work exclusively with playlists and have invested many hours into developing them so for the plugin to be useful I really need the playlists to work.

I have "traffic meters" on the phone and the computer and I did not see any network traffic when the app is spinning so I don't think it is actually doing anything.

Any ideas on what I can do to troubleshoot or is this a known issue? This would be an amazing new way to use MusicBee so I would really love to get this working.

Here is my system info:

MusicBee Remote app: Version 1.5.1 downloaded from f-droid
Phone: Redmi Note 10 Pro, LineageOS (Android 11)
Musicbee: 3.3.7141 P
MusicBee Remote plugin: Version 1.4.1 from Github.

Plugins / Re: (Version 2.0.2) Spotify Integration Plugin
« on: November 27, 2019, 05:17:02 AM »

I am trying to get the plugin working. I have MusicBee 3.3.7141 P and Spotify Integration Plugin 2.0.2. I was able to copy the files to my plugins folder. When I go to Edit Preferences-Plugins-mb_Spotify_plugins there is a configure button however when I press it nothing happens.

I added the Spotify panel to a new Music bee view. It says "No Track Found" when I click on this I get "Bad ID"

If I click on The title header and select "Re-authenticate" I am taken to a Spotify webpage, I enter my credentials then I am taken to a a page:


on this page I see the following:

Json tab: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data
Raw Data tab: OK - This window can be closed now

Cache-Control no-store, no-cache, must-revalidate
Content-Encoding gzip
Content-Length 54
Content-Type application/json; charset=utf-8
Date Wed, 27 Nov 2019 05:13:03 GMT
Expires Mon, 26 Jul 1997 05:00:00 GMT
Keep-Alive timeout=15,max=99
Last-Modified Wed, 27 Nov 2019 05:13:03 GMT
Pragma no-cache
Server embedio/2.0
Accept text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Encoding gzip, deflate
Accept-Language en-US,en;q=0.5
Connection keep-alive
Host localhost:4002
Referer http://localhost:4002/
Upgrade-Insecure-Requests 1
User-Agent Mozilla/5.0 (Windows NT 10.0; rv:68.0) Gecko/20100101 Firefox/68.0

This is as far as I can get, if I go back to Spotify it still says "No Track found" so it doesn't look like it passes the credential back to MusicBee. What am I doing wrong? Any ideas?


Pages: 1