I don't see anything very wrong with the Gst log you provided. You're sure these ring errors & delays occurred when you captured the GST_DEBUG command?
See if you find any errors across all the elements with GST_DEBUG='*:3'. Given the CRITICAL's out see in stderr, I'd really expect something critical in the GStreamer log. You can try running with `G_DEBUG=fatal-criticals` and getting a stack trace of what's causing those range issues, although they're not necessarily "fatal issues". Alternatively, you can also also try building the latest main of GStreamer to see if there's a problem with what is released in 25.04. Ah, you need the object id for /dev/video2, not that path literally. If you look at, gst-device-monitor-1.0 Video/Source And find your video2 device, there will be near it an object.id that you can pass to path= for pipewiresrc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071644 Title: sometimes takes ~5 seconds to _dma_fmt_to_dma_drm_fmts: assertion 'fmt != GST_VIDEO_FORMAT_UNKNOWN' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/2071644/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
