I confirmed this observation with Emby staff. When playing music from within the Emby app or web browser, a song is counted played once for each play.
The same is true when Symfonium counts a song played. The app properly keeps accurate counts.
However, when syncing with Emby, Symfonium’s api or method of syncing, sends to the Emby server a double count for each song played once. This has been repeatedly verified as testing as been done extensively.
The music counts in Emby server are available to see under the song, table view. This is consistent with Android phone or Android tablet.
Device type
Phone
Media provider
Emby
Steps to reproduce
Provided above is the exact process to replicate.
Additional information
This is for your benefit and knowledge. I do not believe a log would provide any additional information as it is device independent. You may close this as you wish, but I wanted to present it to you for your knowledge.
I searched existing issues first
on
I understand that logs are mandatory
on
Log upload name / description
See my comments above. Sometimes logs will not provide the answer. This is one of them since it is device independent.
I mean there’s a check box that says I understand that logs are mandatory. You check that box, but write fuck the logs I know better they are not needed.
WTF do you expect ?
If you don’t respect me or my time then I won’t respect you, every single time it’s the same behavior, I do not respect rules, rules does not apply to me, hey the dev is bad he remind me that I do not respect the rules.
So yes I’m sorry but logs would show exactly what happens so I could answer … Seriously amazing.
And of course never ever acknowledge doing wrong, just double down
I wrote the Team at Emby sometime ago about this issue of the double counts. Gave them about as much detail as this post. They were very interested in the issue and were able to pin-point the problem being on this end. IE. they tried to replicate the issue, but when they used the web browser or their app, the double counts did not happen. Other end users joined the post and they as well were able to verify the same results. The double counts were unique to Symfonium.
So, I then in-turn tried just using their apps or the browser and indeed they were correct. I went back and used Symfonium and the double counts were immediate. They never complained that the problem was not theirs to handle. They have a great, positive customer support.
I wrote the developer an email from within the app and he asked I post the issue. I was hesitant because I have seen some of his prior comments to end users. But I decided a few weeks later to at least give him the knowledge based on what the folks at Emby shared that there was an issue. Mind you, probably not too many people look at the Emby play count when Symfonium provides it as well. So, this is probably a hidden issue most end users do not recognize.
I started the post with the fact this is happening on a cell phone AND tablet. Two different devices. As I kept putting in the information, I came at the end about the logs. (I suggest that field be placed at the top of rather than the bottom of the form). Since in my mind we are talking about two different devices, it did not seem logical to post two sets of logs. The issue seems to be independent of the devices. I also figured if the developer has access to Emby, this would not be difficult to confirm.
In the end I was not really expecting anything, but what I received. But I did feel it worth letting him know. I would have left it as I did in the email. But I didn’t know until near the end of the post I had to upload logs and didn’t make sense since its across the board on my devices. (At least in my mind’s eye at the time of the post). As far as putting in NO for the logs; YES would have been inappropriate and not forthright if I actually had not done it.
And take 1000 more times to write a novel than actually provide the logs and the details.
But hey it’s important to justify that acting wrong is actually not acting wrong
To resume you have fully debugged with Emby but will not give any details about the findings or the logs because it’s not fun, just say that it’s Symfonium’s fault and let the dev do all the debugging again trying to eventually reproduce your issue for the fun, when you could provide the logs that would show everything in 10 seconds ?
One day people will show respect for other’s people time, maybe …
I was trying to answer TheKingPin’s question. Respectfully, I didn’t feel the need to pursue the solution with the application. I respect your skill-set and time. I erred in thinking you would find such feedback helpful despite its incompleteness. Sorry to waste your time. Maybe others will find this post helpful in some other way.
The idea behind support is to get to the bottom of an issue. I think that’s your goal here also. I’ve been long enough in this forum to recognize that the dev works very efficiently, and, to be honest all the tools have been provided, with extra hints, on how to report an issue.
I don’t know the dev personally, but, I definitely sympatize with them, when I see daily posts asking for help but the person making the support request cannot even provided the bare minimum. Logs! Which is even stated as mandatory. Let’s be frank. We are asking for help and why would we feel entitled to change the devs workflow? Dont forget, we ain’t paying for the support in the end either, and, nevertheless get virtually 24/7 support. I cannot think of any other app where that’s the case.
Maybe the issue is deep in the app, maybe not. A short log would have spared all this time going back and forth, and, most probably the dev would have fixed it by now, judging by passed issues which are normally fixed within 24hrs.
I appreciate your positive method of your expressing your opinion. As in this post and in the post the developer linked to on Emby’s site (which he made clear several times on their site, I should have provided logs), “I respect your skill-set and time. I erred in thinking you would find such feedback helpful despite its incompleteness” and on Emby’s website, “I should have supplied you your requested logs. I erred in not doing so. My apologies.”
-I stand by that now. Probably just will not post again to tell you the truth. The juice isn’t worth the squeeze.
I do think putting the log question at the top of the page may help reduce some of the submissions that do not contain logs. At least, apparently, I did discover an legitimate issue.
I had to search for that Emby post …
Post where Emby team did absolutely nothing …
Post where other people shown that it was a bug in Emby betas
But hey yeah you found a bug on Symfonium that actually is a bug in Emby that they could have fixed if you had reported to them correctly as the link on how to report issue for Emby that was given to you that strangely also says provide the … Logs So yes you should have provided Emby logs to emby devs… You really have a strange reading of the situation.
TL;DR; you failed twice but will keep blaming the only one actually trying to still get them fix this …
