And no.....Not starting a thread here about if it should be legal or not, but about the hash value for meta-data found in the media_parts table
If I got a media named x.mkv, then what's the formula behind generating the hash value?
So far I tried the following:
MD5
SHA1
SHA224
SHA384
SHA256
SHA512
Yet still no luck :(
Any insights here?
Best regards
Tommy
And no.....Not starting a thread here about if it should be legal or not, but about the hash value for meta-data found in the media_parts table
If I got a media named x.mkv, then what's the formula behind generating the hash value?
So far I tried the following:
MD5
SHA1
SHA224
SHA384
SHA256
SHA512
Yet still no luck :(
Any insights here?
Best regards
Tommy
Interesting......
But sadly a no-go
Also tried other versions of sha against the guid string.....
And sadly also a bit un-logical to me, since the index is stored in the meta-data dir, and an index is only valid for a specific version of a movie etc, depending on resolution, encoding etc, or ?
But thanks for the idea......it actually caused the amount of thought to multiply by a 1000 here :D
/Tommy
Interesting......
But sadly a no-go
Also tried other versions of sha against the guid string.....
And sadly also a bit un-logical to me, since the index is stored in the meta-data dir, and an index is only valid for a specific version of a movie etc, depending on resolution, encoding etc, or ?
But thanks for the idea......it actually caused the amount of thought to multiply by a 1000 here :D
/Tommy
The first character of the hash is the folder, the next part is the sub folder. It works for me in the past, maybe it changed. Move info here: http://nikansell.wordpress.com/2012/03/14/fixing-corrupt-plex-thumbnails/
Edit: you are right about the multi version and the index maybe being wrong, but I think that is just how it works. I don't think plex creates separate indexes per media file.
The first character of the hash is the folder, the next part is the sub folder. It works for me in the past, maybe it changed. Move info here: http://nikansell.wordpress.com/2012/03/14/fixing-corrupt-plex-thumbnails/
Edit: you are right about the multi version and the index maybe being wrong, but I think that is just how it works. I don't think plex creates separate indexes per media file.
Holly crap.....the link you just provided reviled info I've used + 3 month to figure out, and posted here:
https://forums.plexapp.com/index.php/topic/86694-sharing-info/?p=501898
Man....I re-invented the wheel.....
Anyway, my first initial tests showed it wasn't so, but I'll dig into this again, since it's highly unlikely for Plex to change this on the way.....
As Arnold said...."I'll be back"
/Tommy
Okay.....Plex did change this.
This is from the GUID field:
http://com.plexapp.agents.imdb://tt0114746?lang=en
SHA1 produce:
9ab6c1ce14829ee5316ee438a554a3dea7eccc8e
The wanted outcome was however:
fc4848b897690a5b1c4c10a3151e245e676badae
So kinda stucked here....again....SIGH.....
/Tommy
Okay.....Plex did change this.
This is from the GUID field:
http://com.plexapp.agents.imdb://tt0114746?lang=en
SHA1 produce:
9ab6c1ce14829ee5316ee438■■■4a3dea7eccc8e
The wanted outcome was however:
fc4848b897690a5b1c4c10a3151e245e676badae
So kinda stucked here....again....SIGH.....
/Tommy
Yea, I don't recall a hash being available in the DB before, so maybe that's why it's included now in the parts table. Either way would have to access the DB, so I'm guessing it wouldn't of helped right?
Nope...It would have been a great help, since the guid can be accessed via http, thus avoiding access to the database.
Still hoping, that some dev want's to protect everybody's database from my lousy code though, and share some light here :D
Or expose the other field to the http api
/T
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
