View Single Post
Old 04-18-2020, 04:10 PM   #48
dhdurgee
Guru
dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.
 
Posts: 912
Karma: 3000002
Join Date: Jun 2010
Device: K3W, PW4
Just had a thought occur to me and wonder if it is worth pursuing. Amazon has included a number of gstreamer static elements and core elements plus two custom elements of their own construction. To me this implies they have to have included the underlying dependencies for gstreamer or this would fail to operate.

The debian repositories still contain Jessie armel gstreamer packages. As these are compatible binaries and most, if not all, gstreamer underpinnings are present to support the provided elements I would expect it would be possible to add elements to allow using gstreamer and gst-launch to do what I would want to.

I don't know what would be required to do so, as I don't want to touch the root fs. Is there a shell variable to export that would add wherever I put the additional elements and their missing dependencies to the library search since these are in library form?

Any thoughts and suggestions on this approach?

Dave
dhdurgee is offline   Reply With Quote