Author Topic: Play Count not updated if file played is not from current library  (Read 4407 times)

Novatlan

  • Jr. Member
  • **
  • Posts: 34
I can reproduce this every time:
If an album is played from library A and the user is currently inside another library B, once any file played in library A ends, its play count is not updated. The next file in the queue is played, but the play count does not update.

This using MB 2.5.5690 on Windows 10 Pro 1511.

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34416
yes i am aware this is the case. I have no plans to address this scenario because it involves updating a different database to the one currently in use.

Novatlan

  • Jr. Member
  • **
  • Posts: 34
Oh, ok...

Is there no way to fix this?
I need to have multiple databases for multiple projects and my whole work day consists of listening to tracks from one library while editing another.
If that does not work, that essentially cuts my productivity in half :(

phred

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 9441
Have you tried version 3?
The current patch is for MusicBee 3.0, which does NOT overwrite MusicBee 2.5.
Unzip into the MusicBee application folder and run MusicBee3.exe. Your existing
v2.5 settings and application will remain unchanged. Note that web browser
functionality now requires the Web Browser Plugin. Please report v3 bugs here:
http://getmusicbee.com/forum/index.php?topic=15050.0
Download the latest MusicBee v3.5 or 3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Posting screenshots is here
Searching the forum with Google is  here

Novatlan

  • Jr. Member
  • **
  • Posts: 34
The behaviour is the same in V3 if I recall correctly.
I am very hesistant to use Alpha software, though...

phred

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 9441
I am very hesistant to use Alpha software, though...
I can understand that. 

I will say the the current v3 is quite stable performance-wise.  Almost all of the changes are to the GUI.  -And- (!!) you can run v3 without it changing anything in v2.  It creates its own settings file and as long as you don't open them at the same time, you should be fine. 

Lastly, if you don't like to use alpha software, v3 beta version will be release very soon.

I've been using v3 exclusively for weeks now without any issues (other than graphical.)
Download the latest MusicBee v3.5 or 3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Posting screenshots is here
Searching the forum with Google is  here

Novatlan

  • Jr. Member
  • **
  • Posts: 34
So is this issue not present in V3?
I tried V3 a while ago and it also happened there.

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34416
no change has been made in v3 around this issue. As I mentioned, i am not planning to address this as the change is too substantial

Novatlan

  • Jr. Member
  • **
  • Posts: 34
Ok, thanks. So why is it then suggested that I try V3 if it does not help with the issue?
Just trying to understand if I should take the risk...
With the exception of this issue I am pretty happy with MB, so unless V3 brings something ttuly awesome to the table I'll probably wait until at least 3.1.
Last Edit: January 12, 2016, 06:15:15 PM by Novatlan

phred

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 9441
Ok, thanks. So why is it then suggested that I try V3 if it does not help with the issue?
Just trying to understand if I should take the risk...
I suggested that you try v3 to see if the issue had been addressed.  You hadn't stated that the behavior was still the same.
Download the latest MusicBee v3.5 or 3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Posting screenshots is here
Searching the forum with Google is  here