[4.1.0.26] Latest version doesn't expose the title of what's playing anymore?

[RedaLazri 0]

Hello,

 

I'm running Emby server on a Qnap and accessing it via Chrome on macOS, I use it to listen to stuff as well as watching all sort of videos. One thing I have set up is Timing, a time tracker to see how much time I spend watching TV, working...etc. Before 4.1.0.26 Timing was able to catch the name of playing video and turn them to keywords to track them, since the update I only Get Emby 1h 30m which isn't good since I do many things while Emby is open not just watch TV. What's happened?

 

Before

 

 

After

 

Note that I'm NOT running any Beta version, it's from another software and happens to have a close duration.

[Luke 40077]

Hi, I don't quite understand. So this app is called Timing? How does it get this information from Emby?

[Luke 40077]

Is that a MacOS app?

[RedaLazri 0]

hey Luke, It gets information from the browser tab, for instance if I visit www.youtube.com and watch a 5min video called 'cute cats' it catches the domain name and turns 'cute' and 'cats' into keywords that I can then drag into a category named 'videos' or something like that. I know it catches the page <title></title> but I'm not sure if it goes in and catches the <h1></h1> as well since it was working fine with the previous version of Emby even though Emby wasn't displaying the title of the video on the tab AFAIK.

 

https://timingapp.com/

Edited April 26, 2019 by RedaLazri

[RedaLazri 0]

Update: This seems to a per-video problem. It tracked an episode correctly yesterday evening but failed to track a movie at night. As you can see, it was displayed as 'Emby' 

 

 

But it was fine a few hours before:

 

 

So it's either failing to display the title some of the time or it has something to do with the files being played. All the Metadata is correctly present.

[Luke 40077]

Is it just pulling it from the tab title?

[RedaLazri 0]

Is it just pulling it from the tab title?

 

I think so, yes.

[Luke 40077]

Thanks, we'll take a look at that.

[RedaLazri 0]

Thank you.

[Luke 40077]

It's resolved for the next release, thanks.

[RedaLazri 0]

It's resolved for the next release, thanks.

 

If you mean `4.1.1.0` then the bug is sadly still present.

[Luke 40077]

No, that is already released.