Quote:
Originally Posted by dhdurgee
How then do I install these additional elements and any additional required libraries to the pw4 and integrate them with the existing gstreamer? As this ultimately will wind up as a KUAL extension I guess that would be the logical place for them, but I would need guidance on the scripts to make it run. I can crib some from the mplayer scripts for handling playlists and such, but the pipelines would need to be built to run with gst-launch as well.
|
The plugins are dlopened by gstreamer, so it should be safe to load any of them, as you can just remove them before rebooting if it doesn't work.
Furthermore, you shouldn't even need to touch the main plugins dir, as you can use the --gst-plugin-path option or the GST_PLUGIN_PATH env var to set the user plugins dir. For this, you'll just need to copy the libs for the plugins you want (extract the deb package with dpkg or with ar and tar) to the folder. If they have dependencies (check it with ldd, or just try loading it) which are not built-in to the Kindle firmware, you can use LD_LIBRARY_PATH to refer to a folder with the libs (also extracted from Debian), and as a more permanent solution, you can use patchelf to make the origin relative.
I don't remember all of them off the top of my head, but you'll probably want the convert* ones to be able to resample and convert raw audio, you'll want curlhttpsrc (and libcurl) or souphttpsrc (and libsoup) for loading from a http source (unless you just pass it in stdin), wavparse for parsing wav headers, and so on. You'll also want ffmpeg as a standalone tool (use a static build) if you want to have more flexibility in input options with the least amount of work (most of the functionality from ffmpeg is available in the av* plugins, but this will require a lot more work to use).