Get Back the "original aspect ration" metadata

[skewed_stony 3]

Hi anyone,

this is my last try to get back the very usefull metadata "original aspect ration" in emby server software.

Till to the beta version of emby server 4.1.0.8 there was it possible to enter on each movie title a manual "original aspect ration" in the metadata editor.
After that version the field was deleted without any announcement. 

I am convinced that this data will not get in conflict with any other features of the software. Emby will safe that information at the nfo-data and kodi has the possibility to work with it.
Any Skin on Kodi supports that in the nfo, so if you got a movie with 16:9 aspect and black stripes you can switch it to the real format with that entry.

If you have an aspect working movie screen which supports different aspects, you can turn that screen into the right aspect ration with that option.

In my homecinema it works perfectly till the version 4.1.0.8. After that it wont and I have to switch the screen manually.

So pls vote this post and stand with me for getting this little spot back!

THX 4 your SUPPORT 

[skewed_stony 3]

Hi, 

I am using Kodi with the Skin AEON-NOX SILVO and there are a lot of Media Flags and Infos that will shown up for the video.
Sometimes Kodi will not show correctly the "Aspect Ratio" Flag of the Streaming Details.

I searched the WIKI and find out that Kodi uses "ListItem.Aspect" to show the right Aspect Flag. The Aspect Flags could be customized and stored into the media folder of Kodi.
So I will be very happy If it is possible to edit those items in emby to get it into the NFO of the movie.

I am looking forward to your Feedback

Regards

Timo

 

[ebr 16183]

Same?

 

[skewed_stony 3]

Hi ebr,

It could be. There was even no feedback on my request.
I thought it must be another explanation of it to this feature again. 
 

Perhaps it could be possible that there is another way to promote a userfriendly option to get the aspect ratio flags in kodi

Kind Regard

STONY 

[Luke 42078]

Hi, every database column comes with a cost, and that's why I would like to see more community support before doing this. Otherwise we're making every emby user pay that cost when they have no need for it.

[skewed_stony 3]

Hi Luke, i Unserstand that absolute for Features that will be new and must be integrated. But this feature was already included and was deleted by the Developer depending on "useless" Data in the NFO.

I paid my Part with the emby Premier membership and only Wish that the Feature will be integrated again Like before.

 

[Luke 42078]

Hi, yes you're right, but in this case I don't mean financial cost, I mean the cost of space and performance related to adding more columns.

[skewed_stony 3]

Okay Luke. Try me to understand. What impact of permance does this deleted feature will bring to emby?

The Version I will use is on a very high performance. My Database content is about 8TB and about 3000 items (movies and Series).
I setup with this version an newer NAS System and the scan on the libary performs like a tornado dependig on that amount of data.

I think the performance will only even get better with some changes of the code and structure of the libary database.
FYI I programmed databases for over 3 Years in the industrie like SQL.

[ebr 16183]

1 hour ago, skewed_stony said:

What impact of permance does this deleted feature will bring to emby?

Hi.  It isn't necessarily just this single thing but there are literally 100s of similar things that some subset of users may want and, collectively, maintaining all of those has an impact all the way from database size to query performance to payload size and network bandwidth.

[Luke 42078]

6 hours ago, skewed_stony said:

Okay Luke. Try me to understand. What impact of permance does this deleted feature will bring to emby?

The Version I will use is on a very high performance. My Database content is about 8TB and about 3000 items (movies and Series).
I setup with this version an newer NAS System and the scan on the libary performs like a tornado dependig on that amount of data.

I think the performance will only even get better with some changes of the code and structure of the libary database.
FYI I programmed databases for over 3 Years in the industrie like SQL.

It's an extra column in the database. Queries have to be adjusted to pull back an extra field, save operations have to save an extra value. Now of course you can argue this is a small cost but when you start adding a lot of random ones, things can get unwieldy. That is why I like to keep things lean. If it has value to the broad, general Emby audience, then of course we'll add it.

[skewed_stony 3]

Is it not easy to get the old code of it and implement it to the newer version? Remember the fact that this was an included feature / field / data.

I think you shouldnt make an elephant out of a mosquito, in fact of that was a feature you have deleted without any remark in the change logs.

Emby was the only Database that supported this feature in the past. It was for me THE DATABASE for my content including speed, functionality and features in context with kodi.
What I dont even understand is, that you are so defend against this small thing, depending on speed, content and programming?

Is there not another way to get a similar feature back? I hope we'll find a diplomatic way...

[Luke 42078]

Again it's not a question of level of effort. That's not hard. It's more an issue of keeping the database lean. That's why I want to see community support first before just adding it back.

[skewed_stony 3]

Okay, so ist IS Up to you Community.

Hope you See this an Support my little Feature Request?

Hope to get all the Request I needed for that. Give me a Like, If you agree with me to get the Feature Back.

Thx, Cheers and stay healthy 

Stony