[DJ_Izumi]

It's great for quickly telling if I'm watching h.264 or h.264 10bit, since Kodi only shows them as h,264 by icon. Just one of the useful cases.

I'm also often roughly curious to see what average bitrates I'm chewing on at the time.

[whysoserious]

+1

[J876]

It's great for quickly telling if I'm watching h.264 or h.264 10bit, since Kodi only shows them as h,264 by icon. Just one of the useful cases.

I'm also often roughly curious to see what average bitrates I'm chewing on at the time.

Agreed

[FernetMenta]

You have to distinguish between real-time values that change like drop/skip and static info like codec name. The old debug screen had major flaws i.e. bringing up the screen made many systems get late and drip/skip as a result.
If you want to get info like codec name, you can use JSON-RPC. Another option could be to add a dialog to skins that displays the static information.[/code]

[peppe_sr]

So we will have tools to handle information like the one we have now with "o".
This is good.

[ashlar]

I asked as soon as I saw the discussion on this being removed. I still haven't installed Krypton but from the screenshots provided I really hope relevant information is brought back. If not "always", have it available with a setting, like debugging can be activated from settings. When setting up a new machine, it's crucial to be able to evaluate performance in realtime, with regard to dropped/repeated frames and so on and so forth.
Kodi is already unclear enough in its video/audio handling part, I was hoping it could get better... but I see the opposite happening here.

[FernetMenta]

I asked as soon as I saw the discussion on this being removed. I still haven't installed Krypton but from the screenshots provided I really hope relevant information is brought back. If not "always", have it available with a setting, like debugging can be activated from settings. When setting up a new machine, it's crucial to be able to evaluate performance in realtime, with regard to dropped/repeated frames and so on and so forth.
Kodi is already unclear enough in its video/audio handling part, I was hoping it could get better... but I see the opposite happening here.

I am the main developer of video and audio and need this information displayed in this dialog most of all. Please stop complaining about removed crap that was implemented incorrectly. There was a reason why I did this change. I have given alternatives how to get the information. Feel free to list your contribution to audio/video and how the old crappy overlay did help you doing this.

[DJ_Izumi]

Oh, another thing, frame rate, this function has been super good at seeing which framerate your content is at if it's relevant. My library has a mix of content at 24, 25, 30 and 48fps, it can be useful to quickly tell what the framerate of the file being played is.

[jjd-uk]

you can use JSON-RPC

That's no good for a user who wants to troubleshoot, you might as well say learn Chinese. It's not only devs with the technical know how to use JSON-RPC that this stuff is useful to.

[ashlar]

I am the main developer of video and audio and need this information displayed in this dialog most of all. Please stop complaining about removed crap that was implemented incorrectly. There was a reason why I did this change. I have given alternatives how to get the information. Feel free to list your contribution to audio/video and how the old crappy overlay did help you doing this.

FernetMenta, I am not a programmer. I'm a user discussing in a user section. As such, I resent your implication that "I'm not doing anything for the project". I am doing, politely, what a user is expected to do. Tone down the attitude, it's useless.

[FernetMenta]

you can use JSON-RPC

That's no good for a user who wants to troubleshoot, you might as well say learn Chinese. It's not only devs with the technical know how to use JSON-RPC that this stuff is useful to.

Place this URL as a bookmark into you browser (change host/port appropriately). That's no rocket science.

Code:

localhost:8080/jsonrpc?request={"jsonrpc": "2.0", "method": "Player.GetProperties","params":{"playerid":1,"properties":["currentvideostream"]}, "id": 1}

[DJ_Izumi]

Place this URL as a bookmark into you browser (change host/port appropriately). That's no rocket science.

Code:

localhost:8080/jsonrpc?request={"jsonrpc": "2.0", "method": "Player.GetProperties","params":{"playerid":1,"properties":["currentvideostream"]}, "id": 1}

From a usability perspective, this is vastly inferior to 'Push button on keyboard/remote'.

[thorazine74]

I don't know of many (if any) video player that do not give some sort of real time playback stats.
Removing some basic functionality just because it's not perfectly implemented without having a better implementation to replace it doesn't make any sense for any reasonable user.

[FernetMenta]

I don't know of many (if any) video player that do not give some sort of real time playback stats.
Removing some basic functionality just because it's not perfectly implemented without having a better implementation to replace it doesn't make any sense for any reasonable user.

I am sorry but I am tired of reading such nonsense. Do you really think that I removed this for the sake of removing functionality? I am transforming video player which is a lot of work and I am by far the top contributor in this area. My list of todos is quite long and there are many many things that are much more important than this silly codec stats 99% of users can't interpret correctly anyway.

[newphreak]

Dear FernetMenta.

First off, don't be such a dick in the forum, just because you have done allot of great work and fixed and improved a shitload of things over the years. We are grateful for that, but that does not allow you to be a dick about it to the end users. Not a single person in here will be using kodi the same way you do, and most don't have a second computer in arms reach to use json. And you even say 99% can't interpret it correctly anyways, so what on earth do you think users will do when they're faced with:

Code:

{"id":1,"jsonrpc":"2.0","result":{"currentaudiostream":{"bitrate":638386,"channels":2,"codec":"dca","index":0,"language":"eng","name":"DTS Stereo"},"currentvideostream":{"codec":"h264","height":824,"index":0,"language":"eng","name":"","width":1920}}}

Granted, the code might have been bad and needed fixing, but just removing it and calling users stupid is not a fix. You could say it's due to be fixed, but has low priority right now. Those stats are basic and needed quite often for quite a lot of users to determine how to proceed with debunking their issues. As the code is now, a lot less can be done by the user, making the need for a developer to look at log higher. Resulting in less time to fix issues. That could be seen as shooting yourself in the foot somewhat. If you need somewhere to release some anger, I can suit up in a sumo-wrestler blow-up suit and we can fight.