[ilikenwf]

I'm not sure that it was fixed. Honestly, we could put a lot of time into fixing this, or we could devote that time into basically rewriting most of the back end and front end code, to support the new xulrunner and sqlite.

By doing those, the next version should have it fixed...but I don't personally have the resources to find the cause of this issue myself. One of the other devs may be able to, though.

[tibitts]

(04-18-2013, 04:35 AM)ilikenwf Wrote: I'm not sure that it was fixed.

It wasn't. While I appreciate the efforts to implement a new back end and all the improvements in 1.12, there are some basic things I think users can simply expect to work. Correct play count is one of them. And I don''t think I'm the only one with that opinion. So I'll wait for the next version.

[sparhawk]

I just wanted to mention that I see the same bugs, with all add-ons disabled. Unfortunately, it's a big enough deal-breaker for me to revert back to an older version.

[rsjtdrjgfuzkfg]

We did have a look at the issue, but - at least for me - the bug is not reproduceable in my debug environment; also in the regular environment it mostly works for me, only one time it did not work as described here.

I read through some of the code that updates the play count, but weren't able to find any bugs; as I said everything worked. If somebody has a working STR on windows, I might look at it again; however updating the back end in fact is way more efficient in terms of making NG stable and bug-free. While that takes a while, it will prepare a really awesome release - and we don't have that much ressources in terms of developers so it wouldn't be good for the development if we invest weeks of testing into code we'll rewrite in some months anyways.

I understand that you might disagree with that, but that's how it is. If anyone of you is able to debug and find the issue, or at least is able to track it down to a component, let us know and we can try to fix it or merge your pull request. I tried it for some hours and did not succeed in reproducing the bug, maybe anyone of you can?

[tibitts]

I do understand your point of view, and I'm not blaming you.

With v1.12 I have checked again the Error Console. As opposed to the last time I looked, I do see the following now. Also, this is with the Windows version now (not Linux as last time):

Error: SQLite compile step:
select entry_id, library_guid, media_item_guid, play_time, play_duration from playback_history_entries order by play_time desc
caused the error
no such table: playback_history_entries

Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [sbIPlaybackHistoryService.entries]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: file:///D:/Users/christ1/AppData/Roaming/Nightingale/Profiles/f2lcnuf6.default/extensions/audioscrobbler@songbirdnest.com/components/sbLastFm.js :: sbLastFm_scrobble :: line 1554" data: no]
Source File: file:///D:/Users/christ1/AppData/Roaming/Nightingale/Profiles/f2lcnuf6.default/extensions/audioscrobbler@songbirdnest.com/components/sbLastFm.js
Line: 1554

Error: currItem is null
Source File: file:///C:/Program%20Files/Nightingale/components/sbPublicPlaylistCommands.js
Line: 1703

This is 100% reproducible here.

[ilikenwf]

Whoa...that table should exist...what the heck?

[freaktechnik]

Or to formulate out what ilikenwf said: can you reproduce this in a completely new profile?

[tibitts]

Yes, happens with a new profile too. I did install the extensions suggested by the wizard.

[ilikenwf]

That gives us something to work with

[sparhawk]

Thanks devs. I certainly hope that my comments weren't taken as criticism. I agree with whatever you think is the best solution in the long term. I agree that fixing this (for me, major) bug should take second priority if it will be fixed by doing other coding that will have a better effect in the long term.

I posted above because I just wanted to say that it's an extremely critical bug for me (and other OCD users ), and I feel that it's important to fix at some point, whether that be immediately or in the future. Thanks again for the stellar work!