-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RTSP timestamping problem with imxvpudec ? #271
Comments
This might have been happening because of an internal condition variable that was necessary to keep the VPU's buffer pool happy. The code in v2 works differently, and might behave better. Try it again with the elements in the v2 branch or in the upcoming release. |
Been looking into this but switching to v2 is problematic -- this forces us to update the galcore driver and all libraries (with the version we're using right now we get a compile error: "'G2D_AMPHION_TILED' undeclared"). Updating the libraries in turn requires a newer glibc (since the libs are compiled against glibc-2.29). That in turn forces us to update the toolchain and the kernel. So basically we have to update everything to be able to upgrade to gstreamer-imx v2, which is problematic. Any chance this could be solved in v1? Can you provide more information about the internal condition variable you mentioned in your reply, and whether a workaround would be possible? |
@dv1 Since v2 does not seem to be an option for us at the moment (#293), is there any chance you could elaborate on this:
Can you provide more information about the internal condition variable you mentioned in your reply, and whether a workaround would be possible? |
@guillerodriguez I might have a lead on what is causing #293 , so try that first please. |
Well... late update, but here we go. I've tried to see if this could be revisited in 1.x, but, no way, not feasible. However, if you are still working on this, I could in theory add a configuration check for the presence of |
I would be very happy to test this if you can give it a go! |
To be exact, the problem you have is the build error in If so, check out latest git master. I just pushed a change that checks for the Amphion enums, and disables associated code paths in |
Hi, The G2D_AMPHION_TILED error went away but now it fails here:
|
Ah, of course :) Colorimetry was added later. You can do a hack: Comment out the contents of the function (not the entire function!) |
OK. Next errors are in After this, the build succeeds. I will be testing over the next few days. |
@guillerodriguez I just posted updates that perform the Amphion tile layout checks in the G2D blitter and the Amphion decoder code. The hacks should no longer be needed. |
@guillerodriguez Can you confirm that this is fixed? Do note the checks I mentioned above. |
@dv1 Will test and come back to you asap. |
Sorry for the delay. The original issue does not seem to happen with the latest code in v2 for "normal" resolutions. However while testing whether I would be able to migrate from v1 to v2 I noticed that there are issues with low resolutions, which do not seem to happen in v1. This is reproducible with the same pipeline, specifically I was using the following:
With low resolutions (176x144) I see the following:
There are also low level errors:
|
This looks like an IPU problem. The IPU, or at least the linux-imx IPU driver, is picky about resolutions and other parameters, but it is needed as part of the detiling and frame transfer process inside libimxvpuapi. I'll try out that low resolution. |
I am using gstreamer-imx to fetch live video from IP cameras (RTSP / H.264). The pipeline looks like this (note that I am handling video only; audio is ignored):
In some cases I am seeing stuttering video with many dropped frames. The debug output warns about dropped buffers and says "There may be a timestamping problem, or this computer is too slow.":
Despite the messages, this doesn't look like a performance issue:
imxvpudec
and useavdec_h264
insteadIt seems to be related to imxvpudec; any hints on what may be wrong or how to debug this further ?
The text was updated successfully, but these errors were encountered: