{"action":"created","issue":{"url":"https://api.github.com/repos/raspberrypi/firmware/issues/377","labels_url":"https://api.github.com/repos/raspberrypi/firmware/issues/377/labels{/name}","comments_url":"https://api.github.com/repos/raspberrypi/firmware/issues/377/comments","events_url":"https://api.github.com/repos/raspberrypi/firmware/issues/377/events","html_url":"https://github.com/raspberrypi/firmware/issues/377","id":58966774,"number":377,"title":"mmal: Get component port state debug information","user":{"login":"julianscheel","id":985759,"avatar_url":"https://avatars.githubusercontent.com/u/985759?v=3","gravatar_id":"","url":"https://api.github.com/users/julianscheel","html_url":"https://github.com/julianscheel","followers_url":"https://api.github.com/users/julianscheel/followers","following_url":"https://api.github.com/users/julianscheel/following{/other_user}","gists_url":"https://api.github.com/users/julianscheel/gists{/gist_id}","starred_url":"https://api.github.com/users/julianscheel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/julianscheel/subscriptions","organizations_url":"https://api.github.com/users/julianscheel/orgs","repos_url":"https://api.github.com/users/julianscheel/repos","events_url":"https://api.github.com/users/julianscheel/events{/privacy}","received_events_url":"https://api.github.com/users/julianscheel/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":158,"created_at":"2015-02-25T20:47:46Z","updated_at":"2015-03-27T07:42:45Z","closed_at":null,"body":"Is there a similiar mechanism for mmal to OMX_GetDebugInformation for openmax which enables us to see the state of the active mmal components and their ports?\r\nI am looking for an issue where mmal_port_flush() does not seem to work properly on image_fx component - my internal refcounting says that still one buffer is in use by the input port. It would be quite helpful to have a chance to see the internal port state."},"comment":{"url":"https://api.github.com/repos/raspberrypi/firmware/issues/comments/86857852","html_url":"https://github.com/raspberrypi/firmware/issues/377#issuecomment-86857852","issue_url":"https://api.github.com/repos/raspberrypi/firmware/issues/377","id":86857852,"user":{"login":"julianscheel","id":985759,"avatar_url":"https://avatars.githubusercontent.com/u/985759?v=3","gravatar_id":"","url":"https://api.github.com/users/julianscheel","html_url":"https://github.com/julianscheel","followers_url":"https://api.github.com/users/julianscheel/followers","following_url":"https://api.github.com/users/julianscheel/following{/other_user}","gists_url":"https://api.github.com/users/julianscheel/gists{/gist_id}","starred_url":"https://api.github.com/users/julianscheel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/julianscheel/subscriptions","organizations_url":"https://api.github.com/users/julianscheel/orgs","repos_url":"https://api.github.com/users/julianscheel/repos","events_url":"https://api.github.com/users/julianscheel/events{/privacy}","received_events_url":"https://api.github.com/users/julianscheel/received_events","type":"User","site_admin":false},"created_at":"2015-03-27T07:42:45Z","updated_at":"2015-03-27T07:42:45Z","body":"@6by9\r\n> image_fx shouldn't ever need more than 2 genuine buffers as that is all it needs as the pool, though you may want more for scheduling purposes. Almost the same as for video decode, it will allocate 5 + (MMAL_PARAMETER_EXTRA_BUFFERS) buffers in the image pool. MMAL_PARAMETER_EXTRA_BUFFERS defaults to 0 though (cf 2 for video decode), and is a signed int if you want to reduce the number. \r\nimage_fx appears to have a queue on the input side, so if it runs out of output images, then things will just stack up there until video_decode has allocated all the images out of its image pool.\r\n\r\nThanks for the detail. In fact when I wrote this code initially last year the image_fx (and I think the video_decode component as well, but not too sure about that one) required to have buffer_num >= 20 when using opaque mode. I think it changed sometime in August then. So I'll take my time now and try to reshuffle things to use vout-allocated buffers only. Even if it's not related to the problem itself it would feel a bit cleaner afterwards..."}}