<html><head></head><body><div>On Sat, 2022-08-20 at 15:25 +0200, Tomy Elrond via gstreamer-devel wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>These "hashes" must be related with input names, because for each input name it generates the same hash every time. For example:</div><div>"</div><div>input name: "file:///tmp/input_video_1.mp4" -> generated hash: "0b70cf574e1fef0b694a8a449a94732091cda1ce67bc4bf7c71c59d6c331f5b1/001"<br>input name: "file:///tmp/input_video_2.mp4" -> generated hash: "7960608e8835f3eeaf8fba46351367dd76199a9e133117d4aeeccb862e8da9aa/001"<br></div><div>"</div><div>Is there any way how to "decode" these hashes to the original string (path of video file?</div></div></blockquote><div><br></div><div>It's the SHA256 of the URI, currently. You can't decode that and you must not rely on that staying the same forever.</div><div><br></div><div>The stream IDs are opaque IDs that only allow you to distinguish different streams / find same streams.</div><div><br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div dir="ltr"><div>Or is there some other way to find out stream ids (for example first input -> 0, second input -> 1)?</div></div></blockquote><div><br></div><div>Via the STREAM_START event.</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"></blockquote><div><br></div><div><span><pre>-- <br></pre><div data-evo-paragraph="" class="" style="width: 71ch;" data-evo-signature-plain-text-mode="">Sebastian Dröge, Centricular Ltd · <a href="http://www.centricular.com">https://www.centricular.com</a></div><div data-evo-paragraph="" class="" style="width: 71ch;"><br></div></span></div></body></html>