{"action":"opened","issue":{"url":"https://api.github.com/repos/ohsewon/test/issues/98","repository_url":"https://api.github.com/repos/ohsewon/test","labels_url":"https://api.github.com/repos/ohsewon/test/issues/98/labels{/name}","comments_url":"https://api.github.com/repos/ohsewon/test/issues/98/comments","events_url":"https://api.github.com/repos/ohsewon/test/issues/98/events","html_url":"https://github.com/ohsewon/test/issues/98","id":352060094,"node_id":"MDU6SXNzdWUzNTIwNjAwOTQ=","number":98,"title":"Research Topic: queue overfill handling","user":{"login":"ohsewon","id":12094135,"node_id":"MDQ6VXNlcjEyMDk0MTM1","avatar_url":"https://avatars1.githubusercontent.com/u/12094135?v=4","gravatar_id":"","url":"https://api.github.com/users/ohsewon","html_url":"https://github.com/ohsewon","followers_url":"https://api.github.com/users/ohsewon/followers","following_url":"https://api.github.com/users/ohsewon/following{/other_user}","gists_url":"https://api.github.com/users/ohsewon/gists{/gist_id}","starred_url":"https://api.github.com/users/ohsewon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ohsewon/subscriptions","organizations_url":"https://api.github.com/users/ohsewon/orgs","repos_url":"https://api.github.com/users/ohsewon/repos","events_url":"https://api.github.com/users/ohsewon/events{/privacy}","received_events_url":"https://api.github.com/users/ohsewon/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-08-20T09:46:28Z","updated_at":"2018-08-20T09:46:28Z","closed_at":null,"author_association":"OWNER","body":"We \"know\" that gstreamer supports different modes for synchronization and queue handling.\r\n\r\nHowever, soon, we will need deep understandings in this area.\r\n\r\nSome people (at least two! :)  ) should be familiar enough with this topic so that he can let us know how to:\r\n1. construct stream pipeline with queues or inter-element connections dropping frames whenever \"next\" frame comes while the \"previous\" frame is still being processed.\r\n2. at tensor_mux or tensor_merge, use the most recent tensor frame for each sink-pad, dropping any \"obsolete\" frame and keeping \"recent\" frame EVEN if it is already processed and sent away to next element.\r\n"}}
{"actor":{"display_login":"ohsewon"}}