1.26 locks API - really?

General Discussion
1

Let’s be honest, it’s a convoluted mess.

Some things need quotes & commas, whilst others don’t.
Sometimes it’s live=1, and then it’s is-live=1.
Far too many unorganised plugins to search through.
The “documentation” lacks structure.
The list goes on…

Shouldn’t an API be simple AND consistent?

To be fair, the announcement claiming the API will not change appears to have been removed, so there could be some hope.

Without doubt there are some extremely clever people contributing to GStreamer, but the Internet is crawling with outdated examples that don’t work today. For sub-humans like me, getting started is next to impossible. I need examples that work. And not just command line examples. I need to see examples using various bindings from which I can learn & extrapolate. And, I need to be able to search for plugins by what they do, when I haven’t a clue what might be available.

Aplogies to those I may have upset.

2

I have no idea what you’re talking about to be honest and it’s quite hard to tell if you’re just trolling at this point.

GStreamer has a bit of a learning curve, yes, but there’s a certain consistency and logic to it all that will hopefully become apparent over time :slightly_smiling_face:

I’m not sure what “announcement claiming the API will not change” has been “removed” from where. We have kept a mostly stable and backwards compatible API and ABI for almost 13 years now.

I don’t think you can hold us responsible for outdated examples “on the internet” that don’t work.

Examples in the GStreamer gitlab repository on the other hand we can fix.

If you have specific questions for specific problems feel free to ask those instead, or pop into our #newcomers Matrix channel.

1 Like