View Single Post
Old 04-14-2020, 10:59 AM   #41
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: 910
Karma: 3000002
Join Date: Jun 2010
Device: K3W, PW4
I don't know if this is helpful, but in case it is I used gst-inspect on the two provided custom elements in case it is helpful. I don't know what to do with it, but I had hoped it might give a clue either to what stream format the mixersink expect, or if it is flexible how to specify what input we are passing to it. I had hoped that the audible source details might allow me to use something like:

gst-launch audiblesrc {options} ! mixersink {options}

If this would work then perhaps there would be a way to pull the stream description from the source to the sink. Unfortunately there is a reference to an authentication file in audiblesrc, so unless someone knows where that hides this isn't possible.
Attached Files
File Type: txt audiblesrc.txt (3.1 KB, 319 views)
File Type: txt mixersink.txt (4.5 KB, 311 views)
dhdurgee is offline   Reply With Quote